From owner-freebsd-current Sun Nov 28 2:54:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles511.castles.com [208.214.165.75]) by hub.freebsd.org (Postfix) with ESMTP id 92D7B14CE7 for ; Sun, 28 Nov 1999 02:54:33 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA98732; Sun, 28 Nov 1999 02:55:06 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911281055.CAA98732@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Douglas Kuntz" Cc: current@FreeBSD.ORG Subject: Re: Boot error In-reply-to: Your message of "Fri, 26 Nov 1999 15:31:02 EST." <000c01bf384d$2824c980$29100218@micronetinfo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Nov 1999 02:55:06 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok...for hardware, all I have in the machine is: > A Linksys 10/100 ethernet (uses pn0) > A SCSI card (uses bt0) > A S3 Virge video card > A FIC VA-503+ motherboard w/ 32meg PC66 sdram and a K6-2 400 > the only thing changed between the 2 machines was the other was a Shuttle > Socket 370 motherboard, and a Celeron 366 cpu. > Everything was moved from one case/motherboard to the other > case/motherboard. > The kernel had "ata" compiled in, the options for my hardware, and the basic > floppy and video, nothing that I though was unusual. > > Sorrry about the way I typed before...I actually talk like that (or worse) > half the time, and I have to remember when to talk/type normally. This still doesn't answer the second half of the question. It used to work, then it stopped. What did you change? > Doug > > ----- Original Message ----- > From: "Mike Smith" > To: "Douglas Kuntz" > Cc: > Sent: Friday, November 26, 1999 3:32 AM > Subject: Re: Boot error > > > > > > First things first; try using English for your problem reports. A large > > slice of the community that might be able to answer your questions don't > > use it as their first language, and by using leet-speek you immediately > > eliminate them as a source of help. > > > > > Before I go do a fresh SNAP install, I wanted to see if there was an > easier > > > way to fix this problem... > > > My -current box was a celeron...I had to switch the celeron and mboard > to my > > > windoze machine to get a vidcard werkin...I recompiled the kernel to > 486, > > > 586, and 686, and moved the HD, the cards, etc, over to the K6-2 400 I > > > had...now, everytime at boot, before it even prompts for which OS to > start, > > > it has a bootloader problem...if I recall it was something like: > > > BTX 1.0.0 BTX Loader 1.0.1 > > > then "System Halted" > > > > > > I tried the fixit floppy, etc, and that partially worked, but locked > when it > > > was mounting the filesystem. > > > I'm sorry that I cant provide any more info...I only have 1 monitor and > cant > > > copy/paste between 2 pcs. > > > > I'm sorry, but without a lot more information all I can say is "you done > > something wrong". > > > > You might start with an exhaustive list of the relevant hardware in the > > actual system in question, followed by the actual set of physical changes > > which took it from "working" to "not working". We're not telepathic, and > > we don't have the time to hunt you down and steal all your hardware to > > solve your own problems, so you're going to have to help us out here. > > > > -- > > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 2:59:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0061414CE7 for ; Sun, 28 Nov 1999 02:59:34 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA17712; Sun, 28 Nov 1999 11:59:31 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199911281059.LAA17712@freebsd.dk> Subject: Re: ATA and msdosfs problems / corruption In-Reply-To: from Wes Morgan at "Nov 27, 1999 07:05:43 pm" To: morganw@engr.sc.edu (Wes Morgan) Date: Sun, 28 Nov 1999 11:59:31 +0100 (CET) Cc: FreeBSD-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Wes Morgan wrote: > > ad0: ATA-? disk at ata0 as master > ad0: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 0 depth queue, DMA > ad1: ATA-4 disk at ata0 as slave > ad1: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 31 depth queue, DMA > > The motherboard is fairly old and does not support ATA/66 etc, and the > drive with the fat fs has been rock solid so I doubt it has suddenly gone > bad. I'd like to test this with DMA turned off, what flags will disable > that? OK, I'd like to see the rest of the dmesg, from a verbose at best, before saying anything conclusive, but it looks like the Seagate dont like DMA. There are currently no flags to control the DMA/PIO behavior, the driver relies on the hardware to tell the truth. This might change though... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 3:31:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id C6B7F14A20; Sun, 28 Nov 1999 03:31:50 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id NAA05615; Sun, 28 Nov 1999 13:31:48 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911281131.NAA05615@gratis.grondar.za> Cc: dillon@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: mount_nfs broken Date: Sun, 28 Nov 1999 13:31:48 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi > > Mount_mfs is broken - mounttab\* not present. > > M D'uh. Apart from being inconsistent in my error reporting then screwing it up later when asked to clarify, there was a problem on my cvsupd box that was causing an incomplete mirror, so this problem is complete BS. Apologies. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 3:33:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 43C7314A20 for ; Sun, 28 Nov 1999 03:33:48 -0800 (PST) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 11s2Zg-0009al-00; Sun, 28 Nov 1999 17:33:00 +0600 Date: Sun, 28 Nov 1999 17:32:57 +0600 (ALMT) From: Boris Popov To: Mark Murray Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: mount_nfs broken In-Reply-To: <199911280633.IAA04757@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Nov 1999, Mark Murray wrote: > > Could you be more specific? It seems to work for me (I removed > > /var/db/mounttab and tried it with a new build and it did work). > > Damn. I screwed up the reporting bigtime. > > It is mount_nfs, and there is mention of mounttab.c in the Makefile, > but no mounttab.c anywhere in the source tree. this file located in the src/usr.sbin/rpc.umntall/ directory. However common things should go in the library. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 3:54:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 7A1B514C90 for ; Sun, 28 Nov 1999 03:54:34 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id NAA05674; Sun, 28 Nov 1999 13:54:06 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911281154.NAA05674@gratis.grondar.za> To: Boris Popov Cc: Matthew Dillon , current@FreeBSD.ORG Subject: Re: mount_nfs broken Date: Sun, 28 Nov 1999 13:54:05 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It is mount_nfs, and there is mention of mounttab.c in the Makefile, > > but no mounttab.c anywhere in the source tree. > > this file located in the src/usr.sbin/rpc.umntall/ directory. > However common things should go in the library. Yeah, I found it now. I had a screwed up cvsup-mirror, and I was effectively getting a partial feed. I see it now in usr.sbin/rpc.umntall. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 7:49:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-35.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.163]) by hub.freebsd.org (Postfix) with ESMTP id 220D714F4F for ; Sun, 28 Nov 1999 07:49:15 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id PAA01959 for ; Sun, 28 Nov 1999 15:41:05 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id PAA00555 for ; Sun, 28 Nov 1999 15:41:22 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911281541.PAA00555@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: freebsd-current@FreeBSD.org Subject: HEADS UP - don't forget to MAKEDEV Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Nov 1999 15:41:22 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Just a quick HEADS UP.... since the final bits of the block device removal have gone in, it's now possible to dig yourself a hole if you forget to MAKEDEV your disk devices (with the latest version of MAKEDEV) and end up with a corrupt disk at boot.... fsck will fail to set the device clean. You've then got to mount -f /, MAKEDEV your disk devices, fsck them and then reboot. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 7:56:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id B21C9150AE for ; Sun, 28 Nov 1999 07:56:08 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA16444; Sun, 28 Nov 1999 16:55:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Brian Somers Cc: freebsd-current@FreeBSD.ORG Subject: Re: HEADS UP - don't forget to MAKEDEV In-reply-to: Your message of "Sun, 28 Nov 1999 15:41:22 GMT." <199911281541.PAA00555@hak.lan.Awfulhak.org> Date: Sun, 28 Nov 1999 16:55:27 +0100 Message-ID: <16442.943804527@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199911281541.PAA00555@hak.lan.Awfulhak.org>, Brian Somers writes: >Hi, > >Just a quick HEADS UP.... since the final bits of the block device >removal have gone in, it's now possible to dig yourself a hole if you >forget to MAKEDEV your disk devices (with the latest version of >MAKEDEV) and end up with a corrupt disk at boot.... fsck will fail >to set the device clean. You've then got to mount -f /, MAKEDEV your >disk devices, fsck them and then reboot. I hope this is not true. I think fsck sets the device clean, but the "reload" of the root filesystem seems to fail still. If you get in this situation try this: fsck -p reboot you should now come up with no problem, if not send me email! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 8:13:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-35.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.163]) by hub.freebsd.org (Postfix) with ESMTP id 9923D14D4C for ; Sun, 28 Nov 1999 08:13:23 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id QAA02485; Sun, 28 Nov 1999 16:13:20 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id QAA00986; Sun, 28 Nov 1999 16:13:37 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199911281613.QAA00986@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Poul-Henning Kamp Cc: Brian Somers , freebsd-current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: HEADS UP - don't forget to MAKEDEV In-Reply-To: Message from Poul-Henning Kamp of "Sun, 28 Nov 1999 16:55:27 +0100." <16442.943804527@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Nov 1999 16:13:37 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199911281541.PAA00555@hak.lan.Awfulhak.org>, Brian Somers writes: > >Hi, > > > >Just a quick HEADS UP.... since the final bits of the block device > >removal have gone in, it's now possible to dig yourself a hole if you > >forget to MAKEDEV your disk devices (with the latest version of > >MAKEDEV) and end up with a corrupt disk at boot.... fsck will fail > >to set the device clean. You've then got to mount -f /, MAKEDEV your > >disk devices, fsck them and then reboot. > > I hope this is not true. I think fsck sets the device clean, but > the "reload" of the root filesystem seems to fail still. If you > get in this situation try this: > > fsck -p > reboot > you should now come up with no problem, if not send me email! Well, before doing the MAKEDEV, it didn't *say* it was setting the device clean :-( After the mount -f/MAKEDEV, it did say it was setting it clean, but still wouldn't mount without -f or a reboot. > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 8:18:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C457714D4C for ; Sun, 28 Nov 1999 08:18:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA44756; Sun, 28 Nov 1999 08:17:57 -0800 (PST) (envelope-from dillon) Date: Sun, 28 Nov 1999 08:17:57 -0800 (PST) From: Matthew Dillon Message-Id: <199911281617.IAA44756@apollo.backplane.com> To: Mark Murray Cc: Boris Popov , current@FreeBSD.ORG Subject: Re: mount_nfs broken References: <199911281154.NAA05674@gratis.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> > It is mount_nfs, and there is mention of mounttab.c in the Makefile, :> > but no mounttab.c anywhere in the source tree. :> :> this file located in the src/usr.sbin/rpc.umntall/ directory. :> However common things should go in the library. : :Yeah, I found it now. I had a screwed up cvsup-mirror, and I was :effectively getting a partial feed. I see it now in usr.sbin/rpc.umntall. : :M :-- :Mark Murray :Join the anti-SPAM movement: http://www.cauce.org No problem. I thought it might be a synchronization problem of some sort. I had tested that patchset with a completely new checkout & build on my test box. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 8:20: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2314A14D4C for ; Sun, 28 Nov 1999 08:20:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA44774; Sun, 28 Nov 1999 08:19:50 -0800 (PST) (envelope-from dillon) Date: Sun, 28 Nov 1999 08:19:50 -0800 (PST) From: Matthew Dillon Message-Id: <199911281619.IAA44774@apollo.backplane.com> To: Boris Popov Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: mount_nfs broken References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> It is mount_nfs, and there is mention of mounttab.c in the Makefile, :> but no mounttab.c anywhere in the source tree. : : this file located in the src/usr.sbin/rpc.umntall/ directory. :However common things should go in the library. : :-- :Boris Popov :http://www.butya.kz/~bp/ Well, I'd say the mounttab code is borderline -- if another one or two utilities need it then we should break it out into a library, otherwise it is just taking up unnecessary space in the library mmap. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 8:34:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0F823150A3 for ; Sun, 28 Nov 1999 08:34:35 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA44858; Sun, 28 Nov 1999 08:34:16 -0800 (PST) (envelope-from dillon) Date: Sun, 28 Nov 1999 08:34:16 -0800 (PST) From: Matthew Dillon Message-Id: <199911281634.IAA44858@apollo.backplane.com> To: Peter Wemm Cc: David Greenman , Julian Elischer , current@FreeBSD.ORG Subject: Re: Which is the truth? (sycalls and traps) References: <19991128054519.2CB181C6D@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :I was rather suprised when I found out just how expensive kernel entry was :some time ago.. What I was doing was a reentrant syscall that aquired no :locks and ran about 5 instructions in kernel context.. Anyway, it took :something like 300 times longer to do that (called via int $0x81) than to :do a 'call' to equivalent code in userland. Anyway, with overheads on that :scale, whether we push 5 or 8 or whatever registers in the handler is :almost lost in the noise. : :Cheers, :-Peter Well, it could be 300x but that's like comparing a cache hit to a cache miss - in real terms a UP syscall takes, what, 1-3 uS? An SMP syscall takes 6 uS. This on a PIII-450. Both times can be cut down to less then 500nS with fairly simple optimizations. Unless you are doing hundreds of thousands of context switches a second the overhead is in the noise in real terms, and *definitely* in the noise if you tack on a task switch in the middle of that. Having the kernel do the context switch between threads has a huge number of advantages that should outweight or at least equal the minor increase in overhead. A couple of points that have been brought up in recent emails: * blockages due to VM faults * blockages due to file I/O (not even network I/O) * disk parallelism (thread A reads file block from kernel cache, thread B reads file block and has a cache miss). * event synchronization * kernel state Even if one were to use an asynchronous call gate one then has to deal with the additional overhead imposed by the asynch call gate when a syscall could have been run from the disk cache (that is, not block). Personally speaking, I think async call gates are a huge mistake without a prioritized, vectorable software interrupt mechanism to go along with it. The current unix signal mechanism is simply not up to the task. There are serious issues with async call gates including potential resource hogging issues that frankly scare the hell out of me. I would prefer a kernel stack for each thread and I would prefer a syscall to set a thread runnable/not-runnable. Such a syscall could specify an optional cpu and optional run interval. There are simply too many things that a UP scheduler does not have access to - such as knowing whether a syscall can complete without blocking or not - to allow the UP scheduler to actually perform the context switch. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 8:39:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id EEDFC14BE9 for ; Sun, 28 Nov 1999 08:38:58 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (Shiva-HGW-201.fernuni-hagen.de [132.176.120.201]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id RAA26216; Sun, 28 Nov 1999 17:38:48 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <38415AA1.2586CEA9@fernuni-hagen.de> Date: Sun, 28 Nov 1999 17:38:57 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: German/Germany, de-DE, en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: gcc-2.95.2, jade and freebsd-sgml-documentation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i tried to make me a new handbook, so i needed jade. But the newest C++ fashion (g++ under current) has changed to fast for this very old 1998 heavily template based source code distribution ;-). I had a lot of problems with const and not const .. and gave up. It is far to much to post here ... A lot of error messages are clearly written 1 to 1 from the ansi standard (yes we finally spent the 18 dollars ...), but something especially about a class "Location" looks really strange. What tool is recommendet to rebuild the documentation? -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 9:14: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailgw.cablecom.ne.jp (mailgw.cablecom.ne.jp [202.248.199.37]) by hub.freebsd.org (Postfix) with ESMTP id 1222115092 for ; Sun, 28 Nov 1999 09:13:34 -0800 (PST) (envelope-from motoyuki@snipe.rim.or.jp) Received: from srv2.cablecom.ne.jp by mailgw.cablecom.ne.jp (8.9.3/3.7W) id CAA01806; Mon, 29 Nov 1999 02:13:32 +0900 (JST) Received: from mail.snipe.rim.or.jp by srv2.cablecom.ne.jp (8.9.3/3.7W) id CAA00462; Mon, 29 Nov 1999 02:13:30 +0900 (JST) Received: from sakura.snipe.rim.or.jp (sakura.snipe.rim.or.jp [192.168.11.4]) by mail.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id CAA73314 for ; Mon, 29 Nov 1999 02:13:27 +0900 (JST) Received: from sakura.snipe.rim.or.jp (localhost [127.0.0.1]) by sakura.snipe.rim.or.jp (8.9.3/3.7W) with ESMTP id CAA33652 for ; Mon, 29 Nov 1999 02:13:27 +0900 (JST) Message-Id: <199911281713.CAA33652@sakura.snipe.rim.or.jp> To: current@freebsd.org X-Mailer: mh-e on Mule 2.3 / Emacs 19.34.1 Subject: __do_global_ctors in a.out Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Mon, 29 Nov 1999 02:13:27 +0900 From: Motoyuki Konno Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, "make -DWANT_AOUT world" on my -current machines fails at: -------- log starts here -------- rm -f .depend /usr/obj/aout/usr/src/lib/libncurses/GPATH /usr/obj/aout/usr/src/lib/libncurses/GRTAGS /usr/obj/aout/usr/src/lib/libncurses/GSYMS /usr/obj/aout/usr/src/lib/libncurses/GTAGS cc -o make_keys -O2 -m486 -pipe -I. -I/usr/src/lib/libncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncurses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CONFIG_H -I/usr/obj/aout/usr/src/tmp/usr/include /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/make_keys.c __main.o: Undefined symbol `___do_global_ctors' referenced from text segment *** Error code 1 Stop in /usr/src/lib/libncurses. *** Error code 1 --------- log ends here --------- I think the problem is the following codes in src/contrib/gcc/libgcc2.c, which should be enabled in a.out system. -------- libgcc2.c line 2870 void __do_global_ctors () { DO_GLOBAL_CTORS_BODY; ON_EXIT (__do_global_dtors, 0); } -------- -- ------------------------------------------------------------------------ Motoyuki Konno mkonno@res.yamanashi-med.ac.jp (Univ) motoyuki@snipe.rim.or.jp (Home) motoyuki@FreeBSD.ORG (FreeBSD Project) Yamanashi Medical University http://www.freebsd.org/~motoyuki/ (WWW) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 9:19:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id AA31E14A09 for ; Sun, 28 Nov 1999 09:19:16 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id MAA22274 for ; Sun, 28 Nov 1999 12:19:15 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Sun, 28 Nov 1999 12:19:14 -0500 (EST) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: Vortex Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are our Aureal Vortex sound drivers working yet?? Just wondering because the OSS ones don't work with -CURRENT very well, and I'm a bit anxious to get rid of this stupid SB16... :-) Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 9:20:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id EE01914A09 for ; Sun, 28 Nov 1999 09:20:20 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id LAA28598; Sun, 28 Nov 1999 11:19:49 -0600 (CST) (envelope-from dick) Date: Sun, 28 Nov 1999 11:19:49 -0600 From: "Richard Seaman, Jr." To: Matthew Dillon Cc: Peter Wemm , David Greenman , Julian Elischer , current@FreeBSD.ORG Subject: Re: Which is the truth? (sycalls and traps) Message-ID: <19991128111949.O1408@tar.com> References: <19991128054519.2CB181C6D@overcee.netplex.com.au> <199911281634.IAA44858@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199911281634.IAA44858@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 28, 1999 at 08:34:16AM -0800, Matthew Dillon wrote: > Well, it could be 300x but that's like comparing a cache hit to a cache > miss - in real terms a UP syscall takes, what, 1-3 uS? An SMP syscall > takes 6 uS. This on a PIII-450. Both times can be cut down to less > then 500nS with fairly simple optimizations. Unless you are doing > hundreds of thousands of context switches a second the overhead is in > the noise in real terms, and *definitely* in the noise if you tack on > a task switch in the middle of that. FYI, some measurements I did with the Linuxthreads "port" (ie. native FreeBSD kernel threads using the linux threads code) on a 266Mhz AMD processor showed the ability to do about 150,000 kernel thread context switches/sec. The threads didn't do anything other than context switch, so a "real world" context switch might be slower, and the rate varies somewhat with the number of threads. This was uniprocessor, not SMP. This suggests that kernel thread context switches, to have a measureable impact on performance at even the 1% level, have to be occurring at the rate of 1,500/sec or more. With a faster processor, and the optimizations you suggest, I'm sure you might well be talking 10,000 switches/sec to matter. I don't have any threaded apps that come close to this, but perhaps they exist. And, unless you can fix the "user thread" scheduler so it doesn't make any syscalls, its hard to see much of an advantage for user thread context switches over kernel thread context switches, from a performance standpoint. (The current user thread scheduler can actually be slower at context switches that kernel threads, because of the nubmer of syscalls it makes). -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 9:28:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2580F14BD7 for ; Sun, 28 Nov 1999 09:28:52 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA45072; Sun, 28 Nov 1999 09:28:48 -0800 (PST) (envelope-from dillon) Date: Sun, 28 Nov 1999 09:28:48 -0800 (PST) From: Matthew Dillon Message-Id: <199911281728.JAA45072@apollo.backplane.com> To: "Richard Seaman, Jr." Cc: Peter Wemm , David Greenman , Julian Elischer , current@FreeBSD.ORG Subject: Re: Which is the truth? (sycalls and traps) References: <19991128054519.2CB181C6D@overcee.netplex.com.au> <199911281634.IAA44858@apollo.backplane.com> <19991128111949.O1408@tar.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :FYI, some measurements I did with the Linuxthreads "port" (ie. :native FreeBSD kernel threads using the linux threads code) on a :266Mhz AMD processor showed the ability to do about 150,000 :kernel thread context switches/sec. The threads didn't do anything :other than context switch, so a "real world" context switch might :be slower, and the rate varies somewhat with the number of threads. :This was uniprocessor, not SMP. : :This suggests that kernel thread context switches, to have a measureable :impact on performance at even the 1% level, have to be occurring :at the rate of 1,500/sec or more. With a faster processor, and :the optimizations you suggest, I'm sure you might well be talking :10,000 switches/sec to matter. : :I don't have any threaded apps that come close to this, but perhaps :they exist. And, unless you can fix the "user thread" scheduler so :it doesn't make any syscalls, its hard to see much of an advantage :for user thread context switches over kernel thread context switches, :from a performance standpoint. (The current user thread scheduler :can actually be slower at context switches that kernel threads, :because of the nubmer of syscalls it makes). : :-- :Richard Seaman, Jr. email: dick@tar.com :5182 N. Maple Lane phone: 262-367-5450 :Chenequa WI 53058 fax: 262-367-5852 Your numbers mesh with mine very well -- 266MHz AMD @ 150Kswitch/sec, 450 MHz PIII at around 500K to 1Mswitch/sec (my test was with a simple entry, context switch, and exit. No floating point in the context switch). If you include FP state I would expect around 500Kswitch/sec on a PIII-450. Another thing to note is that the overhead is of course for a single cpu and does not compound when you have additional cpu's. It seems well worth doing to me. Also consider the fact that in a heavily loaded system, scheduling a thread does not necessarily cause an immediate context switch so we are really talking about context switches here as being the limiting factor, not scheduling and descheduling operations, and not asynchronous message-passing operations. 150Kswitch/sec/cpu goes far beyond what most systems require. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 9:43:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from angelsguardian.netquick.net (angelsguardian.netquick.net [199.72.47.239]) by hub.freebsd.org (Postfix) with ESMTP id 6913814D4C for ; Sun, 28 Nov 1999 09:43:30 -0800 (PST) (envelope-from trouble@netquick.net) Received: from netquick.net (localhost [127.0.0.1]) by angelsguardian.netquick.net (Postfix) with ESMTP id 3EE42386A; Sun, 28 Nov 1999 12:39:03 -0500 (EST) Message-ID: <384168B6.D76F8C5@netquick.net> Date: Sun, 28 Nov 1999 17:39:02 +0000 From: TrouBle Reply-To: trouble@netquick.net X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.13-7mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: "Richard Seaman, Jr." , Peter Wemm , David Greenman , Julian Elischer , current@FreeBSD.ORG Subject: Re: Which is the truth? (sycalls and traps) References: <19991128054519.2CB181C6D@overcee.netplex.com.au> <199911281634.IAA44858@apollo.backplane.com> <19991128111949.O1408@tar.com> <199911281728.JAA45072@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ummm Okay are you maybe saying that there is kernel spcae thread support for the current FreeBSD using linux threads ??? if so, is there a way, i can also get a thread supported system using current for some testing also ??? or it is genberic to your installations alone, or is threading actually in 4.0 current using linux threads ?? and does it support pthread_cancel ?? looking forward to a reply Matthew Dillon wrote: > :FYI, some measurements I did with the Linuxthreads "port" (ie. > :native FreeBSD kernel threads using the linux threads code) on a > :266Mhz AMD processor showed the ability to do about 150,000 > :kernel thread context switches/sec. The threads didn't do anything > :other than context switch, so a "real world" context switch might > :be slower, and the rate varies somewhat with the number of threads. > :This was uniprocessor, not SMP. > : > :This suggests that kernel thread context switches, to have a measureable > :impact on performance at even the 1% level, have to be occurring > :at the rate of 1,500/sec or more. With a faster processor, and > :the optimizations you suggest, I'm sure you might well be talking > :10,000 switches/sec to matter. > : > :I don't have any threaded apps that come close to this, but perhaps > :they exist. And, unless you can fix the "user thread" scheduler so > :it doesn't make any syscalls, its hard to see much of an advantage > :for user thread context switches over kernel thread context switches, > :from a performance standpoint. (The current user thread scheduler > :can actually be slower at context switches that kernel threads, > :because of the nubmer of syscalls it makes). > : > :-- > :Richard Seaman, Jr. email: dick@tar.com > :5182 N. Maple Lane phone: 262-367-5450 > :Chenequa WI 53058 fax: 262-367-5852 > > Your numbers mesh with mine very well -- 266MHz AMD @ 150Kswitch/sec, > 450 MHz PIII at around 500K to 1Mswitch/sec (my test was with a simple > entry, context switch, and exit. No floating point in the context > switch). If you include FP state I would expect around 500Kswitch/sec > on a PIII-450. > > Another thing to note is that the overhead is of course for a single > cpu and does not compound when you have additional cpu's. It seems > well worth doing to me. > > Also consider the fact that in a heavily loaded system, scheduling a > thread does not necessarily cause an immediate context switch so we > are really talking about context switches here as being the limiting > factor, not scheduling and descheduling operations, and not asynchronous > message-passing operations. 150Kswitch/sec/cpu goes far beyond what most > systems require. > > -Matt > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 9:46:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AB07014D4C for ; Sun, 28 Nov 1999 09:46:10 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA45248; Sun, 28 Nov 1999 09:46:03 -0800 (PST) (envelope-from dillon) Date: Sun, 28 Nov 1999 09:46:03 -0800 (PST) From: Matthew Dillon Message-Id: <199911281746.JAA45248@apollo.backplane.com> To: TrouBle Cc: "Richard Seaman, Jr." , Peter Wemm , David Greenman , Julian Elischer , current@FreeBSD.ORG Subject: Re: Which is the truth? (sycalls and traps) References: <19991128054519.2CB181C6D@overcee.netplex.com.au> <199911281634.IAA44858@apollo.backplane.com> <19991128111949.O1408@tar.com> <199911281728.JAA45072@apollo.backplane.com> <384168B6.D76F8C5@netquick.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Ummm Okay are you maybe saying that there is kernel spcae thread support for the :current FreeBSD using linux threads ??? if so, is there a way, i can also get a :thread supported system using current for some testing also ??? or it is :genberic to your installations alone, or is threading actually in 4.0 current :using linux threads ?? and does it support pthread_cancel ?? : :looking forward to a reply That isn't what I tested with, but yes, there is currently support for native linux threads in the linux compatibility stuff. In order to use the support you need to compile against a linux environment, though. Annoying, eh? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 9:54:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 16DFE14D4C for ; Sun, 28 Nov 1999 09:54:22 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id LAA28793; Sun, 28 Nov 1999 11:54:13 -0600 (CST) (envelope-from dick) Date: Sun, 28 Nov 1999 11:54:13 -0600 From: "Richard Seaman, Jr." To: Matthew Dillon , TrouBle Cc: current@freebsd.org Subject: Re: Which is the truth? (sycalls and traps) Message-ID: <19991128115413.P1408@tar.com> References: <19991128054519.2CB181C6D@overcee.netplex.com.au> <199911281634.IAA44858@apollo.backplane.com> <19991128111949.O1408@tar.com> <199911281728.JAA45072@apollo.backplane.com> <384168B6.D76F8C5@netquick.net> <199911281746.JAA45248@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199911281746.JAA45248@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 28, 1999 at 09:46:03AM -0800, Matthew Dillon wrote: > > :Ummm Okay are you maybe saying that there is kernel spcae thread support for the > :current FreeBSD using linux threads ??? if so, is there a way, i can also get a > :thread supported system using current for some testing also ??? or it is > :genberic to your installations alone, or is threading actually in 4.0 current > :using linux threads ?? and does it support pthread_cancel ?? > : > :looking forward to a reply > > That isn't what I tested with, but yes, there is currently support for > native linux threads in the linux compatibility stuff. In order to use > the support you need to compile against a linux environment, though. > Annoying, eh? The linuxthreads "port" at http://lt.tar.com didn't compile against a linux environment, and didn't required linux compatibility. The information at that site is now outdated, but there's a pointer there to an updated port produced by Russell Carter that also doesn't require any linux compatibility stuff or linux environment either. You can play with it. It worked quite well both uniprocessor and SMP, though I understand that Russell has encountered problems under SMP recently after Marcel's signal changes in -current. There is a pthread_cancel() included. But, full pthread_cancel() functionality requires a lot of libc support that doesn't currently exist in FreeBSD libc. Therefore, if you're expecting read(), as an example, to be a canellation point (as required by POSIX specs), it won't be. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 10: 7:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from angelsguardian.netquick.net (angelsguardian.netquick.net [199.72.47.239]) by hub.freebsd.org (Postfix) with ESMTP id 2798A14C40 for ; Sun, 28 Nov 1999 10:07:40 -0800 (PST) (envelope-from trouble@netquick.net) Received: from netquick.net (localhost [127.0.0.1]) by angelsguardian.netquick.net (Postfix) with ESMTP id F2028386A; Sun, 28 Nov 1999 13:03:10 -0500 (EST) Message-ID: <38416E5E.6EA52998@netquick.net> Date: Sun, 28 Nov 1999 18:03:10 +0000 From: TrouBle Reply-To: trouble@netquick.net X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.13-7mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: "Richard Seaman, Jr." Cc: Matthew Dillon , current@freebsd.org Subject: Re: Which is the truth? (sycalls and traps) References: <19991128054519.2CB181C6D@overcee.netplex.com.au> <199911281634.IAA44858@apollo.backplane.com> <19991128111949.O1408@tar.com> <199911281728.JAA45072@apollo.backplane.com> <384168B6.D76F8C5@netquick.net> <199911281746.JAA45248@apollo.backplane. <19991128115413.P1408@tar.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The linuxthreads "port" at http://lt.tar.com didn't compile against > a linux environment, and didn't required linux compatibility. The > information at that site is now outdated, but there's a pointer > there to an updated port produced by Russell Carter that also doesn't > require any linux compatibility stuff or linux environment either. probably wount work for Licq 0.71 then under FreeBSD.. even under 3.3 or 4.0 thats the test get Licq 0.71 to run and Ill be happy... I have FreeBSD/OpenBSD boxes at home so ill install the ports and play, who knows maybe ill get lucky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 10:34: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id A095615345 for ; Sun, 28 Nov 1999 10:34:05 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id KAA22972; Sun, 28 Nov 1999 10:33:34 -0800 (PST) Date: Sun, 28 Nov 1999 10:33:34 -0800 (PST) From: Julian Elischer To: "Richard Seaman, Jr." Cc: Matthew Dillon , Peter Wemm , David Greenman , current@FreeBSD.ORG Subject: Re: Which is the truth? (sycalls and traps) In-Reply-To: <19991128111949.O1408@tar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Nov 1999, Richard Seaman, Jr. wrote: (should be in -arch) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 10:43:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id EAFF61531C; Sun, 28 Nov 1999 10:43:45 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id NAA10577; Sun, 28 Nov 1999 13:43:37 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id NAA55160; Sun, 28 Nov 1999 13:43:07 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 28 Nov 1999 13:43:07 -0500 (EST) To: Mike Smith Cc: Julian Elischer , current@freebsd.org Subject: Re: State of Alpha support and Oracle. In-Reply-To: <199911280153.RAA96659@mass.cdrom.com> References: <199911280153.RAA96659@mass.cdrom.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14401.30380.556243.951890@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > > > > I am not sure of thw state of things but if someone wanted to run Oracle-8 > > and had an idea in their mind that they'd like to run it in an Alpha, > > tehn teh following questions would need to be answered (and I dont know > > the answers) > > > > 2/ is there a binary version of Oracle we can run on the alpha? > > The Tru64 version _might_ work. I have left my latest working copy of the osf1-ulator for -current at http://www.freebsd.org/~gallatin/osf1.tar.gz Really, I'll get around to committing it soon. Really... > > 3/ does the alpha give a big increase in speed over the same dollars spent > > on x86? > > Not under Oracle at the low end, no. It might depend on your definition of low end. I don't know what Oracle stresses (probably memory & I/O systems). In those catagories, an $8k Compaq Professional Workstation xp1000 will kick sand in the face of any x86 hardware I've seen which is in the same price range. I haven't played with a rambus based machines yet though.. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 12:45:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id D4BE814A2B for ; Sun, 28 Nov 1999 12:45:37 -0800 (PST) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (root@va-173.skylink.it [194.185.55.173]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id VAA29609 for ; Sun, 28 Nov 1999 21:45:57 +0100 Received: from localhost (n_hibma@localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id TAA24995 for ; Sun, 28 Nov 1999 19:46:53 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Sun, 28 Nov 1999 19:46:53 GMT Date: Sun, 28 Nov 1999 20:46:52 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: current@freebsd.org Subject: loader.conf, ordering of loading of modules Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to change the order in which modules are loaded in loader.conf? I need usb before uhci before ums. usb_load="YES" uhci_load="YES" ums_load="YES" doesn't do it. Nick -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 12:54:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles501.castles.com [208.214.165.65]) by hub.freebsd.org (Postfix) with ESMTP id CD0371523B for ; Sun, 28 Nov 1999 12:54:15 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00447; Sun, 28 Nov 1999 12:54:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911282054.MAA00447@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Hibma Cc: current@freebsd.org Subject: Re: loader.conf, ordering of loading of modules In-reply-to: Your message of "Sun, 28 Nov 1999 20:46:52 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Nov 1999 12:54:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is it possible to change the order in which modules are loaded in > loader.conf? I need usb before uhci before ums. > > usb_load="YES" > uhci_load="YES" > ums_load="YES" > > doesn't do it. Why do you need the ordering? They should be loaded and linked long before the probes start... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 13:15:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 17F9B14A28; Sun, 28 Nov 1999 13:15:42 -0800 (PST) (envelope-from hibma@skylink.it) Received: from heidi.plazza.it (root@va-173.skylink.it [194.185.55.173]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA04530; Sun, 28 Nov 1999 22:15:58 +0100 Received: from localhost (n_hibma@localhost [127.0.0.1]) by heidi.plazza.it (8.9.3/8.8.5) with ESMTP id VAA25359; Sun, 28 Nov 1999 21:17:31 GMT X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Sun, 28 Nov 1999 21:17:31 GMT Date: Sun, 28 Nov 1999 22:17:31 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@heidi.plazza.it Reply-To: Nick Hibma To: Mike Smith Cc: current@freebsd.org Subject: Re: loader.conf, ordering of loading of modules In-Reply-To: <199911282054.MAA00447@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are symbols in usb.ko that are needed by uhci.c . I know it is stupid, but that's the way it is, without a complete rewrite of the USB stack. Nick On Sun, 28 Nov 1999, Mike Smith wrote: > > > > Is it possible to change the order in which modules are loaded in > > loader.conf? I need usb before uhci before ums. > > > > usb_load="YES" > > uhci_load="YES" > > ums_load="YES" > > > > doesn't do it. > > Why do you need the ordering? They should be loaded and linked long > before the probes start... > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > -- e-Mail: hibma@skylink.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 13:48:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles501.castles.com [208.214.165.65]) by hub.freebsd.org (Postfix) with ESMTP id C818D14E1A for ; Sun, 28 Nov 1999 13:48:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA00658; Sun, 28 Nov 1999 13:48:59 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911282148.NAA00658@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Hibma Cc: current@freebsd.org Subject: Re: loader.conf, ordering of loading of modules In-reply-to: Your message of "Sun, 28 Nov 1999 22:17:31 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Nov 1999 13:48:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There are symbols in usb.ko that are needed by uhci.c . I know it is > stupid, but that's the way it is, without a complete rewrite of the USB > stack. Ugh. I would, in that case, just build usb.ko to contain the usb, uhci and ohci modules rather than trying to hack around this. If they're that tightly bound together, anything else will be a grubby hack. > Nick > > On Sun, 28 Nov 1999, Mike Smith wrote: > > > > > > > Is it possible to change the order in which modules are loaded in > > > loader.conf? I need usb before uhci before ums. > > > > > > usb_load="YES" > > > uhci_load="YES" > > > ums_load="YES" > > > > > > doesn't do it. > > > > Why do you need the ordering? They should be loaded and linked long > > before the probes start... > > > > -- > > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > > > > -- > e-Mail: hibma@skylink.it > > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 16:47:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 160D91523B for ; Sun, 28 Nov 1999 16:47:34 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id TAA87837 for freebsd-current@freebsd.org; Sun, 28 Nov 1999 19:47:33 -0500 (EST) (envelope-from steve) Date: Sun, 28 Nov 1999 19:47:33 -0500 From: Steve Ames To: freebsd-current@freebsd.org Subject: strfile -C Message-ID: <19991128194733.A16765@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -current as of about 3 hours ago. vv# strfile -C strfile: illegal option -- C strfile: [iorsx] [-c char] sourcefile [datafile] Not a biggie from my standpoint but the man page says that there is a '-C' option and, more importantly, its used in /usr/src/games/fortune/datfiles -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 16:57: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 5B8781540F for ; Sun, 28 Nov 1999 16:56:59 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id TAA81003 for freebsd-current@FreeBSD.ORG; Sun, 28 Nov 1999 19:56:58 -0500 (EST) (envelope-from steve) Date: Sun, 28 Nov 1999 19:56:57 -0500 From: Steve Ames To: freebsd-current@FreeBSD.ORG Subject: Re: strfile -C Message-ID: <19991128195657.B16765@virtual-voodoo.com> References: <19991128194733.A16765@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19991128194733.A16765@virtual-voodoo.com>; from Steve Ames on Sun, Nov 28, 1999 at 07:47:33PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually... it appears I just have a left over strfile in /usr/bin... that shouldn't be there? The only source for strfile seems to be in games/fortune/strfile and it installs strfile into /usr/games these days... I must have missed this change. -Steve On Sun, Nov 28, 1999 at 07:47:33PM -0500, Steve Ames wrote: > -current as of about 3 hours ago. > > vv# strfile -C > strfile: illegal option -- C > strfile: [iorsx] [-c char] sourcefile [datafile] > > Not a biggie from my standpoint but the man page says that there > is a '-C' option and, more importantly, its used in > /usr/src/games/fortune/datfiles > > -Steve > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 17:26:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24]) by hub.freebsd.org (Postfix) with ESMTP id 4FBB2153F5 for ; Sun, 28 Nov 1999 17:26:55 -0800 (PST) (envelope-from eogren@earthlink.net) Received: from rod.darktech.org (ip245.cambridge2.ma.pub-ip.psi.net [38.32.112.245]) by eagle.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id RAA01943 for ; Sun, 28 Nov 1999 17:26:53 -0800 (PST) Received: by rod.darktech.org (Postfix, from userid 1001) id 0CC5C62; Sun, 28 Nov 1999 19:54:59 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by rod.darktech.org (Postfix) with ESMTP id C050C52 for ; Sun, 28 Nov 1999 19:54:59 -0500 (EST) Date: Sun, 28 Nov 1999 19:54:59 -0500 (EST) From: Eric Ogren X-Sender: eogren@rod.darktech.org To: freebsd-current@freebsd.org Subject: ep driver troubles Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all- I just recently upgraded to 4.0-CURRENT, and I can't seem to get the new ep driver to recognize my 3c509b card (yes, I know it's an awful NIC, but it's what I have, and it's worked fine for me). I have "device ep0" (and nothing else) in my kernel configuration file. Upon booting, I do see: isa0: on isab0 ide_pci0: at device 7.1 on pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7020) at 7.2 irq 9 vga-pci0: at device 15.0 on pci0 pci0: unknown card (vendor=0x121a, dev=0x0002) at 17.0 --> isa0: if_ep: Adapter at 0xb30 in PnP mode! <-- sb_reset_dsp failed fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold However, FreeBSD doesn't automatically bring up the interface, and when I manually do an "ifconfig ep0 inet 10.0.0.2 mask 255.255.0.0" I just get: ifconfig: interface ep0 does not exist In 3.3-STABLE, I had disabled PNP and had set it to port 0x330 irq 7, and I could just say put a "device ep0 at isa? port 0x330 net irq 7". Obviously, that doesn't work for the new driver. I tried searching the archives for information, but couldn't see anything (actually, the last entry I found was a call for somebody to put their 3c509b card into PNP and make sure that the driver works). Is there just some step that I'm missing to make the kernel expose the interface for the ep card? (ls /dev/ep* shows nothing). Thanks. Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 19:51:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from lion.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id B4C5414EC9; Sun, 28 Nov 1999 19:51:47 -0800 (PST) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by lion.butya.kz with local-esmtp (Exim 2.12 #1) id 11sHqp-000ArC-00; Mon, 29 Nov 1999 09:51:43 +0600 Date: Mon, 29 Nov 1999 09:51:37 +0600 (ALMT) From: Boris Popov To: Nick Hibma Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: loader.conf, ordering of loading of modules In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Nov 1999, Nick Hibma wrote: > There are symbols in usb.ko that are needed by uhci.c . I know it is > stupid, but that's the way it is, without a complete rewrite of the USB > stack. You can define module dependency in the uhci module Makefile: KMODDEPS=usb -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 20:37:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles554.castles.com [208.214.165.118]) by hub.freebsd.org (Postfix) with ESMTP id A276E153CC; Sun, 28 Nov 1999 20:37:30 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA01902; Sun, 28 Nov 1999 20:37:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911290437.UAA01902@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Boris Popov Cc: Nick Hibma , Mike Smith , current@FreeBSD.ORG Subject: Re: loader.conf, ordering of loading of modules In-reply-to: Your message of "Mon, 29 Nov 1999 09:51:37 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Nov 1999 20:37:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 28 Nov 1999, Nick Hibma wrote: > > > There are symbols in usb.ko that are needed by uhci.c . I know it is > > stupid, but that's the way it is, without a complete rewrite of the USB > > stack. > > You can define module dependency in the uhci module Makefile: > KMODDEPS=usb The loader's handling of dependancies stated like this is broken, unfortunately. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 20:52:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from nhj.nlc.net.au (nhj.nlc.net.au [203.24.133.1]) by hub.freebsd.org (Postfix) with SMTP id EBAEF1512B for ; Sun, 28 Nov 1999 20:52:45 -0800 (PST) (envelope-from john@nlc.net.au) Received: (qmail 1983 invoked from network); 29 Nov 1999 15:51:41 +1100 Received: from nhj.nlc.net.au (HELO saruman) (203.24.133.1) by nhj.nlc.net.au with SMTP; 29 Nov 1999 15:51:41 +1100 Message-ID: <032901bf3a25$6d55be40$6cb611cb@scitec.com.au> From: "John Saunders" To: "FreeBSD current" Subject: gcc 2.95.2 breaks imake Date: Mon, 29 Nov 1999 15:51:39 +1100 Organization: NORTHLINK COMMUNICATIONS MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just noticed that the new gcc breaks imake because /usr/libexec/cpp doesn't define __FreeBSD__. What is the plan to fix everything in this area? The 2 options I can see is to revert the behaviour of cpp, or find everything that uses cpp and change them to use cc -E. My current "fix" involes #define'ing __FreeBSD_ in imake's file. -- +------------------------------------------------------------+ . | John Saunders - mailto:john@nlc.net.au (EMail) | ,--_|\ | - http://www.nlc.net.au/ (WWW) | / Oz \ | - 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NORTHLINK COMMUNICATIONS P/L - Supplying a professional, | v | and above all friendly, internet connection service. | +------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 21:20:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 3771314A1E for ; Sun, 28 Nov 1999 21:20:47 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id AAA01600; Mon, 29 Nov 1999 00:20:46 -0500 (EST) Date: Mon, 29 Nov 1999 00:20:45 -0500 (EST) From: "Matthew N. Dodd" To: Eric Ogren Cc: freebsd-current@FreeBSD.ORG Subject: Re: ep driver troubles In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 28 Nov 1999, Eric Ogren wrote: > I just recently upgraded to 4.0-CURRENT, and I can't seem to get the > new ep driver to recognize my 3c509b card (yes, I know it's an awful > NIC, but it's what I have, and it's worked fine for me). put controller pnp0 in your config file. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 28 22:52:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id E57C5153FA for ; Sun, 28 Nov 1999 22:52:44 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac10.wam.umd.edu (root@rac10.wam.umd.edu [128.8.10.150]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA08026 for ; Mon, 29 Nov 1999 01:52:41 -0500 (EST) Received: from rac10.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac10.wam.umd.edu (8.9.3/8.9.3) with SMTP id BAA00941 for ; Mon, 29 Nov 1999 01:52:43 -0500 (EST) Received: from localhost (culverk@localhost) by rac10.wam.umd.edu (8.9.3/8.9.3) with ESMTP id BAA00937 for ; Mon, 29 Nov 1999 01:52:42 -0500 (EST) X-Authentication-Warning: rac10.wam.umd.edu: culverk owned process doing -bs Date: Mon, 29 Nov 1999 01:52:42 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: fxtv/bktr driver broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have included a link screenshot of what the picture is doing on my tv card. It seems that since gcc 2.95.2 has been introduced as the default compiler on FreeBSD-CURRENT, the behavior in the jpeg has been occuring. I have tried to locate the source of the problem in the driver, but I don't know what it is. Any help/bugfixes would be appreciated. Thanks. The link is www.wam.umd.edu/~culverk/fxtv.jpg Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 1:23:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with ESMTP id 1FB5314C58 for ; Mon, 29 Nov 1999 01:23:52 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: from lcb115.cvzoom.net (lcb115.cvzoom.net [63.65.159.115]) by ns.cvzoom.net (8.9.3/8.9.3) with ESMTP id EAA07631 for ; Mon, 29 Nov 1999 04:04:40 -0500 (EST) Date: Mon, 29 Nov 1999 04:23:08 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: Compiling drivers as lkm's Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any kernel config option that can be used to link a driver to the kernel dynamically (LKM) instead of statically? Also, I'd like to know how to write a driver as an lkm. Of course, if anyone has any links or info on how to write a driver period, I'd like to know. It seems like the best method to write, test, and debug a new driver would be to use lkm's, since you could just use kldload() and kldunload() to test the driver-in-progress instead of just rebooting. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 1:28:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id BA80114C58; Mon, 29 Nov 1999 01:28:39 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:TvHh5Qd+XAXkDdBvKPQzmFotJ+c13aiO@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id SAA00438; Mon, 29 Nov 1999 18:28:38 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id SAA07584; Mon, 29 Nov 1999 18:33:28 +0900 (JST) Message-Id: <199911290933.SAA07584@zodiac.mech.utsunomiya-u.ac.jp> To: current@freebsd.org, cvs-committers@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: [PATCH] Four patches for review and test Date: Mon, 29 Nov 1999 18:33:12 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Four patches for review and test. They are for 4.0-CURRENT. (moused patch should also work with -STABLE too.) http://www.freebsd.org/~yokota/moused-991129.diff http://www.freebsd.org/~yokota/kbdcontrol-991129.diff http://www.freebsd.org/~yokota/panickey-991129.diff http://www.freebsd.org/~yokota/altlock-991129.diff Kazu yokota@FreeBSD.org ------------------------------------------------------------------------ Patch #1. moused: the -3 option (moused-991129.diff) The three-button emulation of the mouse daemon has been somewhat difficult to use for many people. This patch will try to improve the situation by introdusing a small state machine. There is a new option, -E, to set timeout value to detect two buttons are pressed down simulteneously. The default value for this timeout is 200 msec. The patch should work with both 4.0-CURRENT and 3.3-STABLE. cd /usr/src/usr.sbin/moused patch < moused-991129.diff ------------------------------------------------------------------------ Patch #2. kbdcontrol (kbdcontrol-991129.diff) The patch will add a few new key definitions. This patch is required for the patches 3 and 4 below. cd /usr/src patch < kbdcontrol-991129.diff ------------------------------------------------------------------------ Patch #3. Panic key (panickey-991129.diff) The patch adds "panic key" function to syscons. When this key is defined in a keymap and pressed, the system panic will be forced. As this can be a security problem, this feature must be specifically enabled by a new sysctl variable: machdep.enable_panic_key. The default value is 0. The panic key won't do anything unless this variable is set to non-zero. To use the panic key, add a keyword 'panic' to a key in your keymap file. The following example assigns the panic function to SysReq (Alt-PrintScreen) key (keycode 84). 083 del '.' '.' '.' '.' '.' boot boot N 084 panic nop nop nop panic nop nop nop O 085 nop nop nop nop nop nop nop nop O The patch requires the patch #2 above. Related PR: kern/13721 cd /sys/dev/syscons patch < panickey-991129.diff ------------------------------------------------------------------------ Patch #4. Adding AltLock function to shift keys (altlock-991129.diff) Our keymap may contain AltLock (alock) or AltShift (ashift) keys. This patch will add new keys: lshifta, rshifta, lctrla, rctrla, lalta, and ralta. These keys combine shift/ctrl/alt function and the AltLock function. When these keys pressed together with another key, they act just like the ordinary shift/ctrl/alt keys. When these keys are pressed and released alone, Alt state is locked/unlocked. Related PR: kern/12475 cd /sys/dev/kbd patch < altlock-991129.diff ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 2:50:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E52FE14FE4 for ; Mon, 29 Nov 1999 02:50:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id CAA16428; Mon, 29 Nov 1999 02:50:34 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id CAA67500; Mon, 29 Nov 1999 02:50:33 -0800 (PST) (envelope-from obrien) Date: Mon, 29 Nov 1999 02:50:33 -0800 From: "David O'Brien" To: Donn Miller Cc: current@freebsd.org Subject: Re: Compiling drivers as lkm's Message-ID: <19991129025033.A67479@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dmmiller@cvzoom.net on Mon, Nov 29, 1999 at 04:23:08AM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any kernel config option that can be used to link a driver to the > kernel dynamically (LKM) instead of statically? LKM's are out-dated. We now have the 2nd generation KLD (Kernel Loader) modules. > Of course, if anyone has any links or info on how to write a driver > period, I'd like to know. /usr/share/examples/kld/* > It seems like the best method to write, test, and debug a new driver would > be to use lkm's, since you could just use kldload() and kldunload() to > test the driver-in-progress instead of just rebooting. Yes. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 2:52:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 3C81114FE4 for ; Mon, 29 Nov 1999 02:52:41 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id CAA16452; Mon, 29 Nov 1999 02:52:40 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id CAA67511; Mon, 29 Nov 1999 02:52:40 -0800 (PST) (envelope-from obrien) Date: Mon, 29 Nov 1999 02:52:40 -0800 From: "David O'Brien" To: John Saunders Cc: FreeBSD current Subject: Re: gcc 2.95.2 breaks imake Message-ID: <19991129025240.B67479@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <032901bf3a25$6d55be40$6cb611cb@scitec.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <032901bf3a25$6d55be40$6cb611cb@scitec.com.au>; from john@nlc.net.au on Mon, Nov 29, 1999 at 03:51:39PM +1100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have just noticed that the new gcc breaks imake because > /usr/libexec/cpp doesn't define __FreeBSD__. What is the plan to fix > everything in this area? Yes. The issue is known. I'm not happy with my choices of fixing this. > The 2 options I can see is to revert the behaviour of cpp, Nope. Doing so would add yet more differences from GCC code. > or find everything that uses cpp and change them to use cc -E. For now, that is the best approach. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 3:12:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.netservers.net (smtp01.netservers.net [209.196.128.109]) by hub.freebsd.org (Postfix) with ESMTP id 30B001510E for ; Mon, 29 Nov 1999 03:12:05 -0800 (PST) (envelope-from azani.sanchez@soulness.com) Received: from soulnet (we-24-130-60-75.we.mediaone.net [24.130.60.75]) by smtp01.netservers.net (8.8.8/8.8.8) with SMTP id CAA10081; Mon, 29 Nov 1999 02:48:32 -0800 (PST) (envelope-from azani.sanchez@soulness.com) From: azani.sanchez@soulness.com Message-ID: <003201bf3a15$0411c1a0$4b3c8218@we.mediaone.net> To: Subject: Soulness.com - Open your mind and free your soul Date: Mon, 29 Nov 1999 02:45:27 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0027_01BF3A13.CD8490F0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0027_01BF3A13.CD8490F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, my name is Azani Sanchez, Senior Editor of Soulness.com. 6 = months ago I started Soulness.com as a senior in my dorm at Howard = University in Washington, DC.=20 I would like to invite you to visit www.soulness.com and join our online = community, and take a look for yourself and see what we have to offer=20 =20 Here's just a sample of what we have to help, stimulate your mind, your = body and your soul:=20 Girltalk - A place where women can get together and talk about the issues. Membaz Area (Photos) - Meet the love of your life or Pen Pals Live Chat- Talk and meet new friends from around the planet. Tha 411- Entertainment news and information covering our world Banging Joints- Hip-Hop & R&B countdown. UrbanFashion- Threads for tha Streets =20 If you like the site, please tell a friend.. ------=_NextPart_000_0027_01BF3A13.CD8490F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello, my name is Azani Sanchez, Senior Editor of=20 Soulness.com.   6 months ago I started Soulness.com as a = senior=20 in my dorm at Howard University in Washington, DC.

I would like = to=20 invite you to visit www.soulness.com and join our = online=20 community, and take a look for yourself and see what we have to offer =
 
Here’s just a sample of what we = have to help,=20 stimulate your mind, your body and your soul:

Girltalk -  A place where women = can get=20 together and
talk about the issues.

Membaz Area = (Photos) - Meet the=20 love of your life or
Pen Pals

Live Chat-=20 Talk and meet new friends from around the
planet.

Tha 411- Entertainment news and = information=20 covering
our world

Banging = Joints-=20 Hip-Hop & R&B countdown.

UrbanFashion- Threads for tha Streets

 
If you like the site, please = tell a=20 friend..
= ------=_NextPart_000_0027_01BF3A13.CD8490F0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 6:22:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 73EBB14C26 for ; Mon, 29 Nov 1999 06:22:46 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id C59883E34; Mon, 29 Nov 1999 15:22:45 +0100 (CET) Date: Mon, 29 Nov 1999 15:22:45 +0100 From: Jesper Skriver To: current@freebsd.org Subject: pcm - I can only get noice from it Message-ID: <19991129152245.A10475@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Just managed to get hold of a old Soundblaster 16 card, but I can only get noice from it when I try to play som mp3 files ... It's found upon boot like pcm0: at port 0x220-0x22f irq 5 drq 1 on isa0 I have it wired in the kernel config file, if I don't it wont find it (I have controller pnp0 in there too), it's like device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x0 Any ideas ? /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 6:32:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id 4C08714D8D for ; Mon, 29 Nov 1999 06:32:23 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 257323E35; Mon, 29 Nov 1999 15:32:23 +0100 (CET) Date: Mon, 29 Nov 1999 15:32:23 +0100 From: Jesper Skriver To: current@freebsd.org Subject: Re: pcm - I can only get noice from it Message-ID: <19991129153223.A10548@skriver.dk> References: <19991129152245.A10475@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991129152245.A10475@skriver.dk>; from jesper@skriver.dk on Mon, Nov 29, 1999 at 03:22:45PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My collegue just made my day :-) device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x15 ^^^^ did it. /Jesper On Mon, Nov 29, 1999 at 03:22:45PM +0100, Jesper Skriver wrote: > Hi, > > Just managed to get hold of a old Soundblaster 16 card, but I can only > get noice from it when I try to play som mp3 files ... > > It's found upon boot like > > pcm0: at port 0x220-0x22f irq 5 drq 1 on isa0 > > I have it wired in the kernel config file, if I don't it wont find it (I > have controller pnp0 in there too), it's like > > device pcm0 at isa? port 0x220 irq 5 drq 1 flags 0x0 > > Any ideas ? > > /Jesper > > -- > Jesper Skriver (JS4261-RIPE), Network manager > Tele Danmark DataNet, IP section (AS3292) > > One Unix to rule them all, One Resolver to find them, > One IP to bring them all and in the zone to bind them. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message /Jesper -- Jesper Skriver (JS4261-RIPE), Network manager Tele Danmark DataNet, IP section (AS3292) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 7: 8:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id E9A2115033 for ; Mon, 29 Nov 1999 07:08:32 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991127195332.36233@mojave.sitaranetworks.com> Date: Sat, 27 Nov 1999 19:53:32 -0500 From: Greg Lehey To: "Viren R.Shah" , freebsd-current@FreeBSD.ORG Subject: Re: repeatable crash in -current (softupdates, NFS) Reply-To: Greg Lehey References: <14399.63511.296802.242618@jabberwock.rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <14399.63511.296802.242618@jabberwock.rstcorp.com>; from Viren R.Shah on Sat, Nov 27, 1999 at 10:26:15AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 27 November 1999 at 10:26:15 -0500, Viren R.Shah wrote: > > I'm running a -current system from Nov 26th (approx 4am EST). > > I can currently reliably crash the system by doing: > > ln -s /home/users/vshah/public_html/index.html /home/users/vshah/index.html > > > The crash only works when I do it on a NFS mounted filesystem. I'm > using NFSv2/UDP. The server is a 3.2-STABLE FreeBSD box, running > softupdates on the exported filesystem. I just checked that local > filesystem on the server, and it is a 100% full. Can this just be put > down to the known "softupdates full filesystem bug"? Not based on the (non-existent) evidence you've supplied. Where does it crash? > [BTW: the server hasn't crashed, it's only the FreeBSD client that > crashes] Do you mean the client process or the client operating system? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 7:23:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 022231512B; Mon, 29 Nov 1999 07:23:24 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdnb25.imasy.or.jp [202.227.24.153]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id AAA00320; Tue, 30 Nov 1999 00:23:17 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199911291523.AAA00320@tasogare.imasy.or.jp> To: current@FreeBSD.org Cc: freebsd-mobile@freebsd.org, acpi-jp@jp.freebsd.org Subject: ACPI project progress report - Nov. X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 30 Nov 1999 00:23:16 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 367 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, here is the Nov. progress report from ACPI project in Japan. 1. Summary of our activities in this month: - setup CVS repository and CVSup collection for developing environment (jp-acpi collection on cvsup.jp.FreeBSD.org). - improve device driver (S1 and S5 state transition are supportted on several machines). - gather ASL code and DSDT data (not so many, but still useful to design AML interpreter). - start AML interpreter developing (now it is in the userland, then move it to kernel space later). 2.ACPI CVS repository and CVSup To CVSup acpi development source tree, please try this configuration. --------------------------------------- *default host=cvsup.jp.FreeBSD.org *default base=/usr *default prefix=/home/cvs *default release=cvs *default delete use-rel-suffix jp-acpi #jp-all --------------------------------------- Other CVSup servers (such as cvsup2.jp.FreeBSD.org) are also available. 3. ACPI device driver progress: - detect ACPI BIOS and install the interrupt handler. - experimental support S1 (sleeping state 1) and S5 (soft off). - have abilities to detect and handle power/sleep button press event. - add builtin PTS (prepare to sleep) control method for several machines. this is temporary until finish AML interpreter development. - set sleeping state via ioctl. Yes, now it's possible that shutdown and power machine off by power button, but only work for the limited number of supported machines. Difficulty is to get value of \_Sx package and parse/execute \_PTS method, so our tentative solution is to have builtin PTS functions for the machines using bogos macros :-) Stupid? yes I think so too. We've started discussing AML interpreter implementation. 4. ASL code and DSDT data collection We are gathering them for further design and implementation. CVSup ACPI source tree, compile ACPI/util/ tools, then % cd ACPI/util/dfr/acpitest/ % ./acpitest >foo.asl % cd ACPI/util/takawata/acpi/ % ./acpitblrd foo.dsdt.dat >^D % and finally send them to takawata@shidahara1.planet.sci.kobe-u.ac.jp. Submitted data will be stored in ACPI CVS repository. 5. AML interpreter implementation We've just started based on Doug Rabson's acpitest program, but parsing AML and managing objects in the name space are almost finished. We're going to make configuration utility first with AML interpreter in the userland, then move it to kernel space after brush it out. Please see http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/util/acpiconf?cvsroot=freebsd-jp In the beginning of this project, we thought merging them to 4.0-RELEASE would be very much exciting, but it seems the codes are still young to merge and 4.0-RELEASE feature freeze is comming soon. We will try another chance, hopefully we have AML interpreter in kernel space at that time. Attached diffs are the latest acpi device driver against -current. # cd /usr/src # mkdir sys/i386/acpi # patch < this_patch Suggestions, ideas, patches, bug reports, rewriting the codes, offer of cooperation/volunteers and others are very appreciated. Thanks! begin 644 acpi-sys-19991129.diff.gz M'XL(")N40C@``V%C<&DM94[M5IMF\XE<[H@?[<]0IJD\?#!U)K5!MDKUEMOGGSDGSXL+.W_Z*VLT=>D+8? MW(?N]30F9:?"P(EIW]B>'[KDTHYMSQY3\CZ&JEOX^A!-W8D]M4.[60]FMD?C M>N2X]1M_3&N+NNW4_QT<%Z&]<.-H$2Z(?MDR6K_IY+U[:T?VC?OA-*3TQ.C4 M_?":=V[-9H1UCDA((QHNZ:2.#:QQ2"=N%(?N>!&[P+#M3<@BHL3U2.0O0H>R MFK'KV>$]N?+#>50EMVX\)7[(_O87,4,S]R?NE>O8B*1*[)"2@(9S-X[IA`2A MOW0G4(BG=@R_*"":S?Q;U[LFCN]-7.P4,338<4[C=^RC65^A+B+^E23+\2<` MNHABX"FV@5S$:X_])38)83$L\./YL>O0*H"X$9D!0L23CLQ8S)(%HSHSVYW3 MD$F*'*R3`D,J8I&D`*^3!9#W)U%#.*,2U<1W%G-0>5O.W3Y,BP\`(9G;,0U= M>Q:EXF?SAIA51E)-,,]U@QC]4_.R-=0(E`?#_D>]HW7(R6=HU$AK9)[WAZ35 MZY!VOV<.]9.1V1\:Y%__:AD`_[>_81/7N-YGHGT:##7#(-!#OQAT=<`#B(>M MGJEK1I7HO79WU-%[9U4":$BO;Y*N?J&;`&;VJS@>P[3>E?1/R84V;)_#9^M$ M[^KF9T;2J6[V<+Q3))$,6D-3;X^ZK2$9C(:#OL'1(6<=W6AW6_J%UJD3(`.& M)MI'K6<2X[S5[:J& MJ9LC4R-G_7['8+A@`$,;?M3;FG%(NGV#"6UD:%48Q6PQ`@`-2`R:H7PR,G0F M.[UG:L/A:&#J_5Z%83KO7X)P@-X6=.\P0?=[C&V04W_X&1&C3-@\5,GEN0;U M0Q0KDUP+Q6&`!-LF0Z>`PK@@5%/AE_2TLZY^IO7:&K;V$=.E;F@5F#;=0`"= M#WW9^LS9'#$1X(P!=;RHZ'"5S2O13TFK\U%'\@4PJ(.A"]7IGS)4QJA]+J8@ M71%_%:;TK_BUO[/WD^LYLP78G5T_B"VV34QWE>KWN(\$8,WG]>GQ6GWH.SG5 M\'^S6N8VV!.5BE8SO>7JZ-#73"W@Y7: MN>U,78_N.X#DIJ!M/K&6]BJULC&BUVBJHJ+F>&*'UP6-<534;3G/D[=L#9S] ML>L7]856/H>95C>R]P,O"&D1,>-%$4+87=GFE"/]34USV\NI7A\&:V&?N&+5 MZ')PD]8>Z`0GC$2+,6H3G4MUG=`K((M!6,9%:V!=M#Y9AOY_&F$_S3>(!K:" MA1,S('LR"A2Z-#^!0@V%):SBW_ZBJBL167`ML:VQ$]7*U? M9NLC][\4:O$O5K6P`/_+`ZB*[P-6]9W$Y,LZF5^A[?LA)Q*V.((*9K$Y`7@B`]SZJ^@GU)_"@UC?W+/&RPLYO6:9+%!+P/G%#NI6LEI M8GIO(??4"FSGQKZF)*_R4&AW*=.H"!E53N'3BJ50VNBF.^!4"9F#3!80O63$ M/K'\@'I",;!XJ#2!Y8RH:&-EM='UP9R+1E96&^>H8;P-BX?ITFYWM(^P7/X. MV^5!L[$Z_0Y0&MUR;D3YB$T<`7Z0/*`^(;4JZAEILH%]R):0VA-L@&`&2K+V M-G1CRJM94=8S+B0>]B%;`G!L>0\A_R2K9X]9X/O M8K?=!)?];ZQ,I2,;)HMYP!%A*2$(39.@"(NR_FIF7T=8WY`U8X&YUI26"2HO MP#VGL+DN(@(N]`[WYE$_76Y$/C-;8Y0CA(SJ$/M3#?`JS,LO3<8F:5&83MX4PC0S-++!J80 MMLZH!7$#_KU&<)6,?1_L*VH^!UTUQJR'ZX.M;+(EMX@V(G%]%'A)V2K`2E6) M\C7>-`*GX<\<`;;A./1G?]X0!]L.H>);VK-BC%:,`>0/0G<=T,:6$_D8C-M- MW/88MU6VQV#\<32"BPF!.`TC``T6<3GMXOJX5POU64&UH"IR-%D(3F&VV.U-A@;W$L!,AEA=Y19X%;>)PW MD8]`<&O?/`T!;#I>]$-X07CT$IDC"CX.>(15-/)3_S;V$U&#BP=>QGAQ?8V" M3H7+7!>&A[7";MZ`+L9GHVUVP;Z;95X/P;7>L5HC3!>DT%4"4*?=UIDUO*R2 MYVI#LTIV=S.;!]M7!D/`>5J&N"RJU^N54A#"^%=EMMIMRH*)M!%ZAZ42^BH^"7U_+ES&$DYRV65B("YY3];00O7>7H6'73@N,D?^$96>NAQFTJXP`I^^RM]DE%@*R(D=#EP8SCDH8S M._B5<<9I94B.$W3/G[.I(^^/,I(6S"4R!@+87S52SM!58[TKC.!2#F%D[X@H M\U1*Y([E[QA@\LG+B$()OCB7&TB79/]$O8E[M4)^.ETJ%SD9BT>I MCS#&3[%*@4V.BRP,K'L$XY8V@RP#E6MLI&U@Q!6HTQZBK6TR;\(0@)YS;5"L M0;9E"R'GY'@>M=7\`2$O\X2\7!/R,D?(RVV$'.0(.9V=98Z0EWE"#@J%'*P) M&80FA+LQK,6H=H.4%]#3#M-*0#)'N5;)"^=F?(463H"\J!">4,J1/S34CF?4 MXV)'#A@>V%40";![F&&FS$>![A7R*VF0=T33>Q];W34]2FW-AFB?7,\,M MQJD=8[&:EP\3633V&QA=:Z@0[%H[7LFPK6;2H$4UQR5$`"[HPIN`[643*JFP MQ%`2(9*DC)P07UE)IB)\[1BAX3-,4(KNO5&WJXP2*56H^QR*UPE]37?W[XE7 M!C1XSCQ@X+7CR+WV(/(+P<+N=HR.N5LEKRILROARR<^I8-^*F-C?5[>I$N+A MKK/6_16Y(W%9N2,-J=P%P/=$)BG_#S'?4TA&>]!A=-J]7M6EH/CW.M$]TT2HV[QL\' M3?1N&_!#&LUF$TK-!GXV\U&8%T-``080^@)0#L3923>%.%A-OB'$X')X8O88 M$,`T&WDP1G>@P!SDP@S-=C+2*X1@S;#;"H<+#16-HG4\*K&K,&WVG_9K5;@P0Y4QUQ M)K4AG[-VGJ3L9$_+A?!-+HVJE_;,LM%'GUGC)-Y^BZ>$L\""R.F.[TLBXXR- M89FM>79"06$_OVS]9AFF0<9NC.8,SQZ0"YOX'N76*2?IC)3EI<63"..Y((S] MS?*SG%06N4"-\.%$Y3?XNFN2]^])\S6/\255C`#>XP&@[:CDR?D-9.+^*40G MW(:\XZ\Z[`#T"ZL"!Y##6W;*$':56)#@!OF6$/_R$&G'E6!^'MQ!`Q:U'N?B MJ6./#Q,Y/7GLO,3\4T18$L<1,H34JS*4E06'(I"G12^U`8A#?!.'FRE;!A%X&I6%D=)V!$<-[=*1)#$81&I1-V)#FVTV+B MRCS&32+/4R')XECZ96HC10H\N*2B>CL%95G>74I#/9_ZU* M[OT%WN4B40"&1$Y4)I1-!8K>04C:$'%J'9%3$693\F+/9@R(R>R:>C3D=[JY M!9,N:#*+STGY?T6!+#>)TEM-9OOA+MM-D.I&%;JBR%J;N>D)4T(2A0P5T5;$ MS4;XQSO5!2XA,C),E"MAAG/Q1($5J/::OF5-@:+8TD^`%8>*,JL-%F&`M[8T MOB(:FTU#(Q5D8]4(J!<['K8"C4D%?'\X#6- M]/Y/TGZ8GD0A0C^4N:U;]GA#8O]U!14$^8?IL5%I6[$+!17J_[05W%CQN;;4 MI\*A'UQSV_*DZM*/6V$/;+[-5##-G!7VB'VV^?@5]HC=M?E'5E@S76'-'[K" M_J1=LZFLL.:/7V%;;`%_:(4UBU?8%GO3/:3QEL;!/ M^)L7%DER;:S7ZXJ.9X,R&9L^[+8+Z@ITUZH(8I):>4PY=6<33A$K`C$G(\-J=3I6^USO=LJ\=Q4/ M,L759M)0DBNBDS@*VF'W>"#VY5>S$O)VB\]<\?T`+2=D02$YAV20R:FJ3^?X M6-"[_O+SUW1\?E4+7P_D'4>1LM;[I/=EN%<:_Y>&?CG!5&479_RKM*92$<>3 MGA/AHJZCMQA,1R#WB\Q1]?V#%Y%I#R^V?1<94, MC8[Y(;UAHEYI0=Q5DD\(GH&+$87\,-Z=T,A!>2J]*MS(X/L)MG8ZVLGH;%4' MFZH]D>)K%$^<'<>V,\V;N9Q`64!=8SR.#=A-BGKMY4:5';8KK?+-$C33R,+L M4Y47W?`_(M;-',@K%ZIRS^I7*T-WDE?-!RH:(PRS`?B+(`ZCA^+X;#N[UL_R MSO)"/O]YX4Y97BMSH8"`SEV+%?#ZJV)$E)M:XG;`EH?A.:K$UE0HSKGSSI[% MHR%\(A%,[R/7L6=D3N=^>"^/Z`N6GMBP^1%MN'8T/DR.QOG^G20WR^N'XR$[ M'&=P.10B)CPG'H?^#?42JG(N6FV@%K.V0HSR+5%Z6U20/Z,>J1&\8-D_M6!0 MZ[PSK)!]:1J2:69(URB<8@[FV43J*CM4%F76`;6)7QI);D57P&_@0XMK#SOK M%TARKNULJ0TK%_!@^"_N5Y%I968S4;_$^B4U%9']%'93A5R9:-DS4RVZK\D( MF;D'&3WCXG&KZ1*0>[QZ\+^F5'C^N'K?HN#"Q>I]B^2F"6:ON`(('4HOT/`' M,NHEHWWV;QSX#IY?HM^`%H2PJ\/B3@,XZ*F#PUK3FS46OVP1S5W+F3.#!'9) M.NW2\.&=%S0I.(HE[2(W]\9G`[PB<*W[F/D'?PBZ5X41X[^;L-6<6JVVJ7_4 ME#T\Q9W90C/+GKFDN/)MR1_V>,3JZE]H%ZDQ"/^3P[C#,J\YC'/P!_D>_D,R M#1W$KV::[B#(O''>&FJ8HB'?"F7!ALN(`H<6C#T@='"3I#B?)!G0#\$J+,1% MP%/1;"1!&3[J-X=X^JA9%[K13HX1P50*)Q#[6.D*QT]V=D&>N]/$R,-`&^>9 M#<]E^&S"K5,8;L>2!/R>[E$K[[;2)+PZ./A$>-$6!Y5C)EMP19X$[K`C*8-1 M-[AH$HV'#FGXF[U+(II/7`@FRZ_J/]=?UIOU@PK'@O<&)P3"-/Z^[LJEP+Q_ MM?FN"K^74DF/NQZ73BY*6\,FBJ;S.2.ENKHV9"VSGIS#?']H\/2FRL.#)XQI]*Z>= MO&#B/XN27N6:X'6.1&-X9,9B/Q$HAI@FX#W_:9T--)A"/Z!WYT"Q$84-R'D3`O_[>YP>= MRCQJD3R,YG'987N][_8+=;7O8Z2PWO>)XSYPHV1KN:GO.;?!L])9/-W*J0T?[>*&9Y_V.C&1ESD*$VO*S4LT#9MD+`^,NAI#7B4>O5M$596X:K8G MGT;YB##]QT'235K?[V^XV??@>]2'WXHF-_4A1,@&W0#/-1`*TLE,HBCQZ*N) MP=0Q#ZIJM>29THR]4X*_WK\G;R%&!5T:ESE)9(^XB1/':>(W]0X+Y9,#?#NFA(M`C,H4NU(`VSMN0LF!+CD&X;P5[!:P]_BG^IGW!]E_ MFV,U6LCR*J@]$J\,_I^[H_].&T?^3/X*M;O=@X00&Y*4)+O=\I7$6P(<)DV[ MW3[.@)/X"I@UD*9O7^YOOYF1+,O&!O+1;M_FM6`DS4B:&8U&LC2CK*"BMS(D M5<@$YM6JW.4(E/93'YD]G-H)Q43_`GM7H1_13EE##(H7QE,IV0=_R/OW&#A\SX?WE__+J^LM5-<+ MJA,;`HK0Q`_W]1M_KZ9&L:_3UGM(:%BRI(#"*C%\0Q+E2I&FS9`YHE[)2E:0 M]W*B\4\28M"[_.;H-Y7E:*U/(M(KNO(TDKVZY?<7<"%UWT+`'^9@96Y'!)RG M/9%\]\TBF1>N?2*0CE3U.E)>W_)$BO+*E]Q==7YY6R*[L MC92<>TKN@UT#/8&$YA=$$_<]MX MRR$J.&LR11#O*3GR",]7CQY_5/>"^?-,R?QFH\^O[:%#+Q'^?BQ6N?'D7'Z8 MIZ]_(I>EI?A>0#/HW;BT_#\H?[BGH+G^C*>Z]^4Y_HC1W8\_+VYO+C< M?2HN_WTC^WOC\N-']E(T#^#YDXQL>5X./=OBZP!^4HY?T\57I^)I-,OZSG+Q M;`G;9!/!YM5'\<@W[E?"3?YR5=SS[M#%C/&]SJ#6^,JB0LZ/ M!?)7#\'!0"O\(F'DC%TZ`,'/"&$=MN>YGK].Q`1'7`L]"@8%KRO.%_/F=#H) M1!Y;$7]N5/K1\6\$BTNMT''E2BL*C]$4MWZ"ZZV)QQWD;<\(@JIAKL2@+<5@ MUO"RK]DI=3@6ZC5N_*>11)L9X7/;/S&%F:_XH2CA;^'G7]A>:-6:<'F2GL3Z M5!F<*9\MG')R_1H==%16'7.+[0U"X>6#-::,:%CKBFI6>L+=&%3"8C"2!>6Y?GSG#FC%F%;ZDP_KZ=8CX%KFE"/F_*YT:] M8S2Z7+I*E3>EDUJ*O,?/)\[@5W:XG6'O;>BIP3Z-W<\Y@4/4=V;U/9PZP_[8 MV/(W-4SNR6'*S!G*G-%4(9G8[2"`P/X,Z@%V>JV!%W,(&[8:^Y`6/Q'V5Z:S0__$A<\*8SRP;SD_Z)%3MFK-K.^& M,="U5M-4"+R*(T:C6GL'Y66'5A8.F"AA)&=7`PN&JJ"8M!J0#EG:)QT0+(\`T3NME79)\I1X!X=6>*/*R5D?BFJ'T0V7YV7QFWZ;I MD^L'\\NX7\>SL1ED-\_.L,\.GFW%LW=7&+-E$)TX^W_.'<].(W"S]U^[#SJG MXXQL:-=;?#65P8@G?J&5V-KBH&&`+<-O5HKSAZOAT8I(E[RKC+B?2K]7PAF7 MZ=L,V"OPJ2;7&^X,,YY%TVM_SJUAVIWH6>9.\ID4/*&9`\\+@XH/I6;YMTSJ MZ082H/.Y#(_),L8SH\+%4]>0JOAJU"XV/4D%_"AP;0$/#*FA0Z60$X88VRGM M5E>3?K<]%YT+*L94M]7A7D6[%Z4W9%.U\F7?;(LYL!;X$>M.\KUE_LM`-C1N MY7)N-#WG"CU&D=&&QN$&GO.&#QP4Z3^ZII9E+6[+I[D)B^:^=KL7\Z2%GNXR M"A8]'LO+F*S'/,5@B1J>?U1KY9.L\.%H-+-0MHBG/V_1A52*3P2B MC+`/LJSAHKV11:=N%`566/75\@GTD/\5A4D?K>ZDU2R':[-W\WVJ3PLJY*56 MU<=MCC2`%NG8;JK3U/-^`_C%(5ED5^-%CDN-LZ0B`DNK7JLF%>EG(@EV)&%/ M))R9)YI$@K3`RQYGM/H`'H)@XXX2[P;H'=(Q0J&@;"(]]C+^[<@4UR'`1-#G MT/Y,-!%;G)%+2<071J5',,'P`P4-Q%H&E/>!*#\.$,:]7_A2(QO4&O(<7IHG M@,D*8<'P96+(='1UEUC<'=7#&XLKG$F M9L&ZCZWG248U%2]R^<+1<1^X73$T[@U7Y*.'PZTG<,G;74E[CVOL?BE,7*D/ MXM1!C#:X$[@2=$',B(Z'\!4!YL8`)6J!6"60?-P\O+_ M5'(LY4$/9$3AG2\B?BETCBD8=!%XB!>$60B\R!(C*\ M<&G\99D=5*Z<5;.I(LT/50,>"WEZ-AK'3?R18(H!;CTLM)>V)D:\V@!]90.@ M4`4:(.H1:\K6J8GOO`*SAQ(._+>V8C4HBM$-2461<8V"'8MJ-^B@DH2K!N@# MU!\M)V']=2/6)!)H/8C4$4HO:..B91;6A05I20$V^@9]LN=;263D+;%POH4Y M0\W4OJ$Y4E`K!$%._!DQ5OQ[NU]Q?-`]-AH=7&VO!U,D(HS#4C;!HD@O2&4N3. M#8B*6RRM\5UC*`5T67"9XI4#[F\/373.$XSPC%9@O*1?MQ\ M-5+<6Z:#`N=MFZ)[",'?1_.><"=O"=IJH;9`:<5AYJ?JUU!FL1-X!>^X>U9^ MO1F\+TH_P10>E?!*IUT)2[@^V(\(."^S8O6/LVS%J+Z3&PZ^YZU*M=0)[4+` M-\I,L*_-P7BY-6JY>&-V%FHQZXWF8N)[TUA(/#-/C,BNR,;*C24MX6F=[20] MYFD!-A\/FX]Y6H!=:5XE&5I_K&%I)=E`^@HC\B M">B^HY7@^9@L?C<+^>C[M)"H+:CIT$9WZ:+4KJ*WP?44MO79\@:PZEH:UO@^ MBZYUM[S7T4=AG;)Z1.,L&7Z\B]]U>KJM:ZR+EO?!(B9):\1M=Y"A$:@4GO;0 M?4_M[]GW#&F4[W+?4TM<2GRM79_PKN?WH%(2I2]6\M;8:KNOYH@*[[MG?\CM+P\;S8#2$IJ^&2^ZF8>XMY]`? MG+3M,%,L)G'6C9FWH+I3]S,Z/'-&DR'%CODU\&V-P:>0X8*I=,+^VO)@">O: M(^Z?-_@]ZPV=07A3!%(]^Z9+SC8_Y-$_+GG53:72FS@L+^?C?B9"EX`J&;4X MTG%U\3LN=SU^0%1ZGSI2>!1;(.4_X+E^Z9Z*)/)YR3S'.*7/6_DR?*$(:GSW M!K^YY,6=5!#>ER)O0)`!68FZ4:L@YD:51X$4Z!4)3]J&S]*YVS"R-AB6B*TR MM&Z<^90C4PV`Q!V!.&QDJR*ZTD6[BN-][;[+R2>&`C(O7)G9;+S'NG@=ZIA. MT.0QJ'E&&"_S$?^NB>87=*VX=T`]X(^/K(8HETW1)_N+?^'G'?\2/WS?7J$S MR=P9&4YQJ6B(3I$%PSRE+U6LLR*BPN_Z?B1]DFC2\,6JQH#I$[AEF)C[SGP`!D&I#[N5#B MP@\G-9.[X>0!E?T$[H&3?JE^._TN1$#\-`E%"2&'G[R/$3B>$G4D+;8O9=>@ M"ZHV0:R?KQWT42J+B(;[$=R):C@?S3QX6"Q&FX22O$D%92TN`""'W[M]/$ MD!/-E'=U%`UPR-%COQ3T\ZCJ,L3,ZMNB`>,#>,GV!*:O M<-ZF!C1=I6[5NS8132TOZV6C,A"]YA-O3'Z%ND$6>-U@T5ZR;6_>8+GH/]0)'*T8(H M,FL^$B^N MQG..!BB_,[CJY?I@5@B"I.#W0HE1I,0H4F**`WG'^HQ#X<:&PK(LI&UL43ED M"GV$<&'"!N,%)B/\C]E*_F0DLFVLR!K<=/$AC&-P$RISW8O@N.ZMRTTA,G'\ M5+-6JP>%[!YP%;[X"&LU6KB)S7O>G8PG MN6L8,B#KV\O_8%3Y[MLQN(UH`::N!`R&%:^4V'N]#B@TJ]8\7J=UJSE''[AZ MR?597.)2;BGE4N9\S)JPGB[H3-L]!#4(#XM\4B$6.;07<*B@X["#3S[JV":K MN`-;N`VWAN@T'"R1:])[%.S(&;-;D+M616R!H-K#Z145GS/N#^<`_9S3^#F0 M3B9)?C\GAOOI/V.3)Y9GC7+7KZA%NP?8HCTMJVM<*U/M3DJ[M7%]'>)G-6 M&1@2],KQ3NG'*XW'>J;-3?S;#.)/R11^70-#9SE3=E)OEDMUFC:NW>%@BC&I M6*O39C*>B@^WPQ]X/!_G2GC>Q<9V,3J+;7G]Z[3&0_H0AN?T?RH7&2E5'_'!XFAO$X:Y]4R@5R MPD.,H9!$`HR%I81@9,=^P:V"(ZA=N[50)G_^!7@%AF'[9[[=HFD!P66S[Z3H M,RYPV*R>Z\[`5.FY4WH3QOL.B(>N^XG(ZP(C/;KI'$@2N7(+BWN3BE'KE6)D M3!_R'FR'RO-NO]"*MW3S?EWI._*'"OY;5PVC$AC8DP5-+--7*V-9-'4!%B!I MUUV6UPX+!X=[^21]'``M5\EH`FT57DJ5G+KTW-$A>YW^(1.@>)G;9>FR[7VR MA_:7#-O?*>P064TA=YDG-X]>"GJ99?3NB MYWWM#8)Q"3.&_3AM;]^":AK36HGA+CV:4]UN*TW^52X=;TK[,Z%B@]Z0%J9= M$2&$E\0M!G;D;%_2YHK@F^0/GI9M2G M2$YO:NU&N636\'`;739OE4YJ7?/4..X0]A2!@8(%V@BHD/\#K`2C<8XN<_"_ MBRX)Y(^!0^V+DDI$@H#.=\GS#^V6I)7@(BR%0>$H'MW@EKOHP7:(&GHR:>"" MLN"]+VHHOO#],@O+,^H^_"F;7HAN^Q4&7LGRO,W0`;]TFCR\;V9^X@6'Y.<` MB+*;R2;@XD50IRSVD(*$8F@V2O/L(:QA!R+"'3/&EZXX`DAN*0@;OKB@`#>W M6@%#N2^D[L;Z@E4IJ':1[X2DF-K4K()4>H:5)(^VY1G5JF>H]U(Y5]NT,+)`D2\]-AM;8GN6F?2?WR>W9V_.V9 M,YO.O3DS+DIFZ8T!!N9G:VI]>,+9!$F%I',&#)UH99%K_=^8S0C%Q@L=.G M-^I9T,TVF]C>R)FA'$\\]\89P,/LVIJ1C77I#H?N9[3;8:TV<,0Z":U#`!S9 MN*<&/_18 M%D%9\YB=U=J54_A9*AMUH_.>FG1L=!I8WS$V$::E=L>HG-=+;=8Z;[>:)D>' M/:L:9J5>,LYJU1R#9D#5K/:VUN@P\[14KZL]A7^ACI9KT$;TF$:XJ"+H:-5H MURH=[%'P5`&Z0?/J66:V:A4#'VKO:M"74OM]5N`U:_\^AT*02>BJI3.82DV6 M7D$9X$KEO%T[PQ8#*=&CMI-JLFX8(*S%K[K5&IF4>LWC2):.=F M+G-4AO(UF)%01Q,0XA.\YA0F>>54\&"8$3X1NJ/@=,EYW(,:^Q4]ZQ4.06:=5N5+NW= MG';E*\[X3-7DHSG'[?==VD^@XT"L#6L:.49O.%D\D\N M9.1KS4C^?!27[-JCT.O1(,>SP_&%1;)PI'8'UJ4UX]K$[G;3:3QF8@\R?ABF MN"[QB(:1#J%+K.7]V?T8UP[Q/G:QU3=QR;0^3>A_Y`5Q*"_\HG@A&VJ3S8M4 MZ-G6S/62S)CW/OJ3@Q6S/F@?\2E-D43 M!#NR!Q(4!!7L6].9<"2RDG_+HU)B51F5E=(O[%\QO+JT^E/_Y7@T#U]"A_** M0;AX^-5%9W3#!/DDDT:7D/J^!%6BNT8K#,5K"M>G^,),S%8B,$7SI[NX,^#9 M?\9ERN;NQ35*#6*2D-];D2\C1R3"+\W/+\_VO=C'Y?I^KA/R]%">0A(ELDU2 M=A!V(28[OSR;FIR0ZSL;3\C3E^;ATFD9B_-Q$CGI#F^&^2ZL\!)S"TFYET-K M>MVET&G)N3"6!['-&LQG7W`AGICWV1G,KF-SK2]=:^B-XO)&[C@QKP^FZ=S[ MLFS4%CX48C4CQ7?EBG$-%>6-/N/*@;24[S31#.WC!NK)?,II!GX,<`M00/G1 M7,%FJT4CN5XZPZ%OA,L@]CB+VM,IY(.IS_2S\K-G'`/@O,[!WX8?[W=!ET*G M\7VYW;VQ^_YI(Z;\776';O_3_QL[FYZ$@2`,G^NOF!L88Y&*>O!@#"<2"48/ M'`@Q--:DD2`?[9'_[LX[T]VEW56X$8;N[.P6=M_./L..\1](7E9::1A7:QO; M<)]AVPS=8G3S__"H,-71S*TJC!:E3F-D!>26"Q=7T*:\5U`:@M3U&#$.*2&( M[?W(Q!9J"+GW0O5VL6^T$)O![689Z\[J_3O0QII\3/V']$ZJ\/HS,9X_S-/3 MRT=U!RTLO%4*E'!]$O"V4E6'.H8Y#+4`=98.]23ID4!VQ6+GZ'>&\5[,0\3. MM/J)^RAHV">'AEVL\B4N47YAA\F?\Y,%U/068%CQF9*&X"07L'5P(N%D>7:[ MWM@O4@.$1OP#_%,+PTZ2C\FLWWOM"5*B9:.\:\\HZQIYF%ZVFXOA+4BSEZU@ MV2WZ`C1\?NSUWX+\V`+P[-: 3:,1"'LS`EHC[^0M@PC"Y`<,``,EL ` end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 7:29:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id E20AA14C11 for ; Mon, 29 Nov 1999 07:29:36 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id EE5541CC6 for ; Mon, 29 Nov 1999 23:29:35 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: HEADS UP, bind update shortly... Date: Mon, 29 Nov 1999 23:29:35 +0800 From: Peter Wemm Message-Id: <19991129152935.EE5541CC6@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm about to import bind 8.2.2.p5 into src/contrib/bind and fix up the broken parts of the tree as I go. I will disable the named (and associated tools) build for the duration. If you want to do some make worlds or releases in the next 8 hours or so, do a cvsup pronto! Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 7:55:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from betelgeuse.accessus.net (betelgeuse.accessus.net [209.145.151.40]) by hub.freebsd.org (Postfix) with ESMTP id 6D64014C35; Mon, 29 Nov 1999 07:55:12 -0800 (PST) (envelope-from root@betelgeuse.accessus.net) Received: from localhost (root@localhost) by betelgeuse.accessus.net (8.9.3/8.9.3) with ESMTP id JAA05852; Mon, 29 Nov 1999 09:55:12 -0600 (CST) (envelope-from root@betelgeuse.accessus.net) Date: Mon, 29 Nov 1999 09:55:12 -0600 (CST) From: Libertarian To: FreeBSD-stable@FreeBSD.ORG, FreeBSD-current@FreeBSD.ORG Subject: subscribe zoso@accessus.net Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 8:10:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4A67914CAE for ; Mon, 29 Nov 1999 08:10:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id IAA06195; Mon, 29 Nov 1999 08:10:14 -0800 (PST) (envelope-from dillon) Date: Mon, 29 Nov 1999 08:10:14 -0800 (PST) From: Matthew Dillon Message-Id: <199911291610.IAA06195@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: BOOTP appears to be broken again Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm. BOOTP appears to be broken again in current My diskless systems are insisting on mounting root from fd0c with the latest current (verses one about a month ago). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 8:51:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 00E9B15181 for ; Mon, 29 Nov 1999 08:51:08 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id IAA27910; Mon, 29 Nov 1999 08:51:07 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id IAA01330; Mon, 29 Nov 1999 08:51:07 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 29 Nov 1999 08:51:07 -0800 (PST) Message-Id: <199911291651.IAA01330@vashon.polstra.com> To: dillon@apollo.backplane.com Subject: Re: Route table leaks In-Reply-To: <199911280243.SAA40107@apollo.backplane.com> References: <199911220150.UAA78559@khavrinen.lcs.mit.edu> <199911221552.KAA84691@khavrinen.lcs.mit.edu> <199911270141.RAA29416@vashon.polstra.com> <199911280243.SAA40107@apollo.backplane.com> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199911280243.SAA40107@apollo.backplane.com>, Matthew Dillon wrote: > :1. Do I really need the splnet calls around RTFREE? > > Yes. Because the route table may be flushed from an interrupt in > a low memory situation. I guess I didn't state the question very well. I realize that RTFREE has to be executed at splnet. But I think it's likely that rtalloc and rtalloc_ign are always called at splnet or better. If that's the case and it's already required, then adding the redundant splnet calls would be obfuscatory. I'd rather add a comment instead. > :2. To eliminate all the duplicated code, shall I make rtalloc just > :call rtalloc_ign(ro, 0UL)? I assume that was avoided originally for > :performance reasons, but now there's more code than before. > : > Hmm. One trick I used in the VM code was to put the common code in an > inline static function and leave the external functions broken out to > avoid an unnecessary call chain. OK, that's a possibility. I was hoping our network-meister (Yo, Garrett!) would give me a sign as to whether it would be worthwhile or not. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 9:10:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 0859A14C37 for ; Mon, 29 Nov 1999 09:10:43 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA06637; Mon, 29 Nov 1999 09:10:40 -0800 (PST) (envelope-from dillon) Date: Mon, 29 Nov 1999 09:10:40 -0800 (PST) From: Matthew Dillon Message-Id: <199911291710.JAA06637@apollo.backplane.com> To: John Polstra Cc: current@freebsd.org Subject: Re: Route table leaks References: <199911220150.UAA78559@khavrinen.lcs.mit.edu> <199911221552.KAA84691@khavrinen.lcs.mit.edu> <199911270141.RAA29416@vashon.polstra.com> <199911280243.SAA40107@apollo.backplane.com> <199911291651.IAA01330@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> Yes. Because the route table may be flushed from an interrupt in :> a low memory situation. : :I guess I didn't state the question very well. I realize that RTFREE :has to be executed at splnet. But I think it's likely that rtalloc :and rtalloc_ign are always called at splnet or better. If that's the :case and it's already required, then adding the redundant splnet calls :would be obfuscatory. I'd rather add a comment instead. I ran across this situation in a number of places while fixing the VM system. If you want to get rid of the splnet() calls you have to document the procedure containing the calls in the comments above the procedure, adding something like: /* * fubar: fubar the kernel * * This procedure must be called at splnet() * This procedure does not block * This procedure must .... */ And then make sure that all calls to the procedure indeed occur at splnet(). Then you can get rid of the splnet() calls within the procedure. For examples of the type of documentation necessary, look at vm/swap_pager.c. So what it comes down to are the requirements you wish to impose on the official use of the procedure. Note that making spl*() calls when the current process is already at that spl level do not impose any real overhead. : :John :-- : John Polstra jdp@polstra.com -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 9:48:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id C64001526C for ; Mon, 29 Nov 1999 09:48:10 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 965911CC6 for ; Tue, 30 Nov 1999 01:48:09 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Re: HEADS UP, bind update shortly... In-Reply-To: Message from Peter Wemm of "Mon, 29 Nov 1999 23:29:35 +0800." <19991129152935.EE5541CC6@overcee.netplex.com.au> Date: Tue, 30 Nov 1999 01:48:09 +0800 From: Peter Wemm Message-Id: <19991129174809.965911CC6@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > I'm about to import bind 8.2.2.p5 into src/contrib/bind and fix up the > broken parts of the tree as I go. I will disable the named (and associated > tools) build for the duration. If you want to do some make worlds or > releases in the next 8 hours or so, do a cvsup pronto! Sorry, this is on hold for a little longer. I thought the lib/dnssafe and lib/cylink license and export issues had been resolved, but I'm not so sure now. I'm waiting on more info. named does seem to run happily with the dnssafe (rsa crypto library) removed though, so it should still be possible to update it even if the dnssafe and/or cylink code has to go. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 9:54:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id F03F41555A for ; Mon, 29 Nov 1999 09:54:02 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p02-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.131]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id CAA07274; Tue, 30 Nov 1999 02:53:54 +0900 (JST) Message-ID: <384211C0.7AD5D294@newsguy.com> Date: Mon, 29 Nov 1999 14:40:16 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Nick Hibma Cc: current@FreeBSD.ORG Subject: Re: loader.conf, ordering of loading of modules References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: > > Is it possible to change the order in which modules are loaded in > loader.conf? I need usb before uhci before ums. > > usb_load="YES" > uhci_load="YES" > ums_load="YES" > > doesn't do it. Funny, I thought they were loaded in the order they were declared. Alas, I'm not inclined to add any kind of ordering of module loading, because this ought to be handled by the load/linking functions and module-declared dependencies. Let's not fix the wrong thing. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 10: 7: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id C560B15282 for ; Mon, 29 Nov 1999 10:06:57 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id NAA35374; Mon, 29 Nov 1999 13:06:34 -0500 (EST) (envelope-from wollman) Date: Mon, 29 Nov 1999 13:06:34 -0500 (EST) From: Garrett Wollman Message-Id: <199911291806.NAA35374@khavrinen.lcs.mit.edu> To: John Polstra Cc: wollman@khavrinen.lcs.mit.edu, current@freebsd.org Subject: Re: Route table leaks In-Reply-To: <199911270141.RAA29416@vashon.polstra.com> References: <199911220150.UAA78559@khavrinen.lcs.mit.edu> <199911221552.KAA84691@khavrinen.lcs.mit.edu> <199911270141.RAA29416@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > The route disappears from the routing table, but it is > not freed. (The Leak.) Actually, no. > Now cause some packets to travel on the connection. A new cloned > route is created and added to the routing table. Here is where the leak happens, as demonstrated by your patch. (Great detective work, BTW.) > 1. Do I really need the splnet calls around RTFREE? I don't think so. All calls into the routing code should already be protected by splnet. We may have to revisit this in the future for finer-grained locking. > 2. To eliminate all the duplicated code, shall I make rtalloc just > call rtalloc_ign(ro, 0UL)? I assume that was avoided originally for > performance reasons, but now there's more code than before. Actually, it was avoided originally because it was easier to just cut and paste. There is no inherent reason for the duplication, although Matt's suggestion of topologically sorting the routines so that GCC will have a chance at inlining is not a bad one. (I'd actually like to find all the calls to rtalloc() and simply add an extra argument to them. I can't fathom why I didn't do that five years ago....) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 10:20:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id B4AE4154E7 for ; Mon, 29 Nov 1999 10:20:46 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id LAA10248; Mon, 29 Nov 1999 11:20:46 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA19775; Mon, 29 Nov 1999 11:20:45 -0700 Date: Mon, 29 Nov 1999 11:20:45 -0700 Message-Id: <199911291820.LAA19775@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: HEADS UP, bind update shortly... In-Reply-To: <19991129152935.EE5541CC6@overcee.netplex.com.au> References: <19991129152935.EE5541CC6@overcee.netplex.com.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm about to import bind 8.2.2.p5 into src/contrib/bind and fix up the > broken parts of the tree as I go. I will disable the named (and associated > tools) build for the duration. If you want to do some make worlds or > releases in the next 8 hours or so, do a cvsup pronto! Thanks Peter! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 29 10:32:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from isdn-11.follo.net (isdn-11.follo.net [195.204.140.100]) by hub.freebsd.org (Postfix) with ESMTP id B525A1524D; Mon, 29 Nov 1999 10:32:21 -0800 (PST) (envelope-from des@isdn-11.follo.net) Received: (from des@localhost) by niobe.ewox.org (8.9.3/8.9.1) id TAA09942; Mon, 29 Nov 1999 19:19:25 +0100 (CET) (envelope-from des) To: current@freebsd.org Cc: cg@freebsd.org, tanimura@freebsd.org Subject: More newpcm breakage From: Dag-Erling Smorgrav Date: 29 Nov 1999 19:19:24 +0100 Message-ID: <86zovx6tzn.fsf@niobe.ewox.org> Lines: 18 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=-=-= My SB32 PnP, which had so far worked nicely with newpcm except for the "fast forward" bug, stopped working after the newmidi import. This means that none of my sound cards (except for the GUS PnP, which I haven't tested) work any more, and I am seriously losing faith in the authors' ability to maintain a device driver. I've attached the output of dmesg and pnpinfo from the affected box, both with and without the PNPBIOS option. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no --=-=-= Content-Disposition: attachment; filename=dmesg.with-pnpbios Content-Description: dmesg and pnpinfo with PNPBIOS Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #17: Wed Nov 24 20:31:13 CET 1999 root@niobe.ewox.org:/usr/src/sys/compile/NIOBE Calibrating clock(s) ... TSC clock: 166192956 Hz, i8254 clock: 1193180 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium/P54C (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x002e5000 - 0x07ff7fff, 131149824 bytes (32019 pages) avail memory = 126554112 (123588K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f8630 bios32: Entry = 0xf8080 (c00f8080) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x80b0 pnpbios: Found PnP BIOS data at 0xc00fc730 pnpbios: Entry = f0000:c760 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc02cc000. Intel Pentium detected, installing workaround for F00F bug VESA: information block 56 45 53 41 00 02 d9 6c 00 c0 00 00 00 00 22 00 00 01 24 00 00 00 eb 6c 00 c0 eb 6c 00 c0 eb 6c 00 c0 00 01 01 01 02 01 03 01 04 01 05 01 06 01 07 01 08 01 09 01 0c 01 22 01 24 01 2a 01 1d 01 VESA: 52 mode(s) found VESA: v2.0, 2304k memory, flags:0x0, mode table:0xc027d742 (1000022) VESA: Tseng Labs ET6000 VESA: pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12508086) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 173731758 bytes/sec bzero() bandwidth = 736377025 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12508086) pcib0: on motherboard found-> vendor=0x8086, dev=0x1250, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000e800, size 4 found-> vendor=0x100c, dev=0x3208, revid=0x70 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base f9000000, size 24 map[14]: type 1, range 32, base 0000e000, size 8 found-> vendor=0x8086, dev=0x1229, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base fa800000, size 12 map[14]: type 1, range 32, base 0000d800, size 5 map[18]: type 1, range 32, base f8800000, size 20 found-> vendor=0x9004, dev=0x8178, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[10]: type 1, range 32, base 0000d400, size 8 map[14]: type 1, range 32, base f8000000, size 12 pci0: on pcib0 i4b_pci_probe: unknown PCI type 307265670l! isab0: at device 7.0 on pci0 I/O Recovery Timing: 8-bit 3.5 clocks, 16-bit 3.5 clocks Extended BIOS: disabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: IRQ12, B: disabled, C: IRQ9, D: IRQ9 MB0: IRQ15, MB1: isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=00 status0=fe status1=fe i4b_pci_probe: unknown PCI type 839389196l! vga-pci0: irq 9 at device 9.0 on pci0 fxp0: irq 9 at device 10.0 on pci0 fxp0: Ethernet address 00:a0:c9:4d:1b:d4 bpf: fxp0 attached ahc0: irq 12 at device 12.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: internal 50 cable is present, internal 68 cable is present ahc0: external cable not present ahc0: BIOS eeprom is present ahc0: High byte termination Enabled ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 411 instructions downloaded pnpbios: 13 devices, largest 110 bytes PNP0401: adding dma mask 0x8 PNP0401: adding irq mask 0x80 PNP0401: adding io range 0x378-0x37f, size=0x8, align=0 PNP0401: adding io range 0x778-0x77f, size=0x8, align=0 PNP0401: start dependant pnpbios: handle 0 device ID PNP0401 (0104d041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 PNP0501: start dependant pnpbios: handle 1 device ID PNP0501 (0105d041) PNP0501: adding irq mask 00x8 PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0 PNP0501: start dependant pnpbios: handle 2 device ID PNP0501 (0105d041) PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: adding io range 0x3f2-0x3f5, size=0x4, align=0 PNP0700: start dependant pnpbios: handle 3 device ID PNP0700 (0007d041) PNP0c01: adding memory range 0-0x9ffff, size=0xa0000 PNP0c01: adding memory range 0x100000-0x7ffffff, size=0x7f00000 PNP0c01: adding memory range 0xe8000-0xfffff, size=0x18000 PNP0c01: adding memory range 0xfffe0000-0xffffffff, size=0x20000 PNP0c01: start dependant pnpbios: handle 4 device ID PNP0c01 (010cd041) PNP0000: adding irq mask 00x4 PNP0000: adding io range 0x20-0x21, size=0x2, align=0 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0 PNP0000: start dependant pnpbios: handle 5 device ID PNP0000 (0000d041) PNP0100: adding irq mask 00x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0 PNP0100: start dependant pnpbios: handle 6 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 PNP0b00: start dependant pnpbios: handle 7 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 00x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0 PNP0303: adding io range 0x64-0x64, size=0x1, align=0 PNP0303: start dependant pnpbios: handle 8 device ID PNP0303 (0303d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xf0, size=0x1, align=0 PNP0c04: start dependant pnpbios: handle 9 device ID PNP0c04 (040cd041) PNP0200: adding dma mask 0x10 PNP0200: adding io range 0-0xf, size=0x10, align=0x1 PNP0200: adding io range 0x80-0x90, size=0x11, align=0x1 PNP0200: adding io range 0x94-0x9f, size=0xc, align=0x1 PNP0200: adding io range 0xc0-0xde, size=0x1f, align=0x1 PNP0200: start dependant pnpbios: handle 10 device ID PNP0200 (0002d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 PNP0800: start dependant pnpbios: handle 11 device ID PNP0800 (0008d041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0a03: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0a03: start dependant pnpbios: handle 12 device ID PNP0a03 (030ad041) Trying Read_Port at 203 Trying Read_Port at 243 CTL0031: start dependant CTL0031: adding irq mask 0x20 CTL0031: adding dma mask 0x2 CTL0031: adding dma mask 0x20 CTL0031: adding io range 0x220-0x22f, size=0x10, align=0x1 CTL0031: adding io range 0x330-0x331, size=0x2, align=0x1 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: start dependant CTL0031: adding irq mask 0xca0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: end dependant CTL2011: start dependant CTL2011: adding irq mask 0x400 CTL2011: adding io range 0x168-0x16f, size=0x8, align=0x1 CTL2011: adding io range 0x36e-0x36f, size=0x2, align=0x1 CTL2011: start dependant CTL2011: adding irq mask 0x800 CTL2011: adding io range 0x1e8-0x1ef, size=0x8, align=0x1 CTL2011: adding io range 0x3ee-0x3ef, size=0x2, align=0x1 CTL2011: start dependant CTL2011: adding irq mask 0x8c00 CTL2011: adding io range 0x100-0x1ff, size=0x8, align=0x8 CTL2011: adding io range 0x300-0x3ff, size=0x2, align=0x2 CTL2011: start dependant CTL2011: adding irq mask 0x8000 CTL2011: adding io range 0x170-0x177, size=0x8, align=0x1 CTL2011: adding io range 0x376-0x376, size=0x1, align=0x1 CTL2011: end dependant CTL0021: start dependant CTL0021: adding io range 0x620-0x623, size=0x4, align=0x1 CTL0021: start dependant CTL0021: adding io range 0x620-0x683, size=0x4, align=0x20 CTL0021: end dependant CTL7001: adding io range 0x200-0x207, size=0x8, align=0x1 CTL0051: adding io range 0x100-0x3f8, size=0x1, align=0x8 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0 kbd0 sio0: irq maps: 0x841 0x851 0x841 0x841 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x841 0x849 0x841 0x841 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 isic0 at port 0xd80 irq 5 flags 0x3 on isa0 isic0: Teles S0/16.3 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x960) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x160, AddrB=0x560) isa_probe_children: probing PnP devices unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown0: at iomem 0-0x9ffff,0x100000-0x7ffffff,0xe8000-0xfffff,0xfffe0000-0xffffffff on isa0 unknown: can't assign resources unknown1: at port 0x40-0x43 irq 0 on isa0 unknown2: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown3: at port 0xf0 irq 13 on isa0 unknown4: at port 0-0xf,0x80-0x90,0x94-0x9f,0xc0-0xde drq 4 on isa0 unknown: can't assign resources unknown5: at port 0xcf8-0xcff,0x4d0-0x4d1 on isa0 unknown6:
I just cvsuped to -current right after = bind-8.2.2=20 was merged into the source tree.  I noticed two problems.  Su = won't=20 work and traceroute gives me the following
 
traceroute: icmp socket: Operation not=20 permitted
 
here are its permissions
 
-r-sr-xr-x  1 root  = wheel  12076=20 Dec  1 14:15 /usr/sbin/traceroute
 
su just says Sorry and it has the same = permissions,=20 I ran gdb on it and here's a screen shot
 
253          &= nbsp;           &n= bsp;     =20 if (pwd->pw_uid =3D=3D 0 && (gr =3D getgrgid((gid_t)0)) = &&
(gdb)=20 step
255          &n= bsp;           &nb= sp;           &nbs= p; =20 for (g =3D gr->gr_mem;; ++g) {
(gdb)=20 step
256          &n= bsp;           &nb= sp;           &nbs= p;         =20 if (!*g) {
(gdb)=20 step
262          &n= bsp;           &nb= sp;           &nbs= p;         =20 if (strcmp(username, *g) =3D=3D 0) {
(gdb)=20 step
255          &n= bsp;           &nb= sp;           &nbs= p; =20 for (g =3D gr->gr_mem;; ++g) {
(gdb)=20 step
256          &n= bsp;           &nb= sp;           &nbs= p;         =20 if (!*g) {
(gdb)=20 step
262          &n= bsp;           &nb= sp;           &nbs= p;         =20 if (strcmp(username, *g) =3D=3D 0) {
(gdb)=20 step
271          &n= bsp;         =20 if (*pwd->pw_passwd) {
(gdb)=20 step
278          &n= bsp;           &nb= sp;     =20 p =3D skey_getpass("Password:", pwd, 1);
(gdb)=20 step
Password:
279        &= nbsp;           &n= bsp;       =20 if (!(!strcmp(pwd->pw_passwd, skey_crypt(p, pwd->pw_passwd, pwd,=20 1))
(gdb)=20 step
292          &n= bsp;           &nb= sp;           &nbs= p;         =20 fprintf(stderr, "Sorry\n");
(gdb)
 
 
Anyone have any ideas?  I am in = the wheel=20 group, but I shouldn't have to be for traceroute and I have this problem = for all=20 users, including new ones that I create.
------=_NextPart_000_0145_01BF3C14.4CCD5200-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 13:54:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 5013214BC6 for ; Wed, 1 Dec 1999 13:54:26 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id PAA23912; Wed, 1 Dec 1999 15:53:55 -0600 (CST) Date: Wed, 1 Dec 1999 15:53:55 -0600 From: "Matthew D. Fuller" To: James Howard Cc: Bakul Shah , Steve Kargl , FreeBSD Current Subject: Re: removing enigma(1) Message-ID: <19991201155354.M22444@futuresouth.com> References: <19991201152633.K22444@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-OS: FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 01, 1999 at 04:36:12PM -0500, a little birdie told me that James Howard remarked > On Wed, 1 Dec 1999, Matthew D. Fuller wrote: > > > > [15:25:53] mortis:~ > > (ttyp9):{838}% ll -i `which crypt` `which enigma` > > 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/crypt* > > 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/enigma* > > Why is that a hard link instead of a symbolic link? Probably the same reason most (all?) things in the base system that run linked are hard links: (ll -i | sort is instructive) /sbin: 14445 -r-xr-xr-x 2 root wheel 150840 Oct 29 13:46 mount_mfs* 14445 -r-xr-xr-x 2 root wheel 150840 Oct 29 13:46 newfs* (That's pretty cool, if mildly weird) 14442 -r-xr-xr-x 5 root wheel 59756 Oct 29 13:46 mount_devfs* 14442 -r-xr-xr-x 5 root wheel 59756 Oct 29 13:46 mount_fdesc* 14442 -r-xr-xr-x 5 root wheel 59756 Oct 29 13:46 mount_kernfs* 14442 -r-xr-xr-x 5 root wheel 59756 Oct 29 13:46 mount_procfs* 14442 -r-xr-xr-x 5 root wheel 59756 Oct 29 13:46 mount_std* /bin: 124 -r-xr-xr-x 2 root wheel 48592 Oct 29 13:43 [* 124 -r-xr-xr-x 2 root wheel 48592 Oct 29 13:43 test* Sendmail the same way (I can't show it since I have Postfix installed, but...) (Ah, here's another system:) 430769 -r-sr-xr-x 5 root 7 290816 Nov 18 1998 /usr/bin/mailq* 430769 -r-sr-xr-x 5 root 7 290816 Nov 18 1998 /usr/bin/newaliases* 430769 -r-sr-xr-x 5 root 7 290816 Nov 18 1998 /usr/sbin/sendmail* etc. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Unix Systems Administrator | fullermd@futuresouth.com Specializing in FreeBSD | http://www.over-yonder.net/ FutureSouth Communications | ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 14: 7:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from minubian.houabg.com (minubian.houabg.com [206.109.247.11]) by hub.freebsd.org (Postfix) with ESMTP id E816014F94 for ; Wed, 1 Dec 1999 14:07:28 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from houcbs2.houabg.com (HOUABG.COM [206.109.247.20]) by minubian.houabg.com (8.8.8/8.8.8) with ESMTP id QAA29076 for ; Wed, 1 Dec 1999 16:42:00 -0600 (CST) (envelope-from dchapman@houabg.com) Received: from 216-118-21-147.pdq.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id SG164AKY; Wed, 1 Dec 1999 16:08:25 -0600 Message-ID: <015a01bf3c48$87387800$931576d8@inethouston.net> From: "David W. Chapman Jr." To: References: <014801bf3c46$97e4e140$931576d8@inethouston.net> Subject: Nevermind: su and traceroute Date: Wed, 1 Dec 1999 16:07:58 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0157_01BF3C16.3C31B1A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0157_01BF3C16.3C31B1A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Nevermind, I had nosuid in fstab, totally forgot about it. ----- Original Message -----=20 From: David W. Chapman Jr.=20 To: current@freebsd.org=20 Sent: Wednesday, December 01, 1999 3:54 PM Subject: su and traceroute I just cvsuped to -current right after bind-8.2.2 was merged into the = source tree. I noticed two problems. Su won't work and traceroute = gives me the following traceroute: icmp socket: Operation not permitted here are its permissions -r-sr-xr-x 1 root wheel 12076 Dec 1 14:15 /usr/sbin/traceroute su just says Sorry and it has the same permissions, I ran gdb on it = and here's a screen shot 253 if (pwd->pw_uid =3D=3D 0 && (gr =3D = getgrgid((gid_t)0)) && (gdb) step 255 for (g =3D gr->gr_mem;; ++g) { (gdb) step 256 if (!*g) { (gdb) step 262 if (strcmp(username, = *g) =3D=3D 0) { (gdb) step 255 for (g =3D gr->gr_mem;; ++g) { (gdb) step 256 if (!*g) { (gdb) step 262 if (strcmp(username, = *g) =3D=3D 0) { (gdb) step 271 if (*pwd->pw_passwd) { (gdb) step 278 p =3D skey_getpass("Password:", pwd, = 1); (gdb) step Password: 279 if (!(!strcmp(pwd->pw_passwd, = skey_crypt(p, pwd->pw_passwd, pwd, 1)) (gdb) step 292 fprintf(stderr, = "Sorry\n"); (gdb) Anyone have any ideas? I am in the wheel group, but I shouldn't have = to be for traceroute and I have this problem for all users, including = new ones that I create. ------=_NextPart_000_0157_01BF3C16.3C31B1A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Nevermind, I had nosuid in fstab, = totally forgot=20 about it.
----- Original Message -----
From:=20 David W.=20 Chapman Jr.
Sent: Wednesday, December 01, = 1999 3:54=20 PM
Subject: su and = traceroute

I just cvsuped to -current right after = bind-8.2.2=20 was merged into the source tree.  I noticed two problems.  = Su won't=20 work and traceroute gives me the following

 

traceroute: icmp socket: Operation not=20 permitted

 

here are its permissions

 

-r-sr-xr-x  1 root  = wheel  12076=20 Dec  1 14:15 /usr/sbin/traceroute

 

su just says Sorry and it has the same = permissions,=20 I ran gdb on it and here's a screen shot

 

253          &= nbsp;           &n= bsp;     =20 if (pwd->pw_uid =3D=3D 0 && (gr =3D getgrgid((gid_t)0))=20 &&
(gdb)=20 = step
255          &n= bsp;           &nb= sp;           &nbs= p; =20 for (g =3D gr->gr_mem;; ++g) {
(gdb)=20 = step
256          &n= bsp;           &nb= sp;           &nbs= p;         =20 if (!*g) {
(gdb)=20 = step
262          &n= bsp;           &nb= sp;           &nbs= p;         =20 if (strcmp(username, *g) =3D=3D 0) {
(gdb)=20 = step
255          &n= bsp;           &nb= sp;           &nbs= p; =20 for (g =3D gr->gr_mem;; ++g) {
(gdb)=20 = step
256          &n= bsp;           &nb= sp;           &nbs= p;         =20 if (!*g) {
(gdb)=20 = step
262          &n= bsp;           &nb= sp;           &nbs= p;         =20 if (strcmp(username, *g) =3D=3D 0) {
(gdb)=20 = step
271          &n= bsp;         =20 if (*pwd->pw_passwd) {
(gdb)=20 = step
278          &n= bsp;           &nb= sp;     =20 p =3D skey_getpass("Password:", pwd, 1);
(gdb)=20 = step
Password:
279        &= nbsp;           &n= bsp;       =20 if (!(!strcmp(pwd->pw_passwd, skey_crypt(p, pwd->pw_passwd, pwd, = 1))
(gdb)=20 = step
292          &n= bsp;           &nb= sp;           &nbs= p;         =20 fprintf(stderr, "Sorry\n");
(gdb)

 

 

Anyone have any ideas?  I am in = the wheel=20 group, but I shouldn't have to be for traceroute and I have this = problem for=20 all users, including new ones that I=20 create.

------=_NextPart_000_0157_01BF3C16.3C31B1A0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 14:25:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id AAB23150E7; Wed, 1 Dec 1999 14:23:43 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id WAA22586; Wed, 1 Dec 1999 22:14:40 GMT (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id RAA95853; Wed, 1 Dec 1999 17:55:16 GMT (envelope-from nik@catkin.nothing-going-on.org) Date: Wed, 1 Dec 1999 17:55:15 +0000 From: Nik Clayton To: "F. Heinrichmeyer" Cc: "freebsd-current@FreeBSD.ORG" , doc@freebsd.org Subject: Re: gcc-2.95.2, jade and freebsd-sgml-documentation Message-ID: <19991201175515.A95818@kilt.nothing-going-on.org> References: <38415AA1.2586CEA9@fernuni-hagen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <38415AA1.2586CEA9@fernuni-hagen.de>; from F. Heinrichmeyer on Sun, Nov 28, 1999 at 05:38:57PM +0100 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ I've cc'd FreeBSD-doc on this, in case there's someone there who's solved the problem you're having ] On Sun, Nov 28, 1999 at 05:38:57PM +0100, F. Heinrichmeyer wrote: > i tried to make me a new handbook, so i needed jade. > > But the newest C++ fashion (g++ under current) has changed to fast for > this very old 1998 heavily template based source code distribution ;-). > I had a lot of problems with const and not const .. and gave up. It is > far to much to post here ... > > A lot of error messages are clearly written 1 to 1 from the ansi > standard (yes we finally spent the 18 dollars ...), but something > especially about a class "Location" looks really strange. > > What tool is recommendet to rebuild the documentation? Unfortunately, jade is the tool of choice. I don't run -current, so haven't had a chance to test out jade with the new GCC. However, could you take a look at OpenJade? It's not in the ports tree yet (should you want to submit a port I'll get it committed), and is a continuation of the Jade codebase after the original author (James Clark) moved on to other things. There's an OpenJade home page at http://www.netfolder.com/DSSSL/ and information about the OpenJade CVS repository at http://jade-cvs.avionitek.com/ I hope that helps. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 14:38: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from pm13sm.wcom.com (pm13sm.wcom.com [199.249.20.149]) by hub.freebsd.org (Postfix) with ESMTP id 33BA614E12; Wed, 1 Dec 1999 14:37:54 -0800 (PST) (envelope-from tonymb@mciworld.com) Received: from CONVERSION-DAEMON by mail-relay.mciworld.com (PMDF V5.2-32 #38415) id <0FM3008012N7KQ@mail-relay.mciworld.com>; Wed, 1 Dec 1999 22:33:07 +0000 (GMT) Received: from rames57 ([63.22.182.232]) by mail-relay.mciworld.com (PMDF V5.2-32 #38415) with SMTP id <0FM3009ZW2N0BK@mail-relay.mciworld.com>; Wed, 01 Dec 1999 22:33:07 +0000 (GMT) Date: Wed, 01 Dec 1999 16:40:33 -0600 From: tonymb Subject: I WOULD LIKE TO JOIN THE MAILING LIST To: majordomo@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Message-id: <000c01bf3c4d$182b4320$e8b6163f@rames57> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Mailer: Microsoft Outlook Express 5.00.2919.6600 Content-type: MULTIPART/ALTERNATIVE; BOUNDARY="Boundary_(ID_Glz9veQMmIITNJK6MSTnUA)" X-Priority: 3 X-MSMail-priority: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --Boundary_(ID_Glz9veQMmIITNJK6MSTnUA) Content-type: text/plain; charset="iso-8859-1" Content-transfer-encoding: quoted-printable HELLO MY NAME IS TONY. I HAVE BEEN DOING RESEARCH ON FREEBSD. I'M = PLANNING TO SETUP A SYSTEM WITH THIS OS. I WOULD THANK YOU FOR PLACING = ME ON YOUR MAILING LIST TO BENEFIT FROM THE EXPERIENCE OTHERS AND = EXPERTISE TO MAKE MY TRANSITION SMOOTH.PLEASE USE THIS E-MAIL ADDRESS = tonymb@mciworld.com. THANK YOU FOR YOUR COOPERATION. --Boundary_(ID_Glz9veQMmIITNJK6MSTnUA) Content-type: text/html; charset="iso-8859-1" Content-transfer-encoding: quoted-printable
HELLO MY NAME IS  = TONY. I=20 HAVE BEEN DOING RESEARCH ON FREEBSD. I'M PLANNING TO SETUP A SYSTEM WITH = THIS=20 OS. I WOULD THANK YOU FOR PLACING ME ON YOUR MAILING LIST TO BENEFIT = FROM THE=20 EXPERIENCE OTHERS  AND EXPERTISE TO MAKE MY TRANSITION = SMOOTH.PLEASE USE=20 THIS E-MAIL ADDRESS tonymb@mciworld.com.  THANK = YOU FOR=20 YOUR COOPERATION.
--Boundary_(ID_Glz9veQMmIITNJK6MSTnUA)-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 14:48:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta3.rcsntx.swbell.net (mta3.rcsntx.swbell.net [151.164.30.27]) by hub.freebsd.org (Postfix) with ESMTP id 08FD0150AF; Wed, 1 Dec 1999 14:48:52 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta3.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FM3005JZ32910@mta3.rcsntx.swbell.net>; Wed, 1 Dec 1999 16:42:10 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id QAA13262; Wed, 01 Dec 1999 16:43:58 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Wed, 01 Dec 1999 16:43:57 -0600 From: Chris Costello Subject: Re: I WOULD LIKE TO JOIN THE MAILING LIST In-reply-to: <000c01bf3c4d$182b4320$e8b6163f@rames57> To: tonymb Cc: majordomo@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991201164357.V2233@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <000c01bf3c4d$182b4320$e8b6163f@rames57> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 01, 1999, tonymb wrote: > HELLO MY NAME IS TONY. I HAVE BEEN DOING RESEARCH ON FREEBSD. I'M PLANNING TO SETUP A SYSTEM WITH THIS OS. I WOULD THANK YOU FOR PLACING ME ON YOUR MAILING LIST TO BENEFIT FROM THE EXPERIENCE OTHERS AND EXPERTISE TO MAKE MY TRANSITION SMOOTH.PLEASE USE THIS E-MAIL ADDRESS tonymb@mciworld.com. THANK YOU FOR YOUR COOPERATION. Did you even BOTHER to read the FAQ or ANYTHING at http://www.FreeBSD.org? -- |Chris Costello |Maintenance-free: When it breaks, it can't be fixed... `------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 14:57:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 9641A15057; Wed, 1 Dec 1999 14:57:16 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991201175617.22029@mojave.sitaranetworks.com> Date: Wed, 1 Dec 1999 17:56:17 -0500 From: Greg Lehey To: tonymb , majordomo@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: I WOULD LIKE TO JOIN THE MAILING LIST Reply-To: Greg Lehey References: <000c01bf3c4d$182b4320$e8b6163f@rames57> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <000c01bf3c4d$182b4320$e8b6163f@rames57>; from tonymb on Wed, Dec 01, 1999 at 04:40:33PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 1 December 1999 at 16:40:33 -0600, tonymb wrote: > HELLO MY NAME IS TONY. I HAVE BEEN DOING RESEARCH ON FREEBSD. I'M PLANNING TO SETUP A SYSTEM WITH THIS OS. I WOULD THANK YOU FOR PLACING ME ON YOUR MAILING LIST TO BENEFIT FROM THE EXPERIENCE OTHERS AND EXPERTISE TO MAKE MY TRANSITION SMOOTH.PLEASE USE THIS E-MAIL ADDRESS tonymb@mciworld.com. THANK YOU FOR YOUR COOPERATION. OK. One thing at a time. 1: Look at the left of your keyboard. You'll find a key marked "Caps Lock". Press it. > hello my name is tony. i have been doing research on freebsd. i'm planning to setup a system with this os. i would thank you for placing me on your mailing list to benefit from the experience others and expertise to make my transition smooth.please use this e-mail address tonymb@mciworld.com. thank you for your cooperation. Ah, that's a little better, isn't it? 2: At the other end you'll find another larger key marked "Enter". Use it approximately every 70 characters, between words: > hello my name is tony. i have been doing research on freebsd. i'm > planning to setup a system with this os. i would thank you for > placing me on your mailing list to benefit from the experience > others and expertise to make my transition smooth.please use this > e-mail address tonymb@mciworld.com. thank you for your cooperation. Ah. Now it's readable. You should, of course, use capital letters here and there. 3: Use a web browser and access http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL. It'll tell you which mailing list is for what. I'd suggest -newbies and/or -questions for the start. A bit further down the page you will find instructions for how to subscribe to the mailing list of your choice. While you have the browser running, check out http://www.lemis.com/email.html, which will tell you how to write more legible mail, and http://www.lemis.com/questions.html, which will give you other tips about how to send mail to the FreeBSD mailing lists. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 15: 4:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 2A6B415057; Wed, 1 Dec 1999 15:04:39 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-162.skylink.it [194.185.55.162]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id BAA14307; Thu, 2 Dec 1999 01:07:18 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id JAA00695; Wed, 1 Dec 1999 09:34:50 +0100 (CET) (envelope-from hibma@skylink.it) Date: Wed, 1 Dec 1999 09:34:50 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Warner Losh Cc: Christopher Masto , Mike Smith , FreeBSD CURRENT Mailing List Subject: Re: PCCARD eject freeze (was Re: your mail) In-Reply-To: <199911302304.QAA05780@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Hey, we're getting somewhere. It works, in that it stops the panic. > : I get the "ed0: unloaded" message, and the machine doesn't panic, but > : there are still some problems. It seems that device_delete_child > : is failing (I forgot to print the return code, but it is not zero), > : and reinserting the card results in "ed0 already exists, using > : next available unit number", and then the dreaded "driver allocation > : failed" (presumably the resources have not been freed). > : > : Putting in a different kind of card ends up with two children, so > : it seems that the only part of the delete actually happens. > > Hmmm... That's something... How do you know that the delete_child is > failing? An if printing that it failed or conjecture based on the > insertion results? That is a question of what the drivers are supposed to assume after DEVICE_DETACH(self) has been called on them. In USB land it means, bugger off, please, and don't touch that device no more. Even if the driver is still there (unable to detach for some reason, like a CAM SIM that cannot deallocate the bus), the device is gone anyway and the rest of the children should be zapped as well. So printing a message and continuing to delete the rest is your best bet IMHO. The driver itself should do the right thing. Nick -- hibma@skylink.it n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 15: 5: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from [132.197.97.45] (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 3B8C515121 for ; Wed, 1 Dec 1999 15:04:58 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by [132.197.97.45] (8.9.3/8.9.3) id SAA00655 for freebsd-current@freebsd.org; Wed, 1 Dec 1999 18:04:48 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 01 Dec 1999 18:04:43 -0500 (EST) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: freebsd-current@freebsd.org Subject: rpc.umntall does not work with AIX Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am getting the folowing error messages for each mounted directory every time rpc.umntall is being run: Bad MNT RPC: RPC: Remote system error The following is fragment of my /etc/fstab file: # Device Mountpoint FStype Options Dump Pass# kan:/home/ak03 /usr/home/ak03 nfs rw 0 0 tips6:/usr/local/aix/javapkg /usr/local/javapkg nfs rw 0 0 kan there is running AIX 4.2 and tips6 box is HP/UX I am perfectly willing to do any necessary debugging if someone with sufficient NFS knowledge will point me in right direction. ---------------------------------- E-Mail: Alexander N. Kabaev Date: 01-Dec-99 Time: 17:53:48 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 15:16: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 1FFEB14E1C for ; Wed, 1 Dec 1999 15:16:05 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id JAA78394; Thu, 2 Dec 1999 09:42:37 +1030 (CST) (envelope-from newton) Date: Thu, 2 Dec 1999 09:42:37 +1030 From: Mark Newton To: James Howard Cc: "Matthew D. Fuller" , Bakul Shah , Steve Kargl , FreeBSD Current Subject: Re: removing enigma(1) Message-ID: <19991202094237.A78375@internode.com.au> References: <19991201152633.K22444@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 01, 1999 at 04:36:12PM -0500, James Howard wrote: > > Renaming? > > [15:25:53] mortis:~ > > (ttyp9):{838}% ll -i `which crypt` `which enigma` > > 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/crypt* > > 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/enigma* > > Why is that a hard link instead of a symbolic link? Hard links are faster, require no disk space, and don't consume any extra inodes. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 15:18:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from umd5.umd.edu (umd5.umd.edu [128.8.10.5]) by hub.freebsd.org (Postfix) with ESMTP id A1C28150E7 for ; Wed, 1 Dec 1999 15:18:22 -0800 (PST) (envelope-from howardjp@wam.umd.edu) Received: from frost.umd.edu (frost.umd.edu [128.8.10.186]) by umd5.umd.edu (8.9.1/8.9.1) with ESMTP id SAA07896; Wed, 1 Dec 1999 18:17:50 -0500 (EST) Received: from localhost (howardjp@localhost) by frost.umd.edu (8.9.1/8.9.1) with SMTP id SAA04872; Wed, 1 Dec 1999 18:17:50 -0500 (EST) X-Authentication-Warning: frost.umd.edu: howardjp owned process doing -bs Date: Wed, 1 Dec 1999 18:17:49 -0500 (EST) From: James Howard X-Sender: howardjp@frost.umd.edu To: "Matthew D. Fuller" Cc: Bakul Shah , Steve Kargl , FreeBSD Current Subject: Re: removing enigma(1) In-Reply-To: <19991201155354.M22444@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 1 Dec 1999, Matthew D. Fuller wrote: > On Wed, Dec 01, 1999 at 04:36:12PM -0500, a little birdie told me > that James Howard remarked > > On Wed, 1 Dec 1999, Matthew D. Fuller wrote: > > > > > > [15:25:53] mortis:~ > > > (ttyp9):{838}% ll -i `which crypt` `which enigma` > > > 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/crypt* > > > 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/enigma* > > > > Why is that a hard link instead of a symbolic link? > > Probably the same reason most (all?) things in the base system that run > linked are hard links: > (ll -i | sort is instructive) > > /sbin: > 14445 -r-xr-xr-x 2 root wheel 150840 Oct 29 13:46 mount_mfs* > 14445 -r-xr-xr-x 2 root wheel 150840 Oct 29 13:46 newfs* > (That's pretty cool, if mildly weird) > 14442 -r-xr-xr-x 5 root wheel 59756 Oct 29 13:46 mount_devfs* > 14442 -r-xr-xr-x 5 root wheel 59756 Oct 29 13:46 mount_fdesc* > 14442 -r-xr-xr-x 5 root wheel 59756 Oct 29 13:46 mount_kernfs* > 14442 -r-xr-xr-x 5 root wheel 59756 Oct 29 13:46 mount_procfs* > 14442 -r-xr-xr-x 5 root wheel 59756 Oct 29 13:46 mount_std* > > /bin: > 124 -r-xr-xr-x 2 root wheel 48592 Oct 29 13:43 [* > 124 -r-xr-xr-x 2 root wheel 48592 Oct 29 13:43 test* > > Sendmail the same way (I can't show it since I have Postfix installed, > but...) (Ah, here's another system:) > 430769 -r-sr-xr-x 5 root 7 290816 Nov 18 1998 /usr/bin/mailq* > 430769 -r-sr-xr-x 5 root 7 290816 Nov 18 1998 /usr/bin/newaliases* > 430769 -r-sr-xr-x 5 root 7 290816 Nov 18 1998 /usr/sbin/sendmail* Let me rephrase the question. Why (in general) are hard links used instead of symbolic links? Symlinks are used on the man pages, why not on the binaries? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 15:28:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from lorien.odc.net (lorien.odc.net [207.137.42.14]) by hub.freebsd.org (Postfix) with ESMTP id E48B6150F0 for ; Wed, 1 Dec 1999 15:28:37 -0800 (PST) (envelope-from nwestfal@lorien.odc.net) Received: from localhost (nwestfal@localhost) by lorien.odc.net (8.9.3/8.9.3) with ESMTP id PAA01132 for ; Wed, 1 Dec 1999 15:28:37 -0800 Date: Wed, 1 Dec 1999 15:28:37 -0800 (PST) From: Neal Westfall To: current@freebsd.org Subject: make release failure Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone been able to do a make release recently? It seems to break when trying to build jade from the ports, which I think is due to the new compiler import. I saw that there are recent snapshots on current.freebsd.org, which is confusing because I can't get jade to build: ../include/StringOf.h:38: `String::operator [](unsigned int)' has already been declared in `String' ../include/StringOf.h:40: `String::begin()' has already been declared in `String' *** Error code 1 Stop in /usr/ports/textproc/jade/work/jade-1.2.1/lib. *** Error code 1 Stop in /usr/ports/textproc/jade/work/jade-1.2.1. *** Error code 1 Stop in /usr/ports/textproc/jade/work/jade-1.2.1. *** Error code 1 Stop in /usr/ports/textproc/jade. *** Error code 1 Stop in /usr/ports/textproc/jade. *** Error code 1 Stop in /usr/ports/textproc/jade. -- Neal Westfall | mailto:nwestfal@odc.net | http://www.odc.net/~nwestfal "What is today a matter of academic speculation begins tomorrow to move armies and pull down empires. In that second stage, it has gone too far to be combatted; the time to stop it was when it was still a matter of impassionate debate." -- J. Gresham Machen, "Christianity and Culture" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 20:31:42 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id C223D14C1C; Wed, 1 Dec 1999 20:31:41 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B20971CD804; Wed, 1 Dec 1999 20:31:41 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 1 Dec 1999 20:31:41 -0800 (PST) From: Kris Kennaway To: Brian Fundakowski Feldman Cc: David O'Brien , John Hay , imp@freebsd.org, current@FreeBSD.org Subject: Re: Overflow in banner(1) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 30 Nov 1999, Brian Fundakowski Feldman wrote: > kind of thing I'd rather have. I like the precomputed one (add all > argv[] strlen's and malloc that) better, anyway. ..and as soon as warner reviews my revised patch, it will be committed :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 21:50:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.qx.net (darkstar.qx.net [208.235.88.101]) by hub.freebsd.org (Postfix) with ESMTP id 1DEAB14D0C for ; Wed, 1 Dec 1999 21:50:36 -0800 (PST) (envelope-from gchil0@pop.uky.edu) Received: from mail.qx.net (mail.qx.net [208.235.88.10]) by darkstar.qx.net (8.8.7/8.8.7) with ESMTP id AAA13584 for ; Thu, 2 Dec 1999 00:50:19 -0500 Received: from k7 ([208.200.111.92]) by mail.qx.net (Netscape Messaging Server 3.6) with ESMTP id AAA7030 for ; Thu, 2 Dec 1999 00:53:03 -0500 Message-Id: <4.2.0.58.19991202003302.00953770@pop.uky.edu> X-Sender: gchil0@pop.uky.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 02 Dec 1999 00:49:24 -0500 To: freebsd-current@freebsd.org From: Greg Childers Subject: Problems with ATA Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've updated to the latest -current, and things have gone awry. At boot, the console freezes at the end of the dmesg. The startup process continues, tho, and I can telnet into the box. Then madness ensues. The contents of some files I create disappears, top freezes after listing the processes, never showing cpu usage, &c. Switching to the wd drivers fixes everything. Below is the dmesg from the kernel with ATA. The previous working kernel was compiled from Oct. 5 sources. Just ask for any other info you need. Thanks, Greg Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Wed Dec 1 23:24:15 EST 1999 root@p66.childers.net:/usr/src/sys/compile/MYGENERIC Calibrating clock(s) ... TSC clock: 66644219 Hz, i8254 clock: 1193175 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium/P5 (66.64-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x517 Stepping = 7 Features=0x1bf real memory = 33554432 (32768K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x0023d000 - 0x01ffdfff, 31199232 bytes (7617 pages) avail memory = 30502912 (29788K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f0120 bios32: Entry = 0xf146c (c00f146c) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x1450 pnpbios: Found PnP BIOS data at 0xc00f0130 pnpbios: Entry = f0000:1247 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Intel Pentium detected, installing workaround for F00F bug Creating DISK md0 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x00000000 (0x80000000) pci_open(1b): mode1res=0x00000000 (0xff000001) pci_open(2): mode 2 enable port (0x0cf8) is 0x00 pci_open(2a): mode2res=0x0e (0x0e) pci_open(2a): now trying mechanism 2 pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=04a38086) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 300751879 bytes/sec bzero() bandwidth = 151125887 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x00000000 (0x80000000) pci_open(1b): mode1res=0x00000000 (0xff000001) pci_open(2): mode 2 enable port (0x0cf8) is 0x00 pci_open(2a): mode2res=0x0e (0x0e) pci_open(2a): now trying mechanism 2 pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=04a38086) pcib0: on motherboard found-> vendor=0x8086, dev=0x04a3, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1042, dev=0x1000, revid=0x01 class=01-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base 000001f0, size 3 map[14]: type 1, range 32, base 000003f4, size 2 found-> vendor=0x8086, dev=0x0484, revid=0x00 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 pci0: on pcib0 CPU: Pentium, 66MHz, CPU->Memory posting ON Warning: Cache parity disabled! Warning: DRAM parity mask! Cache: 256KB writeback, cache clocks=3-2-2-2/4-2-2-2 Cache flags: cache-all byte-control DRAM: page mode memory clocks=X-4-4-4 (70ns) CPU->PCI: posting ON, burst mode ON, PCI clocks=2-1-1-1 PCI->Memory: posting ON Refresh: RAS#Only BurstOf4 ata-pci0: at device 1.0 on pci0 ata-pci0: Busmastering DMA not supported ata0: iobase=0x01f0 altiobase=0x03f4 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=50 ata0: devices = 0x3 ata0 at 0x01f0 irq 0 on ata-pci0 isab0: at device 2.0 on pci0 Bus Modes: Bus Park, Resource Lock, Coprocessor errors enabled Keyboard controller: 60h,62h,64h,66h RTC: 70h-77h Port 92: enabled isa0: on isab0 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 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k vga0: vga: WARNING: video mode switching is not fully supported on this adapter VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 a1 bf 1f 00 4f 0d 0e 00 00 07 30 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 a1 bf 1f 00 4f 0d 0e 00 00 07 30 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0 kbd0 sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: not probed (disabled) sio2: not probed (disabled) sio3: irq maps: 0x41 0x49 0x41 0x41 sio3 at port 0x2e8-0x2ef irq 3 on isa0 sio3: type 16550A ppc: parallel port found at 0x378 ppc: chipset forced to generic ppc0: ECP SPP ECP+EPP SPP ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ed0 at port 0x280-0x29f iomem 0xd8000-0xd9fff irq 5 on isa0 ed0: address 02:60:8c:8e:84:d1, type 3c503 (16 bit) bpf: ed0 attached isa_probe_children: probing PnP devices BIOS Geometries: 0:020a1f3f 0..522=523 cylinders, 0..31=32 heads, 1..63=63 sectors 1:026b3f3f 0..619=620 cylinders, 0..63=64 heads, 1..63=63 sectors 0 accounted for Device configuration finished. device combination doesn't support shared irq0 intr_connect(irq0) failed, result=-1 bpf: sl0 attached bpf: ppp0 attached new masks: bio 40080041, tty 4003009a, net 400700ba bpf: lo0 attached ad0: piomode=3 dmamode=1 udmamode=-1 cblid=0 ad0: ATA-? disk at ata0 as master ad0: 515MB (1056384 sectors), 1048 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO Creating DISK ad0 Creating DISK wd0 ad1: piomode=3 dmamode=1 udmamode=-1 cblid=0 ad1: ATA-? disk at ata0 as slave ad1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, PIO Creating DISK ad1 Creating DISK wd1 Mounting root from ufs:wd0s1a wd0s1: type 0xa5, start 63, end = 1056383, size 1056321 : OK start_init: trying /sbin/init wd1s1: type 0xa5, start 63, end = 2503871, size 2503809 : OK Linux-ELF exec handler installed splash: image decoder found: blank_saver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 22:55:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from midway.uchicago.edu (midway.uchicago.edu [128.135.12.12]) by hub.freebsd.org (Postfix) with ESMTP id 38D5B14D39 for ; Wed, 1 Dec 1999 22:55:06 -0800 (PST) (envelope-from charon@freethought.org) Received: from harper.uchicago.edu (root@harper.uchicago.edu [128.135.12.7]) by midway.uchicago.edu (8.9.3/8.9.3) with ESMTP id AAA28518 for ; Thu, 2 Dec 1999 00:54:26 -0600 (CST) From: charon@freethought.org Received: from broad-208-049 (broad-208-049.rh.uchicago.edu [128.135.208.49]) by harper.uchicago.edu (8.9.3/8.9.3) with SMTP id AAA19443 for ; Thu, 2 Dec 1999 00:54:15 -0600 (CST) Message-Id: <3.0.5.32.19991202005411.00a39cb0@nsit-popmail.uchicago.edu> X-Sender: dbsypher@nsit-popmail.uchicago.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 02 Dec 1999 00:54:11 -0600 To: current@freebsd.org Subject: minor bug in ee? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently noticed that ^v (the scroll down a page command in ee) must be entered twice to scroll down once (i.e. if you hit ^v once it won't do anything, you must hit it again) on a 4.0-CURRENT system. As far as I can recall, this has been happening for as long as I've been tracking -CURRENT (~1 month), and still continues on the system I updated as of Nov. 30. 3-STABLE (as of Dec. 1) doesn't have this problem - it has a simple one-to-one ratio for ^v / scroll down. As far as I can recall, none of the other 3.x or 2.x releases had this problem either. I doubt this is very important - should I file a PR or anything? -Charon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 1 23: 1:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 443151511E; Wed, 1 Dec 1999 23:01:16 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.56]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAF165E; Thu, 2 Dec 1999 08:01:02 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id IAA12735; Thu, 2 Dec 1999 08:00:30 +0100 (CET) (envelope-from asmodai) Date: Thu, 2 Dec 1999 08:00:30 +0100 From: Jeroen Ruigrok/Asmodai To: Russell Cattelan Cc: Dag-Erling Smorgrav , current@freebsd.org, cg@freebsd.org Subject: Re: Soundblaster 128 PCI Message-ID: <19991202080030.F12457@daemon.ninth-circle.org> References: <38455C25.D4E917A6@thebarn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38455C25.D4E917A6@thebarn.com>; from cattelan@thebarn.com on Wed, Dec 01, 1999 at 11:34:29AM -0600 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991201 20:01], Russell Cattelan (cattelan@thebarn.com) wrote: >Dag-Erling Smorgrav wrote: >> I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't >> get to work with newpcm. >What mother board are you using? >There have been some reports of the new 1371's not working with >non intel chip sets. Asus boards are know to be a problem. >Apparently it is a timing bug in the sound card. The timing bug, is that a PCI bus clock/signal bug which the card has, or an internal timing problem? -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Learn e-mail netiquette: http://www.lemis.com/email.html We do not count a man's years, until he has nothing left to count... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 0:14:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 5C20D14D63; Thu, 2 Dec 1999 00:14:47 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id DAA21816; Thu, 2 Dec 1999 03:13:47 -0500 (EST) Message-ID: <19991202031346.B17644@netmonger.net> Date: Thu, 2 Dec 1999 03:13:46 -0500 From: Christopher Masto To: Warner Losh Cc: Nick Hibma , Mike Smith , FreeBSD CURRENT Mailing List Subject: Re: PCCARD eject freeze (was Re: your mail) References: <19991130165407.A467@netmonger.net> <199911302159.OAA05508@harmony.village.org> <19991130173920.A22943@netmonger.net> <199911302304.QAA05780@harmony.village.org> <19991130181313.B24151@netmonger.net> <199911302319.QAA05945@harmony.village.org> <19991130182738.A25453@netmonger.net> <199911302352.QAA06230@harmony.village.org> <19991130213532.A2764@netmonger.net> <199912010755.AAA00462@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199912010755.AAA00462@harmony.village.org>; from Warner Losh on Wed, Dec 01, 1999 at 12:55:24AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 01, 1999 at 12:55:24AM -0700, Warner Losh wrote: > In message <19991130213532.A2764@netmonger.net> Christopher Masto writes: > : Well, here's all I've got. It's basically just a sloppy version of > : what you suggested. > > I've cleaned this up, worked it around, and managed to insert and > eject my ep card 5 times in a row on my desktop kludge environment. > It even appeared to be working. Don't know if this will work on a > real laptop, but it is better than nothing. I specifically didn't set > the suspend/resume code, and it is a different code path. I suspect > to still see some hangs, but in the 1-2% range not the 100+% range on > suspend due to the racing nature of things. Hmm.. something's not right. I can eject my ed card (though I get the "pccard: card removed, slot 0" message twice. But it doesn't attach if I insert it again. "driver allocation failed for Linksys(Combo PCMCIA EthernetCard (EC): Device not configured". sio is a bit worse, it doesn't work the first time (same error: device not configured). Dunno what happened. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 0:17:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 8DDFC14E62 for ; Thu, 2 Dec 1999 00:17:02 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id AAA51220 for ; Thu, 2 Dec 1999 00:16:40 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id AAA84343 for current@freebsd.org; Thu, 2 Dec 1999 00:16:40 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <199912020816.AAA84343@realtime.exit.com> Subject: Well, the 3Com 574BT is still broken. To: current@freebsd.org Date: Thu, 2 Dec 1999 00:16:39 -0800 (PST) Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM944122599-84284-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM944122599-84284-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit And there appears to be some more brokenness. I've attached my latest (verbose) dmesg output. USB support is weird, and (not listed in dmesg) pccardd is failing to attach my Xircom modem card (which had been working), claiming "device not configured." Suggestions? I could Really Use an ethernet connection on this laptop; right now I have the cardbus card (3Com 575CT) and the pcmcia card (the 574BT) sitting here, useless. -- Frank Mayhar frank@exit.com --ELM944122599-84284-0_ Content-Type: text/plain Content-Disposition: attachment; filename=dmesg.txt Content-Description: dmesg.txt Content-Transfer-Encoding: 7bit 0000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base e0000000, size 26 found-> vendor=0x8086, dev=0x7191, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x104c, dev=0xac17, revid=0x02 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=255 found-> vendor=0x104c, dev=0xac17, revid=0x02 class=06-07-00, hdrtype=0x02, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=255 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000fcd0, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=11 map[20]: type 1, range 32, base 0000fce0, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 00002180, size 4 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x10c8, dev=0x0005, revid=0x20 class=03-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=255 map[10]: type 1, range 32, base fd000000, size 24 map[14]: type 1, range 32, base fe800000, size 22 map[18]: type 1, range 32, base fec00000, size 20 found-> vendor=0x10c8, dev=0x8005, revid=0x20 class=04-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=11 map[10]: type 1, range 32, base fe000000, size 22 map[14]: type 1, range 32, base fe700000, size 20 pci1: on pcib1 vga-pci0: at device 0.0 on pci1 pci1: unknown card (vendor=0x10c8, dev=0x8005) at 0.1 irq 11 chip1: at device 4.0 on pci0 chip2: at device 4.1 on pci0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=03 status0=50 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0x4 ata1 at 0x0170 irq 15 on ata-pci0 uhci0: irq 11 at device 7.2 on pci0 uhci0: USB version 1.0, chip rev. 1 usb0: on uhci0 usb0: USB revision unknown, not supported uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered intpm0: at device 7.3 on pci0 intpm0: I/O mapped 2180 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 8000 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 isa0: if_ep: unknown ID 0xffffffff isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: status 10 00 64 psm: data 08 00 00 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: APM hooks installed. psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <4 virtual consoles, flags=0x200> sc0: fb0 kbd0 pcic: polling, can't alloc 0 pcic: polling, can't alloc 0 pcic0: on isa0 pccard0: on pcic0 pccard1: on pcic0 sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: not probed (disabled) ppc: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port isa_probe_children: probing PnP devices BIOS Geometries: 0:0273ef3f 0..627=628 cylinders, 0..239=240 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: lo0 attached ata0: master: success setting up UDMA2 mode on PIIX4 chip ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 ad0: ATA-4 disk at ata0 as master ad0: 4645MB (9514260 sectors), 10068 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1: master: success setting up WDMA2 mode on PIIX4 chip acd0: CDROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, DMA acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-RW 120mm data disc loaded, unlocked Mounting root from ufs:/dev/wd0s2a wd0s1: type 0x1b, start 63, end = 5004719, size 5004657 : OK wd0s2: type 0xa5, start 5004720, end = 9510479, size 4505760 : OK pccard: card inserted, slot 0 pccard: card inserted, slot 1 start_init: trying /sbin/init Linux-ELF exec handler installed devclass_alloc_unit: sio1 already exists, using next available unit number ep0: Pass 1 of 2 detection failed (nonfatal) ep0: <3Com 3C574B, Megahertz 3CCFE574BT or Fast Etherlink 3C574-TX> at port 0x240-0x25f irq 10 slot 1 on pccard0 ep0: Ethernet address 4b:57:4b:57:4b:57 bpf: ep0 attached --ELM944122599-84284-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 0:58:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id A073414C1C for ; Thu, 2 Dec 1999 00:58:40 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id DAA09807; Thu, 2 Dec 1999 03:58:25 -0500 (EST) Date: Thu, 2 Dec 1999 03:58:25 -0500 (EST) From: "Matthew N. Dodd" To: Frank Mayhar Cc: current@FreeBSD.ORG Subject: Re: Well, the 3Com 574BT is still broken. In-Reply-To: <199912020816.AAA84343@realtime.exit.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 2 Dec 1999, Frank Mayhar wrote: > Suggestions? I could Really Use an ethernet connection on this > laptop; right now I have the cardbus card (3Com 575CT) and the pcmcia > card (the 574BT) sitting here, useless. Looking at the NetBSD driver it appears that the MAC address for the 574 is stored in the CIS. It appears that the 574 has a different EEPROM layout as well, which is sort of handled by sc->epb.cmd_off but not in a manner I'm happy with. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 1:10:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from pa.scotland.net (pa2.scotland.net [194.247.65.132]) by hub.freebsd.org (Postfix) with ESMTP id 363E815003 for ; Thu, 2 Dec 1999 01:10:24 -0800 (PST) (envelope-from freebsd@timog.prestel.co.uk) Received: from [148.176.237.202] (helo=timog.prestel.co.uk) by pa.scotland.net with esmtp (Exim 2.12 #4) id 11tSEC-00075N-00 for current@freebsd.org; Thu, 2 Dec 1999 09:08:41 +0000 Received: (qmail 85727 invoked from network); 2 Dec 1999 06:45:40 -0000 Received: from unknown (HELO timog.prestel.co.uk) (192.168.0.2) by tabby.timog.prestel.co.uk with SMTP; 2 Dec 1999 06:45:40 -0000 Received: (qmail 293 invoked by uid 1002); 2 Dec 1999 06:46:53 -0000 Date: Thu, 2 Dec 1999 06:46:53 +0000 From: Timo Geusch To: Seigo Tanimura Cc: current@freebsd.org Subject: Re: Please check missing logical IDs for SB Message-ID: <19991202064653.A251@ginger.timog.prestel.co.uk> References: <14404.30562.4717.91839F@rina.r.dl.itc.u-tokyo.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14404.30562.4717.91839F@rina.r.dl.itc.u-tokyo.ac.jp>; from tanimura@r.dl.itc.u-tokyo.ac.jp on Wed, Dec 01, 1999 at 10:18:26AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 01, 1999 at 10:18:26AM +0900, Seigo Tanimura wrote: > If you have an SB card not probed since the import of the bridge > dirvers, could you please apply the following patch, add the logical > ID of your card into sbc_ids[] and see how it works? > (I have asked peter to review the PnP part of the patch) Applying your patch made the kernel recognise the soundcard again without adding additional pnp ids. Thanks, Timo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 1:42:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with SMTP id E96EB14CAF for ; Thu, 2 Dec 1999 01:42:26 -0800 (PST) (envelope-from will@ns.demophon.com) Received: (qmail 4082 invoked by uid 1003); 2 Dec 1999 09:40:37 -0000 Date: 2 Dec 1999 09:40:37 -0000 Message-ID: <19991202094037.4079.qmail@ns.demophon.com> From: Ville-Pertti Keinonen To: current@freebsd.org Cc: marcel@scc.nl, dillon@apollo.backplane.com, bde@zeta.org.au Subject: Re: kernel: -mpreferred-stack-boundary=2 ?? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I've checked, and in -current, userland stack boundary alignment is useless because the stack pointer is initially only aligned on a word-boundary. I've also verified that the correct alignment is indeed expected to apply to frame pointers, i.e. stored frame pointers are at aligned stack slots and the current frame pointer points to an aligned address. Alignment can be verified by doing something like this: struct { int a[4]; } x __attribute__((aligned(16))); printf("offset: %u\n", (unsigned int)&x & 15); You have to run the program using different arguments and argument lengths to ensure that what you get isn't coincidental. When things are working properly, the above should always print 0. Note that double-alignment vs. word-alignment can really have >30% performance impact, at least on an Athlon and one meaningless floating point microbenchmark (operations on small, fixed-sized matrices...maybe it isn't even *that* meaningless). Here's a patch against -current that fixes this problem (note that this doesn't maintain alignment for constructors, and it isn't very pretty because it has to be done all in asm...): Index: crt1.c =================================================================== RCS file: /m/cvs/freebsd/src/lib/csu/i386-elf/crt1.c,v retrieving revision 1.4 diff -u -r1.4 crt1.c --- crt1.c 1999/08/27 23:57:57 1.4 +++ crt1.c 1999/12/02 09:02:05 @@ -92,7 +92,17 @@ monstartup(&eprol, &etext); #endif _init(); - exit( main(argc, argv, env) ); + asm volatile("andl $~15,%%esp;" + "addl $4,%%esp;" + "pushl %2;" + "pushl %1;" + "pushl %0;" + "call main;" + "movl %%eax,(%%esp);" + "call exit" + : : "rm" (argc), "rm" (argv), "rm" (env)); + for (;;) + ; } #ifdef GCRT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 2:31:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A09DD14E51 for ; Thu, 2 Dec 1999 02:31:45 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.040 #1) id 11tTW0-000HGp-00; Thu, 02 Dec 1999 12:31:08 +0200 From: Sheldon Hearn To: charon@freethought.org Cc: current@FreeBSD.ORG Subject: Re: minor bug in ee? In-reply-to: Your message of "Thu, 02 Dec 1999 00:54:11 CST." <3.0.5.32.19991202005411.00a39cb0@nsit-popmail.uchicago.edu> Date: Thu, 02 Dec 1999 12:31:08 +0200 Message-ID: <66390.944130668@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 02 Dec 1999 00:54:11 CST, charon@freethought.org wrote: > I recently noticed that ^v (the scroll down a page command in ee) must be > entered twice to scroll down once (i.e. if you hit ^v once it won't do > anything, you must hit it again) on a 4.0-CURRENT system. Sounds like ncurses takes the first ^v as "next character is literal". > I doubt this is very important - should I file a PR or anything? Probably. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 3: 5:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id BE0B714D8B for ; Thu, 2 Dec 1999 03:05:22 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id MAA25738; Thu, 2 Dec 1999 12:04:03 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id MAA27700; Thu, 2 Dec 1999 12:03:57 +0100 (MEZ) Date: Thu, 2 Dec 1999 12:03:56 +0100 From: Martin Blapp To: freebsd-current@freebsd.org Cc: ak03@gte.com Subject: re: rpc.umntall does not work with AIX Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Bad MNT PRC: RPC: Remote system error > Hi, This is a RPC problem, not an NFS problem. Maybe AIX does not support RPC_UMNTALL ? Because our support was buggy, noone may have notified it before. Or do you have problems with the AIX rpc.mountd ? Can you trace mountd(8) on the AIX side and look at the output ? Can you test the following cases too and tell me if it works or not (please umount and mount kan:/home/ak03 again after each command) # rpc.umtall -h kan -p /home/ak03 # rpc.umtall -h kan # umount kan:/home/ak03 What entries do you have in /var/db/mounttab ? Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 3:17:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 9A34B14D8B; Thu, 2 Dec 1999 03:17:43 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id WAA20515; Thu, 2 Dec 1999 22:22:33 +1100 Date: Thu, 2 Dec 1999 22:15:20 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: charon@freethought.org Cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: minor bug in ee? In-Reply-To: <3.0.5.32.19991202005411.00a39cb0@nsit-popmail.uchicago.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 2 Dec 1999 charon@freethought.org wrote: > I recently noticed that ^v (the scroll down a page command in ee) must be > entered twice to scroll down once (i.e. if you hit ^v once it won't do > anything, you must hit it again) on a 4.0-CURRENT system. As far as I can > recall, this has been happening for as long as I've been tracking -CURRENT > (~1 month), and still continues on the system I updated as of Nov. 30. > 3-STABLE (as of Dec. 1) doesn't have this problem - it has a simple > one-to-one ratio for ^v / scroll down. As far as I can recall, none of the > other 3.x or 2.x releases had this problem either. > > I doubt this is very important - should I file a PR or anything? This is the classic IEXTEN bug. The interaction of IEXTEN with ICANON is implementation-defined. In FreeBSD, IEXTEN is independent of ICANON. Buggy software doesn't know this and leaves IEXTEN set in "raw" mode. This normally leaves ^V as the lnext character. This bug, as it affects ee, is another libncurses bug. The old libcurses never had it, and it was "fixed" in in rev.1.4 of lib_raw.c in the old libncurses. Here is the "fix" cleaned up and merged into the current lib_raw.c: Index: ncurses/tinfo/lib_raw.c =================================================================== RCS file: /home/ncvs/src/contrib/ncurses/ncurses/tinfo/lib_raw.c,v retrieving revision 1.1.1.1 diff -c -2 -r1.1.1.1 lib_raw.c *** lib_raw.c 1999/08/24 01:06:44 1.1.1.1 --- lib_raw.c 1999/12/02 10:39:01 *************** *** 75,78 **** --- 75,82 ---- #endif /* TRACE */ + #ifdef TERMIOS + static tcflag_t iexten = 0; + #endif + int raw(void) { *************** *** 89,93 **** #ifdef TERMIOS BEFORE("raw"); ! cur_term->Nttyb.c_lflag &= ~(ICANON|ISIG); cur_term->Nttyb.c_iflag &= ~(COOKED_INPUT); cur_term->Nttyb.c_cc[VMIN] = 1; --- 93,99 ---- #ifdef TERMIOS BEFORE("raw"); ! if (iexten == 0) ! iexten = cur_term->Nttyb.c_lflag & IEXTEN; ! cur_term->Nttyb.c_lflag &= ~(ICANON|ISIG|IEXTEN); cur_term->Nttyb.c_iflag &= ~(COOKED_INPUT); cur_term->Nttyb.c_cc[VMIN] = 1; *************** *** 158,162 **** #ifdef TERMIOS BEFORE("noraw"); ! cur_term->Nttyb.c_lflag |= ISIG|ICANON; cur_term->Nttyb.c_iflag |= COOKED_INPUT; AFTER("noraw"); --- 164,168 ---- #ifdef TERMIOS BEFORE("noraw"); ! cur_term->Nttyb.c_lflag |= ISIG|ICANON|iexten; cur_term->Nttyb.c_iflag |= COOKED_INPUT; AFTER("noraw"); Problems with this fix: `iexten' shouldn't exist. The IEXTEN setting for the "noraw" state should be obtained from the original setting or forced on or off. Unfixed nearby problems: About 27 termios flags must be set (on or off) for raw mode (see libc/gen/termios.c:cfmakeraw()), but raw() only sets about 5 of them. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 3:29:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id E2C8214EAC for ; Thu, 2 Dec 1999 03:29:29 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11tUPi-0004C3-00; Thu, 2 Dec 1999 11:28:42 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id MAA38472; Thu, 2 Dec 1999 12:28:39 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <384657E7.B3E461D5@scc.nl> Date: Thu, 02 Dec 1999 12:28:39 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ville-Pertti Keinonen Cc: current@freebsd.org, dillon@apollo.backplane.com, bde@zeta.org.au Subject: Re: kernel: -mpreferred-stack-boundary=2 ?? References: <19991202094037.4079.qmail@ns.demophon.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ville-Pertti Keinonen wrote: > +++ crt1.c 1999/12/02 09:02:05 > @@ -92,7 +92,17 @@ > monstartup(&eprol, &etext); > #endif > _init(); > - exit( main(argc, argv, env) ); > + asm volatile("andl $~15,%%esp;" > + "addl $4,%%esp;" > + "pushl %2;" > + "pushl %1;" > + "pushl %0;" > + "call main;" > + "movl %%eax,(%%esp);" > + "call exit" > + : : "rm" (argc), "rm" (argv), "rm" (env)); AFAICT, it's enough to just align the stack before doing anything else. In this case it means aligning the stack somewhere before (exit(main(...)). gcc maintains proper alignment on an aligned stack. Maybe alignment can even be done in the kernel... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 3:48:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id B989B150A8 for ; Thu, 2 Dec 1999 03:48:29 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id GAA12799 for ; Thu, 2 Dec 1999 06:48:20 -0500 (EST) Date: Thu, 2 Dec 1999 06:48:20 -0500 (EST) From: "Matthew N. Dodd" To: current@freebsd.org Subject: HEADS UP! device_add_child() change. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm going to be committing the changes to eliminate the 'ivars' arguement to device_add_child(), and device_add_child_ordered(). The functionality will be provided by device_set_ivars(). I've got a go-ahead from Doug and Peter but as this change touches many files I'd like to give other driver maintainers a chance to assimilate the relevent portions of my patch into their own trees. The files I'm going to be touching follow. The patch is at: ftp://ftp.jurai.net/users/winter/patches/device_add_child.diff Please note that the device_set_ivars() function is not present in this patch. I will add this manually to sys/kern/subr_bus.c before I commit, as well as the changes to the man page. I will be committing this in 12 hours or so. alpha/alpha/autoconf.c alpha/pci/apecs.c alpha/pci/apecs_pci.c alpha/pci/cia.c alpha/pci/cia_pci.c alpha/pci/lca.c alpha/pci/lca_pci.c alpha/pci/tsunami.c alpha/pci/tsunami_pci.c alpha/tc/ioasic.c alpha/tc/tc.c alpha/tc/tcasic.c alpha/tc/tcds.c alpha/tlsb/gbus.c alpha/tlsb/kftxx.c alpha/tlsb/tlsb.c alpha/tlsb/zs_tlsb.c dev/amr/amr.c dev/bktr/bktr_i2c.c dev/ida/ida.c dev/iicbus/iicbus.c dev/iicbus/iiconf.c dev/mca/mca_bus.c dev/mii/mii.c dev/mlx/mlx.c dev/pccard/pccard.c dev/pcic/i82365.c dev/ppbus/lpbb.c dev/smbus/smbconf.c dev/smbus/smbus.c dev/sound/isa/gusc.c dev/sound/isa/sbc.c dev/sound/pci/csa.c dev/usb/usb_subr.c i386/eisa/eisaconf.c i386/i386/autoconf.c i386/i386/nexus.c i386/isa/pcf.c i386/isa/pcibus.c isa/atkbdc_isa.c isa/fd.c isa/isa_common.c isa/vga_isa.c kern/subr_bus.c pc98/pc98/fd.c pccard/pccard.c pccard/pcic.c pci/alpm.c pci/intpm.c pci/ohci_pci.c pci/pci.c pci/pcisupport.c pci/uhci_pci.c sys/bus.h -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 3:51:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 6440F14F44 for ; Thu, 2 Dec 1999 03:51:40 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup7-10.iptelecom.net.ua [212.9.227.138]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA16153 for ; Thu, 2 Dec 1999 13:54:27 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id NAA06871 for ; Thu, 2 Dec 1999 13:50:33 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <38465D07.8A25A0D@altavista.net> Date: Thu, 02 Dec 1999 13:50:31 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: Problem with syscons in VESA mode Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm using non-standard 100x37 console mode on my notebook, because in 80x25 text mode letters seems too big for my 12' panel, while other modes doesn't cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600 100x37 mode (instead of default 80x25) with 8x16 font, and in most cases all works just fine (including ncurses and dialog bases apps), but sometimes when I'm building world or some other app text suddenly shifts from the edge of the screen by several spaces and all text passed to the console after that also being printed with that offset. For example: bash$ make someapp [...] blablabla blablabla blablabla blablabla blablabla [...] bash$ ls a b c d bash$ [...] I've also found that this effect disappears by switching to the other virtual console and returning to the misbehaving one. I've did some tests to find out what exactly should be passed to the console to trigger this misbehaviour and found that following string being printed when mergemaster is executing expose that (please note that this should be ONE CONTINUOUS STRING): for i in answer isdntel.sh record tell tell-record ; do install -c -o root -g wheel -m 700 $i /var/tmp/temproot/etc/isdn ; done ; for i in isdnd.rates.D isdnd.rates.F isdnd.rates.UK.BT isdnd.rc.sample isdntel.alias.sample ; do install -c -o root -g wheel -m 600 $i /var/tmp/temproot/etc/isdn ; done Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 4: 4:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id B8C0014F44; Thu, 2 Dec 1999 04:04:35 -0800 (PST) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id NAA16857; Thu, 2 Dec 1999 13:03:13 +0100 (CET) (envelope-from des) To: Russell Cattelan Cc: current@freebsd.org, cg@freebsd.org Subject: Re: Soundblaster 128 PCI References: <38455C25.D4E917A6@thebarn.com> Organization: Yes Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 02 Dec 1999 13:03:13 +0100 In-Reply-To: Russell Cattelan's message of "Wed, 01 Dec 1999 11:34:29 -0600" Message-ID: Lines: 11 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Russell Cattelan writes: > Dag-Erling Smorgrav wrote: > > I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't > > get to work with newpcm. > What mother board are you using? Asus Socket 7. DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 4: 5:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with SMTP id 554B814F44 for ; Thu, 2 Dec 1999 04:05:15 -0800 (PST) (envelope-from will@ns.demophon.com) Received: (qmail 4621 invoked by uid 1003); 2 Dec 1999 12:02:12 -0000 Date: 2 Dec 1999 12:02:12 -0000 Message-ID: <19991202120212.4618.qmail@ns.demophon.com> From: Ville-Pertti Keinonen To: marcel@scc.nl Cc: current@freebsd.org, dillon@apollo.backplane.com, bde@zeta.org.au In-reply-to: <384657E7.B3E461D5@scc.nl> (message from Marcel Moolenaar on Thu, 02 Dec 1999 12:28:39 +0100) Subject: Re: kernel: -mpreferred-stack-boundary=2 ?? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > AFAICT, it's enough to just align the stack before doing anything else. > In this case it means aligning the stack somewhere before > (exit(main(...)). gcc maintains proper alignment on an aligned stack. I wouldn't rely on that, gcc is free to assume that it can address local variables relative to the stack. In practice, it uses %ebp unless you use -fomit-frame-pointer, but I don't think that manipulating the stack pointer without gcc knowing about it is guaranteed to be safe (alloca is a special case, gcc detects that it is used internally). Future improvements in code generation would also be likely to break things. However, an easy alternative would be to make the _start entry point an assembly language stub that calls a C function: That would look something like this if done in crt1.c: asm(".text; .globl _start; _start:;" "lea 4(%esp),%eax;" "andl $~15,%esp;" "subl $4,%esp;" "pushl %eax;" "call c_start"); static void c_start(char **argv) { etc... This of course assumes that static symbols have naming conventions identical to global symbols. (It can easily be made more predictable by assigning the function a specific symbol) > Maybe alignment can even be done in the kernel... It gets messy, it has to be done before putting the env and argv pointers in place... On program entry, (%esp) is argc, %esp + 4 is the beginning of the argv array and env array is located immediately after the argv array. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 4: 5:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id B0E081505D; Thu, 2 Dec 1999 04:05:47 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id NAA18815; Thu, 2 Dec 1999 13:04:39 +0100 (CET) (envelope-from asmodai) Date: Thu, 2 Dec 1999 13:04:38 +0100 From: Jeroen Ruigrok van der Werven To: Nik Clayton Cc: "F. Heinrichmeyer" , "freebsd-current@FreeBSD.ORG" , doc@FreeBSD.ORG Subject: Re: gcc-2.95.2, jade and freebsd-sgml-documentation Message-ID: <19991202130438.F18029@lucifer.bart.nl> References: <38415AA1.2586CEA9@fernuni-hagen.de> <19991201175515.A95818@kilt.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991201175515.A95818@kilt.nothing-going-on.org>; from nik@FreeBSD.ORG on Wed, Dec 01, 1999 at 05:55:15PM +0000 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991201 23:30], Nik Clayton (nik@FreeBSD.ORG) wrote: >On Sun, Nov 28, 1999 at 05:38:57PM +0100, F. Heinrichmeyer wrote: >> i tried to make me a new handbook, so i needed jade. >> >> But the newest C++ fashion (g++ under current) has changed to fast for >> this very old 1998 heavily template based source code distribution ;-). >> I had a lot of problems with const and not const .. and gave up. It is >> far to much to post here ... > >Unfortunately, jade is the tool of choice. I don't run -current, so >haven't had a chance to test out jade with the new GCC. I think someone (obrien prolly) committed some patches to the jade port to make it compile on CURRENT. HTH, -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / Tel: +31 - (0) 10 - 240 39 70 VIA NET.WORKS Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 4:31:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 1876814DC3 for ; Thu, 2 Dec 1999 04:31:06 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11tVNG-0004KV-00; Thu, 2 Dec 1999 12:30:15 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id NAA40388; Thu, 2 Dec 1999 13:30:16 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38466658.CA1D78BA@scc.nl> Date: Thu, 02 Dec 1999 13:30:16 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ville-Pertti Keinonen Cc: current@freebsd.org, dillon@apollo.backplane.com, bde@zeta.org.au Subject: Re: kernel: -mpreferred-stack-boundary=2 ?? References: <19991202120212.4618.qmail@ns.demophon.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ville-Pertti Keinonen wrote: > > Maybe alignment can even be done in the kernel... > > It gets messy, it has to be done before putting the env and argv > pointers in place... Alignment also applies to calling signal handlers... -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 5: 1: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with SMTP id C13E514DBA for ; Thu, 2 Dec 1999 05:01:05 -0800 (PST) (envelope-from will@ns.demophon.com) Received: (qmail 4775 invoked by uid 1003); 2 Dec 1999 12:58:36 -0000 Date: 2 Dec 1999 12:58:36 -0000 Message-ID: <19991202125836.4772.qmail@ns.demophon.com> From: Ville-Pertti Keinonen To: marcel@scc.nl Cc: current@freebsd.org, dillon@apollo.backplane.com, bde@zeta.org.au In-reply-to: <38466658.CA1D78BA@scc.nl> (message from Marcel Moolenaar on Thu, 02 Dec 1999 13:30:16 +0100) Subject: Re: kernel: -mpreferred-stack-boundary=2 ?? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Maybe alignment can even be done in the kernel... > > > > It gets messy, it has to be done before putting the env and argv > > pointers in place... > > Alignment also applies to calling signal handlers... Which is easier because sigframe has a constant size and you know what the relationship between the start of the sigframe and the stack pointer at the point of signal handler entry is (unlike when copying the arguments, in which case the fixup-code for the binary type determines this). And signal handlers probably don't execute performance-critical floating point code very often... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 5:30:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 3CB3214E8D for ; Thu, 2 Dec 1999 05:30:11 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id AAA26591; Fri, 3 Dec 1999 00:34:07 +1100 Date: Fri, 3 Dec 1999 00:26:57 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Ville-Pertti Keinonen Cc: current@freebsd.org, marcel@scc.nl, dillon@apollo.backplane.com Subject: Re: kernel: -mpreferred-stack-boundary=2 ?? In-Reply-To: <19991202094037.4079.qmail@ns.demophon.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2 Dec 1999, Ville-Pertti Keinonen wrote: >... > Note that double-alignment vs. word-alignment can really have >30% > performance impact, at least on an Athlon and one meaningless floating > point microbenchmark (operations on small, fixed-sized > matrices...maybe it isn't even *that* meaningless). I verified that the default alignment is a pessimisation of 1% for a meaningful benchmark (compiling a RELENG_3 kernel) on a Celeron: gcc (current) compiled with gcc: 29.00 real 11.42 user 2.28 sys 158.47 real 146.48 user 10.35 sys 13.58 real 11.31 user 2.20 sys 157.99 real 146.16 user 11.19 sys 13.58 real 11.37 user 2.14 sys 158.06 real 146.57 user 10.87 sys gcc (current) compiled with gcc -mpreferred-stack-boundary=2: 13.42 real 10.92 user 2.34 sys 156.94 real 144.14 user 11.16 sys 13.29 real 10.87 user 2.34 sys 156.43 real 144.22 user 11.23 sys 13.30 real 10.85 user 2.38 sys 156.14 real 144.70 user 10.73 sys The times are for `time make depend; time make' after `make clean; sync; sleep 1' (2 times for each run). The stack may have been perfectly misaligned for the default gcc. Corresponding times for egcs with various PQ_L2_SIZE's a few months ago: 16 pages: 28.50 real 11.78 user 2.62 sys 140.53 real 129.08 user 10.55 sys 14.17 real 11.72 user 2.43 sys 140.27 real 129.13 user 10.83 sys 14.15 real 11.77 user 2.35 sys 140.45 real 129.25 user 10.85 sys 32 pages: 28.57 real 11.60 user 2.69 sys 139.89 real 129.34 user 9.74 sys 14.09 real 11.67 user 2.39 sys 139.65 real 128.91 user 10.42 sys 14.06 real 11.57 user 2.45 sys 139.80 real 129.10 user 10.33 sys 64 pages: 28.51 real 11.88 user 2.46 sys 140.12 real 129.18 user 10.01 sys 14.11 real 11.59 user 2.49 sys 139.98 real 129.10 user 10.67 sys 14.10 real 11.89 user 2.18 sys 140.24 real 129.24 user 10.59 sys 128 pages: 28.11 real 11.94 user 2.40 sys 140.14 real 129.11 user 10.14 sys 14.08 real 11.82 user 2.23 sys 139.97 real 129.01 user 10.66 sys 14.09 real 11.64 user 2.44 sys 140.22 real 129.15 user 10.83 sys 256 pages: 28.31 real 11.74 user 2.45 sys 139.87 real 128.90 user 10.13 sys 14.17 real 11.67 user 2.48 sys 139.58 real 129.36 user 9.95 sys 14.15 real 11.49 user 2.60 sys 139.90 real 129.07 user 10.45 sys Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 6:56:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 1252B14CAA; Thu, 2 Dec 1999 06:56:23 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991201201641.55771@mojave.sitaranetworks.com> Date: Wed, 1 Dec 1999 20:16:41 -0500 From: Greg Lehey To: Bruce Evans , Thomas Stromberg Cc: "Andrey A. Chernov" , freebsd-current@FreeBSD.org Subject: Re: semi-HEADS-UP (dumpon now wants raw disk device) Reply-To: Greg Lehey References: <3843F225.34D5E976@rtci.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Bruce Evans on Wed, Dec 01, 1999 at 04:43:05AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 1 December 1999 at 4:43:05 +1100, Bruce Evans wrote: > On Tue, 30 Nov 1999, Thomas Stromberg wrote: > > [ache wrote]: >> " >>> I see no needs of this change. I have -current dumpon/savecore work with >>> old entrly like /dev/wd0... >>> savecore understand both character and old block devices now. > > You must not have a very current -current :-). /dev/wd0 is a character > device (with the same major/minor and character as /dev/rwd0) in -current: > > crw-r----- 1 root operator 3, 0x00010002 Dec 1 04:34 rwd0 > crw-r----- 1 root operator 3, 0x00010002 Dec 1 04:34 wd0 Just doing a 'make world' won't do this; indeed, make world doesn't even install the new ./MAKEDEV. What steps do you use to keep your device nodes up to date? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 7: 3:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with SMTP id C077F14CBF for ; Thu, 2 Dec 1999 07:03:44 -0800 (PST) (envelope-from will@ns.demophon.com) Received: (qmail 5373 invoked by uid 1003); 2 Dec 1999 15:00:47 -0000 Date: 2 Dec 1999 15:00:47 -0000 Message-ID: <19991202150047.5370.qmail@ns.demophon.com> From: Ville-Pertti Keinonen To: bde@zeta.org.au Cc: current@freebsd.org, marcel@scc.nl, dillon@apollo.backplane.com In-reply-to: (message from Bruce Evans on Fri, 3 Dec 1999 00:26:57 +1100 (EST)) Subject: Re: kernel: -mpreferred-stack-boundary=2 ?? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Note that double-alignment vs. word-alignment can really have >30% > > performance impact, at least on an Athlon and one meaningless floating > > point microbenchmark (operations on small, fixed-sized > > matrices...maybe it isn't even *that* meaningless). > > I verified that the default alignment is a pessimisation of 1% for a > meaningful benchmark (compiling a RELENG_3 kernel) on a Celeron: If you haven't patched crt1.c (and assuming random-length command lines) on average half of the command invocations produce double-misaligned and 75% 16-byte-misaligned stacks. The effect might not be significant when there isn't a lot of floating point code involved, it may have inadvertent side-effects on the cache-line locality of local variables. If the pessimization persists when the initial alignment is fixed, then there's a trade-off between a small pessimization for typical code and a big pessimization for less common (but more often performance-critical) code. > gcc (current) compiled with gcc: > 29.00 real 11.42 user 2.28 sys > 158.47 real 146.48 user 10.35 sys > 13.58 real 11.31 user 2.20 sys > 157.99 real 146.16 user 11.19 sys The first run should be ignored because you don't have predictable cache contents at that point (I assume that's the explanation for the above), or start each sequence of timed runs in a predictable state (e.g. fresh boot). The initial overhead doesn't affect your conclusions, though, since the further runs are consistent. > The times are for `time make depend; time make' after `make clean; sync; > sleep 1' (2 times for each run). The stack may have been perfectly > misaligned for the default gcc. It depends on the command line. It took me a while to figure out what was going on the first time I benchmarked a program that ran much faster when run under one name compared to when it was run using another name... ;--) > Corresponding times for egcs with various PQ_L2_SIZE's a few months ago: Properly benchmarking page coloring can't be done in a straightforward manner, since one of the desired effects is to prevent the page selection behavior from degrading over time. Did you set up the machine specially for those runs? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 7:43:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1B55814D2A; Thu, 2 Dec 1999 07:43:06 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA31820; Fri, 3 Dec 1999 02:49:20 +1100 Date: Fri, 3 Dec 1999 02:42:14 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Greg Lehey Cc: Thomas Stromberg , "Andrey A. Chernov" , freebsd-current@FreeBSD.org Subject: Re: semi-HEADS-UP (dumpon now wants raw disk device) In-Reply-To: <19991201201641.55771@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 1 Dec 1999, Greg Lehey wrote: > > You must not have a very current -current :-). /dev/wd0 is a character > > device (with the same major/minor and character as /dev/rwd0) in -current: > > > > crw-r----- 1 root operator 3, 0x00010002 Dec 1 04:34 rwd0 > > crw-r----- 1 root operator 3, 0x00010002 Dec 1 04:34 wd0 > > Just doing a 'make world' won't do this; indeed, make world doesn't > even install the new ./MAKEDEV. What steps do you use to keep your > device nodes up to date? I use cp to install MAKEDEV after merging it into my version. Since I read all the diffs when I merged it, I know what changed :). I haven't actually remade all my disk devices, since that would break testing of old kernels without changing userland. I made the above devices in /dev/z to get some ls output to put in the mail. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 7:50:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 7F0EA14DC5 for ; Thu, 2 Dec 1999 07:50:45 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 11tYV3-0007oW-00; Thu, 2 Dec 1999 15:50:29 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id QAA50803; Thu, 2 Dec 1999 16:50:28 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38469544.FBA70F80@scc.nl> Date: Thu, 02 Dec 1999 16:50:28 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ville-Pertti Keinonen Cc: bde@zeta.org.au, current@freebsd.org, dillon@apollo.backplane.com Subject: Re: kernel: -mpreferred-stack-boundary=2 ?? References: <19991202150047.5370.qmail@ns.demophon.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ville-Pertti Keinonen wrote: > > If the pessimization persists when the initial alignment is fixed, > then there's a trade-off between a small pessimization for typical > code and a big pessimization for less common (but more often > performance-critical) code. Performance critical code should always be coded and compiled in such a way that the machine code is optimal (for whatever optimal means in this case). It doesn't really make sense to argue how default compiler settings affect the performance critical code, because default compiler settings are per definition set to suit the majority of the programs. With 16 byte alignment and even with 8 byte alignment, defaults are not set for the majority of the programs, but clearly for the special cases. That's why I want 4 byte alignments by default and 8 or 16 byte alignments explicitely set for the special cases. Anyway, enough said. This has already taken enough bandwidth without any intent to change anything :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 8:20:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4844014DC5; Thu, 2 Dec 1999 08:20:46 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA17636; Thu, 2 Dec 1999 09:18:50 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA02544; Thu, 2 Dec 1999 09:18:49 -0700 (MST) Message-Id: <199912021618.JAA02544@harmony.village.org> To: Christopher Masto Subject: Re: PCCARD eject freeze (was Re: your mail) Cc: Nick Hibma , Mike Smith , FreeBSD CURRENT Mailing List In-reply-to: Your message of "Thu, 02 Dec 1999 03:13:46 EST." <19991202031346.B17644@netmonger.net> References: <19991202031346.B17644@netmonger.net> <19991130165407.A467@netmonger.net> <199911302159.OAA05508@harmony.village.org> <19991130173920.A22943@netmonger.net> <199911302304.QAA05780@harmony.village.org> <19991130181313.B24151@netmonger.net> <199911302319.QAA05945@harmony.village.org> <19991130182738.A25453@netmonger.net> <199911302352.QAA06230@harmony.village.org> <19991130213532.A2764@netmonger.net> <199912010755.AAA00462@harmony.village.org> Date: Thu, 02 Dec 1999 09:18:49 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991202031346.B17644@netmonger.net> Christopher Masto writes: : Hmm.. something's not right. I can eject my ed card (though I get : the "pccard: card removed, slot 0" message twice. But it doesn't : attach if I insert it again. "driver allocation failed for : Linksys(Combo PCMCIA EthernetCard (EC): Device not configured". : sio is a bit worse, it doesn't work the first time (same error: : device not configured). Odd. Very odd. I can't help you much until I get my laptop back, since this works for me and my ep (3C589D) card. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 8:21:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 9A4A214DC5 for ; Thu, 2 Dec 1999 08:21:28 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id DAA00525; Fri, 3 Dec 1999 03:28:02 +1100 Date: Fri, 3 Dec 1999 03:20:57 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Ville-Pertti Keinonen Cc: current@freebsd.org, marcel@scc.nl, dillon@apollo.backplane.com Subject: Re: kernel: -mpreferred-stack-boundary=2 ?? In-Reply-To: <19991202150047.5370.qmail@ns.demophon.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2 Dec 1999, Ville-Pertti Keinonen wrote: > > The times are for `time make depend; time make' after `make clean; sync; > > sleep 1' (2 times for each run). The stack may have been perfectly > > misaligned for the default gcc. > > It depends on the command line. It took me a while to figure out what > was going on the first time I benchmarked a program that ran much > faster when run under one name compared to when it was run using > another name... ;--) It also depends on the environment. The bw_pipe benchmark in lmbench is 20% (?) slower on some machines (P5's or K6/1's but not both) with certain enviroments and/or command lines, because it puts its buffers on the stack and the kernel doesn't bother to align the target addresses to more than 4-byte boundaries. > > Corresponding times for egcs with various PQ_L2_SIZE's a few months ago: > > Properly benchmarking page coloring can't be done in a straightforward > manner, since one of the desired effects is to prevent the page > selection behavior from degrading over time. Did you set up the > machine specially for those runs? I was improving page coloring, but wasn't very careful with those benchmarks, only with makeworld benchmarks. There was enough memory (320MB) to not stress my color allocator at all for kernel builds. That made kernel builds a bad benchmark for degradation of coloring but good for a quick test that color allocation hasn't become too expensive. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 8:26:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 6A0B314A0B; Thu, 2 Dec 1999 08:26:49 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-151.skylink.it [194.185.55.151]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id RAA03424; Thu, 2 Dec 1999 17:26:28 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id QAA02574; Thu, 2 Dec 1999 16:33:44 +0100 (CET) (envelope-from hibma@skylink.it) Date: Thu, 2 Dec 1999 16:33:44 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Christopher Masto Cc: Warner Losh , Mike Smith , FreeBSD CURRENT Mailing List Subject: Re: PCCARD eject freeze (was Re: your mail) In-Reply-To: <19991201123629.A5734@netmonger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There are other contexts for the same issues anyway. USB has devices > that go away suddenly, and it _is_ designed to be hot-removable, so > people are going to be pulling the plug on network adapters, ZIP > drives, etc. We need drivers that are capable of going away cleanly, > or at least without a panic. If a USB device all of a sudden disappears, in the middle of a transaction for example, the transaction simply fails. This means that all is needed is proper error checking on all functions that return an error. PCMCIA has the problem that the hardware register you are talking to can disappear on the spot, between 2 outb()s. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 8:38:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 1C42614A15 for ; Thu, 2 Dec 1999 08:38:17 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id IAA56251; Thu, 2 Dec 1999 08:37:15 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id IAA91231; Thu, 2 Dec 1999 08:37:15 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <199912021637.IAA91231@realtime.exit.com> Subject: Re: Well, the 3Com 574BT is still broken. In-Reply-To: from "Matthew N. Dodd" at "Dec 2, 1999 03:58:25 am" To: winter@jurai.net (Matthew N. Dodd) Date: Thu, 2 Dec 1999 08:37:15 -0800 (PST) Cc: frank@exit.com (Frank Mayhar), current@FreeBSD.ORG Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew N. Dodd wrote: > On Thu, 2 Dec 1999, Frank Mayhar wrote: > > Suggestions? I could Really Use an ethernet connection on this > > laptop; right now I have the cardbus card (3Com 575CT) and the pcmcia > > card (the 574BT) sitting here, useless. > Looking at the NetBSD driver it appears that the MAC address for the 574 > is stored in the CIS. > > It appears that the 574 has a different EEPROM layout as well, which is > sort of handled by sc->epb.cmd_off but not in a manner I'm happy with. Well, if there's _anything_ I can help with, please let me know. I did dump the CIS using pccardc, but I didn't see the MAC address. I can even set the laptop up with a serial console and hook it up to a system you can log into, if that would help. I'm a pretty good kernel programmer, btw, so I _can_ get down and dirty with the code. The problem is that there's just so much I don't know about the FreeBSD kernel, that it would take me hours or days just to figure out where to start. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 8:39:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 1029814E45 for ; Thu, 2 Dec 1999 08:39:26 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id LAA18843; Thu, 2 Dec 1999 11:39:23 -0500 (EST) Date: Thu, 2 Dec 1999 11:39:23 -0500 (EST) From: "Matthew N. Dodd" To: Frank Mayhar Cc: current@FreeBSD.ORG Subject: Re: Well, the 3Com 574BT is still broken. In-Reply-To: <199912021637.IAA91231@realtime.exit.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 2 Dec 1999, Frank Mayhar wrote: > Well, if there's _anything_ I can help with, please let me know. I did > dump the CIS using pccardc, but I didn't see the MAC address. I can even > set the laptop up with a serial console and hook it up to a system you can > log into, if that would help. > > I'm a pretty good kernel programmer, btw, so I _can_ get down and dirty with > the code. The problem is that there's just so much I don't know about the > FreeBSD kernel, that it would take me hours or days just to figure out where > to start. Add debugging printfs to print the value of the various things that are set using get_e(). I suspect that everything will be set to the card's board ID. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 9: 3:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from timbuk.cray.com (timbuk-fddi.cray.com [128.162.8.102]) by hub.freebsd.org (Postfix) with ESMTP id 336EC14E06; Thu, 2 Dec 1999 09:03:21 -0800 (PST) (envelope-from cattelan@thebarn.com) Received: from clink.americas.sgi.com (clink.cray.com [128.162.84.70]) by timbuk.cray.com (8.8.8/CRI-gate-news-1.3) with ESMTP id LAA04954; Thu, 2 Dec 1999 11:03:09 -0600 (CST) Received: from thebarn.com (localhost [127.0.0.1]) by clink.americas.sgi.com (980427.SGI.8.8.8/CRI-news-1.3) with ESMTP id LAA64959; Thu, 2 Dec 1999 11:03:07 -0600 (CST) Message-ID: <3846A64B.D75079EA@thebarn.com> Date: Thu, 02 Dec 1999 11:03:07 -0600 From: Russell Cattelan X-Mailer: Mozilla 4.7 [en] (X11; I; IRIX64 6.5-ALPHA-1275916020 IP27) X-Accept-Language: en MIME-Version: 1.0 To: Jeroen Ruigrok/Asmodai Cc: Dag-Erling Smorgrav , current@freebsd.org, cg@freebsd.org Subject: Re: Soundblaster 128 PCI References: <38455C25.D4E917A6@thebarn.com> <19991202080030.F12457@daemon.ninth-circle.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > -On [19991201 20:01], Russell Cattelan (cattelan@thebarn.com) wrote: > >Dag-Erling Smorgrav wrote: > >> I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't > >> get to work with newpcm. > > >What mother board are you using? > >There have been some reports of the new 1371's not working with > >non intel chip sets. Asus boards are know to be a problem. > >Apparently it is a timing bug in the sound card. > > The timing bug, is that a PCI bus clock/signal bug which the card has, or an > internal timing problem? I found this message in the als archives. http://hyppo.screwdriver.net/show.phtml?id=119845 Summary: I had quite a few conversations via email with David Sowa at Ensoniq, ran a boatload of tests, found that the card worked fine in a different system, swapped cards, and finally learned the answer. Turns out that there's a hardware bug in one batch of one vendor's codecs, which causes them to lock up if the PCI reset-line timing is just so. The ALI chipset in my ASUS motherboard tickled the bug, while the Intel chipset in my test system at work did not. I have been watching the list to see if anybody has found a solution to the problem. I've had at least 4 reports of the new PCI128 not working with an ASUS board. > > > -- > Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl > The BSD Programmer's Documentation Project > Network/Security Specialist BSD: Technical excellence at its best > Learn e-mail netiquette: http://www.lemis.com/email.html > We do not count a man's years, until he has nothing left to count... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 9: 4:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id A2D8714C92 for ; Thu, 2 Dec 1999 09:04:50 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup6-53.iptelecom.net.ua [212.9.227.117]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id TAA02208; Thu, 2 Dec 1999 19:07:50 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id TAA07611; Thu, 2 Dec 1999 19:03:50 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <3846A672.524B188A@altavista.net> Date: Thu, 02 Dec 1999 19:03:46 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Tony Finch Cc: current@freebsd.org Subject: Re: Problem with syscons in VESA mode References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Finch wrote: > Maxim Sobolev wrote: > > > >I'm using non-standard 100x37 console mode on my notebook, because in 80x25 > >text mode letters seems too big for my 12' panel, while other modes doesn't > >cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600 > >100x37 mode (instead of default 80x25) with 8x16 font, and in most cases all > >works just fine (including ncurses and dialog bases apps), but sometimes when > >I'm building world or some other app text suddenly shifts from the edge of the > >screen by several spaces and all text passed to the console after that also > >being printed with that offset. > > I've seen this on -stable with standard large modes set by vidcontrol. It is interesting. Seems like it is not only VESA modes bug. Strange that nobody else observed this misbehaviour. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 9:23:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id D5A9A14CA6 for ; Thu, 2 Dec 1999 09:23:46 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id MAA47364; Thu, 2 Dec 1999 12:22:54 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <199912021722.MAA47364@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3846A672.524B188A@altavista.net> Date: Thu, 02 Dec 1999 12:22:54 -0500 (EST) From: John Baldwin To: Maxim Sobolev Subject: Re: Problem with syscons in VESA mode Cc: current@FreeBSD.org, Tony Finch Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02-Dec-99 Maxim Sobolev wrote: > Tony Finch wrote: > >> Maxim Sobolev wrote: >> > >> >I'm using non-standard 100x37 console mode on my notebook, because >> >in 80x25 >> >text mode letters seems too big for my 12' panel, while other modes >> >doesn't >> >cover all panel size. So I've patched vidcontrol to switch to the >> >VESA_800x600 >> >100x37 mode (instead of default 80x25) with 8x16 font, and in most >> >cases all >> >works just fine (including ncurses and dialog bases apps), but >> >sometimes when >> >I'm building world or some other app text suddenly shifts from the >> >edge of the >> >screen by several spaces and all text passed to the console after >> >that also >> >being printed with that offset. >> >> I've seen this on -stable with standard large modes set by >> vidcontrol. > > It is interesting. Seems like it is not only VESA modes bug. Strange > that nobody > else observed this misbehaviour. > > -Maxim I have seen it in 132 x anything on both -stable and -current but just haven't been bothered enough by it to complain. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 9:40:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 3CE0414BFC; Thu, 2 Dec 1999 09:40:11 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id MAA20197; Thu, 2 Dec 1999 12:38:57 -0500 (EST) Date: Thu, 2 Dec 1999 12:38:57 -0500 (EST) From: "Matthew N. Dodd" To: Nick Hibma Cc: Christopher Masto , Warner Losh , Mike Smith , FreeBSD CURRENT Mailing List Subject: Re: PCCARD eject freeze (was Re: your mail) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 2 Dec 1999, Nick Hibma wrote: > PCMCIA has the problem that the hardware register you are talking to can > disappear on the spot, between 2 outb()s. Can't we do something about this using bus_space? This would give us a fair bit of overhead for PCMCIA devices as well as require us to more tightly couple newbus and bus_space (we'd probably want to 'cache' a function pointer to the method to avoid method lookup overhead.) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 11: 2:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B63CD14C31; Thu, 2 Dec 1999 11:02:47 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA18359; Thu, 2 Dec 1999 12:02:19 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA03732; Thu, 2 Dec 1999 12:02:18 -0700 (MST) Message-Id: <199912021902.MAA03732@harmony.village.org> To: Nick Hibma Subject: Re: PCCARD eject freeze (was Re: your mail) Cc: Christopher Masto , Mike Smith , FreeBSD CURRENT Mailing List In-reply-to: Your message of "Thu, 02 Dec 1999 16:33:44 +0100." References: Date: Thu, 02 Dec 1999 12:02:18 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Nick Hibma writes: : PCMCIA has the problem that the hardware register you are talking to can : disappear on the spot, between 2 outb()s. Yes. That's why one must poll the device, from time to time, to see if it is gone. Yucky-poo. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 11:12:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B62A014DCF; Thu, 2 Dec 1999 11:12:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA18424; Thu, 2 Dec 1999 12:11:52 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA03854; Thu, 2 Dec 1999 12:11:51 -0700 (MST) Message-Id: <199912021911.MAA03854@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: PCCARD eject freeze (was Re: your mail) Cc: Nick Hibma , Christopher Masto , Mike Smith , FreeBSD CURRENT Mailing List In-reply-to: Your message of "Thu, 02 Dec 1999 12:38:57 EST." References: Date: Thu, 02 Dec 1999 12:11:51 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : On Thu, 2 Dec 1999, Nick Hibma wrote: : > PCMCIA has the problem that the hardware register you are talking to can : > disappear on the spot, between 2 outb()s. : : Can't we do something about this using bus_space? This would give us a : fair bit of overhead for PCMCIA devices as well as require us to more : tightly couple newbus and bus_space (we'd probably want to 'cache' a : function pointer to the method to avoid method lookup overhead.) I had the same thought, but w/o a signal or other out of band error communication, I'm not sure how to implement this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 11:17:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 7D5E814C24; Thu, 2 Dec 1999 11:17:43 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id OAA22599; Thu, 2 Dec 1999 14:16:03 -0500 (EST) Date: Thu, 2 Dec 1999 14:16:03 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: Nick Hibma , Christopher Masto , Mike Smith , FreeBSD CURRENT Mailing List Subject: Re: PCCARD eject freeze (was Re: your mail) In-Reply-To: <199912021911.MAA03854@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 2 Dec 1999, Warner Losh wrote: > I had the same thought, but w/o a signal or other out of band error > communication, I'm not sure how to implement this. Well, if we do the detach and set a timeout freeing the device_t & softc the next read or write will fail and the 'sleeper' can bail out. Or something. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 11:24: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id B233114BFC for ; Thu, 2 Dec 1999 11:23:58 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-174.skylink.it [194.185.55.174]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id UAA08156; Thu, 2 Dec 1999 20:21:03 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id SAA00522; Thu, 2 Dec 1999 18:11:58 +0100 (CET) (envelope-from hibma@skylink.it) Date: Thu, 2 Dec 1999 18:11:57 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: thyerm@camtech.net.au Cc: current@FreeBSD.ORG Subject: Re: How do I get a USB mouse working in todays -CURRENT ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem is that the mouse doesn't work (its not a hardware problem), > all I get whenever I move the mouse are lots of the following messages > on the console: > > Discarded 7 bytes in queue This means that your mouse is working but moused is closing while the buffer is not empty yet. This looks a lot like my mistake I fixed earlier. > Do I need to change /etc/usbd.conf in some way ? No, you are probably looking at a stale moused.c. Please update the file /usr/src/usr.sbin/moused/moused.c with the following diff (there is an extra semicolon at the end of that line) and execute make&&make install in that directory: Index: src/usr.sbin/moused/moused.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/moused/moused.c,v retrieving revision 1.32 retrieving revision 1.33 diff -u -w -r1.32 -r1.33 --- moused.c 1999/11/29 17:21:07 1.32 +++ moused.c 1999/11/30 10:20:33 1.33 @@ -746,7 +746,7 @@ } /* mouse event */ - if (read(rodent.mfd, &b, 1) == -1); + if (read(rodent.mfd, &b, 1) == -1) return; /* file seems to be closed on us */ if (r_protocol(b, &action)) { /* handler detected action */ Nick -- hibma@skylink.it n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 11:24:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 362F014BFC for ; Thu, 2 Dec 1999 11:24:13 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-174.skylink.it [194.185.55.174]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id UAA08165; Thu, 2 Dec 1999 20:21:27 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id SAA00527; Thu, 2 Dec 1999 18:17:15 +0100 (CET) (envelope-from hibma@skylink.it) Date: Thu, 2 Dec 1999 18:17:15 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Kenneth Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: modules building... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Did you do a config of your kernel after updating? opt_linux.h is generated by config. Nick On Tue, 30 Nov 1999, Kenneth Culver wrote: > I tried to rebuild the linux kernel module, but it doesn't work: > > Warning: Object directory not changed from original > /usr/src/sys/modules/linux > cc -c -O -pipe -DKERNEL -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- > -I/usr/src/sys/modules/linux -I/usr/src/sys/modules/linux/@ > -mpreferred-stack-boundary=2 -UKERNEL > /usr/src/sys/modules/linux/../../i386/linux/linux_genassym.c > cc -static -O -pipe -DKERNEL -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- > -I/usr/src/sys/modules/linux -I/usr/src/sys/modules/linux/@ > -mpreferred-stack-boundary=2 -o linux_genassym linux_genassym.o > ./linux_genassym > linux_assym.h > make: don't know how to make opt_linux.h. Stop > > several other modules exhibit similar behavior... > > > ================================================================= > | Kenneth Culver | FreeBSD: The best OS around. | > | Unix Systems Administrator | ICQ #: 24767726 | > | and student at The | AIM: AgRSkaterq | > | The University of Maryland, | Website: (Under Construction) | > | College Park. | http://www.wam.umd.edu/~culverk/| > ================================================================= > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- hibma@skylink.it n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 11:24:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 0EE6814F0E for ; Thu, 2 Dec 1999 11:24:16 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-174.skylink.it [194.185.55.174]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id UAA08181; Thu, 2 Dec 1999 20:21:48 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id SAA00514; Thu, 2 Dec 1999 18:02:41 +0100 (CET) (envelope-from hibma@skylink.it) Date: Thu, 2 Dec 1999 18:02:41 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Poul-Henning Kamp Cc: frank@exit.com, current@FreeBSD.ORG Subject: Re: block devices & dumpon. In-Reply-To: <2306.943984703@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I agree (patches accepted), although it is hard to figure out just > exactly what is needed to "run one's system". > > Maybe a "remake" entry in MAKEDEV which remakes all current entries > if possible. cd /dev/; sh MAKEDEV * perhaps? It is going to be one hell of a ride on your disk, remaking some nodes various times, but it should work. As Warner says, it's time for devfs. Julian? Nick -- hibma@skylink.it n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 13: 1:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id D2BD514EC7; Thu, 2 Dec 1999 13:01:34 -0800 (PST) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id VAA13263; Thu, 2 Dec 1999 21:54:18 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id WAA17379; Thu, 2 Dec 1999 22:01:03 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id WAA30977; Thu, 2 Dec 1999 22:00:55 +0100 (CET) (envelope-from ticso) Date: Thu, 2 Dec 1999 22:00:54 +0100 From: Bernd Walter To: John Baldwin Cc: Maxim Sobolev , current@FreeBSD.ORG, Tony Finch Subject: Re: Problem with syscons in VESA mode Message-ID: <19991202220053.A30950@cicely8.cicely.de> References: <3846A672.524B188A@altavista.net> <199912021722.MAA47364@server.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912021722.MAA47364@server.baldwin.cx> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 02, 1999 at 12:22:54PM -0500, John Baldwin wrote: > > On 02-Dec-99 Maxim Sobolev wrote: > > Tony Finch wrote: > > > >> Maxim Sobolev wrote: > >> > > >> >I'm using non-standard 100x37 console mode on my notebook, because > >> >in 80x25 > >> >text mode letters seems too big for my 12' panel, while other modes > >> >doesn't > >> >cover all panel size. So I've patched vidcontrol to switch to the > >> >VESA_800x600 > >> >100x37 mode (instead of default 80x25) with 8x16 font, and in most > >> >cases all > >> >works just fine (including ncurses and dialog bases apps), but > >> >sometimes when > >> >I'm building world or some other app text suddenly shifts from the > >> >edge of the > >> >screen by several spaces and all text passed to the console after > >> >that also > >> >being printed with that offset. > >> > >> I've seen this on -stable with standard large modes set by > >> vidcontrol. > > > > It is interesting. Seems like it is not only VESA modes bug. Strange > > that nobody > > else observed this misbehaviour. > > > > -Maxim > > I have seen it in 132 x anything on both -stable and -current but just > haven't been bothered enough by it to complain. > Same here - just havn't found the time to check if it's maybe BIOS related (it's a rather old version on the card) or is already fixed in a newer current. It happens with current from July on a Millenium using 132x60. I don't know about other modes but I never saw this in plain mode. VESA: v2.0, 8192k memory, flags:0x0x1, mode table:0xc0bc0102 (0x1000022) VESA: Matrox Graphics Inc. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 13: 2:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id C130614F56 for ; Thu, 2 Dec 1999 13:02:26 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id WAA27494 for current@freebsd.org; Thu, 2 Dec 1999 22:02:23 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id C4CA58863; Thu, 2 Dec 1999 21:06:42 +0100 (CET) Date: Thu, 2 Dec 1999 21:06:42 +0100 From: Ollivier Robert To: current@freebsd.org Subject: Re: Problem with syscons in VESA mode Message-ID: <19991202210642.A96274@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <3846A672.524B188A@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <3846A672.524B188A@altavista.net> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Maxim Sobolev: > It is interesting. Seems like it is not only VESA modes bug. Strange that > nobody else observed this misbehaviour. I used to see that in 132 col. mode a year or so (maybe more) and it was fixed at that time... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 13:47: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 16EA214F82 for ; Thu, 2 Dec 1999 13:46:55 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id PAA98987 for ; Thu, 2 Dec 1999 15:46:51 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Thu, 2 Dec 1999 15:46:51 -0600 (CST) From: David Scheidt To: freebsd-current@freebsd.org Subject: panic: vm_page_free: freeing wired page Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am having the following panic, with a -CURRENT system as fo CTM cvs-cur.5868. I *think* the panic was induced by running mpg123 with a not an mp3 file. I've had two (maybe three, something happened to the box over night.) of these panics, but hte first was with no dump device configured. I suspect I can reproduce it, since this one I did. su-2.03# gdb -k GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /u/crash/kernel.0 (kgdb) core-file /u/crash/vmcore.0 IdlePTD 3047424 initial pcb at 2749e0 panicstr: vm_page_free: freeing wired page panic messages: --- panic: vm_page_free: freeing wired page syncing disks... 6 done dumping to dev #wd/0x20001, offset 262144 dump ata0: resetting devices .. done 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:273 273 dumppcb.pcb_cr3 = rcr3(); (kgdb) trace trace command requires an argument (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:273 #1 0xc0137115 in panic (fmt=0xc02405c0 "vm_page_free: freeing wired page\n") at ../../kern/kern_shutdown.c:523 #2 0xc01e1bf6 in vm_page_free_toq (m=0xc04e5a50) at ../../vm/vm_page.c:1102 #3 0xc01d9f59 in vm_fault (map=0xd8a18980, vaddr=672231424, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_page.h:504 #4 0xc021a46a in trap_pfault (frame=0xd9451fa8, usermode=1, eva=672231424) at ../../i386/i386/trap.c:781 #5 0xc0219f7f in trap (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134661840, tf_esi = -1077946152, tf_ebp = 0, tf_isp = -649781292, tf_ebx = -1077946153, tf_edx = -1077946796, tf_ecx = -1077946796, tf_eax = 672231424, tf_trapno = 12, tf_err = 4, tf_eip = 134592249, tf_cs = 31, tf_eflags = 66070, tf_esp = -1077946820, tf_ss = 47}) at ../../i386/i386/trap.c:348 (kgdb) dmesg: opyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #6: Thu Dec 2 15:55:20 GMT 1999 toor@rally3.jazz.att.com:/usr/src/sys/compile/RALLY3 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (348.49-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping = 1 Features=0x183f9ff real memory = 134217728 (131072K bytes) avail memory = 127102976 (124124K bytes) Preloaded elf kernel "kernel" at 0xc02d6000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02d609c. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 fxp0: irq 10 at device 18.0 on pci0 fxp0: Ethernet address 00:08:c7:89:57:ed isab0: at device 20.0 on pci0 isa0: on isab0 ata-pci0: at device 20.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 20.2 chip1: at device 20.3 on pci0 isa0: unexpected tag 14 isa0: unexpected tag 14 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown0: at port 0x268-0x26f on isa0 pcm0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa 0 unknown1: at iomem 0-0x9ffff,0xe0000-0xfffff,0x100000-0x7ffffff,0xfffc 0000-0xffffffff,0xc9000-0xcbfff on isa0 unknown2: at port 0xf0-0xff irq 13 on isa0 unknown: can't assign resources unknown3: at port 0x40-0x43 irq 0 on isa0 unknown4: at port 0-0xf,0x80-0x8f,0xc0-0xdf drq 4 on isa0 unknown: can't assign resources unknown5: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown: can't assign resources unknown6: on isa0 unknown7: at port 0x10-0x1f,0x50-0x52,0x72-0x73,0x76-0x77,0x78-0x7f,0x 90-0x9f,0x15c-0x15d,0x4d0-0x4d1,0x77e-0x77f,0xc06-0xc07,0xc50-0xc51,0xc70-0xc77, 0xc82,0xcf8-0xcff on isa0 unknown8: at port 0xf800-0xf81f,0xf820-0xf83f,0xfc00-0xfc0f on isa0 ad0: ATA-4 disk at ata0 as master ad0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as master acd0: read 5500KB/s (5500KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked, lock protected Mounting root from ufs:/dev/wd0s1a WARNING: / was not properly dismounted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 14: 5:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from indyio.rz.uni-sb.de (indyio.rz.uni-sb.de [134.96.7.3]) by hub.freebsd.org (Postfix) with ESMTP id 8580B14F53; Thu, 2 Dec 1999 14:05:39 -0800 (PST) (envelope-from netchild@Leidinger.net) Received: from mars.rz.uni-sb.de (ns0.rz.uni-sb.de [134.96.7.5]) by indyio.rz.uni-sb.de (8.9.3/8.9.3) with ESMTP id XAA13600907; Thu, 2 Dec 1999 23:04:30 +0100 (CET) Received: from Magelan.Leidinger.net (maxtnt-239.telip.uni-sb.de [134.96.71.110]) by mars.rz.uni-sb.de (8.8.8/8.8.4/8.8.2) with ESMTP id XAA11172; Thu, 2 Dec 1999 23:04:36 +0100 (CET) Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id UAA02118; Thu, 2 Dec 1999 20:30:53 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <199912021930.UAA02118@Magelan.Leidinger.net> Date: Thu, 2 Dec 1999 20:30:52 +0100 (CET) From: Alexander Leidinger Subject: Re: Problem with syscons in VESA mode To: jhb@FreeBSD.ORG Cc: sobomax@altavista.net, current@FreeBSD.ORG, dot@dotat.at In-Reply-To: <199912021722.MAA47364@server.baldwin.cx> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2 Dec, John Baldwin wrote: >> It is interesting. Seems like it is not only VESA modes bug. Strange >> that nobody >> else observed this misbehaviour. > I have seen it in 132 x anything on both -stable and -current but just > haven't been bothered enough by it to complain. IŽve seen this once (but normaly I use a xterm): - current - 132x60 If I remember correcly switching virtual consoles didnŽt helped me. Bye, Alexander. -- Slower than a herd of turtles stampeding through peanut butter. http://netchild.home.pages.de Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 14:13:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 152A314F24; Thu, 2 Dec 1999 14:13:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA00629; Thu, 2 Dec 1999 14:06:58 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912022206.OAA00629@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: "Matthew N. Dodd" , Nick Hibma , Christopher Masto , Mike Smith , FreeBSD CURRENT Mailing List Subject: Re: PCCARD eject freeze (was Re: your mail) In-reply-to: Your message of "Thu, 02 Dec 1999 12:11:51 MST." <199912021911.MAA03854@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Dec 1999 14:06:58 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message "Matthew N. Dodd" writes: > : On Thu, 2 Dec 1999, Nick Hibma wrote: > : > PCMCIA has the problem that the hardware register you are talking to can > : > disappear on the spot, between 2 outb()s. > : > : Can't we do something about this using bus_space? This would give us a > : fair bit of overhead for PCMCIA devices as well as require us to more > : tightly couple newbus and bus_space (we'd probably want to 'cache' a > : function pointer to the method to avoid method lookup overhead.) > > I had the same thought, but w/o a signal or other out of band error > communication, I'm not sure how to implement this. You can't without a race. You'd have to poll the hardware before and after every I/O operation to ensure that it was still there. Yick. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 16:15:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 619A914D89 for ; Thu, 2 Dec 1999 16:15:21 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:dOeyIJ/Bb8H33TD9+vdAJ50mUNzhH2nI@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id JAA17511; Fri, 3 Dec 1999 09:13:12 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA29566; Fri, 3 Dec 1999 09:18:00 +0900 (JST) Message-Id: <199912030018.JAA29566@zodiac.mech.utsunomiya-u.ac.jp> To: sobomax@altavista.net Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Problem with syscons in VESA mode In-reply-to: Your message of "Thu, 02 Dec 1999 13:50:31 +0200." <38465D07.8A25A0D@altavista.net> References: <38465D07.8A25A0D@altavista.net> Date: Fri, 03 Dec 1999 09:17:59 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I'm using non-standard 100x37 console mode on my notebook, because in 80x25 >text mode letters seems too big for my 12' panel, while other modes doesn't >cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600 >100x37 mode (instead of default 80x25) with 8x16 font, and in most cases all >works just fine (including ncurses and dialog bases apps), but sometimes when >I'm building world or some other app text suddenly shifts from the edge of the >screen by several spaces and all text passed to the console after that also >being printed with that offset. For example: [...] This strange behavior was reported several times in the past. It must be related to screen update logic in syscons. But, I don't think we have successfully fixed it at that time :-( It's time to analyze the problem again... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 17:22:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 26BFD14ECC; Thu, 2 Dec 1999 17:22:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id RAA04101; Thu, 2 Dec 1999 17:21:55 -0800 Date: Thu, 2 Dec 1999 17:21:55 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. In-Reply-To: <19991125133001.64729@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I am truly f*cked now. I read enough of this thread, saw nothing new in UPDATING, and did the following: alpha kernel from today MAKEDEV from today (but not a make world install- the binaries/libs are ~week old) cannot get out of single user mode. fsck core dumps. Any failed command causes the single user shell to exit. What can I do to get out of this disaster other than attempt a reinstall? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 17:24:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from mojave.sitaranetworks.com (mojave.sitaranetworks.com [199.103.141.157]) by hub.freebsd.org (Postfix) with ESMTP id 6F2F414CB9; Thu, 2 Dec 1999 17:24:22 -0800 (PST) (envelope-from grog@mojave.sitaranetworks.com) Message-ID: <19991202202419.01433@mojave.sitaranetworks.com> Date: Thu, 2 Dec 1999 20:24:19 -0500 From: Greg Lehey To: mjacob@feral.com Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. Reply-To: Greg Lehey References: <19991125133001.64729@mojave.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Matthew Jacob on Thu, Dec 02, 1999 at 05:21:55PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 2 December 1999 at 17:21:55 -0800, Matthew Jacob wrote: > > Well, I am truly f*cked now. I read enough of this thread, saw nothing new > in UPDATING, and did the following: > > alpha > > kernel from today > MAKEDEV from today > (but not a make world install- the binaries/libs are ~week old) > > cannot get out of single user mode. fsck core dumps. Any failed command > causes the single user shell to exit. > > What can I do to get out of this disaster other than attempt a reinstall? Can't you boot from the old kernel? Or have you already wiped the bdevs? If so, how about the fixit floppy/CD-ROM? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 17:29:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 08B8414F67; Thu, 2 Dec 1999 17:29:16 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id RAA04139; Thu, 2 Dec 1999 17:29:14 -0800 Date: Thu, 2 Dec 1999 17:29:14 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. In-Reply-To: <19991202202419.01433@mojave.sitaranetworks.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can't you boot from the old kernel? Or have you already wiped the I can boot the old kernel. A MAKEDEV using the new MAKEDEV has now wiped all block devs, so swapon, etc. ,fail.. However, this is the conundrum- it's not safe to do a 'make installworld' on a two week old kernel, but the new kernel with old mount, fsck, etc., obviously cannot cope with the new 'raw-only' devices. An experience like this will move users to OpenBSD. This kind of jump up is completely unacceptable. > bdevs? If so, how about the fixit floppy/CD-ROM? This is alpha, and no floppy. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 17:35:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 11B5714FC2 for ; Thu, 2 Dec 1999 17:35:31 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA19055; Thu, 2 Dec 1999 17:34:56 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA13551; Thu, 2 Dec 1999 17:34:55 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 2 Dec 1999 17:34:55 -0800 (PST) Message-Id: <199912030134.RAA13551@vashon.polstra.com> To: dscheidt@enteract.com Subject: Re: World breakage in libpam? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , David Scheidt wrote: > Seeing this trying to build world, cvsup'd earlier today. > > cc -O -pipe -static -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING > -Wall -I/usr/src/libexec/ftpd/../../contrib-crypto/telnet -DINTERNAL_LS > -Dmain=ls_main -I/usr/src/libexec/ftpd/../../bin/ls > -I/usr/obj/usr/src/tmp/usr/include -o ftpd ftpd.o ftpcmd.o logwtmp.o > popen.o skey-stuff.o ls.o cmp.o print.o stat_flags.o util.o -lskey -lmd > -lcrypt -lutil -lpam > /usr/obj/usr/src/tmp/usr/lib/libpam.a(pam_static_modules.o): In function > `_pam_get_static_sym': > pam_static_modules.o(.text+0x299): undefined reference to > `rad_create_request' > pam_static_modules.o(.text+0x2af): undefined reference to `rad_strerror' > pam_static_modules.o(.text+0x2cc): undefined reference to `rad_put_string' > pam_static_modules.o(.text+0x2e9): undefined reference to `rad_put_string' ... I think it's because of the "-static" in the link command. I don't have time to find the fix at the moment, but if you look at src/bin/login you might be able to work it out yourself. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 18:25: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from imsp074.netvigator.com (imsp074.netvigator.com [205.252.144.129]) by hub.freebsd.org (Postfix) with ESMTP id D385A14CDE for ; Thu, 2 Dec 1999 18:25:01 -0800 (PST) (envelope-from c5666305@hkstar.com) Received: from imsp234.hkstar.com (imsp234.netvigator.com [208.151.73.70]) by imsp074.netvigator.com (8.9.3+Sun/8.9.1) with ESMTP id KAA08524; Fri, 3 Dec 1999 10:24:23 +0800 (HKT) Received: from localhost (c5666305@localhost) by imsp234.hkstar.com (8.8.8+Sun/8.8.8) with ESMTP id KAA28152; Fri, 3 Dec 1999 10:24:39 +0800 (HKT) X-Authentication-Warning: imsp234.hkstar.com: c5666305 owned process doing -bs Date: Fri, 3 Dec 1999 10:24:39 +0800 (HKT) From: Chan Yiu Wah To: freebsd-current@freebsd.org Cc: ein@hkstar.com Subject: panic after make new kernel with ctm source upto src-cur.4115 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello, I make world and new kernel with ctm source up to src-cur.4115 successfully. However, my system go to panic when I boot it with new kernel. The error was ======= Error ======= resume IOPL = 0 interrupt mask none <-- SMPXXX trap number = 12 mp_lock = 01000002 cpuid = 1 boot() call on cpu #1 . . ======= Error ======= any idea ? Thanks clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 19: 6:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4C17114FF7; Thu, 2 Dec 1999 19:06:12 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id WAA18323; Thu, 2 Dec 1999 22:05:04 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA70771; Thu, 2 Dec 1999 22:04:33 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 2 Dec 1999 22:04:33 -0500 (EST) To: mjacob@feral.com Cc: Greg Lehey , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. In-Reply-To: References: <19991202202419.01433@mojave.sitaranetworks.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14407.12709.371848.954058@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob writes: > > > Can't you boot from the old kernel? Or have you already wiped the > > I can boot the old kernel. A MAKEDEV using the new MAKEDEV has now wiped > all block devs, so swapon, etc. ,fail.. However, this is the conundrum- > it's not safe to do a 'make installworld' on a two week old kernel, but > the new kernel with old mount, fsck, etc., obviously cannot cope with the > new 'raw-only' devices. > > An experience like this will move users to OpenBSD. This kind of jump up > is completely unacceptable. Slow down. You are getting screwed by a combination of things. It isn't all phk's fault. The bdev elimination is one factor, but the most important one (the fsck/mount segv) is due to int/long breakage introduced version 1.85 of mount.h. This happened at the worst possible time (just after the bdev elimination). If I wasn't such a timid committer, I would have just committed the damned fix yesterday, before running it by Kirk & you wouldn't have had this problem. I tried to be vocal about it (messages to -alpha and -committers), but I guss that wasn't enought. Sorry, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 19:15:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8DBD214DAE; Thu, 2 Dec 1999 19:15:42 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id TAA04426; Thu, 2 Dec 1999 19:16:18 -0800 Date: Thu, 2 Dec 1999 19:16:18 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: FOLLOWUP: Re: HEADS-UP: bdevs have been assimilated. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry- maybe more of an edge case. It really has to do with 'ad' support seemingly vanishing from the alpha. Or, rather, it's hard to say exactly what has happened: Mounting root from ufs:/dev/rad0a no such device 'rad' setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 But then, there's an older system on da0: Mounting root from ufs:da0a WARNING: clock gained 14 days -- CHECK AND RESET THE DATE! swapon: adding /dev/da0b as swap device which makes it less of a bad bad but still very very annoying. It's hard to find out what's going on because even though there is some vague attempts to stop the loader (whereupon you get a phony 'ok' prompt), no passing of variables set there occurs (so no 'bootverbose'). So, it's conceivable that this is just edge case alpha breakage. With < 2 weeks to feature freeze for 4.0 it is very hard for some of us who attempt to make sure things we deliver actually work on both platforms if the second platform is broken. I'm plenty pissed off, but, c'est la vie... -matt On Thu, 2 Dec 1999, Matthew Jacob wrote: > > Well, I am truly f*cked now. I read enough of this thread, saw nothing new > in UPDATING, and did the following: > > alpha > > kernel from today > MAKEDEV from today > (but not a make world install- the binaries/libs are ~week old) > > cannot get out of single user mode. fsck core dumps. Any failed command > causes the single user shell to exit. > > What can I do to get out of this disaster other than attempt a reinstall? > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 19:23: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7D15114C04; Thu, 2 Dec 1999 19:23:00 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id TAA04452; Thu, 2 Dec 1999 19:23:20 -0800 Date: Thu, 2 Dec 1999 19:23:20 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. In-Reply-To: <14407.12709.371848.954058@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (removed from general list) > Slow down. You are getting screwed by a combination of things. It > isn't all phk's fault. > > The bdev elimination is one factor, but the most important one (the > fsck/mount segv) is due to int/long breakage introduced version 1.85 > of mount.h. This happened at the worst possible time (just after the > bdev elimination). > > If I wasn't such a timid committer, I would have just committed the > damned fix yesterday, before running it by Kirk & you wouldn't have > had this problem. I tried to be vocal about it (messages to -alpha > and -committers), but I guss that wasn't enought. Well, I wasn't back in town until last night with 5000 messages to catch up on. Sorry for not getting your questions first. There are other things broken too. Oh well- I really shouldn't get wired. *BSD will get taken as a serious effort as much as it deserves based upon what actually *occurs*, not what I would *wish* to actually occur.... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 19:30:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 995F914BC8; Thu, 2 Dec 1999 19:30:41 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id TAA04471; Thu, 2 Dec 1999 19:30:49 -0800 Date: Thu, 2 Dec 1999 19:30:49 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Sorry.... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I wasn't back in town until last night with 5000 messages to catch > up on. Sorry for not getting your questions first. > > There are other things broken too. Oh well- I really shouldn't get wired. > *BSD will get taken as a serious effort as much as it deserves based upon > what actually *occurs*, not what I would *wish* to actually occur.... Sorry- I shouldn't get so bitchy. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 19:54:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 50F3F14EB0 for ; Thu, 2 Dec 1999 19:54:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA04033; Thu, 2 Dec 1999 19:54:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912030354.TAA04033@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: FOLLOWUP: Re: HEADS-UP: bdevs have been assimilated. In-reply-to: Your message of "Thu, 02 Dec 1999 19:16:18 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Dec 1999 19:54:45 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Sorry- maybe more of an edge case. It really has to do with 'ad' support > seemingly vanishing from the alpha. Or, rather, it's hard to say exactly > what has happened: > > > Mounting root from ufs:/dev/rad0a > no such device 'rad' You never mount 'r' devices. That should be '/dev/ad0a', and you can override the default with either: set vfs.root.mountfrom="ufs:/dev/ad0a" in the loader at the 'ok' prompt, or by entering 'ufs:/dev/ad0a' at the emergency recovery prompt that you get after the error messages you've quoted above. > But then, there's an older system on da0: > > Mounting root from ufs:da0a > WARNING: clock gained 14 days -- CHECK AND RESET THE DATE! > swapon: adding /dev/da0b as swap device > > which makes it less of a bad bad but still very very annoying. It's hard > to find out what's going on because even though there is some vague > attempts to stop the loader (whereupon you get a phony 'ok' prompt), no > passing of variables set there occurs (so no 'bootverbose'). The variable's name is boot_verbose, but the Alpha has never supported it (a combination of oversight and overbusiness on both my part and Doug's). You'll find that 'boot -v' and 'load kernel -v' will achieve the desired results in the meantime, and I'll try to get it working "right" soon now that I have a 'real' alpha to work on. I'm also curious as to what's "phony" about the 'ok' prompt? Is it just that things aren't 'ok'? 8) > So, it's conceivable that this is just edge case alpha breakage. With < 2 > weeks to feature freeze for 4.0 it is very hard for some of us who attempt > to make sure things we deliver actually work on both platforms if the > second platform is broken. I'm plenty pissed off, but, c'est la vie... So we should, like, feature freeze before we feature freeze? That's not so good. I don't mean to be insulting or anything, but so far most of your problems appear to be pilot error. If you take them out of the picture, it's not _really_ that bad. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 22:44:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DAC5814CFA; Thu, 2 Dec 1999 22:44:32 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA04823; Thu, 2 Dec 1999 22:44:49 -0800 Date: Thu, 2 Dec 1999 22:44:49 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Greg Lehey Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Apologies In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I realize that I have been much more upset and unpleasant about this than the situation warranted, and I would like to extend my apologies to all and sundry for venting my frustration so publicly. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 23:34:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 68AF914E0A for ; Thu, 2 Dec 1999 23:34:10 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA10726; Thu, 2 Dec 1999 23:34:03 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA84287; Thu, 2 Dec 1999 23:34:01 -0800 (PST) (envelope-from obrien) Date: Thu, 2 Dec 1999 23:34:01 -0800 From: "David O'Brien" To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. Message-ID: <19991202233401.A84265@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991125133001.64729@mojave.sitaranetworks.com> <19991202202419.01433@mojave.sitaranetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991202202419.01433@mojave.sitaranetworks.com>; from grog@mojave.sitaranetworks.com on Thu, Dec 02, 1999 at 08:24:19PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 02, 1999 at 08:24:19PM -0500, Greg Lehey wrote: > Can't you boot from the old kernel? Or have you already wiped the > bdevs? If so, how about the fixit floppy/CD-ROM? At 2MB the Alpha fixit floppy isn't very useful. Nor is there a live files system for the Alpha. Nor can you even boot sysinstall and get a shell if you use a serial console. All-in-all recovery on the Alpha is "lacking". -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 2 23:35: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail001.mediacity.com (mail001.mediacity.com [205.216.172.9]) by hub.freebsd.org (Postfix) with SMTP id 637FE151CE for ; Thu, 2 Dec 1999 23:34:50 -0800 (PST) (envelope-from spock@techfour.net) Received: (qmail 20726 invoked from network); 3 Dec 1999 07:34:30 -0000 Received: from cm-208-138-198-17.fredericksburg.mg.ispchannel.com (HELO enterprise.muriel.penguinpowered.com) (208.138.198.17) by mail001.mediacity.com with SMTP; 3 Dec 1999 07:34:30 -0000 Content-Length: 1779 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 X-SENDERNAME: `Mike Heffner` Date: Fri, 03 Dec 1999 02:34:42 -0500 (EST) From: Mike Heffner To: FreeBSD-current Subject: incorrect irqs with pci devices Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have recently noticed that the irqs for my PCI devices are being screwed up somehow. It is easily noticeable with dmesg, the correct one's are in paren.: vga-pci0: irq 17(real 11) at device 0.0 on pci1 ^^ ^^ pcm1: irq 16(real 10) at device 15.0 on pci0 ^^ ^^ ed0: irq 18(real 9) at device 18.0 on pci0 ^^ ^ I used the following hack to show the real irqs: --- pci.c.orig Fri Dec 3 02:20:56 1999 +++ pci.c Fri Dec 3 02:25:08 1999 @@ -1149,8 +1149,10 @@ retval += bus_print_child_header(dev, child); - if (cfg->intpin > 0 && cfg->intline != 255) + if (cfg->intpin > 0 && cfg->intline != 255){ retval += printf(" irq %d", cfg->intline); + printf("(real %u)", pci_read_config(child, PCI_INTERRUPT_REG, 1)); + } retval += printf(" at device %d.%d", pci_get_slot(child), pci_get_function(child)); pciconf also shows the incorrect irqs (but I can read the correct ones with the -r option for pciconf). Is this a known problem, is anyone else experiencing this? I haven't really looked at any of the code yet ( i got lost). Here's some other relevant info (more available on request): pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 --------------------------------- Mike Heffner Fredericksburg, VA ICQ# 882073 Date: 03-Dec-99 Time: 02:08:53 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 0:21:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 215B7150E6 for ; Fri, 3 Dec 1999 00:20:47 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA03623; Fri, 3 Dec 1999 09:18:10 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. In-reply-to: Your message of "Thu, 02 Dec 1999 17:21:55 PST." Date: Fri, 03 Dec 1999 09:18:09 +0100 Message-ID: <3621.944209089@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: > >Well, I am truly f*cked now. I read enough of this thread, saw nothing new >in UPDATING, and did the following: > >alpha > > kernel from today > MAKEDEV from today > (but not a make world install- the binaries/libs are ~week old) > >cannot get out of single user mode. fsck core dumps. Any failed command >causes the single user shell to exit. This doesn't sound like a /dev related problem to me. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 0:22:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CC43C150F1 for ; Fri, 3 Dec 1999 00:20:57 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id AAA05055; Fri, 3 Dec 1999 00:21:16 -0800 Date: Fri, 3 Dec 1999 00:21:16 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. In-Reply-To: <3621.944209089@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message , Matthew > Jacob writes: > > > >Well, I am truly f*cked now. I read enough of this thread, saw nothing new > >in UPDATING, and did the following: > > > >alpha > > > > kernel from today > > MAKEDEV from today > > (but not a make world install- the binaries/libs are ~week old) > > > >cannot get out of single user mode. fsck core dumps. Any failed command > >causes the single user shell to exit. > > This doesn't sound like a /dev related problem to me. You're probably right about this. Maybe we should all call it "Matt's really bad day where he got vicious" and we'll try again tomorrow after a new update/nightly build. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 0:22:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 709B6151D6 for ; Fri, 3 Dec 1999 00:22:47 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA03695; Fri, 3 Dec 1999 09:21:13 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: FOLLOWUP: Re: HEADS-UP: bdevs have been assimilated. In-reply-to: Your message of "Thu, 02 Dec 1999 19:16:18 PST." Date: Fri, 03 Dec 1999 09:21:13 +0100 Message-ID: <3693.944209273@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: > >Sorry- maybe more of an edge case. It really has to do with 'ad' support >seemingly vanishing from the alpha. Or, rather, it's hard to say exactly >what has happened: > > >Mounting root from ufs:/dev/rad0a >no such device 'rad' Bruce and Mike smith took out a testing-shim a little early which allowed us to test with /dev/r* in /etc/fstab. Change your /etc/fstab to read /dev/ad0a and you should be happy again. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 0:28:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4678D15086 for ; Fri, 3 Dec 1999 00:28:07 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id AAA05073; Fri, 3 Dec 1999 00:28:54 -0800 Date: Fri, 3 Dec 1999 00:28:54 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: FOLLOWUP: Re: HEADS-UP: bdevs have been assimilated. In-Reply-To: <3693.944209273@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message , Matthew > Jacob writes: > > > >Sorry- maybe more of an edge case. It really has to do with 'ad' support > >seemingly vanishing from the alpha. Or, rather, it's hard to say exactly > >what has happened: > > > > > >Mounting root from ufs:/dev/rad0a > >no such device 'rad' > > Bruce and Mike smith took out a testing-shim a little early which > allowed us to test with /dev/r* in /etc/fstab. Change your > /etc/fstab to read /dev/ad0a and you should be happy again. Actually, no, I'm not- the 'rad' was less worrisome than the other stuff (like fsck core dumping, mount dyings, etc.). but, but we'll see what happens tomorrow. I'll be up to date and have a fresh build with the new mount.h and I'll make it work if it doesn't (I have to as I have too many other things backed up behind this toe stub). I probably should have used an i386 to test this change first rather than an alpha. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 1: 1:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 8C5FA14C57 for ; Fri, 3 Dec 1999 01:01:44 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-25.iptelecom.net.ua [212.9.227.25]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id LAA15945; Fri, 3 Dec 1999 11:04:46 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id KAA10599; Fri, 3 Dec 1999 10:59:31 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <38478671.F57E2780@altavista.net> Date: Fri, 03 Dec 1999 10:59:29 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: current@FreeBSD.ORG Subject: Re: Problem with syscons in VESA mode References: <38465D07.8A25A0D@altavista.net> <199912030018.JAA29566@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > >I'm using non-standard 100x37 console mode on my notebook, because in 80x25 > >text mode letters seems too big for my 12' panel, while other modes doesn't > >cover all panel size. So I've patched vidcontrol to switch to the VESA_800x600 > >100x37 mode (instead of default 80x25) with 8x16 font, and in most cases all > >works just fine (including ncurses and dialog bases apps), but sometimes when > >I'm building world or some other app text suddenly shifts from the edge of the > >screen by several spaces and all text passed to the console after that also > >being printed with that offset. For example: > [...] > > This strange behavior was reported several times in the past. It must > be related to screen update logic in syscons. But, I don't think we > have successfully fixed it at that time :-( > > It's time to analyze the problem again... Obviously... If any help with debugging/testing would be necessary please do not hesitate to contact me. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 1:46:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id BCD3C14DAC for ; Fri, 3 Dec 1999 01:46:38 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA72257; Fri, 3 Dec 1999 09:53:32 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 3 Dec 1999 09:53:31 +0000 (GMT) From: Doug Rabson To: Mike Heffner Cc: FreeBSD-current Subject: Re: incorrect irqs with pci devices In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 3 Dec 1999, Mike Heffner wrote: > Hi, > > I have recently noticed that the irqs for my PCI devices are being screwed up > somehow. It is easily noticeable with dmesg, the correct one's are in paren.: Is this an SMP box by any chance? Does the kernel work with the irqs which it chose? -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 1:58:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id 2A6BD150A3 for ; Fri, 3 Dec 1999 01:58:33 -0800 (PST) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id KAA24394 for ; Fri, 3 Dec 1999 10:57:29 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.3/8.9.3) id KAA70793 for current@FreeBSD.ORG; Fri, 3 Dec 1999 10:57:29 +0100 (CET) Date: Fri, 3 Dec 1999 10:57:28 +0100 From: Cejka Rudolf To: current@FreeBSD.ORG Subject: Re: Problem with syscons in VESA mode Message-ID: <19991203105728.A68768@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Kazutaka YOKOTA on Fri, Dec 03, 1999 at 09:17:59AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote (1999/12/03): > This strange behavior was reported several times in the past. It must > be related to screen update logic in syscons. But, I don't think we > have successfully fixed it at that time :-( > It's time to analyze the problem again... Yes. I know about this problem too but I have no time to fix and test it. Is anybody interested in bug reports? ;-) * Left margin moving to the right is related to the screen width not divisible by 8 and an use of tabulators at the end of line after the last valid tab position. So the same problem could be seen for example with screen width 90, which is accessible for all -current users: Let's suppose that cursor range is 0..89: If the cursor is on 80..87, it will move to position 88 and everything is ok. If the cursor is on 88..89, the position is calculated properly (you can switch to another console then return and cursor will be on the right position on column 0), but cursor is moved incorrectly on column 8 on the next line and next lines are moved to the left too until you switch between consoles. I think the fix should be trivial (syscons.c,v 1.327) - but it is speculated right now without testing: -- *** syscons.c Sun Nov 28 15:29:28 1999 --- /tmp/syscons.c Fri Dec 3 10:28:59 1999 *************** *** 2946,2956 **** case 0x09: /* non-destructive tab */ mark_for_update(scp, scp->cursor_pos); scp->cursor_pos +=3D (8 - scp->xpos % 8u); - mark_for_update(scp, scp->cursor_pos); if ((scp->xpos +=3D (8 - scp->xpos % 8u)) >=3D scp->xsize) { scp->xpos =3D 0; scp->ypos++; } break; =20 case 0x0a: /* newline, same pos */ --- 2946,2957 ---- case 0x09: /* non-destructive tab */ mark_for_update(scp, scp->cursor_pos); scp->cursor_pos +=3D (8 - scp->xpos % 8u); if ((scp->xpos +=3D (8 - scp->xpos % 8u)) >=3D scp->xsize) { scp->xpos =3D 0; scp->ypos++; + scp->cursor_pos =3D scp->xsize * scp->ypos; } + mark_for_update(scp, scp->cursor_pos); break; =20 case 0x0a: /* newline, same pos */ -- * There are another problems with syscons updating: When a block of text is selected by mouse, it should be hidden when text in this block is changed. Unfortunately in many cases the block stays selected on the same position... I think we should learn from xterm. (But when I tested xterm, it had some problems too...) I have created small testing script which can show all upcoming problems (I think). But in some cases you have to know which block of text should be selected... -- #!/usr/local/bin/bash c_before() { tput clear I=3D20 while [ $I -gt 0 ]; do echo "$I $I $I $I $I $I $I $I $I $I $I $I $I $I $I $I $I $I $I $I" I=3D`expr $I - 1` done tput sc ; tput cm $1 $2 ; echo -n "*" ; tput rc echo "Mark a block and then press Enter and after test too..." read Q tput cm $1 $2 } c_after() { read Q clear } c_cycle() { I=3D$1 while [ $I -gt 0 ]; do echo -n $2 I=3D`expr $I - 1` done } c_print() { tput cm 89 8 printf "\t\nThis text must start at the beginning of the line!\n" } clear PS3=3D"Which test? " select X in Tab Text Mu1 El0 El1 El2 Il1 Dl1 Dc1 Ic1 Su1 Sd1 Ec1 Sw1 Quit ;= do if [ -z "$X" ]; then echo "Unknown selection" break fi if [ $X =3D Quit ]; then break fi c_before 40 8 case $X in Tab) c_print ;; # Bug - 90x30 and tab at the end of line Text) c_cycle 4 "Text " ;; # Bug - remove_markings Mu1) c_cycle 22 "=1BM" ;; # Bug - remove_markings El0) c_cycle 1 "=1B[0K" ;; # Bug - remove_markings El1) c_cycle 1 "=1B[1K" ;; # Bug - remove_markings El2) c_cycle 1 "=1B[2K" ;; # Bug - remove_markings Il1) c_cycle 5 "=1B[1L" ;; # Bug - remove_markings Dl1) c_cycle 5 "=1B[1M" ;; # Bug - remove_markings Dc1) c_cycle 10 "=1B[1P" ;; # Bug - remove_markings Ic1) c_cycle 10 "=1B[1@" ;; # Bug - remove_markings Su1) c_cycle 10 "=1B[1S" ;; # Bug - remove_markings Sd1) c_cycle 10 "=1B[1T" ;; # Bug - remove_markings Ec1) c_cycle 1 "=1B[10X" ;; # Bug - remove_markings Sw1) c_cycle 1 "=1B[100z" ;; # Bug - don't beep after this esac c_after done -- I have a fast-partial-fix for syscons.c,v 1.308. But please don't apply this patch - it should be much more intelligent than following patch - the block is hidden in all cases but I would like to see solution similar to xterm - a block is hidden only in needed cases. -- *** syscons.c Thu Jun 24 20:14:56 1999 --- syscons.c.new Thu Jun 24 20:16:52 1999 *************** *** 2442,2447 **** --- 2442,2448 ---- sc_vtb_ins(&scp->vtb, 0, scp->xsize, sc->scr_map[0x20], scp->term.cur_color); mark_all(scp); + sc_remove_cutmarking(scp); } break; #if notyet *************** *** 2567,2572 **** --- 2568,2574 ---- mark_for_update(scp, scp->cursor_pos); mark_for_update(scp, scp->cursor_pos + scp->xsize - 1 - scp->xpos); + sc_remove_cutmarking(scp); break; case 1: /* clear from beginning of line to cursor */ sc_vtb_erase(&scp->vtb, scp->cursor_pos - scp->xpos, *************** *** 2574,2579 **** --- 2576,2582 ---- sc->scr_map[0x20], scp->term.cur_color); mark_for_update(scp, scp->ypos * scp->xsize); mark_for_update(scp, scp->cursor_pos); + sc_remove_cutmarking(scp); break; case 2: /* clear entire line */ sc_vtb_erase(&scp->vtb, scp->cursor_pos - scp->xpos, *************** *** 2581,2586 **** --- 2584,2590 ---- sc->scr_map[0x20], scp->term.cur_color); mark_for_update(scp, scp->ypos * scp->xsize); mark_for_update(scp, (scp->ypos + 1) * scp->xsize - 1); + sc_remove_cutmarking(scp); break; } break; *************** *** 2593,2598 **** --- 2597,2603 ---- sc->scr_map[0x20], scp->term.cur_color); mark_for_update(scp, scp->ypos * scp->xsize); mark_for_update(scp, scp->xsize * scp->ysize - 1); + sc_remove_cutmarking(scp); break; =20 case 'M': /* Delete n lines */ *************** *** 2603,2608 **** --- 2608,2614 ---- sc->scr_map[0x20], scp->term.cur_color); mark_for_update(scp, scp->ypos * scp->xsize); mark_for_update(scp, scp->xsize * scp->ysize - 1); + sc_remove_cutmarking(scp); break; =20 case 'P': /* Delete n chars */ *************** *** 2615,2620 **** --- 2621,2627 ---- sc->scr_map[0x20], scp->term.cur_color); mark_for_update(scp, scp->cursor_pos); mark_for_update(scp, scp->cursor_pos + n + count - 1); + sc_remove_cutmarking(scp); break; =20 case '@': /* Insert n chars */ *************** *** 2627,2632 **** --- 2634,2640 ---- sc->scr_map[0x20], scp->term.cur_color); mark_for_update(scp, scp->cursor_pos); mark_for_update(scp, scp->cursor_pos + n + count - 1); + sc_remove_cutmarking(scp); break; =20 case 'S': /* scroll up n lines */ *************** *** 2636,2641 **** --- 2644,2650 ---- sc_vtb_delete(&scp->vtb, 0, n * scp->xsize, sc->scr_map[0x20], scp->term.cur_color); mark_all(scp); + sc_remove_cutmarking(scp); break; =20 case 'T': /* scroll down n lines */ *************** *** 2645,2650 **** --- 2654,2660 ---- sc_vtb_ins(&scp->vtb, 0, n * scp->xsize, sc->scr_map[0x20], scp->term.cur_color); mark_all(scp); + sc_remove_cutmarking(scp); break; =20 case 'X': /* erase n characters in line */ *************** *** 2655,2660 **** --- 2665,2671 ---- sc->scr_map[0x20], scp->term.cur_color); mark_for_update(scp, scp->cursor_pos); mark_for_update(scp, scp->cursor_pos + n - 1); + sc_remove_cutmarking(scp); break; =20 case 'Z': /* move n tabs backwards */ -- --=20 Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 2:23:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from dnvrpop1.dnvr.uswest.net (dnvrpop1.dnvr.uswest.net [206.196.128.3]) by hub.freebsd.org (Postfix) with SMTP id 9DE1214C84 for ; Fri, 3 Dec 1999 02:23:13 -0800 (PST) (envelope-from Davec@unforgettable.com) Received: (qmail 3489 invoked by alias); 3 Dec 1999 10:21:09 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 3483 invoked by uid 0); 3 Dec 1999 10:21:09 -0000 Received: from odsl228.dnvr.uswest.net (HELO Amber.XtremeDev.com) (209.181.79.228) by dnvrpop1.dnvr.uswest.net with SMTP; 3 Dec 1999 10:21:09 -0000 From: Davec Reply-To: Davec@unforgettable.com To: freebsd-current@FreeBSD.ORG Subject: ssh2 port Date: Fri, 3 Dec 1999 03:19:07 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99120303211100.27957@Amber.XtremeDev.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tried to build ssh2 (after installing ssh1) from the ports, and I got the following error: SHELL@:No such file or directory I added USE_GMAKE= yes to the security/ssh2/Makefile, and tried it again and it completed successfully. Has anyone else came across this? Davec -- Davec@unforgettable.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 2:51:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from jfh00.fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by hub.freebsd.org (Postfix) with ESMTP id 27E78150E0 for ; Fri, 3 Dec 1999 02:51:36 -0800 (PST) (envelope-from jfh@jfh00.fernuni-hagen.de) Received: (from jfh@localhost) by jfh00.fernuni-hagen.de (8.9.3/8.9.3) id LAA69397; Fri, 3 Dec 1999 11:51:23 +0100 (CET) (envelope-from jfh) To: freebsd-current@freebsd.org Subject: Re: gcc-2.95.2, jade and freebsd-sgml-documentationSubject: From: Fritz Heinrichmeyer Date: 03 Dec 1999 11:51:22 +0100 Message-ID: Lines: 13 User-Agent: Gnus/5.070099 (Pterodactyl Gnus v0.99) XEmacs/21.2 (Yoko) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thanks for the responses! "make" and "make install" worked fine with the newest port changes, but when making the handbook jade dumped core at last. Memory consumption raised to over 30 MByte before the core dump. I made a mistake in the former posting as i tried to compile jade-1.2.2.tar.gz and forgot to mention this fact, sorry. -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://ES-i2.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 3:28:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 33A3714F1F for ; Fri, 3 Dec 1999 03:28:22 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:Wals/oAyiboHMndBslYOZlUal5QkCrZ/@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id UAA24157; Fri, 3 Dec 1999 20:27:04 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id UAA20911; Fri, 3 Dec 1999 20:31:57 +0900 (JST) Message-Id: <199912031131.UAA20911@zodiac.mech.utsunomiya-u.ac.jp> To: Cejka Rudolf Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Problem with syscons in VESA mode In-reply-to: Your message of "Fri, 03 Dec 1999 10:57:28 +0100." <19991203105728.A68768@dcse.fee.vutbr.cz> References: <19991203105728.A68768@dcse.fee.vutbr.cz> Date: Fri, 03 Dec 1999 20:31:56 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Yes. I know about this problem too but I have no time to fix and test >it. Is anybody interested in bug reports? ;-) > >* Left margin moving to the right is related to the screen width not > divisible by 8 and an use of tabulators at the end of line after the > last valid tab position. So the same problem could be seen for > example with screen width 90, which is accessible for all [...] > I think the fix should be trivial (syscons.c,v 1.327) - but it is > speculated right now without testing: This is an excellent analysis. I will test your patch. Thank you. >* There are another problems with syscons updating: When a block > of text is selected by mouse, it should be hidden when text in this > block is changed. Unfortunately in many cases the block stays > selected on the same position... I think we should learn from > xterm. (But when I tested xterm, it had some problems too...) This is a known problem which I haven't worked on... ;-< Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 3:33:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 72E7614F1F for ; Fri, 3 Dec 1999 03:33:40 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-47.iptelecom.net.ua [212.9.227.47]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA08540; Fri, 3 Dec 1999 13:36:50 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id NAA12429; Fri, 3 Dec 1999 13:32:48 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <3847AA5D.5947E0EE@altavista.net> Date: Fri, 03 Dec 1999 13:32:45 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Cejka Rudolf Cc: current@FreeBSD.ORG Subject: Re: Problem with syscons in VESA mode References: <19991203105728.A68768@dcse.fee.vutbr.cz> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cejka Rudolf wrote: > Kazutaka YOKOTA wrote (1999/12/03): > > This strange behavior was reported several times in the past. It must > > be related to screen update logic in syscons. But, I don't think we > > have successfully fixed it at that time :-( > > It's time to analyze the problem again... > > Yes. I know about this problem too but I have no time to fix and test > it. Is anybody interested in bug reports? ;-) > > * Left margin moving to the right is related to the screen width not > divisible by 8 and an use of tabulators at the end of line after the > last valid tab position. So the same problem could be seen for > example with screen width 90, which is accessible for all > -current users: Let's suppose that cursor range is 0..89: If the > cursor is on 80..87, it will move to position 88 and everything is ok. > If the cursor is on 88..89, the position is calculated properly (you > can switch to another console then return and cursor will be on > the right position on column 0), but cursor is moved incorrectly > on column 8 on the next line and next lines are moved to the left too > until you switch between consoles. > I think the fix should be trivial (syscons.c,v 1.327) - but it is > speculated right now without testing: > > -- > *** syscons.c Sun Nov 28 15:29:28 1999 > --- /tmp/syscons.c Fri Dec 3 10:28:59 1999 > *************** > *** 2946,2956 **** > [...] Thanks! It seems fixed my problems with syscons. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 4:48:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from camtech.net.au (goliath.camtech.net.au [203.5.73.2]) by hub.freebsd.org (Postfix) with SMTP id D2E3F14E5C for ; Fri, 3 Dec 1999 04:48:47 -0800 (PST) (envelope-from matt@camtech.net.au) Received: from dialup-ad-10-39.camtech.net.au ([203.28.1.167]) by camtech.net.au ; Fri, 03 Dec 1999 23:18:39 +1030 Date: Fri, 3 Dec 1999 23:18:39 +1030 (CST) From: Matthew Thyer X-Sender: matt@localhost Reply-To: thyerm@camtech.net.au To: Nick Hibma Cc: current@FreeBSD.ORG Subject: Re: How do I get a USB mouse working in todays -CURRENT ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks Nick, my USB mouse works perfectly now. On Thu, 2 Dec 1999, Nick Hibma wrote: > > The problem is that the mouse doesn't work (its not a hardware problem), > > all I get whenever I move the mouse are lots of the following messages > > on the console: > > > > Discarded 7 bytes in queue > > This means that your mouse is working but moused is closing while the > buffer is not empty yet. This looks a lot like my mistake I fixed > earlier. > > > Do I need to change /etc/usbd.conf in some way ? > > No, you are probably looking at a stale moused.c. Please update the file > /usr/src/usr.sbin/moused/moused.c with the following diff (there is an > extra semicolon at the end of that line) and execute make&&make install > in that directory: > > Index: src/usr.sbin/moused/moused.c > =================================================================== > RCS file: /home/ncvs/src/usr.sbin/moused/moused.c,v > retrieving revision 1.32 > retrieving revision 1.33 > diff -u -w -r1.32 -r1.33 > --- moused.c 1999/11/29 17:21:07 1.32 > +++ moused.c 1999/11/30 10:20:33 1.33 > @@ -746,7 +746,7 @@ > } > > /* mouse event */ > - if (read(rodent.mfd, &b, 1) == -1); > + if (read(rodent.mfd, &b, 1) == -1) > return; /* file seems to be closed on us */ > > if (r_protocol(b, &action)) { /* handler detected action */ > > Nick > -- > hibma@skylink.it > n_hibma@freebsd.org USB project > http://www.etla.net/~n_hibma/ > > -- /=======================================================================\ | Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au | \=======================================================================/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 6:56:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail001.mediacity.com (mail001.mediacity.com [205.216.172.9]) by hub.freebsd.org (Postfix) with SMTP id D2EBD15176 for ; Fri, 3 Dec 1999 06:56:30 -0800 (PST) (envelope-from spock@techfour.net) Received: (qmail 2165 invoked from network); 3 Dec 1999 14:55:27 -0000 Received: from cm-208-138-198-17.fredericksburg.mg.ispchannel.com (HELO enterprise.muriel.penguinpowered.com) (208.138.198.17) by mail001.mediacity.com with SMTP; 3 Dec 1999 14:55:27 -0000 Content-Length: 668 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: X-SENDERNAME: `Mike Heffner` Date: Fri, 03 Dec 1999 09:55:43 -0500 (EST) From: Mike Heffner To: Doug Rabson Subject: Re: incorrect irqs with pci devices Cc: FreeBSD-current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Dec-99 Doug Rabson said: | On Fri, 3 Dec 1999, Mike Heffner wrote: | |> Hi, |> |> I have recently noticed that the irqs for my PCI devices are being screwed |> up |> somehow. It is easily noticeable with dmesg, the correct one's are in |> paren.: | | Is this an SMP box by any chance? Does the kernel work with the irqs which | it chose? | Yes, it is a SMP box, and yes, the devices work fine. I just thought it was odd that the kernel would report incorrect ones. --------------------------------- Mike Heffner Fredericksburg, VA ICQ# 882073 Date: 03-Dec-99 Time: 09:54:12 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 7:58:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from hurricane.columbus.rr.com (columbus.rr.com [204.210.252.19]) by hub.freebsd.org (Postfix) with ESMTP id DEEC914BE4 for ; Fri, 3 Dec 1999 07:58:18 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([24.95.60.151]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Fri, 3 Dec 1999 10:55:40 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id KAA05419; Fri, 3 Dec 1999 10:55:38 -0500 (EST) (envelope-from caa) Date: Fri, 3 Dec 1999 10:55:38 -0500 From: "Charles Anderson" To: Davec Cc: freebsd-current@FreeBSD.ORG Subject: Re: ssh2 port Message-ID: <19991203105538.A5382@midgard.dhs.org> References: <99120303211100.27957@Amber.XtremeDev.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <99120303211100.27957@Amber.XtremeDev.com>; from Davec on Fri, Dec 03, 1999 at 03:19:07AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the same type of problem compiling rpm (so I could install the latest linux_base to try vmware) My problem turned out to be I had autoconf 2.12 installed and I needed 2.13 the @SHELL@ is supposed to be substituted by configure, but wasn't because of the autoconf bit. Check your autoconf. -Charlie On Fri, Dec 03, 1999 at 03:19:07AM -0700, Davec wrote: > Tried to build ssh2 (after installing ssh1) from the ports, and I got the > following error: > > SHELL@:No such file or directory > > I added USE_GMAKE= yes to the security/ssh2/Makefile, and tried it again > and it completed successfully. Has anyone else came across this? > Davec@unforgettable.com -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 8:56:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id AB7E415341 for ; Fri, 3 Dec 1999 08:56:45 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA08053; Fri, 3 Dec 1999 11:56:24 -0500 (EST) (envelope-from wollman) Date: Fri, 3 Dec 1999 11:56:24 -0500 (EST) From: Garrett Wollman Message-Id: <199912031656.LAA08053@khavrinen.lcs.mit.edu> To: Mike Heffner Cc: Doug Rabson , FreeBSD-current Subject: Re: incorrect irqs with pci devices In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Yes, it is a SMP box, and yes, the devices work fine. I just thought it was odd > that the kernel would report incorrect ones. They are not incorrect. SMP uses a different interrupt system. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 9:10:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B0B201504A; Fri, 3 Dec 1999 09:10:10 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA06421; Fri, 3 Dec 1999 09:11:23 -0800 Date: Fri, 3 Dec 1999 09:11:23 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. In-Reply-To: <36126.943469434@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With todays' build, the previous problems went away. Other problems have replaced them (sio's wierd again for alpha), but that's a different story. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 9:27:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 7D10015025 for ; Fri, 3 Dec 1999 09:27:03 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id LAA44631 for current@FreeBSD.org; Fri, 3 Dec 1999 11:25:18 -0600 (CST) (envelope-from dan) Date: Fri, 3 Dec 1999 11:25:18 -0600 From: Dan Nelson To: current@FreeBSD.org Subject: NFS client zeroing out blocks on write? Message-ID: <19991203112518.A43843@dan.emsphone.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="UlVJffcvxoiEqYs2" X-Mailer: Mutt 1.0i X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii I just upgraded a server from 2.2.8 to -current (991201 kernel) and am seeing some NFS corruption. It looks like byte ranges are getting zeroed out by the client (or not getting written at all, and the server at the other end is filling with zeros?). I've seen it while writing to both a Solaris 2.6 server (NFSv3) and a Netware NFS server (NFSv2), so I'm pretty sure it's the client causing the problem. Details: 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Thu Dec 2 17:07:57 CST 1999 CPU: Dual Pentium III/Xeon 600 Mhz RAM: 256MB NIC: fxp0, full-duplex 100mbit NFS mount point: /mnt/filesystem/u01, mounting a Solaris 2.6 box also with a 100mbit full-duplex net connection, 8K NFS blocksize, UDP, via amd. My testcase is a 7-gig text file that I'm copying around with the following commands: $ cd /net/remotesystem/u01 $ split -b 1000000000 /u01/bigfile.txt file creating seven 1-gig files fileaa .. fileag (running at a nice rate of 5-6 MB/sec :). I then run "blankcheck" (attached) to scan the file for runs of zeroes, and get the following: $ for i in filea{a,b,c,d,e,f} ; do echo $i ; ./blankcheck < $i ; done fileaa fileab 168173568-168179199(5632) 384966656-384972287(5632) 385753088-385758719(5632) ( snip 156 lines just like the above, all ranges 5632 bytes in size ) 464068608-464074239(5632) 464723968-464729599(5632) 465248256-465253887(5632) fileac 203448320-203451391(3072) filead fileae 372097024-372103167(6144) fileaf 561774592-561778175(3584) $ All the zeroed out blocks start on an 8k NFS boundary, and I have verified that the rest of the 8k block has the correct data in it. Each corrupted block is always a multiple of 512 bytes long (so far multiples are 6, 7, 11, and 12). On this example run, each file either has no corruption at all, or has corruption with all the zeroed out ranges the same size. Dunno if this matters, but it's interesting. If I run without nfsiod, or copy from a remote NFS mount to a remote NFS mount, the corruption goes way down but still happens. I got only one corrupted block in my 7-gig test run in each of those test cases. I'm afraid I don't know much about the internal workings of NFS, so I'm hoping my description is enough to pinpoint the problem. -- Dan Nelson dnelson@emsphone.com --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #2: Thu Dec 2 17:07:57 CST 1999 zsh@emssrv7.emsphone.com:/usr/src/sys/compile/EMSSRV7 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Xeon (596.92-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383fbff real memory = 268427264 (262136K bytes) avail memory = 257163264 (251136K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0303000. VESA: v2.0, 2048k memory, flags:0x0, mode table:0xc02af1c2 (1000022) VESA: ATI MACH64 Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: at device 0.0 on pci1 pcib2: at device 2.0 on pci0 pci2: on pcib2 ahc0: irq 21 at device 9.0 on pci2 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: irq 16 at device 11.0 on pci2 ahc1: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs isab0: at device 7.0 on pci0 isa0: on isab0 chip1: at device 7.1 on pci0 pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 19 Timecounter "PIIX" frequency 3579545 Hz intpm0: at device 7.3 on pci0 intpm0: I/O mapped 850 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 800 fxp0: irq 18 at device 14.0 on pci0 fxp0: Ethernet address 00:90:27:dc:44:eb fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (atapi): , removable, intr, dma, iordis wcd0: drive speed 6875KB/sec, 128KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA, packet track wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 3 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! Mounting root from ufda0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 51200MB (104857600 512 byte sectors: 255H 63S/T 6527C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 44032MB (90177536 512 byte sectors: 255H 63S/T 5613C) s:/dev/da2s2a da2 at ahc1 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da2: 8683MB (17783301 512 byte sectors: 255H 63S/T 1106C) --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=EMSSRV7 # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.freebsd.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.199 1999/11/01 04:02:56 peter Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident GENERIC maxusers 100 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols makeoptions COPTFLAGS="-O -pipe" # use some optimizations options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3000 #Be optimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options SOFTUPDATES # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 controller pnp0 # PnP support for ISA controller eisa0 controller pci0 # Floppy drives controller fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 options IDE_DELAY=3000 # Be optimistic about Joe IDE device # IDE controller and disks controller wdc0 at isa? port IO_WD1 irq 14 device wd0 at wdc0 drive 0 device wd1 at wdc0 drive 1 controller wdc1 at isa? port IO_WD2 irq 15 device wd2 at wdc1 drive 0 device wd3 at wdc1 drive 1 # ATAPI devices on wdc? device wcd0 #IDE CD-ROM device wfd0 #IDE Floppy (e.g. LS-120) device wst0 #IDE Tape (e.g. Travan) # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. controller ahc0 # AHA2940 and onboard AIC7xxx devices #controller adv0 at isa? port ? irq ? #controller adw0 #controller bt0 at isa? port ? irq ? #controller aha0 at isa? port ? irq ? # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. controller scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts options VGA_WIDTH90 # support 90 column modes options VESA # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at isa? #device pcic1 at isa? # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 # Printer device plip0 # TCP/IP over parallel device ppi0 # Parallel port interface device #controller vpo0 # Requires scbus and da0 # PCI Ethernet NICs. device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter # USB support #controller uhci0 # UHCI PCI->USB interface #controller ohci0 # OHCI PCI->USB interface #controller usb0 # USB Bus (required) #device ugen0 # Generic #device uhid0 # "Human Interface Devices" #device ukbd0 # Keyboard #device ulpt0 # Printer #controller umass0 # Disks/Mass storage - Requires scbus and da0 #device ums0 # Mouse # System Management Bus support provided by the 'smbus' device. controller smbus0 controller intpm0 controller alpm0 device smb0 at smbus? options MSGBUF_SIZE=32768 options INCLUDE_CONFIG_FILE # Include this file in kernel --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="blankcheck.c" #include #define BS (65536) /* print the byte ranges and sizes of any runs of zeros in a datafile more than 5 bytes long */ int main (void) { char buf[BS]; long long offset = 0; long long first = -1; int size; int bufoff = 0; setvbuf (stdin, NULL, _IOFBF, BS); while ((size = fread (buf, 1, BS, stdin))) { for (bufoff = 0; bufoff < size; bufoff++, offset++) { if (buf[bufoff] == 0) { if (first == -1) first = offset; } else { if (first != -1) { if (offset - first > 5) printf ("%lld-%lld(%lld) \n", first, offset - 1, offset - first); first = -1; } } } } if (first != -1) { if (offset - first + 1 > 5) printf ("%lld-%lld(%lld) \n", first, offset, offset - first + 1); first = -1; } return 0; } --UlVJffcvxoiEqYs2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 9:38:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id D1B541504A for ; Fri, 3 Dec 1999 09:38:42 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id F0B3E1CC8; Sat, 4 Dec 1999 01:37:52 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Heffner Cc: Doug Rabson , FreeBSD-current Subject: Re: incorrect irqs with pci devices In-Reply-To: Message from Mike Heffner of "Fri, 03 Dec 1999 09:55:43 EST." Date: Sat, 04 Dec 1999 01:37:52 +0800 From: Peter Wemm Message-Id: <19991203173752.F0B3E1CC8@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Heffner wrote: > > On 03-Dec-99 Doug Rabson said: > | On Fri, 3 Dec 1999, Mike Heffner wrote: > | > |> Hi, > |> > |> I have recently noticed that the irqs for my PCI devices are being screw ed > |> up > |> somehow. It is easily noticeable with dmesg, the correct one's are in > |> paren.: > | > | Is this an SMP box by any chance? Does the kernel work with the irqs whic h > | it chose? > | > > Yes, it is a SMP box, and yes, the devices work fine. I just thought it was o dd > that the kernel would report incorrect ones. It isn't "incorrect".. SMP motherboards have a seperate interrupt controller (APIC - Advanced programmable interupt controller) that is used for message passing as well as distributing interrupts per cpu. It also generally has 24 interrupt pins, and there can be more than one APIC in a system. When a system boots, it's in "legacy" mode until the switch is thrown and it's running in SMP mode. At that time, the alternative IRQ assignments are activated. fxp0: irq 18 at device 6.0 on pci0 ahc0: irq 17 at device 9.0 on pci0 etc. Run the mptable(1) program to see your motherboard config. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 10:54: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 2E95F1523F for ; Fri, 3 Dec 1999 10:54:01 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA06821 for ; Fri, 3 Dec 1999 19:53:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: make world failure in pccardc From: Poul-Henning Kamp Date: Fri, 03 Dec 1999 19:53:48 +0100 Message-ID: <6819.944247228@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> usr.sbin/pccard/pccardc cc -O -pipe -I/usr/src/usr.sbin/pccard/pccardc/../pccardd -Wall -g -static -c /usr/src/usr.sbin/pccard/pccardc/power.c /usr/src/usr.sbin/pccard/pccardc/power.c: In function `power_main': /usr/src/usr.sbin/pccard/pccardc/power.c:79: `PIOCSVIR' undeclared (first use in this function) /usr/src/usr.sbin/pccard/pccardc/power.c:79: (Each undeclared identifier is reported only once /usr/src/usr.sbin/pccard/pccardc/power.c:79: for each function it appears in.) *** Error code 1 Stop in /usr/src/usr.sbin/pccard/pccardc. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 11:34:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext12.compaq.com (mailext12.compaq.com [207.18.199.188]) by hub.freebsd.org (Postfix) with ESMTP id DAD9314A14 for ; Fri, 3 Dec 1999 11:34:37 -0800 (PST) (envelope-from bruceb@txn.cpqcorp.net) Received: by mailext12.compaq.com (Postfix, from userid 12345) id 2977157AB1; Fri, 3 Dec 1999 13:33:55 -0600 (CST) Received: from mailint12.im.hou.compaq.com (mailint12.compaq.com [207.18.199.190]) by mailext12.compaq.com (Postfix) with ESMTP id 2706154601 for ; Fri, 3 Dec 1999 13:33:55 -0600 (CST) Received: by mailint12.im.hou.compaq.com (Postfix, from userid 12345) id 95C284FB02; Fri, 3 Dec 1999 13:33:48 -0600 (CST) Received: from fedex.txn.cpqcorp.net (fedex-s1.txn.cpqcorp.net [16.74.4.108]) by mailint12.im.hou.compaq.com (Postfix) with ESMTP id 38FC84C90B for ; Fri, 3 Dec 1999 13:33:44 -0600 (CST) From: bruce.burden@compaq.com Posted-Date: Fri, 3 Dec 1999 13:33:53 -0600 (CST) Received: (from bruceb@localhost) by panther.txn.cpqcorp.net (8.9.3/8.9.3) id NAA08260 for freebsd-current@freebsd.org; Fri, 3 Dec 1999 13:30:18 -0600 (CST) Message-Id: <199912031930.NAA08260@panther.txn.cpqcorp.net> Subject: Current state of native Netscape? To: freebsd-current@freebsd.org Date: Fri, 3 Dec 1999 13:30:17 -0600 (CST) Reply-To: bruceb@devnull.mpd.tandem.com X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has the signal structure problem that hangs native Netscape been corrected? I haven't seen a definitive "its fixed" statement recently... Thanks, Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 11:37:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailext04.compaq.com (mailext04.compaq.com [207.18.199.42]) by hub.freebsd.org (Postfix) with ESMTP id 0669C14A14 for ; Fri, 3 Dec 1999 11:37:35 -0800 (PST) (envelope-from bruceb@txn.cpqcorp.net) Received: by mailext04.compaq.com (Postfix, from userid 12345) id 71A7B104E45; Fri, 3 Dec 1999 13:37:18 -0600 (CST) Received: from mailint12.im.hou.compaq.com (mailint12.compaq.com [207.18.199.190]) by mailext04.compaq.com (Postfix) with ESMTP id 6DCA7FB101 for ; Fri, 3 Dec 1999 13:37:18 -0600 (CST) Received: by mailint12.im.hou.compaq.com (Postfix, from userid 12345) id D05A84FB02; Fri, 3 Dec 1999 13:37:11 -0600 (CST) Received: from fedex.txn.cpqcorp.net (fedex-s1.txn.cpqcorp.net [16.74.4.108]) by mailint12.im.hou.compaq.com (Postfix) with ESMTP id 787684C90E for ; Fri, 3 Dec 1999 13:37:11 -0600 (CST) From: bruce.burden@compaq.com Posted-Date: Fri, 3 Dec 1999 13:37:20 -0600 (CST) Received: (from bruceb@localhost) by panther.txn.cpqcorp.net (8.9.3/8.9.3) id NAA08268 for freebsd-current@freebsd.org; Fri, 3 Dec 1999 13:33:49 -0600 (CST) Message-Id: <199912031933.NAA08268@panther.txn.cpqcorp.net> Subject: FA410TXC support in -current To: freebsd-current@freebsd.org Date: Fri, 3 Dec 1999 13:33:49 -0600 (CST) Reply-To: bruceb@devnull.mpd.tandem.com X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi gang, I noticed that /src/etc/pccard.conf.sample listed the Netgear FA410TX card as supported. Does it still use the ed0 driver? I take it I no longer need to worry about the PAO additions if I use a build of -current that lists the FA410TX as supported, right? Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 12:47:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from ozz.freebsd.org.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 485A514BED for ; Fri, 3 Dec 1999 12:46:57 -0800 (PST) (envelope-from osa@freebsd.org.ru) Received: from localhost (localhost.freebsd.org.ru [127.0.0.1]) by ozz.freebsd.org.ru (8.9.3/8.9.3) with ESMTP id XAA00493 for ; Fri, 3 Dec 1999 23:46:35 +0300 (MSK) (envelope-from osa@freebsd.org.ru) Date: Fri, 3 Dec 1999 23:46:35 +0300 (MSK) From: Sergey Osokin To: freebsd-current@FreeBSD.org Subject: -current build failed... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! After cvsuped my source, i try rebuild my -current system... ===> usr.bin/truss cp /usr/src/usr.bin/truss/../../sys/kern/syscalls.master syscalls.master /bin/sh /usr/src/usr.bin/truss/../../sys/kern/makesyscalls.sh syscalls.master /usr/src/usr.bin/truss/i386.co nf cp /usr/src/usr.bin/truss/../../sys/i386/linux/syscalls.master i386l-syscalls.master /bin/sh /usr/src/usr.bin/truss/../../sys/kern/makesyscalls.sh i386l-syscalls.master /usr/src/usr.bin/truss/i 386linux.conf cc -nostdinc -O -pipe -I/usr/src/usr.bin/truss -I. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/t russ/main.c cc -nostdinc -O -pipe -I/usr/src/usr.bin/truss -I. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/t russ/setup.c cc -nostdinc -O -pipe -I/usr/src/usr.bin/truss -I. -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/t russ/syscalls.c /bin/sh /usr/src/usr.bin/truss/../../usr.bin/kdump/mkioctls > ioctl.c *** Error code 1 Stop in /usr/src/usr.bin/truss. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Rgdz, Osokin Sergey, osa@etrust.ru osa@FreeBSD.org.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 12:49: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 9484A14CE7 for ; Fri, 3 Dec 1999 12:49:01 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA01256; Fri, 3 Dec 1999 12:49:53 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912032049.MAA01256@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: bruceb@devnull.mpd.tandem.com Cc: freebsd-current@freebsd.org Subject: Re: FA410TXC support in -current In-reply-to: Your message of "Fri, 03 Dec 1999 13:33:49 CST." <199912031933.NAA08268@panther.txn.cpqcorp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Dec 1999 12:49:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I noticed that /src/etc/pccard.conf.sample listed the > Netgear FA410TX card as supported. > > Does it still use the ed0 driver? I take it I no longer > need to worry about the PAO additions if I use a build of > -current that lists the FA410TX as supported, right? Yes. Note that you need to be up-to-date with the pccard.conf entry; until a few weeks ago it was a cut-and-paste from PAO that didn't work. You're reading this courtesy of one, so I know it's working. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 13: 4:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id 69C5F15288 for ; Fri, 3 Dec 1999 13:04:12 -0800 (PST) (envelope-from tstromberg@rtci.com) Received: from karma (karma.afterthought.org [208.11.244.6]) by barracuda.aquarium.rtci.com (8.9.3+Sun/8.9.3) with SMTP id QAA20661; Fri, 3 Dec 1999 16:03:21 -0500 (EST) Message-ID: <84694702.944254987164.JavaMail.chenresig@karma> Date: Fri, 3 Dec 1999 16:03:07 -0500 (EST) From: tstromberg@rtci.com To: freebsd-current@freebsd.org Subject: More crashes under heavy exec() load in -CURRENT (and strange savecore) Cc: mdillon@apollo.backplane.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailer: ICEMail (rel 2.8.2) Organization: Research Triangle Commerce, Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been experiencing more strange crashes. I've been getting them about once or twice a day lately, but only if I'm running my testing for the FreeBSD-audit project. I'm basically brute forcing the FreeBSD toolchain, and reporting the results to the audit mailing list. Unfortunatly, the crashes have been getting in the way.. Matt Dillon told me to try to up my PV's in my kernel as a first step. After upping it to 1000 (this could have nothing to do with it), my machine would no longer dump core, or drop into DDB, it'd simply reboot. So I lowered it back down to the default, and now it cored again. I'll pop it up to 1000 again to what it does. For an idea of the load, it was probably at about 1.50. I had three processes doing a bunch of execs, and just before the crash the tester was only at ~1800 exec()'s a minute. I've got all of the info (dmesg, kernel conf, vmcore, kernel) sitting at http://www.afterthought.org/freebsd/crashes/ I also noticed this oddity in my /var/log/messages: Dec 3 15:35:45 karma savecore: reboot after panic: page fault Dec 3 15:35:45 karma savecore: /var/crash/bounds: No such file or directory Dec 3 15:35:45 karma savecore: /dev/rrwd0s1b: No such file or directory; using block device Dec 3 15:35:45 karma savecore: writing core to /var/crash/vmcore.0 Dec 3 15:36:03 karma savecore: writing kernel to /var/crash/kernel.0 Dec 3 15:36:03 karma savecore: read: No such file or directory My rc.conf says: dumpdev="/dev/wd0s1b" Kernel: FreeBSD karma.afterthought.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Dec 2 13:04:29 EST 1999 chenresig@karma.afterthought.org:/usr/src/sys/compile/KARMA i386 Last 'make world': November 29th. Here's a backtrace: =================== panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc01d8339 stack pointer = 0x10:0xcf71addc frame pointer = 0x10:0xcf71adec 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 = 86209 (cc1plus) interrupt mask = none trap number = 12 panic: page fault syncing disks... 34 8 done dumping to dev #wd/0x20001, offset 1413889 dump ata0: resetting devices .. WARNING: WAIT_READY active=UNKNOWN done 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:273 273 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:273 #1 0xc0132295 in panic (fmt=0xc0244fcf "page fault") at ../../kern/kern_shutdown.c:523 #2 0xc02158e2 in trap_fatal (frame=0xcf71ad9c, eva=0) at ../../i386/i386/trap.c:908 #3 0xc0215595 in trap_pfault (frame=0xcf71ad9c, usermode=0, eva=0) at ../../i386/i386/trap.c:801 #4 0xc0215167 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16777232, tf_edi = 0, tf_esi = -1071179392, tf_ebp = -814633492, tf_isp = -814633528, tf_ebx = -1071179392, tf_edx = 0, tf_ecx = 11, tf_eax = 0, tf_trapno = 12, tf_err = 2, tf_eip = -1071807687, tf_cs = 8, tf_eflags = 66118, tf_esp = -1071172824, tf_ss = -814624768}) at ../../i386/i386/trap.c:425 #5 0xc01d8339 in _vm_map_clip_end (map=0xc0273328, entry=0xc0271980, end=3480358912) at ../../vm/vm_map.c:835 #6 0xc01d93bf in vm_map_delete (map=0xc0273328, start=3480342528, end=3480358912) at ../../vm/vm_map.c:1751 #7 0xc01d9536 in vm_map_remove (map=0xc0273328, start=3480342528, end=3480358912) at ../../vm/vm_map.c:1822 #8 0xc01d747d in kmem_free (map=0xc0273328, addr=3480342528, size=16384) at ../../vm/vm_kern.c:233 #9 0xc0141731 in pipeclose (cpipe=0xccd40a20) at ../../kern/sys_pipe.c:1093 #10 0xc014161d in pipe_close (fp=0xc3154540, p=0xcf67a300) at ../../kern/sys_pipe.c:1049 #11 0xc012a4f1 in fdrop (fp=0xc3154540, p=0xcf67a300) at ../../sys/file.h:211 #12 0xc012a42f in closef (fp=0xc3154540, p=0xcf67a300) at ../../kern/kern_descrip.c:1017 #13 0xc0129b90 in close (p=0xcf67a300, uap=0xcf71af80) at ../../kern/kern_descrip.c:515 #14 0xc0215b1a in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 136883640, tf_esi = 0, tf_ebp = -1077978820, tf_isp = -814633004, tf_ebx = 136674112, tf_edx = 136674200, tf_ecx = 0, tf_eax = 6, tf_trapno = 7, tf_err = 2, tf_eip = 136203996, tf_cs = 31, tf_eflags = 647, tf_esp = -1077978848, tf_ss = 47}) at ../../i386/i386/trap.c:1057 #15 0xc020a516 in Xint0x80_syscall () #16 0x81dd327 in ?? () #17 0x807fd54 in ?? () #18 0x80d8979 in ?? () #19 0x80db8cb in ?? () #20 0x80480f9 in ?? () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 13: 4:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 5B21215288; Fri, 3 Dec 1999 13:04:42 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-154.skylink.it [194.185.55.154]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id WAA09971; Fri, 3 Dec 1999 22:04:34 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id PAA00309; Fri, 3 Dec 1999 15:36:48 +0100 (CET) (envelope-from hibma@skylink.it) Date: Fri, 3 Dec 1999 15:36:47 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List , FreeBSD Ports Mailing List Subject: modules in ports Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone ever devised a good way to put a module in a port? Like so: module usio firmware in hex and source format. They are strongly connected in that the API in the firmware might change. Maybe it is the more general question of how to relate modules to other parts of the base system, like the kernel, downloadable firmware files, etc. Nick -- hibma@skylink.it n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 13:10:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id 51A7F14CA7 for ; Fri, 3 Dec 1999 13:10:27 -0800 (PST) (envelope-from tstromberg@rtci.com) Received: from karma (karma.afterthought.org [208.11.244.6]) by barracuda.aquarium.rtci.com (8.9.3+Sun/8.9.3) with SMTP id QAA21026 for ; Fri, 3 Dec 1999 16:10:40 -0500 (EST) Message-ID: <84725992.944255425920.JavaMail.chenresig@karma> Date: Fri, 3 Dec 1999 16:10:25 -0500 (EST) From: tstromberg@rtci.com To: freebsd-current@freebsd.org Subject: Re: More crashes under heavy exec() load in -CURRENT (and strange savecore) In-Reply-To: <84694702.944254987164.JavaMail.chenresig@karma> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailer: ICEMail (rel 2.8.2) Organization: Research Triangle Commerce, Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -------------------------------- -> -> Matt Dillon told me to try to up my PV's in my kernel as a first step. After upping it to 1000 (this could have nothing to do with it), my machine would no longer dump core, or drop into DDB, it'd simply reboot. So I lowered it back down to the default, and now it cored again. I'll pop it up to 1000 again to what it does. - Just a little bit more information that I noticed. I had DDB in my kernel, and it never dropped into it (that I know of, I came into the room when it was rebooting). I don't have DDB_UNATTENDED, so there should not have been a timeout.. So I'm left to presume that DDB mode was never initialized. Is it ignored if dumpon is configured? ============================================================================ Thomas R. Stromberg Asst. IS Manager / Systems Guru FreeBSD Contrib, BeOS Dev, Security Geek Research Triangle Commerce, Inc. http://www.afterthought.org/ http://www.rtci.com/ thomas@stromberg.org tstromberg@rtci.com ======================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 13:27:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 87E91152B6 for ; Fri, 3 Dec 1999 13:27:21 -0800 (PST) (envelope-from freebsd-current@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id WAA47453 for current@FreeBSD.org; Fri, 3 Dec 1999 22:17:20 +0100 (CET) (envelope-from freebsd-current@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for current@FreeBSD.org (current@FreeBSD.org) To: current@FreeBSD.org Date: Fri, 03 Dec 1999 22:17:16 +0100 From: Marcel Moolenaar Message-ID: <3848335C.B66EACF0@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: Subject: Re: -current build failed... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergey Osokin wrote: > > Hello! > After cvsuped my source, i try rebuild my -current system... Please re-cvsup. There was a longish delay between 2 related commits. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 13:46:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 6CE231528A for ; Fri, 3 Dec 1999 13:45:15 -0800 (PST) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id DAA31957 for ; Sat, 4 Dec 1999 03:44:28 +0600 (NS) (envelope-from semen@iclub.nsu.ru) Date: Sat, 4 Dec 1999 03:44:27 +0600 (NS) From: Ustimenko Semen To: freebsd-current@FreeBSD.org Subject: Where to put HPFS driver? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Promised somewhere in spring, i am now almost ready to put HPFS driver into current. So i have question: Where have to go driver sources src/sys/hpfs or src/sys/i386/hpfs, or something else ? Where have to go mount_hpfs: src/sbin/i386/mount_hpfs? As i will patch mountd.c to support hpfs, do we need ifdef I386 there? And in the src/sys/modules/Makefile and others? Good luck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 13:52:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D94761528A for ; Fri, 3 Dec 1999 13:52:36 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA07523; Fri, 3 Dec 1999 22:50:18 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Ustimenko Semen Cc: freebsd-current@FreeBSD.ORG Subject: Re: Where to put HPFS driver? In-reply-to: Your message of "Sat, 04 Dec 1999 03:44:27 +0600." Date: Fri, 03 Dec 1999 22:50:18 +0100 Message-ID: <7521.944257818@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Ustimenko S emen writes: >Hi! > >Promised somewhere in spring, i am now >almost ready to put HPFS driver into current. > >So i have question: >Where have to go driver sources >src/sys/hpfs or src/sys/i386/hpfs, or something else ? >Where have to go mount_hpfs: >src/sbin/i386/mount_hpfs? The code for a filesystem should not be architecture dependent. I would advocate for sys/fs/hpfs. We have too many filesystems cluttering up /sys already, we should start to cluster them in sys/fs -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 14:43:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from [132.197.97.45] (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id AAA8114A16 for ; Fri, 3 Dec 1999 14:43:46 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by [132.197.97.45] (8.9.3/8.9.3) id RAA69023; Fri, 3 Dec 1999 17:42:19 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 03 Dec 1999 17:42:13 -0500 (EST) Organization: GTE Laboratories Inc. From: "Alexander N. Kabaev" To: Martin Blapp Subject: re: rpc.umntall does not work with AIX [LONG] Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it seems like RPCMNT_UMNTALL call always fails with RPC_SYSTEMERROR on all systems except FreeBSD. I tested HP/UX, AIX and Solaris boxes - they all behave identically as follows: rpc.umntall -h $HOST always fails rpc.umntall -h $HOST -p $DIR - works just fine since it is using RPCMNT_UMOUNT umount $HOST:$DIR works just fine Interesting, even if RPC_UMNTALL call returns error code, it nonetheless causes mount entry to be removed from the server, i.e. showmount -a $HOST output does not report my client machine as having any mounts on $HOST anymore. All entries in my /var/db/mounttab appear to be correct, I do not think they are causing the problem. Also, I have questions regarding the following code fragment from the rpc.umntall.c file: 1) for (mtab = mtabhead; mtab != NULL; mtab = mtab->next) { 2) if (*mtab->mtab_host != '\0' && 3) (do_umntall(mtab->mtab_host) || 4) mtab->mtab_time <= (time(now) - expire))) { 5) if (keep && is_mounted(mtab->mtab_host, 6) mtab->mtab_dirp)) { 7) if (verbose) { 8) warnx("skipping entry %s:%s", 9) mtab->mtab_host, 10) mtab->mtab_dirp); 11) } 12) } else 13) clean_mtab(mtab->mtab_host, NULL); 14) } 15) } It seems like it does RPCMNT_UMNTALL call for each mounttab entry regardless of the -k parameter passed in the command line, while man page suggests that it should simply skip entries for currently mounted filesystems. -k Keep entries for existing NFS filesystems. Compare the NFS filesystems from the mounttab against the kernel mount list and do not send the RPC to existing mount entries. Useful during startup of the system. It may be possible that there are already mounted NFS filesystems, so calling RPC UMNTALL isn't a good idea. This is the case if the user has rebooted to 'single user mode' and starts up the system again. Furthermore, using RPC_UMNTALL in the above loop is probably not a good idea either because client host may have two different directories mounted from the same server. If -k flag is specified, you cannot use UMNTALL because it will remove /var/run/mountdtab entries not only for the mount point left over from the crash but also for all other mounts some of which may be perfectly valid and should be kept intact. May be, we should use RPCMNT_UMOUNT call instead? It seems to me that RMCMNT_UMNTALL is only applicable when utility is called with -h option as the only option. -Alexander Kabaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 15: 5:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 3764C14FFC; Fri, 3 Dec 1999 15:05:26 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-154.skylink.it [194.185.55.154]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id AAA12653; Sat, 4 Dec 1999 00:04:43 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id XAA54087; Fri, 3 Dec 1999 23:10:34 +0100 (CET) (envelope-from hibma@skylink.it) Date: Fri, 3 Dec 1999 23:10:33 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Mike Smith Cc: Warner Losh , FreeBSD CURRENT Mailing List Subject: Re: your mail In-Reply-To: <199912010952.BAA00549@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, I don't think so. I'm not 100% sure, but I think that you end > up in the interrupt handler for the card that's going away, but with tty > interrupts masked so you can't get back into DDB. If it's a modem card, > then you'll have them masked as well. > > I'm _fairly_ sure that you'll find you're spinning in the card's > interrupt handler. Stick a printf or two in there and see for yourself. I guess you must have been right. The card suspend and resumes fine now (apart from resource allocation, but that is a different issue). It seems that the proper deleting of the driver solved the problem of freezing my machine. Cheers, Nick -- hibma@skylink.it n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 15: 5:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 44306152F7 for ; Fri, 3 Dec 1999 15:05:31 -0800 (PST) (envelope-from hibma@skylink.it) Received: from skylink.it (va-154.skylink.it [194.185.55.154]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id AAA12663; Sat, 4 Dec 1999 00:04:49 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id WAA28911; Fri, 3 Dec 1999 22:23:08 +0100 (CET) (envelope-from hibma@skylink.it) Date: Fri, 3 Dec 1999 22:23:08 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: thyerm@camtech.net.au Cc: FreeBSD CURRENT Mailing List , USB BSD list Subject: Re: How do I get a USB mouse working in todays -CURRENT ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks Nick, my USB mouse works perfectly now. If you have any comments on the (lack of) functionality provided, let us (the lists current@freebsd.org or usb-bsd@egroups.com know about it. There is a lot of useful things that could be added to usbd... Nick -- hibma@skylink.it n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 15:18:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id DEE73152C8 for ; Fri, 3 Dec 1999 15:18:52 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA02723; Fri, 3 Dec 1999 15:15:16 -0800 (PST) Date: Fri, 3 Dec 1999 15:15:15 -0800 (PST) From: Julian Elischer To: Poul-Henning Kamp Cc: Ustimenko Semen , freebsd-current@FreeBSD.ORG Subject: Re: Where to put HPFS driver? In-Reply-To: <7521.944257818@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I second this.. however we have miscfs, How should we treat that? is miscfs really "trivialfs"? should stuff move? fs/miscfs? in the same vein should netinet move under net? (hard because of the includes in /usr/include.) The sys tree is getting ot be a bit unwieldy. Maybe we nned to start doing this? julian On Fri, 3 Dec 1999, Poul-Henning Kamp wrote: > In message , Ustimenko S > emen writes: > >Hi! > > > >Promised somewhere in spring, i am now > >almost ready to put HPFS driver into current. > > > >So i have question: > >Where have to go driver sources > >src/sys/hpfs or src/sys/i386/hpfs, or something else ? > >Where have to go mount_hpfs: > >src/sbin/i386/mount_hpfs? > > The code for a filesystem should not be architecture dependent. > > I would advocate for sys/fs/hpfs. > > We have too many filesystems cluttering up /sys already, we should > start to cluster them in sys/fs > > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 16:48:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 9B340152D2 for ; Fri, 3 Dec 1999 16:48:22 -0800 (PST) (envelope-from kargl@troutmask.apl.washington.edu) Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id QAA68175 for freebsd-current@freebsd.org; Fri, 3 Dec 1999 16:48:23 -0800 (PST) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <199912040048.QAA68175@troutmask.apl.washington.edu> Subject: modules/netgraph/bpf breaks world To: freebsd-current@freebsd.org Date: Fri, 3 Dec 1999 16:48:23 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG *** Makefile.orig Fri Dec 3 16:46:54 1999 --- Makefile Fri Dec 3 16:46:25 1999 *************** *** 6,11 **** MAN8= ng_bpf.8 KMODDEPS= netgraph ! .PATH: ../../../net .include --- 6,11 ---- MAN8= ng_bpf.8 KMODDEPS= netgraph ! .PATH: ${.CURDIR}/../../../net .include -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 17: 2:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from friley-160-236.res.iastate.edu (friley-160-236.res.iastate.edu [129.186.160.236]) by hub.freebsd.org (Postfix) with ESMTP id EB40414C13 for ; Fri, 3 Dec 1999 17:02:15 -0800 (PST) (envelope-from cc@137.org) Received: from ameslab.gov (friley-160-235.res.iastate.edu [129.186.160.235]) by friley-160-236.res.iastate.edu (Postfix) with ESMTP id 54453117; Fri, 3 Dec 1999 19:02:14 -0600 (CST) Message-ID: <38486816.E224F87C@ameslab.gov> Date: Fri, 03 Dec 1999 19:02:14 -0600 From: Chris Csanady X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.5 i386) X-Accept-Language: en, ru, ja, ko MIME-Version: 1.0 To: Garrett Wollman Cc: FreeBSD-current Subject: Re: incorrect irqs with pci devices References: <199912031656.LAA08053@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > > < said: > > > Yes, it is a SMP box, and yes, the devices work fine. I just thought it was odd > > that the kernel would report incorrect ones. > > They are not incorrect. SMP uses a different interrupt system. They are on my box, where incorrect is defined as the interrupts not reaching their supposed destination. I would really like to fix this, but I don't know enough about exactly what is wrong. Any ideas would really be appreciated, as I would like to remove my disgusting hack. :) I have an AMI raid controller that the system reports that it is on irq 11. The problem is that the interrupts actually go to irq 17. If I hard wire them with *** pci.c.old Mon Nov 29 19:34:46 1999 --- pci.c Thu Dec 2 17:48:42 1999 *************** *** 347,352 **** --- 347,356 ---- } } } + if (cfg->intline == 11) { + printf("apic_io: incorrect int 11 -> 17\n"); + cfg->intline = 17; + } #endif /* APIC_IO */ cfg->mingnt = pci_cfgread(cfg, PCIR_MINGNT, 1); ...everything works fine. I believe the problem has something to do with the fact that it is a bridged card, but I'm not sure how things should work. Any thoughts? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 19:11: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B1EF414CB9 for ; Fri, 3 Dec 1999 19:11:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA34540 for ; Fri, 3 Dec 1999 19:09:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: current@freebsd.org Subject: -current no longer builds on the alpha Date: Fri, 03 Dec 1999 19:09:12 -0800 Message-ID: <34537.944276952@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/reader.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/skeleton.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/symtab.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/verbose.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/warshall.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -static -o yacc closure.o error.o lalr.o lr0.o main.o mkpar.o output.o reader.o skeleton.o symtab.o verbose.o warshall.o install -c -o root -g wheel -m 555 /usr/src/usr.bin/yacc/yyfix.sh /usr/obj/usr/src/tmp/usr/bin/yyfix *** Signal 11 Stop in /usr/src/usr.bin/yacc. *** Error code 1 It dies every time right there, which makes me think this is more than the usual memory/cache issues. Also, the alpha in question (beast) will build the world just fine from 3 days ago. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 19:17:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E4A7614CB9 for ; Fri, 3 Dec 1999 19:17:20 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id TAA08522; Fri, 3 Dec 1999 19:17:39 -0800 Date: Fri, 3 Dec 1999 19:17:39 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: -current no longer builds on the alpha In-Reply-To: <34537.944276952@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is beast? I was happily able to build -current at about 5 this morning on a pc164. On Fri, 3 Dec 1999, Jordan K. Hubbard wrote: > cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/reader.c > cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/skeleton.c > cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/symtab.c > cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/verbose.c > cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/yacc/warshall.c > cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -static -o yacc closure.o error.o lalr.o lr0.o main.o mkpar.o output.o reader.o skeleton.o symtab.o verbose.o warshall.o > install -c -o root -g wheel -m 555 /usr/src/usr.bin/yacc/yyfix.sh /usr/obj/usr/src/tmp/usr/bin/yyfix > *** Signal 11 > > Stop in /usr/src/usr.bin/yacc. > *** Error code 1 > > > It dies every time right there, which makes me think this is more than > the usual memory/cache issues. Also, the alpha in question (beast) > will build the world just fine from 3 days ago. > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 19:53:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id BE19614F98 for ; Fri, 3 Dec 1999 19:53:51 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id TAA09230; Fri, 3 Dec 1999 19:53:43 -0800 (PST) Date: Fri, 3 Dec 1999 19:53:42 -0800 (PST) From: Julian Elischer To: "Steven G. Kargl" Cc: freebsd-current@FreeBSD.ORG Subject: Re: modules/netgraph/bpf breaks world In-Reply-To: <199912040048.QAA68175@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thanks, committed. For thise wondering this is a netgraph node that can do arbitrary filtering using the existing bpf engine. On Fri, 3 Dec 1999, Steven G. Kargl wrote: > > *** Makefile.orig Fri Dec 3 16:46:54 1999 > --- Makefile Fri Dec 3 16:46:25 1999 > *************** > *** 6,11 **** > MAN8= ng_bpf.8 > KMODDEPS= netgraph > > ! .PATH: ../../../net > > .include > --- 6,11 ---- > MAN8= ng_bpf.8 > KMODDEPS= netgraph > > ! .PATH: ${.CURDIR}/../../../net > > .include > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 20:58:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.196.87]) by hub.freebsd.org (Postfix) with ESMTP id 3B70015325 for ; Fri, 3 Dec 1999 20:58:45 -0800 (PST) (envelope-from culverk@culverk.student.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.3/8.9.3) with ESMTP id XAA00318 for ; Fri, 3 Dec 1999 23:56:18 -0500 (EST) (envelope-from culverk@culverk.student.umd.edu) Date: Fri, 3 Dec 1999 23:56:18 -0500 (EST) From: Kenneth Culver To: freebsd-current@freebsd.org Subject: Bktr driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that the bktr driver is still broken. I have looked through the code for the driver, and have yet to find the problem. here is a dmesg output with the error that seems to be causeing my problem: bktr0: irq 9 at device 17.0 on pci0 bktr0: Hauppauge Model 61291 D110 Warning - Unknown Hauppauge Tuner 0xa Hauppauge WinCast/TV, Philips NTSC tuner, remote control. The problem with the driver can be found at: www.wam.umd.edu/~culverk/fxtv.jpg I am positive that this problem is not with X or fxtv, I have already talked to the X people about this problem. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 21:17: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E512D15325 for ; Fri, 3 Dec 1999 21:16:57 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA34751; Fri, 3 Dec 1999 21:15:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: -current no longer builds on the alpha In-reply-to: Your message of "Fri, 03 Dec 1999 19:17:39 PST." Date: Fri, 03 Dec 1999 21:15:15 -0800 Message-ID: <34747.944284515@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What is beast? I was happily able to build -current at about 5 this > morning on a pc164. It's an Aspen systems DEC Durango PC164 motherboard based system. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 21:27:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id B9F2214D2F; Fri, 3 Dec 1999 21:27:13 -0800 (PST) (envelope-from darius@dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id PAA07250; Sat, 4 Dec 1999 15:55:04 +1030 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 04 Dec 1999 15:53:09 +1030 (CST) From: "Daniel J. O'Connor" To: Nick Hibma Subject: RE: modules in ports Cc: FreeBSD Ports Mailing List Cc: FreeBSD Ports Mailing List , FreeBSD CURRENT Mailing List Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03-Dec-99 Nick Hibma wrote: > Has anyone ever devised a good way to put a module in a port? Well the skip port creates a module.. > Maybe it is the more general question of how to relate modules to > other parts of the base system, like the kernel, downloadable firmware > files, etc. Urk! :) Creating a module which will build outside the source tree is fairly simple, for an example have a look at wpaul's if_dc driver which does this. Then you can just install in in /usr/local/share/myport/kld and load it from /usr/local/etc/rc.d/myport.sh --- 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 21:35:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 61AE015279 for ; Fri, 3 Dec 1999 21:35:11 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA82259; Fri, 3 Dec 1999 21:34:45 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912040534.VAA82259@gndrsh.dnsmgr.net> Subject: Re: modules/netgraph/bpf breaks world In-Reply-To: from Julian Elischer at "Dec 3, 1999 07:53:42 pm" To: julian@whistle.com (Julian Elischer) Date: Fri, 3 Dec 1999 21:34:44 -0800 (PST) Cc: kargl@troutmask.apl.washington.edu (Steven G. Kargl), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > thanks, committed. > For thise wondering this is a netgraph node that can do arbitrary > filtering using the existing bpf engine. And just when is ipfw going to become a netgraph node 0.5 * :-) God I wish I had some free time to go play with this code....!! > On Fri, 3 Dec 1999, Steven G. Kargl wrote: > > > > > *** Makefile.orig Fri Dec 3 16:46:54 1999 > > --- Makefile Fri Dec 3 16:46:25 1999 > > *************** > > *** 6,11 **** > > MAN8= ng_bpf.8 > > KMODDEPS= netgraph > > > > ! .PATH: ../../../net > > > > .include > > --- 6,11 ---- > > MAN8= ng_bpf.8 > > KMODDEPS= netgraph > > > > ! .PATH: ${.CURDIR}/../../../net > > > > .include > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 21:46:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.az.home.com (ha1.rdc1.az.home.com [24.1.240.66]) by hub.freebsd.org (Postfix) with ESMTP id 9D1C615334 for ; Fri, 3 Dec 1999 21:46:28 -0800 (PST) (envelope-from straka@home.com) Received: from home.com ([24.1.209.47]) by mail.rdc1.az.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19991204054625.YOCF7363.mail.rdc1.az.home.com@home.com> for ; Fri, 3 Dec 1999 21:46:25 -0800 Message-ID: <3848AAB0.6EA5AA6C@home.com> Date: Fri, 03 Dec 1999 22:46:24 -0700 From: "Richard S. Straka" X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: ide dma support not enabled Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A kernel built from current source which was cvsup'ed today at approximately 10:00 pm MST no longer enables DMA support on my IDE drives. A previous kernel from 27 Nov had no problems recognizing and enabling IDE DMA support. Any help would be greatly appreciated. Rich Straka straka@home.com Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Dec 3 21:51:20 MST 1999 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 333188878 Hz CPU: AMD-K6(tm) 3D processor (333.19-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf AMD Features=0x80000800 real memory = 134152192 (131008K bytes) avail memory = 127021056 (124044K bytes) Preloaded elf kernel "kernel" at 0xc0303000. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 chip1: at device 7.1 on pci0 chip2: at device 7.3 on pci0 sym0: <875> irq 10 at device 8.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, parity checking sym0: open drain IRQ line driver, using on-chip SRAM vga-pci0: at device 9.0 on pci0 fxp0: irq 12 at device 10.0 on pci0 fxp0: Ethernet address 00:a0:c9:27:fc:1d fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 flags 0xa008a008 on isa0 wdc0: unit 0 (wd0): , 32-bit, multi-block-8 wd0: 4134MB (8467200 sectors), 8400 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 flags 0xa008a008 on isa0 wdc1: unit 0 (wd2): , 32-bit, multi-block-8 wd2: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (atapi): , removable, dma, iordy wcd0: drive speed 2062KB/sec, 240KB cache wcd0: supported read types: CD-R, CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2 at port 0x3e8-0x3ef irq 5 on isa0 sio2: type 16550A ppc0 at port 0x378-0x37f irq 7 drq 3 on isa0 ppc0: Winbond chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pcm0: at port 0x530-0x53f irq 11 drq 1 flags 0xa610 on isa0 Waiting 8 seconds for SCSI devices to settle sym0: Downloading SCSI SCRIPTS. (noperiph:sym0:0:-1:-1): SCSI bus reset delivered. Mounting root from ufs:/dev/wd0s2a da0 at sym0 bus 0 target 3 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing Enabled da0: 2170MB (4445380 512 byte sectors: 255H 63S/T 276C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 22:25: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1BBC214A2A for ; Fri, 3 Dec 1999 22:25:04 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA08922; Fri, 3 Dec 1999 22:23:14 -0800 Date: Fri, 3 Dec 1999 22:23:13 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: -current no longer builds on the alpha In-Reply-To: <34747.944284515@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Q'uelle strange- what I have... well, we'll see what my nightly build brings... On Fri, 3 Dec 1999, Jordan K. Hubbard wrote: > > What is beast? I was happily able to build -current at about 5 this > > morning on a pc164. > > It's an Aspen systems DEC Durango PC164 motherboard based system. > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 22:37:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 23EEE14BF6 for ; Fri, 3 Dec 1999 22:37:17 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA62241; Fri, 3 Dec 1999 23:35:15 -0700 (MST) (envelope-from ken) Message-Id: <199912040635.XAA62241@panzer.kdm.org> Subject: Re: Bktr driver In-Reply-To: from Kenneth Culver at "Dec 3, 1999 11:56:18 pm" To: culverk@culverk.student.umd.edu (Kenneth Culver) Date: Fri, 3 Dec 1999 23:35:15 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Culver wrote... > It seems that the bktr driver is still broken. I have looked through the > code for the driver, and have yet to find the problem. here is a dmesg > output with the error that seems to be causeing my problem: > > bktr0: irq 9 at device 17.0 on pci0 > bktr0: Hauppauge Model 61291 D110 > Warning - Unknown Hauppauge Tuner 0xa > Hauppauge WinCast/TV, Philips NTSC tuner, remote control. > > The problem with the driver can be found at: > > www.wam.umd.edu/~culverk/fxtv.jpg > > I am positive that this problem is not with X or fxtv, I have already > talked to the X people about this problem. You should probably look at the -multimedia list. Chris Csanady reported that his problems went away when he backed bktr_core.c from version 1.102 to version 1.101. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 22:53:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from po8.andrew.cmu.edu (PO8.ANDREW.CMU.EDU [128.2.10.108]) by hub.freebsd.org (Postfix) with ESMTP id 11B3914E82; Fri, 3 Dec 1999 22:53:15 -0800 (PST) (envelope-from tcrimi+@andrew.cmu.edu) Received: (from postman@localhost) by po8.andrew.cmu.edu (8.9.3/8.9.3) id BAA27861; Sat, 4 Dec 1999 01:52:16 -0500 (EST) Received: via switchmail; Sat, 4 Dec 1999 01:52:16 -0500 (EST) Received: from unix11.andrew.cmu.edu via qmail ID ; Sat, 4 Dec 1999 01:51:37 -0500 (EST) Received: from unix11.andrew.cmu.edu via qmail ID ; Sat, 4 Dec 1999 01:51:36 -0500 (EST) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix11.andrew.cmu.edu.sun4m.54 via MS.5.6.unix11.andrew.cmu.edu.sun4_51; Sat, 4 Dec 1999 01:51:36 -0500 (EST) Message-ID: Date: Sat, 4 Dec 1999 01:51:36 -0500 (EST) From: Thomas Valentino Crimi To: obrien@FreeBSD.ORG Subject: Re: HEADS-UP: bdevs have been assimilated. Cc: current@FreeBSD.ORG In-Reply-To: <19991202233401.A84265@dragon.nuxi.com> References: <19991125133001.64729@mojave.sitaranetworks.com> <19991202202419.01433@mojave.sitaranetworks.com> <19991202233401.A84265@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Excerpts from FreeBSD-Current: 2-Dec-99 Re: HEADS-UP: bdevs have be.. by "David O'Brien"@FreeBSD. > At 2MB the Alpha fixit floppy isn't very useful. Nor is there a live > files system for the Alpha. Nor can you even boot sysinstall and get a > shell if you use a serial console. All-in-all recovery on the Alpha is > "lacking". Yup, at the times when I trashed my alpha install the install disk and NFS have been my only friends (the emergency shell is just enough to get you to mount_nfs a snapshot sitting elsewhere, albeit not in a friendly way not even having 'ls' :) One could make an NFS-client bootdisk for rescue, although a live cdrom fits the bill far better... is there room on the i386 disk for alpha bits? It would save having to ship an extra disk if that's an issue. It's no big deal to cd /cdrom/alpha, maybe toss a few symlinks around, to easilly recover the system. Tom (who is joyful enough since floppy support appeared on the alpha) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 23:26: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 81AA714BDB; Fri, 3 Dec 1999 23:26:04 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 73C431CD7F0 for ; Fri, 3 Dec 1999 23:26:04 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 3 Dec 1999 23:26:04 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: Importing OpenSSL Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to get OpenSSL imported into -current. I currently have the build framework almost ready to go, I'm just running some buildworld tests to make sure it's working properly. OpenSSL would give a number of potential benefits. Some of the coolest ones are: * Precursor to importing OpenSSH and providing secure network connectivity out-of-the-box * Possibility of teaching fetch to talk to https servers (i.e. talk SSL) * Fixing the HUGE SECURITY HOLE in CTM, namely the fact that it provides no authentication of what it's stuffing into your source tree (it only provides integrity). * Integration of cryptography into other parts of the system where it would be useful. There are potential issues which need to be addressed before this can proceed, namely how to best deal with US patent restrictions on e.g. the RSA code. What I'm thinking of is this: * distribution sites within the US carry an "openssl-lite" distribution which has all the RSA code removed, plus anything else which is usage restricted (IDEA?). This absolves them from any legal liability for providing patented source code. International sites carry the full version. * Supposing someone in the US downloads the RSA code from an international site, the RSA code would only be built conditional on USA_RESIDENT == NO. Currently we don't set USA_RESIDENT out of the box (AFAIK) - this would mean that US people have to take explicit action in order to have RSA binary code built. At least this way no-one will accidentally ship a product containing RSA, although I don't know if it's still illegal to just possess (non-RSAREF) RSA source without a license. This has the downside that international folks have to also take explicit action to get RSA built, but it's probably better to be conservative and document the process well. I think it's high time we expanded our cryptographic support beyond the bare minimum of DES - anyone violently disagree? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 23:31:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 34BCE14BDB; Fri, 3 Dec 1999 23:31:47 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA35422; Fri, 3 Dec 1999 23:31:04 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: Importing OpenSSL In-reply-to: Your message of "Fri, 03 Dec 1999 23:26:04 PST." Date: Fri, 03 Dec 1999 23:31:04 -0800 Message-ID: <35418.944292664@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think you should look at exactly how OpenBSD 2.6 has integrated it and then report back with your amended proposal. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 3 23:39:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 87C9C151B4; Fri, 3 Dec 1999 23:39:09 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id JAA11750; Sat, 4 Dec 1999 09:35:59 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199912040735.JAA11750@gratis.grondar.za> To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: Importing OpenSSL Date: Sat, 04 Dec 1999 09:35:59 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think it's high time we expanded our cryptographic support beyond the > bare minimum of DES - anyone violently disagree? On the contrary; I violently agree! We need to make OpenSSH work with K5 as a matter of priority. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 0:21: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 8527514DDD; Sat, 4 Dec 1999 00:21:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 765261CD7C0; Sat, 4 Dec 1999 00:21:07 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 4 Dec 1999 00:21:07 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Importing OpenSSL In-Reply-To: <35418.944292664@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 3 Dec 1999, Jordan K. Hubbard wrote: > I think you should look at exactly how OpenBSD 2.6 has integrated it > and then report back with your amended proposal. :-) It looks like they distribute RSA to everyone, including the US mirrors, and it's not built by default unless you take explicit action to enable it (i.e. it just builds a subset of the full distribution). Last time I raised this, a few people expressed concerns about their mirrors carrying patented code which might cause them legal issues, but the "default is no RSA" policy is the same as what I proposed. Unfortunately, that will probably mean no openssh out of the box, since it depends on RSA :-( Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 0:39:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns1.portal2.com (ns1.portal2.com [203.85.226.193]) by hub.freebsd.org (Postfix) with SMTP id 8702014D64 for ; Sat, 4 Dec 1999 00:39:33 -0800 (PST) (envelope-from yusufg@outblaze.com) Received: (qmail 55997 invoked from network); 4 Dec 1999 08:37:10 -0000 Received: from yusufg.portal2.com (qmailr@203.85.226.249) by ns1.portal2.com with SMTP; 4 Dec 1999 08:37:10 -0000 Received: (qmail 11150 invoked by uid 500); 4 Dec 1999 08:37:08 -0000 Date: 4 Dec 1999 08:37:08 -0000 Message-ID: <19991204083708.11149.qmail@yusufg.portal2.com> From: Yusuf Goolamabbas To: freebsd-current@freebsd.org Subject: Is there anything special to do for a first time cvsup to current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have been doing cvsup to -stable and buildworlds for close to a year and have subscribed to the cvs-all list , I read archives of -current/-stable regularly and recently decided to do my first cvsup -current After moving to -current, I did a /usr/sbin/config and it complained about "machine i386" and cpu "I386_CPU". Do I have to do anything diffent for -current compared to -stable Cheers, Yusuf -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 0:42:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3405014D64; Sat, 4 Dec 1999 00:42:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA35641; Sat, 4 Dec 1999 00:41:52 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: Importing OpenSSL In-reply-to: Your message of "Sat, 04 Dec 1999 00:21:07 PST." Date: Sat, 04 Dec 1999 00:41:52 -0800 Message-ID: <35638.944296912@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It looks like they distribute RSA to everyone, including the US mirrors, > and it's not built by default unless you take explicit action to enable it > (i.e. it just builds a subset of the full distribution). Last time I Hmm, according to their own press, there's some mechanism more clever than that which automatically downloads the "appropriate" RSA code for US vs non-US people. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 0:56: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id B67C21512D; Sat, 4 Dec 1999 00:56:04 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id ABB921CD7EF; Sat, 4 Dec 1999 00:56:04 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 4 Dec 1999 00:56:04 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Importing OpenSSL In-Reply-To: <35638.944296912@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 4 Dec 1999, Jordan K. Hubbard wrote: > > It looks like they distribute RSA to everyone, including the US mirrors, > > and it's not built by default unless you take explicit action to enable it > > (i.e. it just builds a subset of the full distribution). Last time I > > Hmm, according to their own press, there's some mechanism more clever > than that which automatically downloads the "appropriate" RSA code for > US vs non-US people. Perhaps it's different in 2.6: I checked a US mirror which only carried 2.5. I'll look for a 2.6 one.. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 0:57:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 234D91512D; Sat, 4 Dec 1999 00:57:57 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA16237; Sat, 4 Dec 1999 00:57:04 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA03932; Sat, 4 Dec 1999 00:57:04 -0800 (PST) (envelope-from obrien) Date: Sat, 4 Dec 1999 00:57:04 -0800 From: "David O'Brien" To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: Importing OpenSSL Message-ID: <19991204005703.A3903@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <35418.944292664@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Sat, Dec 04, 1999 at 12:21:07AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Last time I raised this, a few people expressed concerns about their > mirrors carrying patented code which might cause them legal issues, NO. There are not patent problems until you *USE* the code. The issue is the export of encryption from the US. That is the concern with RSA and IDEA. You will probably need to import RSA, IDEA, etc the same way we do DES. In a separate area, and then have Internat.FreeBSD.org import it also. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 1: 8:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 03BBD1512D for ; Sat, 4 Dec 1999 01:08:50 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id JAA04242; Sat, 4 Dec 1999 09:46:02 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id JAA55879; Sat, 4 Dec 1999 09:46:26 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912040846.JAA55879@yedi.iaf.nl> Subject: Re: -current no longer builds on the alpha In-Reply-To: from Matthew Jacob at "Dec 3, 1999 10:23:13 pm" To: mjacob@feral.com Date: Sat, 4 Dec 1999 09:46:26 +0100 (CET) Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Matthew Jacob wrote ... > > Q'uelle strange- what I have... well, we'll see what my nightly build > brings... Mine fell over in 'truss'. I already reported it to Marcel, looks like something was changed in kdump/mkioctls, a script that 'truss' also uses. > > On Fri, 3 Dec 1999, Jordan K. Hubbard wrote: > > > > What is beast? I was happily able to build -current at about 5 this > > > morning on a pc164. > > > > It's an Aspen systems DEC Durango PC164 motherboard based system. Doesn't that one have ECC memory (refering to a previous post where you theorised a bit on memory problems and sig-11s ;) -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 1:23: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id C14B115355 for ; Sat, 4 Dec 1999 01:23:00 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id KAA04907; Sat, 4 Dec 1999 10:05:17 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id KAA56241; Sat, 4 Dec 1999 10:03:22 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912040903.KAA56241@yedi.iaf.nl> Subject: Re: Is there anything special to do for a first time cvsup to current In-Reply-To: <19991204083708.11149.qmail@yusufg.portal2.com> from Yusuf Goolamabbas at "Dec 4, 1999 8:37: 8 am" To: yusufg@outblaze.com (Yusuf Goolamabbas) Date: Sat, 4 Dec 1999 10:03:21 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Yusuf Goolamabbas wrote ... > Hi, I have been doing cvsup to -stable and buildworlds for close to a > year and have subscribed to the cvs-all list , I read archives of > -current/-stable regularly and recently decided to do my first cvsup > -current > > After moving to -current, I did a /usr/sbin/config and it > complained about "machine i386" and cpu "I386_CPU". Do I have to do > anything diffent for -current compared to -stable Loose the "" See the LINT file that comes with -current -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 1:45: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 74C5A14A2C for ; Sat, 4 Dec 1999 01:45:00 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 95004 invoked by uid 1001); 4 Dec 1999 09:44:44 +0000 (GMT) To: jkh@zippy.cdrom.com Cc: current@FreeBSD.ORG Subject: Re: Importing OpenSSL From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 04 Dec 1999 00:41:52 -0800" References: <35638.944296912@zippy.cdrom.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 04 Dec 1999 10:44:44 +0100 Message-ID: <95002.944300684@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It looks like they distribute RSA to everyone, including the US mirrors, > > and it's not built by default unless you take explicit action to enable it > > (i.e. it just builds a subset of the full distribution). Last time I > > Hmm, according to their own press, there's some mechanism more clever > than that which automatically downloads the "appropriate" RSA code for > US vs non-US people. Theo de Raadt posted the following to BUGTRAQ a couple of days ago (extract). "OpenBSD ships with applications using public key cryptography. Because we are trying to make release CDROMs for the entire world, we cannot put RSA onto the CD (yeah, major bummer). Instead, we've made it so that the RSA patented code stays in a package containing some shared libraries, and our installation software installs this package from over the 'net. Each package contains two shared libraries: libcrypto and libssl; just like regular OpenSSL. People outside the USA can use these two libraries, found in the "ssl26" package. Non-commercial entities in the USA cannot -- because of the patent issue -- and for them we provide the "sslUSA26" package. Commercial entities in the USA must contact RSA for a licence, or wait till next September. The "sslUSA26" package is OpenSSL, like the other package, but we have removed the OpenSSL RSA code and replaced it with RSAREF2. This permits the non-commercial use of "sslUSA26" inside the USA. Commercial users who think they can use the RSA without a licence in the USA should see a lawyer and a therapist." Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 2:35:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 863E914F48 for ; Sat, 4 Dec 1999 02:35:37 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id LAA09672; Sat, 4 Dec 1999 11:34:54 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id LAA03764; Sat, 4 Dec 1999 11:34:52 +0100 (MEZ) Date: Sat, 4 Dec 1999 11:34:52 +0100 From: Martin Blapp To: "Alexander N. Kabaev" Cc: freebsd-current@freebsd.org Subject: Re: rpc.umntall does not work with AIX [LONG] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Well, it seems like RPCMNT_UMNTALL call always fails with RPC_SYSTEMERROR on > all systems except FreeBSD. I tested HP/UX, AIX and Solaris boxes - they all > behave identically as follows: exactly. The other systems reply is 5, which is MNT_IOERR for the authentification handle. I still do not know the reason for this. The call iteslf gets accepted and executed on the remote system. > rpc.umntall -h $HOST always fails > rpc.umntall -h $HOST -p $DIR - works just fine since it is using RPCMNT_UMOUNT > umount $HOST:$DIR works just fine > > Interesting, even if RPC_UMNTALL call returns error code, it nonetheless > causes mount entry to be removed from the server, i.e. showmount -a $HOST > output does not report my client machine as having any mounts on $HOST anymore. > > All entries in my /var/db/mounttab appear to be correct, I do not think they > are causing the problem. > > Also, I have questions regarding the following code fragment from the > rpc.umntall.c file: I'll fix this. > > > It seems like it does RPCMNT_UMNTALL call for each mounttab entry regardless of > the -k parameter passed in the command line, while man page suggests that > it should simply skip entries for currently mounted filesystems. > > > Furthermore, using RPC_UMNTALL in the above loop is probably not a good idea > either because client host may have two different directories mounted from the > same server. If -k flag is specified, you cannot use UMNTALL because it will > remove /var/run/mountdtab entries not only for the mount point left over > from the crash but also for all other mounts some of which may be perfectly > valid and should be kept intact. I'll add a check for this. Probably it is better to kill use UMNT instead of UMNTALL as you said. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 3:54:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id E35D614FF8 for ; Sat, 4 Dec 1999 03:54:08 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id WAA23815; Sat, 4 Dec 1999 22:58:22 +1100 Date: Sat, 4 Dec 1999 22:52:19 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: tstromberg@rtci.com Cc: freebsd-current@FreeBSD.ORG, mdillon@apollo.backplane.com Subject: Re: More crashes under heavy exec() load in -CURRENT (and strange savecore) In-Reply-To: <84694702.944254987164.JavaMail.chenresig@karma> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > #0 boot (howto=256) at ../../kern/kern_shutdown.c:273 > 273 dumppcb.pcb_cr3 = rcr3(); > (kgdb) bt > #0 boot (howto=256) at ../../kern/kern_shutdown.c:273 > #1 0xc0132295 in panic (fmt=0xc0244fcf "page fault") at ../../kern/kern_shutdown.c:523 > #2 0xc02158e2 in trap_fatal (frame=0xcf71ad9c, eva=0) at ../../i386/i386/trap.c:908 > #3 0xc0215595 in trap_pfault (frame=0xcf71ad9c, usermode=0, eva=0) at ../../i386/i386/trap.c:801 > #4 0xc0215167 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16777232, tf_edi = 0, tf_esi = -1071179392, tf_ebp = -814633492, > tf_isp = -814633528, tf_ebx = -1071179392, tf_edx = 0, tf_ecx = 11, tf_eax = 0, tf_trapno = 12, tf_err = 2, > tf_eip = -1071807687, tf_cs = 8, tf_eflags = 66118, tf_esp = -1071172824, tf_ss = -814624768}) > at ../../i386/i386/trap.c:425 > #5 0xc01d8339 in _vm_map_clip_end (map=0xc0273328, entry=0xc0271980, end=3480358912) at ../../vm/vm_map.c:835 > #6 0xc01d93bf in vm_map_delete (map=0xc0273328, start=3480342528, end=3480358912) at ../../vm/vm_map.c:1751 > #7 0xc01d9536 in vm_map_remove (map=0xc0273328, start=3480342528, end=3480358912) at ../../vm/vm_map.c:1822 > #8 0xc01d747d in kmem_free (map=0xc0273328, addr=3480342528, size=16384) at ../../vm/vm_kern.c:233 > #9 0xc0141731 in pipeclose (cpipe=0xccd40a20) at ../../kern/sys_pipe.c:1093 > #10 0xc014161d in pipe_close (fp=0xc3154540, p=0xcf67a300) at ../../kern/sys_pipe.c:1049 PR 15235 has some fixes for pipe bugs. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 4: 2:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 9C60114FF8; Sat, 4 Dec 1999 04:02:42 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id XAA24129; Sat, 4 Dec 1999 23:08:07 +1100 Date: Sat, 4 Dec 1999 23:02:04 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "Richard S. Straka" Cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: ide dma support not enabled In-Reply-To: <3848AAB0.6EA5AA6C@home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 3 Dec 1999, Richard S. Straka wrote: > A kernel built from current source which was cvsup'ed today at > approximately 10:00 pm MST no longer enables DMA support on my > IDE drives. A previous kernel from 27 Nov had no problems > recognizing and enabling IDE DMA support. This was broken in rev.1.132 of sys/pci.pci.c. Quick fix (ifdef away rev.1.132): diff -c2 pci.c~ pci.c *** pci.c~ Sat Dec 4 20:08:44 1999 --- pci.c Sat Dec 4 22:28:37 1999 *************** *** 879,884 **** --- 879,888 ---- if (name) { device_set_desc_copy(dev, name); + #ifdef WANT_BROKEN_IDE_PCI /* Allow newbus drivers to match "better" */ error = -1000; + #else + error = 0; + #endif } } Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 7:18: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 7CC9614C9A; Sat, 4 Dec 1999 07:17:58 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA18710; Sat, 4 Dec 1999 10:17:18 -0500 (EST) (envelope-from wollman) Date: Sat, 4 Dec 1999 10:17:18 -0500 (EST) From: Garrett Wollman Message-Id: <199912041517.KAA18710@khavrinen.lcs.mit.edu> To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: Importing OpenSSL In-Reply-To: <19991204005703.A3903@dragon.nuxi.com> References: <35418.944292664@zippy.cdrom.com> <19991204005703.A3903@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > NO. There are not patent problems until you *USE* the code. That's not clear. See also ``contributory infringement''. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 7:18:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id BF66F14EC1 for ; Sat, 4 Dec 1999 07:18:34 -0800 (PST) (envelope-from charnier@xp11.frmug.org) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id QAA19816 for current@FreeBSD.org; Sat, 4 Dec 1999 16:18:29 +0100 (CET) (envelope-from charnier@xp11.frmug.org) Received: from xp11.frmug.org (xp11.frmug.org [127.0.0.1]) by xp11.frmug.org (8.9.3/8.9.2/xp11-uucp-1.1) with ESMTP id OAA24991 for ; Sat, 4 Dec 1999 14:52:01 +0100 (CET) (envelope-from charnier@xp11.frmug.org) Message-Id: <199912041352.OAA24991@xp11.frmug.org> To: current@FreeBSD.org Subject: incorrect output in pstat -s Date: Sat, 04 Dec 1999 14:52:01 +0100 From: "Philippe Charnier" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Running pstat -s, I get: Device 1K-blocks Used Avail Capacity Type /dev/rda0s2b 131808 0 131808 0% Interleaved /dev/rda1s1b 66432 0 66432 0% Interleaved /dev/rda2s1b 32640 0 32640 0% Interleaved /dev/rda3s1b 32640 0 32640 0% Interleaved Total 263520 0 263520 0% Which I corrected with the following changes. Printing /dev/da... instead of /dev/rda... is maybe a better fix? Index: pstat.c =================================================================== RCS file: /home0h/FreeBSD.cvsroot/src/usr.sbin/pstat/pstat.c,v retrieving revision 1.46 diff -u -r1.46 pstat.c --- pstat.c 1999/11/27 17:03:07 1.46 +++ pstat.c 1999/12/04 13:42:02 @@ -996,13 +996,13 @@ header = getbsize(&hlen, &blocksize); if (totalflag == 0) { - (void)printf("%-11s %*s %8s %8s %8s %s\n", + (void)printf("%-12s %*s %8s %8s %8s %s\n", "Device", hlen, header, "Used", "Avail", "Capacity", "Type"); for (i = 0; i < n; ++i) { (void)printf( - "%-11s %*d ", + "%-12s %*d ", kswap[i].ksw_devname, hlen, CONVERT(kswap[i].ksw_total) @@ -1029,7 +1029,7 @@ ); } else if (n > 1) { (void)printf( - "%-11s %*d %8d %8d %5.0f%%\n", + "%-12s %*d %8d %8d %5.0f%%\n", "Total", hlen, CONVERT(kswap[n].ksw_total), ------ ------ Philippe Charnier charnier@{lirmm.fr,xp11.frmug.org,FreeBSD.org} ``a PC not running FreeBSD is like a venusian with no tentacles'' ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 7:56: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E1D2614FB6 for ; Sat, 4 Dec 1999 07:56:04 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id HAA09955; Sat, 4 Dec 1999 07:57:03 -0800 Date: Sat, 4 Dec 1999 07:57:03 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte , "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: -current no longer builds on the alpha In-Reply-To: <199912040846.JAA55879@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As Matthew Jacob wrote ... > > > > Q'uelle strange- what I have... well, we'll see what my nightly build > > brings... > > Mine fell over in 'truss'. I already reported it to Marcel, looks > like something was changed in kdump/mkioctls, a script that 'truss' also > uses. Mine's still going (I start mine at 0430 PST8PDT, the update from freefall runs at 0107 PST8PDT)).... Nope, what a coincidence. It *just* finished. Went all the way through w/o errors on a buildworld. > > > > > On Fri, 3 Dec 1999, Jordan K. Hubbard wrote: > > > > > > What is beast? I was happily able to build -current at about 5 this > > > > morning on a pc164. > > > > > > It's an Aspen systems DEC Durango PC164 motherboard based system. > > Doesn't that one have ECC memory (refering to a previous post where > you theorised a bit on memory problems and sig-11s ;) It may or may not, but memory problems are typically detected pretty well on alphas and you'll get a 670 machine check if it was recoverable (which the PALcode has already done, except for TurboLaser if the memory problem was caused by one of the I/O boards (PALcode cannot go offboard to read registers on another board to find out what address was porked, IIRC)), or a 660 machine check, which is a panic. At any rate, this is a different entry point than mmu traps. It's not like I don't get sig-11s... ctags always seems to core dump on me- somewhere up in libc. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 8:17: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 1CE0414D36 for ; Sat, 4 Dec 1999 08:16:57 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.22]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA558C; Sat, 4 Dec 1999 17:16:24 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id RAA04038; Sat, 4 Dec 1999 17:16:17 +0100 (CET) (envelope-from asmodai) Date: Sat, 4 Dec 1999 17:16:17 +0100 From: Jeroen Ruigrok/Asmodai To: Maxim Sobolev Cc: Tony Finch , current@freebsd.org Subject: Re: Problem with syscons in VESA mode Message-ID: <19991204171617.E3330@daemon.ninth-circle.org> References: <3846A672.524B188A@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3846A672.524B188A@altavista.net>; from sobomax@altavista.net on Thu, Dec 02, 1999 at 07:03:46PM +0200 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991202 19:24], Maxim Sobolev (sobomax@altavista.net) wrote: >Tony Finch wrote: >> Maxim Sobolev wrote: >> > >> >but sometimes when I'm building world or some other app text >> >suddenly shifts from the edge of the screen by several spaces and >> >all text passed to the console after that also being printed with >> >that offset. >> >> I've seen this on -stable with standard large modes set by >> vidcontrol. > >It is interesting. Seems like it is not only VESA modes bug. Strange >that nobody else observed this misbehaviour. I see exact the same behaviour. When I switch between vty's the cursor seems to move back to the position where it should've been and when I press enter the new lines start at the normal position again. This is in VESA_132x25 using: VESA: v2.0, 4096k memory, flags:0x0, mode table:0xc02cc1c8 (10000a8) VESA: Tseng Labs ET6000 -- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Learn e-mail netiquette: http://www.lemis.com/email.html ...fools rush in where Daemons fear to tread. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 8:29:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 29AEA14CF6 for ; Sat, 4 Dec 1999 08:29:27 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (beefcake.zeta.org.au [203.26.10.12]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id DAA31234; Sun, 5 Dec 1999 03:34:05 +1100 Date: Sun, 5 Dec 1999 03:28:09 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Philippe Charnier Cc: current@FreeBSD.ORG Subject: Re: incorrect output in pstat -s In-Reply-To: <199912041352.OAA24991@xp11.frmug.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 4 Dec 1999, Philippe Charnier wrote: > Hello, > > Running pstat -s, I get: > > Device 1K-blocks Used Avail Capacity Type > /dev/rda0s2b 131808 0 131808 0% Interleaved > /dev/rda1s1b 66432 0 66432 0% Interleaved > /dev/rda2s1b 32640 0 32640 0% Interleaved > /dev/rda3s1b 32640 0 32640 0% Interleaved > Total 263520 0 263520 0% > > Which I corrected with the following changes. Printing /dev/da... instead > of /dev/rda... is maybe a better fix? Printing the 'r's is a temporary bug (*). The extra column that you added is required anyway for printing 2-digit unit numbers in "/dev/rda10s1b". One more column is required for printing 3-digit unit numbers in "/dev/rda100s1b". We support unit numbers up to 511, except for bugs like this. Several more columns are required for printing verbose driver names like "amrd". (*) If you have a current -current with /dev/da0s2b being a character device with the same device number as /dev/rda0s2b, then dev_mkdb(8) won't be able to create a one to one mapping between disk numbers and disk names. If /dev/da0s2b is still a block device, then there are more confusing aliasing problems due to the kernel translating the device numbers of bdevs without translating the corresponding names. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 9:28: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.az.home.com (ha1.rdc1.az.home.com [24.1.240.66]) by hub.freebsd.org (Postfix) with ESMTP id DC78C15192; Sat, 4 Dec 1999 09:28:02 -0800 (PST) (envelope-from straka@home.com) Received: from home.com ([24.1.209.47]) by mail.rdc1.az.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19991204172729.CGKF7363.mail.rdc1.az.home.com@home.com>; Sat, 4 Dec 1999 09:27:29 -0800 Message-ID: <38494F00.84C5E0D@home.com> Date: Sat, 04 Dec 1999 10:27:28 -0700 From: "Richard S. Straka" X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: Bruce Evans Cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: ide dma support not enabled References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: > On Fri, 3 Dec 1999, Richard S. Straka wrote: > > > A kernel built from current source which was cvsup'ed today at > > approximately 10:00 pm MST no longer enables DMA support on my > > IDE drives. A previous kernel from 27 Nov had no problems > > recognizing and enabling IDE DMA support. > > This was broken in rev.1.132 of sys/pci.pci.c. > > Quick fix (ifdef away rev.1.132): > > diff -c2 pci.c~ pci.c > *** pci.c~ Sat Dec 4 20:08:44 1999 > --- pci.c Sat Dec 4 22:28:37 1999 > *************** > *** 879,884 **** > --- 879,888 ---- > if (name) { > device_set_desc_copy(dev, name); > + #ifdef WANT_BROKEN_IDE_PCI > /* Allow newbus drivers to match "better" */ > error = -1000; > + #else > + error = 0; > + #endif > } > } > > Bruce Bruce, Works like a champ. IDE DMA is back. Thanks, Rich Straka straka@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 10: 1:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id C523814CD0 for ; Sat, 4 Dec 1999 10:01:15 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA01558 for current@freebsd.org; Sat, 4 Dec 1999 13:04:46 -0500 From: Bill Paul Message-Id: <199912041804.NAA01558@skynet.ctr.columbia.edu> Subject: HEADS UP: if_dc imports, al, ax, pn, dc and mx removed To: current@freebsd.org Date: Sat, 4 Dec 1999 13:04:45 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1350 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Heads up people: the if_dc driver and all its bits and pieces are now in the tree and the al, ax, dm, pn and mx drivers have been removed. People previously using these drivers need to update their /etc/rc.conf files accordingly. Also note that if_dc should now handle 21143-based NICs. If you were previously using if_de for a 21143 card, you may see if_dc take over support for it depending on your kernel config. If you have a 21143-based NIC which worked with if_de and *doesn't* work with if_dc, please let me know ASAP. Most 10/100 NICs should work fine: the only questionable ones are 10Mbps only versions. If you have a NIC that doesn't work, please show me the output of pciconf -l from your system when reporting a problem. As usual, the place to complain is: wpaul@skynet.ctr.columbia.edu. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 12:52:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 79BEC154CC for ; Sat, 4 Dec 1999 12:52:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA56920; Sat, 4 Dec 1999 12:51:59 -0800 (PST) (envelope-from dillon) Date: Sat, 4 Dec 1999 12:51:59 -0800 (PST) From: Matthew Dillon Message-Id: <199912042051.MAA56920@apollo.backplane.com> To: Dan Nelson Cc: current@FreeBSD.ORG Subject: Re: NFS client zeroing out blocks on write? References: <19991203112518.A43843@dan.emsphone.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I just upgraded a server from 2.2.8 to -current (991201 kernel) and am :seeing some NFS corruption. It looks like byte ranges are getting :zeroed out by the client (or not getting written at all, and the server :at the other end is filling with zeros?). I've seen it while writing :to both a Solaris 2.6 server (NFSv3) and a Netware NFS server (NFSv2), :so I'm pretty sure it's the client causing the problem. Hmm. I thought we had fixed all the zeroing problems. Are you sure you compiled your current up from the latest source? I am presuming there are no other clients accessing the output files while the split is running? Also, change your blankcheck program to display the ranges in hex, doing so brings to light the pattern. : fileaa : fileab : 168173568-168179199(5632) A062000-A063FFF : 384966656-384972287(5632) 16F22000-16F235FF Interesting. It looks very similar to a problem we fixed months ago. That problem was related only to NFSv3 and mmap(), and you aren't using mmap() here. It's disturbing to see this problem occur with both NFSv2 and NFSv3. I wonder if the problem occurs between a FreeBSD client and server. -Matt Matthew Dillon :All the zeroed out blocks start on an 8k NFS boundary, and I have :verified that the rest of the 8k block has the correct data in it. :Each corrupted block is always a multiple of 512 bytes long (so far :multiples are 6, 7, 11, and 12). : :On this example run, each file either has no corruption at all, or has :corruption with all the zeroed out ranges the same size. Dunno if this :matters, but it's interesting. : :If I run without nfsiod, or copy from a remote NFS mount to a remote :NFS mount, the corruption goes way down but still happens. I got only :one corrupted block in my 7-gig test run in each of those test cases. : :I'm afraid I don't know much about the internal workings of NFS, so I'm :hoping my description is enough to pinpoint the problem. : :-- : Dan Nelson : dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 13:24:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 5CB1F151A7 for ; Sat, 4 Dec 1999 13:24:26 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA32507; Sat, 4 Dec 1999 22:04:15 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id RAA81924; Sat, 4 Dec 1999 17:11:31 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912041611.RAA81924@yedi.iaf.nl> Subject: Re: -current no longer builds on the alpha In-Reply-To: from Matthew Jacob at "Dec 4, 1999 7:57: 3 am" To: mjacob@feral.com Date: Sat, 4 Dec 1999 17:11:31 +0100 (CET) Cc: jkh@time.cdrom.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Matthew Jacob wrote ... > > As Matthew Jacob wrote ... > > > > > > Q'uelle strange- what I have... well, we'll see what my nightly build > > > brings... > > > > Mine fell over in 'truss'. I already reported it to Marcel, looks > > like something was changed in kdump/mkioctls, a script that 'truss' also > > uses. > > Mine's still going (I start mine at 0430 PST8PDT, the update from > freefall runs at 0107 PST8PDT)).... Nope, what a coincidence. It *just* > finished. Went all the way through w/o errors on a buildworld. My buildworld is OK now. Minor snag in the truss Makefile that Marcel committed already. > > > > It's an Aspen systems DEC Durango PC164 motherboard based system. > > > > Doesn't that one have ECC memory (refering to a previous post where > > you theorised a bit on memory problems and sig-11s ;) > > It may or may not, but memory problems are typically detected pretty well Right, that is my experience. > on alphas and you'll get a 670 machine check if it was recoverable (which > the PALcode has already done, except for TurboLaser if the memory problem I don't have TL :) Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 13:52:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles545.castles.com [208.214.165.109]) by hub.freebsd.org (Postfix) with ESMTP id 015041534E for ; Sat, 4 Dec 1999 13:52:11 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA04820; Sat, 4 Dec 1999 13:53:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912042153.NAA04820@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: match@elen.utah.edu Cc: current@freebsd.org, mckusick@mckusick.com Subject: Mounting one FS on more than one system In-reply-to: Your message of "Sat, 04 Dec 1999 10:10:20 MST." <19991204170659.B8DEE5420@ee.elen.utah.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Dec 1999 13:53:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (moved to -current where there are more eyes that are interested) > P.S. Mike, at comdex I spoke to you some about clustering two > computers and one RAID array, remember? You mentioned that > someone had pursued that avenue some, perhaps not to a working > solution, but I don't remember who. Can you (or anyone else) point > me to the guilty parties? We would like to pick up the work and run > with it for a while. Yup, I remember. I also remember going through my stack of business cards wondering whether I remembered to get one from you; obviously not. 8) The sticking issue that we discussed was allowing more than one system to mount a given filesystem; I seemed to recall that Kirk has spoken about this before, and there may be some folks here (or Kirk himself, also copiedd) who may have some more input on the topic. Once this is resolved, everything else is (relatively!) straightforward... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 14: 5:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id E983614C2E; Sat, 4 Dec 1999 14:05:07 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id XAA14996; Sat, 4 Dec 1999 23:05:02 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: match@elen.utah.edu, current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: Mounting one FS on more than one system In-reply-to: Your message of "Sat, 04 Dec 1999 13:53:26 PST." <199912042153.NAA04820@mass.cdrom.com> Date: Sat, 04 Dec 1999 23:05:02 +0100 Message-ID: <14994.944345102@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912042153.NAA04820@mass.cdrom.com>, Mike Smith writes: >The sticking issue that we discussed was allowing more than one system to >mount a given filesystem; I pressume we're talking R/W mounts here, since a R/O mount obviously would not be a problem. With UFS/FFS there are significant meta-data caching which would need not only high-level locking (for atomic rename(2) calls) but also low-level locking (who allocates a particular free block). In short: a major hazzle. It might be possible to allow one machine R/W and have the others R/O snoop on the same device, but a more agressive write policy would be needed to get closer to real-time behaviour. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 14:38:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 9EB6515321 for ; Sat, 4 Dec 1999 14:38:15 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA03300; Sat, 4 Dec 1999 23:27:05 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA24045; Sat, 4 Dec 1999 23:15:16 +0100 (CET) (envelope-from wilko) From: Wilko Bulte Message-Id: <199912042215.XAA24045@yedi.iaf.nl> Subject: Re: -current no longer builds on the alpha In-Reply-To: <199912041611.RAA81924@yedi.iaf.nl> from Wilko Bulte at "Dec 4, 1999 5:11:31 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sat, 4 Dec 1999 23:15:16 +0100 (CET) Cc: mjacob@feral.com, jkh@time.cdrom.com, current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Wilko Bulte wrote ... > As Matthew Jacob wrote ... > > > > As Matthew Jacob wrote ... > > > > > > > > Q'uelle strange- what I have... well, we'll see what my nightly build > > > > brings... > > > > > > Mine fell over in 'truss'. I already reported it to Marcel, looks > > > like something was changed in kdump/mkioctls, a script that 'truss' also > > > uses. > > > > Mine's still going (I start mine at 0430 PST8PDT, the update from > > freefall runs at 0107 PST8PDT)).... Nope, what a coincidence. It *just* > > finished. Went all the way through w/o errors on a buildworld. > > My buildworld is OK now. Minor snag in the truss Makefile that Marcel > committed already. Make that: commited a fix for already. Blrgh. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 15:11:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from flamingo.McKusick.COM (flamingo.mckusick.com [209.31.233.178]) by hub.freebsd.org (Postfix) with ESMTP id C163815363; Sat, 4 Dec 1999 15:11:45 -0800 (PST) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id MAA05073; Sat, 4 Dec 1999 12:44:43 -0800 (PST) Message-Id: <199912042044.MAA05073@flamingo.McKusick.COM> To: Mike Smith Subject: Re: Mounting one FS on more than one system Cc: match@elen.utah.edu, current@freebsd.org In-reply-to: Your message of "Sat, 04 Dec 1999 13:53:26 PST." <199912042153.NAA04820@mass.cdrom.com> Date: Sat, 04 Dec 1999 12:44:43 -0800 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: match@elen.utah.edu cc: current@freebsd.org, mckusick@mckusick.com Subject: Mounting one FS on more than one system In-reply-to: Your message of "Sat, 04 Dec 1999 10:10:20 MST." <19991204170659.B8DEE5420@ee.elen.utah.edu> Date: Sat, 04 Dec 1999 13:53:26 -0800 From: Mike Smith (moved to -current where there are more eyes that are interested) > P.S. Mike, at comdex I spoke to you some about clustering two > computers and one RAID array, remember? You mentioned that > someone had pursued that avenue some, perhaps not to a working > solution, but I don't remember who. Can you (or anyone else) point > me to the guilty parties? We would like to pick up the work and run > with it for a while. Yup, I remember. I also remember going through my stack of business cards wondering whether I remembered to get one from you; obviously not. 8) The sticking issue that we discussed was allowing more than one system to mount a given filesystem; I seemed to recall that Kirk has spoken about this before, and there may be some folks here (or Kirk himself, also copiedd) who may have some more input on the topic. Once this is resolved, everything else is (relatively!) straightforward... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com Mounting on more than one system is generally problematical unless you are willing to have all systems read-only. The problem is cache coherence between the machines. If one changes a block, the other machines will not see it. Basically, this is why we have the NFS filesystem. That lets a disk be mounted on one machine, but shared out to others. If you wanted to write a protocol that would allow for multiple machines, then you would need to have some central coordinator running some sort of coherency protocol with a complexity akin to that of NFS. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 15:47: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id B231F14C2E; Sat, 4 Dec 1999 15:46:59 -0800 (PST) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (azure.dstc.edu.au [130.102.176.27]) by piglet.dstc.edu.au (8.9.3/8.9.3) with ESMTP id JAA14780; Sun, 5 Dec 1999 09:44:33 +1000 (EST) To: Kirk McKusick Cc: Mike Smith , match@elen.utah.edu, current@FreeBSD.ORG Subject: Re: Mounting one FS on more than one system In-reply-to: Your message of "Sat, 04 Dec 1999 12:44:43 PST." <199912042044.MAA05073@flamingo.McKusick.COM> Date: Sun, 05 Dec 1999 09:44:32 +1000 Message-ID: <1082.944351072@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Allowing for cache writeback delays, is the speed of direct-to-shared-disk fast enough that using NFS as an "abstraction" layer would be faster than any network extant? Would it be as fast? would the effort to make this work exceed the cost of making real networks exist? It would seem that there might be opportunities to do 'cut through' in the coding for known-private files after open (ok, inode allocation/extension has problems) to optimize them to at-worst 'disk+bits' instead of NFS costs. If one party mounts -r the FS (eg news spool) then does this reduce the complexity? eg /usr mounted read-mostly for a bunch of tightly coupled boxes. If some other protocol is used for interlock, does this make mmap shares across clusters faster? -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 16: 2:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id AFFF0152F5; Sat, 4 Dec 1999 16:02:16 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id QAA87504; Sat, 4 Dec 1999 16:01:53 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id QAA39637; Sat, 4 Dec 1999 16:01:52 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <199912050001.QAA39637@realtime.exit.com> Subject: Re: Mounting one FS on more than one system In-Reply-To: <1082.944351072@dstc.edu.au> from George Michaelson at "Dec 5, 1999 09:44:32 am" To: ggm@dstc.edu.au (George Michaelson) Date: Sat, 4 Dec 1999 16:01:52 -0800 (PST) Cc: mckusick@flamingo.McKusick.COM (Kirk McKusick), msmith@FreeBSD.ORG (Mike Smith), match@elen.utah.edu, current@FreeBSD.ORG Reply-To: frank@exit.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Regarding a filesystem mounted on multiple boxes, check out DFS; there's a spec available from the Open Group in the UK for $58.00: http://www.opengroup.org/pubs/catalog.saved/p409.htm If you allow multiple R/W mounts, it's certainly not trivial. As Kirk said, you need a strong coherency mechanism; DFS uses a token mechanism invented, AFAIK, by Locus Computing Corporation. I work on the former Locus clustering stuff (for Compaq, these days), so I can't really contribute, but I know there are white papers and other docs out there. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 17:29:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from flamingo.McKusick.COM (flamingo.mckusick.com [209.31.233.178]) by hub.freebsd.org (Postfix) with ESMTP id 0C82A15366; Sat, 4 Dec 1999 17:29:51 -0800 (PST) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id PAA05208; Sat, 4 Dec 1999 15:02:18 -0800 (PST) Message-Id: <199912042302.PAA05208@flamingo.McKusick.COM> To: George Michaelson Subject: Re: Mounting one FS on more than one system Cc: Mike Smith , match@elen.utah.edu, current@freebsd.org In-reply-to: Your message of "Sun, 05 Dec 1999 09:44:32 +1000." <1082.944351072@dstc.edu.au> Date: Sat, 04 Dec 1999 15:02:18 -0800 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To: Kirk McKusick cc: Mike Smith , match@elen.utah.edu, current@FreeBSD.ORG Subject: Re: Mounting one FS on more than one system In-reply-to: Your message of "Sat, 04 Dec 1999 12:44:43 PST." <199912042044.MAA05073@flamingo.McKusick.COM> Date: Sun, 05 Dec 1999 09:44:32 +1000 From: George Michaelson Let me start by saying that I do not have the definitive answers to all your questions. I'll take a crack at some of them. Allowing for cache writeback delays, is the speed of direct-to-shared-disk fast enough that using NFS as an "abstraction" layer would be faster than any network extant? The gains come from being able to read data directly from the disk rather than transferring it across the network. However, the cost of maintaining cache coherency would be at least as difficult and bandwidth consuming as a distributed filesystem. Would it be as fast? would the effort to make this work exceed the cost of making real networks exist? As the network speed approaches the disk speed, the gains would diminish. It would seem that there might be opportunities to do 'cut through' in the coding for known-private files after open (ok, inode allocation/extension has problems) to optimize them to at-worst 'disk+bits' instead of NFS costs. The problem is in identifying when private goes to shared. Also as you point out, new block and inode allocations have to be centrally coordinated. If one party mounts -r the FS (eg news spool) then does this reduce the complexity? eg /usr mounted read-mostly for a bunch of tightly coupled boxes. If any machine can write, then all the other machines have to have some way of keeping their caches consistent with the machine that did the modification. If some other protocol is used for interlock, does this make mmap shares across clusters faster? Mmap sharing across machines is going to be slow. I have never been a fan of distributed shared memory as a programming model, and this does not look like a way of making it run any faster. -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 18:48:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5B8C8153BC for ; Sat, 4 Dec 1999 18:48:11 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id SAA11863 for ; Sat, 4 Dec 1999 18:48:13 -0800 Date: Sat, 4 Dec 1999 18:48:13 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: current@freebsd.org Subject: disklabel -W now seems to not work(?) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that in the latest running around with things, disklabel -W doesn't seem to quite work, at least on the alpha- it seems to set the label writable, but the next attempt to open the disk sets the label area non-writable again. Before I go tracking this down as a bug, is it? Secondly, how do people feel about having dd(1) use the DIOCWLABEL argument to enable writing the label area of the disk if the output is a disk and there is no offset from zero? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 4 20: 2:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (Postfix) with ESMTP id E932A1513C for ; Sat, 4 Dec 1999 20:02:39 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from ida-89-77.Reshall.Berkeley.EDU (ida-89-77.Reshall.Berkeley.EDU [169.229.89.77]) by soda.CSUA.Berkeley.EDU (8.8.8/) via ESMTP id UAA06790 for ; Sat, 4 Dec 1999 20:01:38 -0800 (PST) env-from (brian@CSUA.Berkeley.EDU) Date: Sat, 4 Dec 1999 20:01:43 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: current@freebsd.org Subject: mount(2) broken? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After an unfortunate hard reboot today, the system fscked everything and then barfed attempting to mount /, claiming it to be unclean. I dropped to single-user mode and proceeded to re-fsck / and then tried to mount it again to no avail. Rebooting didn't help things either. # fsck -p /dev/wd0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/wd0s1a: clean, 157026 free (2306 frags, 19340 blocks, 0.8% fragmentation) /dev/wd0s2f: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/wd0s2f: clean, 1089990 free (10286 frags, 134963 blocks, 0.2% fragmentation ) /dev/wd0s2e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/wd0s2e: clean, 564709 free (23093 frags, 67702 blocks, 1.9% fragmentation) /dev/wd1s1e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/wd1s1e: clean, 266984 free (72 frags, 33364 blocks, 0.0% fragmentation) /dev/wd1s2e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/wd1s2e: clean, 204574 free (25134 frags, 22430 blocks, 1.1% fragmentation) # mount / WARNING: R/W mount of / denied. Filesystem is not clean - run fsck mount: Operation not permitted # mount /dev/wd0s1a on / (ufs, local, read-only, writes: sync 12 async 3, reads: sync 11 3 async 3) # mount /dev/wd0s1a on / (ufs, local, read-only, writes: sync 12 async 3, reads: sync 11 3 async 3) # mount -a WARNING: R/W mount of / denied. Filesystem is not clean - run fsck mount: Operation not permitted # mount -f / WARNING: / was not properly dismounted # uname -a FreeBSD thought 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Dec 2 00:43:25 PST 1999 brian@thought:/usr/src/sys/compile/THOUGHT i386 -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message