From owner-freebsd-current Sun Oct 7 0:13:41 2001 Delivered-To: freebsd-current@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 9A3A637B403 for ; Sun, 7 Oct 2001 00:13:37 -0700 (PDT) Received: from mindspring.com (dialup-209.244.104.16.Dial1.SanJose1.Level3.net [209.244.104.16]) by pintail.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA16386; Sun, 7 Oct 2001 00:12:59 -0700 (PDT) Message-ID: <3BC000AE.405057F9@mindspring.com> Date: Sun, 07 Oct 2001 00:13:50 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Kris Kennaway , Nate Williams , Lyndon Nerenberg , Bernd Walter , current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit References: <20011006200417.B86A13808@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm wrote: > > Terry Lambert wrote: > > Peter Wemm wrote: > > > param.c was moved to kern/subr_param.c and is fully dynamic, and already > > > has these changes. > > > > Nice to know that my changes previously posted to -current in > > the 4.3 timeframe have been incorporated during the rewrite. > > BULLSHIT! They came from yahoo, pre-4.1 OK, so great minds think alike... they certainly hadn't been integrated in before the 4.3 release, since I did the original (of mine) back in early April, and posted it later that month. I think if you will examine the -current archives, you'll see my post; specifically: on April 24th. > > Thanks! > > No thanks! I never saw your post, and I resent the accusation! It was posted to -current (see above). > > Yeah; I made it last April, and posted it to -current, if you'll > > recollect. > > Well, I'm sorry, but we beat you. Good! It's an idea that was well past due! In any case, are the other patches going to be committed? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 0:17:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 635B737B406 for ; Sun, 7 Oct 2001 00:17:28 -0700 (PDT) Received: from mindspring.com (dialup-209.244.104.16.Dial1.SanJose1.Level3.net [209.244.104.16]) by pintail.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA23080; Sun, 7 Oct 2001 00:17:15 -0700 (PDT) Message-ID: <3BC001AD.82973943@mindspring.com> Date: Sun, 07 Oct 2001 00:18:05 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Kris Kennaway , Nate Williams , Lyndon Nerenberg , Bernd Walter , current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit References: <20011006202056.CD30C3808@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm wrote: > Incidently, *knowingly* posting patches that are a year out of date do not > look good for anybody. :-( 24 Apr 2001 was not a year ago. I won't get into the "we don't use -current" argument again; if you want the patches, take them. The diffs will apply cleanly for the most part, and those that don't will apply anyway, if you set the fuzz factor up. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 0:41: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 1D6CC37B401 for ; Sun, 7 Oct 2001 00:41:04 -0700 (PDT) Received: from mindspring.com (dialup-209.244.104.16.Dial1.SanJose1.Level3.net [209.244.104.16]) by falcon.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f977et620430; Sun, 7 Oct 2001 00:40:56 -0700 (PDT) Message-ID: <3BC00739.6633D737@mindspring.com> Date: Sun, 07 Oct 2001 00:41:45 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: KRIS: FOR YOU TO COMMIT: soft interrupt coelescing References: <20011006203219.AC2683808@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm wrote: > > This is based on ideas in the Jeff Mogul (DEC Western Research > > Labs) paper from 1995: > > These look like a subset of what Garrett was working on in 1996: Guess Jeff Mogul beat him to it; I wish Garrett's code had been committed, so I wouldn't have had to reinvent it myself. It's actually an idea from the serial communications era. Digital Press published a book by McNamara, called "Technical Aspects of Data Communication", which described taking a serial interrupt, and then polling like hell until there was no more data. This was really the only way to handle the highest possible baud rates on things like 8MHz PCs. My copy is from 1982. > > http://www.research.digital.com/wrl/techreports/abstracts/95.8.html > > http://ftp.digital.com/%7emogul/usenix96.ps > > > > Kris: Commit this... K PLZ THX. > > Certainly not with this lousy patch with no context! I don't understand the complaint. If it's the if_dc.c patch you are upset about, I *did* say the if_ti.c patch was cleaner. The problem is that the other drivers don't really lend themselves to doing this in a clean way, without a rewrite of the interrupt processing. If you can tell me what context you lack, or why you think the patch is lousy (it passes style(9), perhaps I can make you less negative? If it's just context, and you are unwilling to read the papers cited, the basic idea is this: 1) Handle interrupts normally 2) Have a seperate routine to do the transfer completion polling (almost every driver ever written by Bill Paul has this already) 3) Set a flag if any data was transferred (i.e. there was active data -- this will always be true for either the transmit or the receive the first time through) 4) Make the transmit and receive interrupt handlers return this flag 5) If the flag is set, repeat the process of the poll; this assumes that the interrupt notification is not the only notification of data transfer completion, and that there is a ring descriptor or other method to successfully determine if the data transfer has been completed, without needing an interrupt The result is that if a card is very, very busy, rather than taking an interrupt, doing ether input, and then exiting, only to immediately get an interrupt again, and taking the trap overhead twice and the restart overhead twice (or more), the single interrupt is used to do the work. In practice, this in itself will not prevent receiver livelock; it's a necessary, but not sufficient design change. As I also said: you're not going to see improvement from this unless you can drive the card at its highest rate. Clearly this would also be very applicable to non-Gigabit cards, but the only one we use is the FXP, and the FXP driver is very poorly structured for being able to do this type of thing (I really like Bill Paul's recent drivers much better). I can't test with other cards, and I'm not sure they meet the assumption I documented in #5, above. In any case, feel free to pee on it to make it smell like you, or rewrite it from scratch, if you want. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 0:46:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 2764437B408 for ; Sun, 7 Oct 2001 00:46:19 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.6/8.11.1) id f977jDv32286; Sun, 7 Oct 2001 00:45:13 -0700 (PDT) (envelope-from obrien) Date: Sun, 7 Oct 2001 00:45:13 -0700 From: "David O'Brien" To: Terry Lambert Cc: Kris Kennaway , Nate Williams , Lyndon Nerenberg , Bernd Walter , current@FreeBSD.ORG Subject: Re: uucp user shell and home directory Message-ID: <20011007004513.A32079@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <15292.43702.284147.973393@nomad.yogotech.com> <3BBD8369.835E9190@mindspring.com> <20011005130234.B79332@xor.obsecurity.org> <3BBEC328.BBA18D7C@mindspring.com> <20011006014817.A87811@xor.obsecurity.org> <3BBEC895.7DDC13C4@mindspring.com> <20011006021556.A88143@xor.obsecurity.org> <3BBECE11.94EDC09D@mindspring.com> <20011006025321.A88421@xor.obsecurity.org> <3BBEDC60.F8599D84@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BBEDC60.F8599D84@mindspring.com>; from tlambert2@mindspring.com on Sat, Oct 06, 2001 at 03:26:40AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Oct 06, 2001 at 03:26:40AM -0700, Terry Lambert wrote: > I could rent one at a colocation facility. But I live in Silicon > Valley, and I can't even get a connection faster than an ISDN line; > I'm 2000 feet "too far away" for DSL. Uh Terry, you know very well you have a freefall.freebsd.org account and thus the ability to publish files on ftp.freebsd.org. Nice how you leave out that detail as it does not back up your claim. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 0:56: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id 8EF2437B40F for ; Sun, 7 Oct 2001 00:55:57 -0700 (PDT) Received: from mindspring.com (dialup-209.244.104.16.Dial1.SanJose1.Level3.net [209.244.104.16]) by falcon.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f977tr610651; Sun, 7 Oct 2001 00:55:54 -0700 (PDT) Message-ID: <3BC00ABC.20ECAAD8@mindspring.com> Date: Sun, 07 Oct 2001 00:56:44 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: current@FreeBSD.ORG Subject: Re: Why do soft interrupt coelescing? References: <3BBF5E49.65AF9D8E@mindspring.com> <20011006144418.A6779@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > [ I don't particularly want to get involved in this thread...but... ] > > Can you explain why the ti(4) driver needs a coalescing patch? It already > has in-firmware coalescing paramters that are tuneable by the user. It > also already processes all outstanding BDs in ti_rxeof() and ti_txeof(). The answer to your question is that the card will continue to DMA into the ring buffer, even though you are in the middle of the interrupt service routine, and that the amount of time taken in ether input is long enough that you can have more packets come in while you are processing (this is actually a good thing). This is even *more* likely with hardware interrupt coelescing, since the default setting is to coelesce 32 packets into a single interrupt, meaning that you have up to 32 iterations of ether input to call, and thus the amount of time spent processing them actually affords *more* time for additional packets to come in. In my own personal situation, I have also implemented Lazy Receiver Processing (per the research done by Rice University and in the "Click Router" project; no relation to "ClickArray"), which does all stack processing at the hardware interrupt, rather then queueing between the hardware interrupt and NETISR, so my processing path is actually longer; I get more benefit from the change than you would, but on a heavily loaded system, you would also get some benefit, if you were able to load the wire heavily enough. The LRP implementation should be considered by FreeBSD as well, since it takes the connection rate from ~7,000/second up to ~23,000/second, by avoiding the NetISR. Rice University did an implementation in 2.2.x, and then another one (using resource containers -- I recommend against this one, not only because of license issues with the second implementation) for 4.2; both sets of research were done in FreeBSD. Unfortunately, neither implementation was production quality (among other things, they broke RFC 1323, and they have to run a complete duplicate stack as a different protocol family because some of their assumptions make it non-interoperable with other protocol stacks). > It isn't terribly clear what you're doing in the patch, since it isn't a > context diff. It's a "cvs diff" output. You could always check out a sys tree, apply it, and then cvs diff -c (or -u or whatever your favorite option is) to get a diff more to your tastes. > You also never gave any details behind your statement last week: > "Because at the time the Tigon II was released, the jumbogram > wire format had not solidified. Therefore cards built during > that time used different wire data for the jumbogram framing." > > I asked, in response: > > "Can you give more details? Did someone decide on a different ethertype > than 0x8870 or something? > > That's really the only thing that's different between a standard ethernet > frame and a jumbo frame. (other than the size)" I believe it was the implementation of the length field. I would have to get more information from the person who did the interoperability testing for the autonegotiation (which failed between the Tigon II and the Intel Gigabit cards). I can assure you anecdotally, however, that autonegotiation _did_ fail. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 0:58:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 3453037B418 for ; Sun, 7 Oct 2001 00:58:28 -0700 (PDT) Received: from mindspring.com (dialup-209.244.104.16.Dial1.SanJose1.Level3.net [209.244.104.16]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA20619; Sun, 7 Oct 2001 00:58:05 -0700 (PDT) Message-ID: <3BC00B3F.E7CE269A@mindspring.com> Date: Sun, 07 Oct 2001 00:58:55 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: current@FreeBSD.ORG Subject: Re: KRIS: FOR YOU TO COMMIT: soft interrupt coelescing References: <20011006204442.AB52E3808@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm wrote: > > Certainly not with this lousy patch with no context! > > To be clear: I was complaining about the non-context diff, not the diff > itself. We cant safely use it like this unless you give us an exact time/ > date of the corresponding freebsd version. OK. It was against FreeBSD 4.3-RELEASE (that was the last import of the code into the local source tree). I can convert the others to context diffs, as well, if you need them converted (the operation is trivial). I remember being yelled at before for sending context diffs instead of unidiffs! 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 1:10: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id D5A6237B403 for ; Sun, 7 Oct 2001 01:10:01 -0700 (PDT) Received: from mindspring.com (dialup-209.244.104.16.Dial1.SanJose1.Level3.net [209.244.104.16]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA06055; Sun, 7 Oct 2001 01:09:58 -0700 (PDT) Message-ID: <3BC00E08.1F800907@mindspring.com> Date: Sun, 07 Oct 2001 01:10:48 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit References: <20011005130234.B79332@xor.obsecurity.org> <3BBEC328.BBA18D7C@mindspring.com> <20011006014817.A87811@xor.obsecurity.org> <3BBEC895.7DDC13C4@mindspring.com> <20011006021556.A88143@xor.obsecurity.org> <3BBECE11.94EDC09D@mindspring.com> <20011006025321.A88421@xor.obsecurity.org> <3BBEDC60.F8599D84@mindspring.com> <20011006040424.A89151@xor.obsecurity.org> <3BBF584B.BA87E7ED@mindspring.com> <20011006161423.B98049@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway wrote: > No, Terry, I didn't offer you carte blanche to "submit any change to > FreeBSD and I'll commit it", I offered to commit your specific changes > to an area of FreeBSD you were complaining about (registration of > sysinstall distributions as packages), which I happened to agree > needed to be fixed. I called your bluff then, and I called it again > when you started complaining about the UUCP port. > > Here are the messages I sent you to which I refer above. You never > replied to either -- presumably because I'd pinned you down into a > position where you were forced to do work in order to continue. I did not see the second message, since Earthlink has screwed up my "lambert.org" email forwarding which Primenet never screwed up in the 5 years before Earthlink bought their dialup customers from Global crossing (who acquired Primenet). As to the work itself, I have been avoiding it, since we have a new person at ClickArray whose "trial by fire" is building an updated "developer workstation release CDROM" based on the FreeBSD 4.3-RELEASE plus our heavily modified kernel code, and our distribution package for our current release product (i.e. a CDROM that can be used to install engineering desktop machines, and can also be used as a "golden master" for the release engineering process). As soon as he has successfully been mentored through this process (which involves many local patches, some of which I posted to you, and which must be manually integrated, since the FreeBSD "add patches during ``make release''" doesn't work if you are patching the top level release Makefile), I will be able to turn my attention to it without stepping on his toes or his learning process. Thanks for the copy of the email I missed, and thanks for your patience until the release work in progress has been completed (new FreeBSD hackers have to come from somewhere, after all). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 1:13:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id B753637B401 for ; Sun, 7 Oct 2001 01:13:19 -0700 (PDT) Received: from mindspring.com (dialup-209.244.104.16.Dial1.SanJose1.Level3.net [209.244.104.16]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA09879; Sun, 7 Oct 2001 01:13:07 -0700 (PDT) Message-ID: <3BC00EC5.F0326FBE@mindspring.com> Date: Sun, 07 Oct 2001 01:13:57 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn Cc: Kris Kennaway , Nate Williams , Lyndon Nerenberg , Bernd Walter , current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit References: <44013.1002412762@axl.seasidesoftware.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sheldon Hearn wrote: > The change is not undefended. It's been made very clear from the > beginning that the security officer team sees the UUCP software as a > security liability, and would like the software "relegated" to ports so > as to limit the impact of vulnerabilities. The specific problem is the "--config" vulnerability noted on BugTraq, which ios easily fixed by "#ifdef'ing" it out. I understand that there have been a lot of bugs that have been listed as "FreeBSD bugs", when they were really software from third parties, but that's really no reason to be so hypersensitive about the distinction that FreeBSD becomes nothing more than the kernel and perl. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 1:24:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 0667937B401; Sun, 7 Oct 2001 01:24:41 -0700 (PDT) Received: from mindspring.com (dialup-209.244.104.16.Dial1.SanJose1.Level3.net [209.244.104.16]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA23097; Sun, 7 Oct 2001 01:24:38 -0700 (PDT) Message-ID: <3BC01179.E3DE2BA2@mindspring.com> Date: Sun, 07 Oct 2001 01:25:29 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: Kris Kennaway , Nate Williams , Lyndon Nerenberg , Bernd Walter , current@FreeBSD.ORG Subject: Re: uucp user shell and home directory References: <15292.43702.284147.973393@nomad.yogotech.com> <3BBD8369.835E9190@mindspring.com> <20011005130234.B79332@xor.obsecurity.org> <3BBEC328.BBA18D7C@mindspring.com> <20011006014817.A87811@xor.obsecurity.org> <3BBEC895.7DDC13C4@mindspring.com> <20011006021556.A88143@xor.obsecurity.org> <3BBECE11.94EDC09D@mindspring.com> <20011006025321.A88421@xor.obsecurity.org> <3BBEDC60.F8599D84@mindspring.com> <20011007004513.A32079@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Sat, Oct 06, 2001 at 03:26:40AM -0700, Terry Lambert wrote: > > I could rent one at a colocation facility. But I live in Silicon > > Valley, and I can't even get a connection faster than an ISDN line; > > I'm 2000 feet "too far away" for DSL. > > Uh Terry, you know very well you have a freefall.freebsd.org account and > thus the ability to publish files on ftp.freebsd.org. Nice how you leave > out that detail as it does not back up your claim. I haven't been able to log in since they went to SSH, which is one of the reasons my .forward file still points to terry@lambert.org insterad of tlambert2@mindspring.com, and email sent there currently bounces while I sort out the email forwarding issue for my domain with Earthlink, which doesn't provide the level of service of the ISP they purchased my dialup account from. It's also the reason I don't take down my UMICH LDAP patches (they were folded in with the UMICH code as the basis for the OpenLDAP project, so they're not really needed any more). Check the lastlog, if you don't believe me. I know that Garrett Wollman suffered from the same problem (the SSH changover shot him in the shorts) until just recently. I just (as in a matter of weeks) got SSH clients working on my local systems so I could work from home, but for file transfers, I'd still have to come out of the account to an FTP somewhere else (i.e. pull the files -- a chicken and egg problem, as I do not have an FTP server) or set up a procmail filter to capture and not forward specific email (I'm willing to do that). So while you are correct that there is an account there, I can't log into it right now, and I don't know to whom I should send the passwd file line now that I'm able to do that, since the changeover was long enough ago that the hosting for the machine has changed since then. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 3:39: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (Postfix) with ESMTP id E94B137B403; Sun, 7 Oct 2001 03:38:49 -0700 (PDT) Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM) id f97Ack5109847; Sun, 7 Oct 2001 19:38:46 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM) id f97AckE102756; Sun, 7 Oct 2001 19:38:46 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:LTYJOV/J2YnL9vQrQpxRylhiJ2deNwUq@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id TAA07886; Sun, 7 Oct 2001 19:48:40 +0900 (JST) Message-Id: <200110071048.TAA07886@zodiac.mech.utsunomiya-u.ac.jp> To: current@freebsd.org Cc: doc@freebsd.org, Giorgos Keramidas , yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Proposal: Replacement for VISUALUSERCONFIG (was: Re: Need to update man section 4!) In-reply-to: Your message of "Sun, 07 Oct 2001 15:13:36 JST." <200110070613.PAA06382@zodiac.mech.utsunomiya-u.ac.jp> References: <200110061018.TAA03313@zodiac.mech.utsunomiya-u.ac.jp> <20011006142219.A12443@hades.hell.gr> <200110070613.PAA06382@zodiac.mech.utsunomiya-u.ac.jp> Date: Sun, 07 Oct 2001 19:48:38 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG We can manipulate "device hints" and loader/kernel environment variables in /boot/device.hints by the "set/unset/show" commands in the boot loader(8). This corresponds to what we used to do in the USERCONFIG menu in the kernel. I think it may be a good idea to have "visual" (or friendly?) interface to manipulate the device hints (and other loader variables) in the boot loader, just like the VISUALUSERCONFIG front-end, for novice users and those who are not quite familiar with the boot loader commands. If we are to have this facility in the boot loader, we can get rid of USERCONFIG and VISUALUSERCONFIG from the kernel :-) I wrote an experimental patch to the boot loader. You can find it at: ftp://people.freebsd.org/~yokota/vuserconfig.tar.gz It includes: vuserconfig.diff patch for /sys/boot/common/Makefile.inc and /sys/boot/i386/libi386/vidconsole.c vuseconfig.c put this in /sys/boot/common hints.diff patch for /sys/i386/conf/GENERIC.hints (and /boot/device.hints) to add some descriptive strings for device drivers Rebuild the loader. Type "userconfig" at the loader prompt, then you will be in this VISUALUSERCONFIG-like front-end. Use TAB, ENTER, and cursor keys to navigate. Type 'Q' to quit, and you will be put back to the loader prompt. Some notes: - I don't intend to do everything in this front-end. It provides just a simple interface to set/reset/edit device hints and other variables. - This front-end is not an exact "clone" of VISUALUSERCONFIG. But the basic idea is the same. - Maybe I should have written this in Forth, rather than in C. But, I have almost nil knowledge of Forth. - One big drawback: this will bloat the boot loader and will consume precious disk space in kern.flp... *sigh* I welcome any comments, suggestions, and ideas. Thank you, Kazu In my previous post, I wrote: >Thank you for your comments. > >The User Config menu is completely disabled and isn't available >in -CURRENT now. > >I strongly doubt it will ever come back. You see, we can now >set/unset/edit device resource "hints" from the loader(8) prompt, >thus, there is little need to have the old User Config menu compiled >into the kernel. > >Please also have a look at my draft on the man page for device.hints(5). > >http://people.freebsd.org/~yokota/device.hints.5 > >The only thing which were available in the User Config, but is not in >the loader(8) is the "Visual" User Config option. > >But, I expect such visual front-end to edit the device resource hints >can be added to the loader, in one way or another. > >Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 3:52:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id 7CAD637B406; Sun, 7 Oct 2001 03:52:27 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f97Aqk280052; Sun, 7 Oct 2001 11:52:46 +0100 (BST) (envelope-from nik) Date: Sun, 7 Oct 2001 11:52:45 +0100 From: Nik Clayton To: Terry Lambert Cc: obrien@FreeBSD.ORG, Kris Kennaway , Nate Williams , Lyndon Nerenberg , Bernd Walter , current@FreeBSD.ORG Subject: Re: uucp user shell and home directory Message-ID: <20011007115245.D41288@clan.nothing-going-on.org> References: <20011005130234.B79332@xor.obsecurity.org> <3BBEC328.BBA18D7C@mindspring.com> <20011006014817.A87811@xor.obsecurity.org> <3BBEC895.7DDC13C4@mindspring.com> <20011006021556.A88143@xor.obsecurity.org> <3BBECE11.94EDC09D@mindspring.com> <20011006025321.A88421@xor.obsecurity.org> <3BBEDC60.F8599D84@mindspring.com> <20011007004513.A32079@dragon.nuxi.com> <3BC01179.E3DE2BA2@mindspring.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="tpXFRyzAyQ/GSAaD" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BC01179.E3DE2BA2@mindspring.com>; from tlambert2@mindspring.com on Sun, Oct 07, 2001 at 01:25:29AM -0700 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --tpXFRyzAyQ/GSAaD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 07, 2001 at 01:25:29AM -0700, Terry Lambert wrote: > So while you are correct that there is an account there, I can't > log into it right now, and I don't know to whom I should send > the passwd file line now that I'm able to do that, since the > changeover was long enough ago that the hosting for the > machine has changed since then. Send an ssh public key for your account to admins@freebsd.org. I suggest you sign this using PGP, or similar, so that they can verify the e-mail came from you. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --tpXFRyzAyQ/GSAaD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjvAM/0ACgkQk6gHZCw343VNWgCgkX7gLpqGJMXsWMi0tXoXHoKe UwgAnRJapL+AF81JdSJjPAnYcLBr0kOK =NaSg -----END PGP SIGNATURE----- --tpXFRyzAyQ/GSAaD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 8:20:53 2001 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 7D9A637B403 for ; Sun, 7 Oct 2001 08:20:50 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f97FLTh32994; Sun, 7 Oct 2001 10:21:29 -0500 (CDT) (envelope-from jlemon) Date: Sun, 7 Oct 2001 10:21:29 -0500 (CDT) From: Jonathan Lemon Message-Id: <200110071521.f97FLTh32994@prism.flugsvamp.com> To: tlambert2@mindspring.com, current@freebsd.org Subject: Re: KRIS: FOR YOU TO COMMIT: soft interrupt coelescing X-Newsgroups: local.mail.freebsd-current In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article you write: >Clearly this would also be very applicable to non-Gigabit cards, >but the only one we use is the FXP, and the FXP driver is very >poorly structured for being able to do this type of thing (I Oh, bah. The fxp clearly has the equivalent of fxp_rxeof and fxp_txeof routines, these are just inlined into the fxp_intr routine instead of being separate functions. It was all of 10 minutes work to break them out into separate functions. I did this to allow polled transmit/receive for some work in progress that will be committed soon. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 8:53: 8 2001 Delivered-To: freebsd-current@freebsd.org Received: from sii.linuxsweden.nu (h211n2fls32o867.telia.com [217.208.37.211]) by hub.freebsd.org (Postfix) with ESMTP id 14A3037B405 for ; Sun, 7 Oct 2001 08:53:05 -0700 (PDT) Received: (from siigron@localhost) by sii.linuxsweden.nu (8.11.4/8.11.3) id f97Fr5G43922 for freebsd-current@freebsd.org; Sun, 7 Oct 2001 17:53:05 +0200 (CEST) (envelope-from siigron) Date: Sun, 7 Oct 2001 17:53:05 +0200 (CEST) From: Joel Wilsson Message-Id: <200110071553.f97Fr5G43922@sii.linuxsweden.nu> To: freebsd-current@freebsd.org Subject: high-density floppies Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I'm copying in some tar-files, which are written directly to floppy disks. It worked fine for "normal" floppies, but now I have 7 floppies that fail (when I use "dd if=/dev/fd0 of=diskN.tar") with: fd0: hard error reading fsbn 0 (ST0 40 ST1 1 ST2 0 cyl 0 hd 0 sec 1) For the first floppies that got this error, I assumed they had been damaged. The reason I think they might NOT be damaged is that they are all of the same type (different type from the floppies I could read), and they are all "double density" floppies. So, I thought I'd try using a raw device configured for higher density disks. However, I can't find any such device; I only have /dev/fd0, but without devfs (in -stable) I had /dev/fd*. which is described in fdc(4) The fdc man page seem to be out of date. My question is, how can I do the equivalent of opening, for example, /dev/fd0.1720 (in -stable) under -current? Thanks, Joel Wilsson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 9: 8: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4BE2737B403; Sun, 7 Oct 2001 09:08:00 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f97G7au98499; Sun, 7 Oct 2001 10:07:36 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f97G7X752395; Sun, 7 Oct 2001 10:07:34 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110071607.f97G7X752395@harmony.village.org> To: Kazutaka YOKOTA Subject: Re: Proposal: Replacement for VISUALUSERCONFIG (was: Re: Need to update man section 4!) Cc: current@FreeBSD.ORG, doc@FreeBSD.ORG, Giorgos Keramidas In-reply-to: Your message of "Sun, 07 Oct 2001 19:48:38 +0900." <200110071048.TAA07886@zodiac.mech.utsunomiya-u.ac.jp> References: <200110071048.TAA07886@zodiac.mech.utsunomiya-u.ac.jp> <200110061018.TAA03313@zodiac.mech.utsunomiya-u.ac.jp> <20011006142219.A12443@hades.hell.gr> <200110070613.PAA06382@zodiac.mech.utsunomiya-u.ac.jp> Date: Sun, 07 Oct 2001 10:07:33 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200110071048.TAA07886@zodiac.mech.utsunomiya-u.ac.jp> Kazutaka YOKOTA writes: : - One big drawback: this will bloat the boot loader and will consume : precious disk space in kern.flp... *sigh* This is the only downside to the work that you've done. Sometimes I think we'd get more boot loader maintainers if we had LISP in the loader :-) Then again, maybe not... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 9:32:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 4C60637B40B for ; Sun, 7 Oct 2001 09:32:54 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.4/8.11.4) id f97GWVN91450; Sun, 7 Oct 2001 09:32:31 -0700 (PDT) (envelope-from sgk) Date: Sun, 7 Oct 2001 09:32:31 -0700 From: Steve Kargl To: Terry Lambert Cc: Peter Wemm , Kris Kennaway , Nate Williams , Lyndon Nerenberg , Bernd Walter , current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit Message-ID: <20011007093231.A91417@troutmask.apl.washington.edu> References: <20011006200417.B86A13808@overcee.netplex.com.au> <3BC000AE.405057F9@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BC000AE.405057F9@mindspring.com>; from tlambert2@mindspring.com on Sun, Oct 07, 2001 at 12:13:50AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Oct 07, 2001 at 12:13:50AM -0700, Terry Lambert wrote: > > Terry Lambert wrote: > > It was posted to -current (see above). > man send-pr A search of the GNATS databases with "terry" and "lambert" returns zero hits. The freebsd-current mailing list is not the preferred method for submission of patches and change requests. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 10:13:33 2001 Delivered-To: freebsd-current@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id CF27137B401; Sun, 7 Oct 2001 10:13:26 -0700 (PDT) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id f97HD7v36567; Sun, 7 Oct 2001 19:13:07 +0200 (CEST) (envelope-from wkb) Date: Sun, 7 Oct 2001 19:13:07 +0200 From: Wilko Bulte To: Warner Losh Cc: Kazutaka YOKOTA , current@FreeBSD.ORG, doc@FreeBSD.ORG, Giorgos Keramidas Subject: Re: Proposal: Replacement for VISUALUSERCONFIG (was: Re: Need to update man section 4!) Message-ID: <20011007191307.A36553@freebie.xs4all.nl> References: <200110071048.TAA07886@zodiac.mech.utsunomiya-u.ac.jp> <200110061018.TAA03313@zodiac.mech.utsunomiya-u.ac.jp> <20011006142219.A12443@hades.hell.gr> <200110070613.PAA06382@zodiac.mech.utsunomiya-u.ac.jp> <200110071048.TAA07886@zodiac.mech.utsunomiya-u.ac.jp> <200110071607.f97G7X752395@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110071607.f97G7X752395@harmony.village.org>; from imp@harmony.village.org on Sun, Oct 07, 2001 at 10:07:33AM -0600 X-OS: FreeBSD 4.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Oct 07, 2001 at 10:07:33AM -0600, Warner Losh wrote: > In message <200110071048.TAA07886@zodiac.mech.utsunomiya-u.ac.jp> Kazutaka YOKOTA writes: > : - One big drawback: this will bloat the boot loader and will consume > : precious disk space in kern.flp... *sigh* > > This is the only downside to the work that you've done. Sometimes I > think we'd get more boot loader maintainers if we had LISP in the > loader :-) Then again, maybe not... FWIW: everything that bloats the loader tends to break the alpha port. Caveat empor.. -- | / o / /_ _ email: wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 13:33: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 41E9037B401 for ; Sun, 7 Oct 2001 13:32:58 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 7 Oct 2001 21:32:57 +0100 (BST) To: current@freebsd.org Subject: Missing stack frames in kgdb/ddb traces Date: Sun, 07 Oct 2001 21:32:56 +0100 From: Ian Dowse Message-ID: <200110072132.aa77889@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I noticed recently two problems with gdb/ddb traces that involve an interrupt frame (both of these are in i386-specific code, but maybe similar issues exist on other architectures): The first is that kgdb sometimes messes up a stack frame that includes an interrupt, e.g in the trace below, the cpu_idle() frame is corrupted. #7 0xc0325246 in siointr1 (com=0xc092a400) at machine/cpufunc.h:63 #8 0xc0325137 in siointr (arg=0xc092a400) at ../../../isa/sio.c:1859 #9 0x8 in ?? () #10 0xc01ff391 in idle_proc (dummy=0x0) at ../../../kern/kern_idle.c:99 #11 0xc01ff210 in fork_exit (callout=0xc01ff370 , arg=0x0, frame=0xc40ffd48) at ../../../kern/kern_fork.c:785 This is because gdb was never updated when cpl was removed from the interrupt frame (ddb was changed in i386/i386/db_trace.c rev 1.37). The following patch seems to fix it: Index: gnu/usr.bin/binutils/gdb/i386/kvm-fbsd.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/gnu/usr.bin/binutils/gdb/i386/kvm-fbsd.c,v retrieving revision 1.27 diff -u -r1.27 kvm-fbsd.c --- gnu/usr.bin/binutils/gdb/i386/kvm-fbsd.c 19 Sep 2001 18:42:19 -0000 1.27 +++ gnu/usr.bin/binutils/gdb/i386/kvm-fbsd.c 7 Oct 2001 19:45:28 -0000 @@ -176,7 +176,7 @@ return (read_memory_integer (fr->frame + 8 + oEIP, 4)); case tf_interrupt: - return (read_memory_integer (fr->frame + 16 + oEIP, 4)); + return (read_memory_integer (fr->frame + 12 + oEIP, 4)); case tf_syscall: return (read_memory_integer (fr->frame + 8 + oEIP, 4)); Secondly, fast interrupts do not have an XresumeN style of symbol, so neither gdb nor ddb treat their frames as interrupt frames. This causes the frame listed as XfastintrN to gobble up the frame that was executing at the time of the interrupt, which is especially annoying when a serial console is being used to debug an infinite loop in the kernel. The following patch adds an XresumefastN to fast interrupt handlers, which allows gdb and ddb to correctly see the missing frame. The name Xresumefast is chosen because it involves no ddb or gdb changes (they just check for a name beginning with "Xresume"). Any comments? Ian Index: sys/i386/isa/icu_vector.s =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/i386/isa/icu_vector.s,v retrieving revision 1.29 diff -u -r1.29 icu_vector.s --- sys/i386/isa/icu_vector.s 12 Sep 2001 08:37:34 -0000 1.29 +++ sys/i386/isa/icu_vector.s 7 Oct 2001 19:48:06 -0000 @@ -60,6 +60,7 @@ mov %ax,%es ; \ mov $KPSEL,%ax ; \ mov %ax,%fs ; \ +__CONCAT(Xresumefast,irq_num): ; \ FAKE_MCOUNT((12+ACTUALLY_PUSHED)*4(%esp)) ; \ movl PCPU(CURTHREAD),%ebx ; \ incl TD_INTR_NESTING_LEVEL(%ebx) ; \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 13:45:34 2001 Delivered-To: freebsd-current@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 81F7437B401 for ; Sun, 7 Oct 2001 13:45:31 -0700 (PDT) Received: from mindspring.com (dialup-209.247.136.187.Dial1.SanJose1.Level3.net [209.247.136.187]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id NAA05031; Sun, 7 Oct 2001 13:44:47 -0700 (PDT) Message-ID: <3BC0BEF1.1D2725CE@mindspring.com> Date: Sun, 07 Oct 2001 13:45:37 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Steve Kargl Cc: Peter Wemm , Kris Kennaway , Nate Williams , Lyndon Nerenberg , Bernd Walter , current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit References: <20011006200417.B86A13808@overcee.netplex.com.au> <3BC000AE.405057F9@mindspring.com> <20011007093231.A91417@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Steve Kargl wrote: > > It was posted to -current (see above). > > man send-pr > > A search of the GNATS databases with "terry" and "lambert" > returns zero hits. The freebsd-current mailing list is not > the preferred method for submission of patches and change > requests. Yeah; I'd prefer it if "send-pr" ran under Windows, or of FreeBSD would support WinModems. I'd also prefer it that it not reject my source email address. Perhaps it doesn't reject Earthlink, like it did Primenet. NB: Other people have complained about this as well. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 14: 4:31 2001 Delivered-To: freebsd-current@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id A46E837B405 for ; Sun, 7 Oct 2001 14:04:27 -0700 (PDT) Received: from mindspring.com (dialup-209.247.136.187.Dial1.SanJose1.Level3.net [209.247.136.187]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id OAA22589; Sun, 7 Oct 2001 14:04:20 -0700 (PDT) Message-ID: <3BC0C36D.3BF61FC9@mindspring.com> Date: Sun, 07 Oct 2001 14:04:45 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Jonathan Lemon Cc: current@freebsd.org Subject: Re: KRIS: FOR YOU TO COMMIT: soft interrupt coelescing References: <200110071521.f97FLTh32994@prism.flugsvamp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jonathan Lemon wrote: > > In article you write: > >Clearly this would also be very applicable to non-Gigabit cards, > >but the only one we use is the FXP, and the FXP driver is very > >poorly structured for being able to do this type of thing (I > > Oh, bah. The fxp clearly has the equivalent of fxp_rxeof and > fxp_txeof routines, these are just inlined into the fxp_intr > routine instead of being separate functions. It was all of 10 > minutes work to break them out into separate functions. I did > this to allow polled transmit/receive for some work in progress > that will be committed soon. I look forward to seeing the commits. I was considering doing this for similar reasons, using poling based on opportunistic timer (per the research by Banga, of Rice University), and had discussed with Bill Paul the merits of exposing the tx_eof and rx_eof routines in the device API (Bill didn't like the idea, since it had overhead, and argued that some cards won't transfer data again until the interrupt was acknowledged). I didn't bother to do this work, as with a 1GHz processor, a 100Mbit driver really can't push the interrupt overhead high enough for me to worry about it while there is other lower hanging fruit to be harvested first. For the gigabit cards, the interrupt rate was high enough that it actually mattered. I was also not sure that the FXP card would continue to DMA new data into the ring, with an unacknowledged interrupt pending. I'm more concerned with the fact that ~8% of the profiled time is being spent in the ipfw code (with only 6 rules present), and ~60% of the time is being spent in the inpcbhash code (even if you jack the table size to some ridiculously large number)... clearly, the code needs a rewrite (a trie seems like the most correct data structure here). The use of anonymous ports (host picks port) for a single bound source IP address (as opposed to INADDR_ANY) breaks outgoing connections, limiting them to 65535, since they are all treated (incorrectly) as being in the same port collision domain -- that needs fixed, too, if I'm going to have half a million connections in and half a million connections out, at the same time. There are some problems with the routing code as well; in particular, returned packes from a default gateway set up as the explicit route for an IP work, but if there is a default route to the machine hosting the gateway, the packet gets all the way back (indeed, tcpdump on the target machine sees it), but the target machine's ping program doesn't see the packet (very strange; still under investigation). On a related note, it seems that ping will hang forever and not respond to ^T or ^C, if it hasn't gotten at least one packet back (something bogus in the singal handlers -- also under investigation). I was also considering rewriting the Tigon III firmware to move a SYN cookie implementation onto the card itself, but of course, you would need a card with a lot of RAM to do this. The bottom line is that there is a lot of work to be done, and the FXP stuff is way, way down the list -- if people want performance, they can buy the high end product (Tigon) instead of the low end (FXP). Regards, -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 15: 7:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id D2D3737B403 for ; Sun, 7 Oct 2001 15:07:41 -0700 (PDT) Received: from hades.hell.gr (patr530-b087.otenet.gr [195.167.121.215]) by mailsrv.otenet.gr (8.11.5/8.11.5) with ESMTP id f97M7av08246; Mon, 8 Oct 2001 01:07:37 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id f97M7Zd11306; Mon, 8 Oct 2001 01:07:35 +0300 (EEST) (envelope-from charon@labs.gr) Date: Mon, 8 Oct 2001 01:07:33 +0300 From: Giorgos Keramidas To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit Message-ID: <20011008010733.C73967@hades.hell.gr> References: <20011006200417.B86A13808@overcee.netplex.com.au> <3BC000AE.405057F9@mindspring.com> <20011007093231.A91417@troutmask.apl.washington.edu> <3BC0BEF1.1D2725CE@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BC0BEF1.1D2725CE@mindspring.com> User-Agent: Mutt/1.3.22.1i X-GPG-Fingerprint: C1EB 0653 DB8B A557 3829 00F9 D60F 941A 3186 03B6 X-URL: http://labs.gr/~charon/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > Steve Kargl wrote: > > > > man send-pr > > Yeah; I'd prefer it if "send-pr" ran under Windows, or of > FreeBSD would support WinModems. What fails to work for you in the Web Interface at http://www.FreeBSD.org/send-pr.html ? -giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 15:21:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id 874CB37B406 for ; Sun, 7 Oct 2001 15:21:08 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id f97MEZC04536; Sun, 7 Oct 2001 23:14:35 +0100 (BST) (envelope-from nik) Date: Sun, 7 Oct 2001 23:14:35 +0100 From: Nik Clayton To: Terry Lambert Cc: Steve Kargl , Peter Wemm , Kris Kennaway , Nate Williams , Lyndon Nerenberg , Bernd Walter , current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit Message-ID: <20011007231435.C966@clan.nothing-going-on.org> References: <20011006200417.B86A13808@overcee.netplex.com.au> <3BC000AE.405057F9@mindspring.com> <20011007093231.A91417@troutmask.apl.washington.edu> <3BC0BEF1.1D2725CE@mindspring.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="OBd5C1Lgu00Gd/Tn" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3BC0BEF1.1D2725CE@mindspring.com>; from tlambert2@mindspring.com on Sun, Oct 07, 2001 at 01:45:37PM -0700 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --OBd5C1Lgu00Gd/Tn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 07, 2001 at 01:45:37PM -0700, Terry Lambert wrote: > Steve Kargl wrote: > > > It was posted to -current (see above). > >=20 > > man send-pr > >=20 > > A search of the GNATS databases with "terry" and "lambert" > > returns zero hits. The freebsd-current mailing list is not > > the preferred method for submission of patches and change > > requests. >=20 > Yeah; I'd prefer it if "send-pr" ran under Windows,=20 It does. Point your web browser at http://www.FreeBSD.org/send-pr.html N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- --OBd5C1Lgu00Gd/Tn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjvA08sACgkQk6gHZCw343Ws9ACfU3i4SavCwI44FJ5+EnJE9+5m LjcAn0Qgo7+MLkSxFSO//kLA/bK1e6hG =ZrYr -----END PGP SIGNATURE----- --OBd5C1Lgu00Gd/Tn-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 15:35:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id E72CC37B408 for ; Sun, 7 Oct 2001 15:35:07 -0700 (PDT) Received: from hades.hell.gr (patr530-b087.otenet.gr [195.167.121.215]) by mailsrv.otenet.gr (8.11.5/8.11.5) with ESMTP id f97MZ3v27581; Mon, 8 Oct 2001 01:35:03 +0300 (EEST) Received: (from charon@localhost) by hades.hell.gr (8.11.6/8.11.6) id f97MZ2O18717; Mon, 8 Oct 2001 01:35:02 +0300 (EEST) (envelope-from charon@labs.gr) Date: Mon, 8 Oct 2001 01:35:01 +0300 From: Giorgos Keramidas To: Jason Cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit Message-ID: <20011008013500.A17148@hades.hell.gr> References: <20011006200417.B86A13808@overcee.netplex.com.au> <3BC0BEF1.1D2725CE@mindspring.com> <20011008010733.C73967@hades.hell.gr> <200110072223.f97MNOit024452@ns2.austin.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110072223.f97MNOit024452@ns2.austin.rr.com> User-Agent: Mutt/1.3.22.1i X-GPG-Fingerprint: C1EB 0653 DB8B A557 3829 00F9 D60F 941A 3186 03B6 X-URL: http://labs.gr/~charon/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jason wrote: > > The web interface doesn't allow for patches to be attached. > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27653 [ Synopsis: Updates to send-pr.html to support MIME ] Don't use attachments. MIME is evil. Copy/paste the patch in the report. There are people out there that do not have MIME-aware MUA's and you'll break the nice query-pr command that developers can use in freefall to read the entire text of a PR. freefall% query-pr -F 27653 | more If you use base64/quoted-printable or some other exotic encoding of the attached patch, the above command will be pretty useless. -giorgos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 15:42:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from rj.sgi.com (rj.SGI.COM [204.94.215.100]) by hub.freebsd.org (Postfix) with ESMTP id 3191E37B405; Sun, 7 Oct 2001 15:42:15 -0700 (PDT) Received: from yog-sothoth.sgi.com (eugate.neu.sgi.com [144.253.131.5]) by rj.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f97MgDL10492; Sun, 7 Oct 2001 15:42:13 -0700 Received: from sgiger.munich.sgi.com (sgiger.munich.sgi.com [144.253.192.2]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id XAA2564152; Sun, 7 Oct 2001 23:51:07 +0200 (CEST) mail_from (gwk@sgi.com) Received: from cuckoo.munich.sgi.com (cuckoo.munich.sgi.com [144.253.192.109]) by sgiger.munich.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id XAA07048; Sun, 7 Oct 2001 23:51:26 +0200 Received: from hunter.munich.sgi.com ([192.26.53.52]) by cuckoo.munich.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id XAA76615; Sun, 7 Oct 2001 23:51:08 +0200 (CEST) Received: from hunter.munich.sgi.com (localhost.munich.sgi.com [127.0.0.1]) by hunter.munich.sgi.com (8.11.6/8.11.6) with ESMTP id f97LoSe01213; Sun, 7 Oct 2001 23:50:39 +0200 (CEST) (envelope-from gwk@sgi.com) Date: Sun, 07 Oct 2001 23:50:28 +0200 Message-ID: From: "Georg-W. Koltermann" To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: VMWare2 permission problems on -current as of Sep 26 In-Reply-To: References: User-Agent: Wanderlust/2.4.1 (Stand By Me) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/20.7 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: SGI X-Attribution: gwk MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Robert, it doesn't seem to be securelevel-related. sysctl(8) says: hunter[5]$ sysctl kern.securelevel kern.securelevel: -1 I also hacked the securelevel_g[et] routines to immediately return 0 as you suggested, and it doesn't make a difference. Besides, securelevel_g[et] doesn't seem to be used much. I think I found only one reference when doing a find/grep in /usr/src/sys. And there are just a few hard-coded tests of securelevel > 0 as well. I ran the vmware command through ktrace(1) (had to do that as root since it won't trace a SUID program for a normal user), and it does get an error return from an access(2) on .Xauthority: 1207 vmware CALL access(0xbfbff759,0x4) 1207 vmware NAMI "/compat/linux/home/hunter/gwk/.Xauthority" 1207 vmware NAMI "/home/hunter/gwk/.Xauthority" 1207 vmware RET access -1 errno -13 Unknown error: -13 It seems I am going to debug the access() call next. -- Regards, Georg. At Tue, 2 Oct 2001 20:28:16 -0400 (EDT), Robert Watson wrote: > > > There have been a number of permission-related changes in the tree of > late, in particular relating to securelevel support. I haven't > experienced any local problems running the new code, but there is always > the potential for such a problem, especially in areas of the code I'm not > actively using. In particular, I haven't used vmware2 on my test boxes in > quite a while, since the KSE changes certainly at least. A first question > for you would be: are you using a securelevel other than -1? As a quick > hack, try the following: edit securelevel_ge() and securelevel_gt() in > kern_prot.c to always return 0. See if the problem goes away. It's > possible I botched a securelevel check in the device code, or > mis-transcribed a securelevel value. Depending on how into kernel > debugging you are, you could also try setting breakpoints in the > securelevel code and see what's getting spat out. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > On Tue, 2 Oct 2001, Georg-W. Koltermann wrote: > > > Hi, > > > > I have applied the KSE patches to vmware2 that were posted on > > http://www.ripe.net/home/mark/files/vmware2_kse.patch.tgz. I can now > > build vmware2, but run into a number of permission problems running > > it: > > > > 1. Xlib: connection to ":0.0" refused by server > > Xlib: Client is not authorized to connect to Server > > Error: Can't open display: :0 > > > > Can be worked around by "chmod 644 ~/.Xauthority". > > > > 2. Cannot open /dev/tty0: permission denied (in a GUI message box). > > > > Linux /dev/tty0 seems to refer to FreeBSD /dev/ttyv0, > > using a chain of two symlinks. "chown $USER /dev/ttyv0" doesn't > > seem to be effective, but "chmod 666 /dev/ttyv0" makes the message > > go away. > > > > 3. Active virtual terminal (/dev/tty9) is not valid. Permission > > denied. (in a GUI message box). > > > > Seems to be like the above, Linux tty9 is really FreeBSD ttyv8, > > and a chown is ineffective but a chmod 666 solves it. > > > > 4. Warning: Tried to connect to session manager, Authentication > > Rejected, reason : None of the authentication protocols specified > > are supported and host-based authentication failed > > > > on stderr. Don't know if this is a problem or just a warning. > > > > 5. Permission error creating lockfiles (vmware-lock.whoever) > > > > The directory is owned by me. > > > > In summary, it seems as though the vmware binary (which is SUID root) > > is unable to access any files that are only accessible to the invoking > > user (like .Xauthority), and also unable to access any files > > accessible by root (like the /dev nodes). > > > > Is there a kind of changed permission policy in the new linuxulator > > that could cause this? By any chance, would I need to recompile the > > linux_base port? > > > > Is anyone using VMWare2 successfully on a recent -current? > > > > -- > > Regards, > > Georg. > > > > 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 Oct 7 16:29:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 0F21137B407 for ; Sun, 7 Oct 2001 16:29:41 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.5) with SMTP id f97NSaB84789; Sun, 7 Oct 2001 19:28:36 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 7 Oct 2001 19:28:35 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Georg-W. Koltermann" Cc: current@FreeBSD.ORG Subject: Re: VMWare2 permission problems on -current as of Sep 26 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 7 Oct 2001, Georg-W. Koltermann wrote: > Hi Robert, > > it doesn't seem to be securelevel-related. sysctl(8) says: > > hunter[5]$ sysctl kern.securelevel > kern.securelevel: -1 > > I also hacked the securelevel_g[et] routines to immediately return 0 > as you suggested, and it doesn't make a difference. > > Besides, securelevel_g[et] doesn't seem to be used much. I think I > found only one reference when doing a find/grep in /usr/src/sys. And > there are just a few hard-coded tests of securelevel > 0 as well. Then you must be running a souce tree from before the commits that I was worried about--in my -CURRENT tree, I see about 22 references to securelevel_gt(), and 7 to securelevel_ge() (including prototype and implementation). On September 26, I committed a fairly sweeping set of changes to replace direct securelevel checks with calls to securelevel_g[et]() so as to support per-jail securelevels, and these commits were the ones I was concerned might be causing the problems you're experiencing. > I ran the vmware command through ktrace(1) (had to do that as root since > it won't trace a SUID program for a normal user), and it does get an > error return from an access(2) on .Xauthority: > > 1207 vmware CALL access(0xbfbff759,0x4) > 1207 vmware NAMI "/compat/linux/home/hunter/gwk/.Xauthority" > 1207 vmware NAMI "/home/hunter/gwk/.Xauthority" > 1207 vmware RET access -1 errno -13 Unknown error: -13 > > It seems I am going to debug the access() call next. I'm a little surprised that they're calling access(). Are you using the linux_kdump from the ports collection, btw? Otherwise the system calls aren't listed right, due to differences in system call number. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 18:13:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 6DC4C37B406 for ; Sun, 7 Oct 2001 18:13:53 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f981Dpu99816; Sun, 7 Oct 2001 19:13:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f981Dm755212; Sun, 7 Oct 2001 19:13:48 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110080113.f981Dm755212@harmony.village.org> To: tlambert2@mindspring.com Subject: Re: PATCHES for Kris Kennaway to commit Cc: Steve Kargl , Peter Wemm , Kris Kennaway , Nate Williams , Lyndon Nerenberg , Bernd Walter , current@FreeBSD.ORG In-reply-to: Your message of "Sun, 07 Oct 2001 13:45:37 PDT." <3BC0BEF1.1D2725CE@mindspring.com> References: <3BC0BEF1.1D2725CE@mindspring.com> <20011006200417.B86A13808@overcee.netplex.com.au> <3BC000AE.405057F9@mindspring.com> <20011007093231.A91417@troutmask.apl.washington.edu> Date: Sun, 07 Oct 2001 19:13:48 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3BC0BEF1.1D2725CE@mindspring.com> Terry Lambert writes: : NB: Other people have complained about this as well. That's why I always use the web interface to deal with bugs... That way the web server does the mailing, which seems to be much better at getting into the databse. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 18:14:56 2001 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D441137B405 for ; Sun, 7 Oct 2001 18:14:46 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f981Eju99826; Sun, 7 Oct 2001 19:14:45 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f981Eg755232; Sun, 7 Oct 2001 19:14:44 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110080114.f981Eg755232@harmony.village.org> To: Giorgos Keramidas Subject: Re: PATCHES for Kris Kennaway to commit Cc: Jason , Terry Lambert , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 08 Oct 2001 01:35:01 +0300." <20011008013500.A17148@hades.hell.gr> References: <20011008013500.A17148@hades.hell.gr> <20011006200417.B86A13808@overcee.netplex.com.au> <3BC0BEF1.1D2725CE@mindspring.com> <20011008010733.C73967@hades.hell.gr> <200110072223.f97MNOit024452@ns2.austin.rr.com> Date: Sun, 07 Oct 2001 19:14:42 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011008013500.A17148@hades.hell.gr> Giorgos Keramidas writes: : Don't use attachments. MIME is evil. Copy/paste the patch in the : report. There are people out there that do not have MIME-aware MUA's : and you'll break the nice query-pr command that developers can use in : freefall to read the entire text of a PR. : : freefall% query-pr -F 27653 | more : : If you use base64/quoted-printable or some other exotic encoding of : the attached patch, the above command will be pretty useless. Actually, MIME isn't evil, if used properly. Trouble is that gnats doesn't use it properly :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 19: 8:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (Postfix) with ESMTP id 81AEA37B406 for ; Sun, 7 Oct 2001 19:08:36 -0700 (PDT) Received: from dsto-ms2.dsto.defence.gov.au (dsto-ms2.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au (8.10.1/8.10.1) with ESMTP id f9827v818885 for ; Mon, 8 Oct 2001 11:37:57 +0930 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by dsto-ms2.dsto.defence.gov.au (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Mon, 8 Oct 2001 11:36:17 +0930 Received: from salex001.dsto.defence.gov.au (salex001.dsto.defence.gov.au [131.185.2.9]) by muttley.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id LAA26083; Mon, 8 Oct 2001 11:30:54 +0930 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by salex001.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 4AVVTCC5; Mon, 8 Oct 2001 11:30:51 +0930 Received: from dsto.defence.gov.au (fuzz.dsto.defence.gov.au [131.185.75.229]) by fang.dsto.defence.gov.au (8.9.3/8.9.3/8.9.3.LMD.990513) with ESMTP id LAA20285; Mon, 8 Oct 2001 11:30:48 +0930 (CST) Message-ID: <3BC108D4.2AA1D712@dsto.defence.gov.au> Date: Mon, 08 Oct 2001 11:30:52 +0930 From: "Thyer, Matthew" X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Georg-W. Koltermann" Cc: Andrew Gallatin , bandix@looksharp.net, current@freebsd.org Subject: Re: NIS client performance seems very poor under network load References: <20010928022500.I24843-100000@turtle.looksharp.net> <3BBAD3F3.241A1FEE@dsto.defence.gov.au> <15291.10120.604882.602699@grasshopper.cs.duke.edu> <3BBBE105.9863D667@dsto.defence.gov.au> <15292.24342.741023.939305@grasshopper.cs.duke.edu> <3BBD6015.9EB74634@dsto.defence.gov.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Georg-W. Koltermann" wrote: > > You know, I have been using and NSD, at work on IRIX. I had trouble > with it, it sometimes wouldn't sync with the nameserver, or would > cease to serve any names until I HUPed it. I dont have such problems. Patch or upgrade to 6.5.13. IRIX 6.5's nsd is the name service daemon. It does the lookups be they via DNS, NIS or whatever. > And, seriously, I don't really understand what it's good for. Bind > has been responsible for resolving host names as long as I know. WHY > would anyone want to use NIS for hostname resolution? I never said I use NIS for hostname resolution (and I dont) but I still need NIS to work for user and group lookups. You misunderstand the purpose of IRIX nsd and Solaris nscd, they are not solely for NIS. They are for caching results of all types of naming service lookups be it hosts, passwd, services and by all type of methods e.g. DNS, NIS, NIS+ whatever. If you look at your IRIX 6.5.X NIS client, you'll see that it doesn't run a process called ypbind. The functionality of ypbind has been incorporated into nsd. From the nis(7p) manual page: NOTE The daemon nsd(1M) uses this library to replace the ypbind daemon from previous IRIX releases. Similarly, nsd uses the nisserv(7P) library to replace the ypserv daemon from previous releases. > I always configure the resolver to use bind (aka named), and have NIS > resolve passwd, group, alias maps etc. if I need that functionality. > When I'm worried about network load, I run a local named in caching > only mode. None of that solves the user and group use of NIS problem. > Named makes a nice system-wide cache, it is maintained > well, so why bother and write another daemon for that? A system-wide cache for hostname resolution via DNS only. -- Matthew Thyer Phone: +61 8 8259 7249 Science Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Edinburgh PO Box 1500 Edinburgh South Australia 5111 IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 20:32: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id B261537B403 for ; Sun, 7 Oct 2001 20:31:57 -0700 (PDT) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f983VuM71411 for ; Sun, 7 Oct 2001 20:31:56 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 0DF2D38CC; Sun, 7 Oct 2001 20:31:56 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Warner Losh Cc: Giorgos Keramidas , Jason , Terry Lambert , current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit In-Reply-To: <200110080114.f981Eg755232@harmony.village.org> Date: Sun, 07 Oct 2001 20:31:56 -0700 From: Peter Wemm Message-Id: <20011008033156.0DF2D38CC@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <20011008013500.A17148@hades.hell.gr> Giorgos Keramidas writes: > : Don't use attachments. MIME is evil. Copy/paste the patch in the > : report. There are people out there that do not have MIME-aware MUA's > : and you'll break the nice query-pr command that developers can use in > : freefall to read the entire text of a PR. > : > : freefall% query-pr -F 27653 | more > : > : If you use base64/quoted-printable or some other exotic encoding of > : the attached patch, the above command will be pretty useless. > > Actually, MIME isn't evil, if used properly. Trouble is that gnats > doesn't use it properly :-( s/use it properly/use it at all/. It effectively destroys MIME. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 21: 3:48 2001 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 9F4D637B403 for ; Sun, 7 Oct 2001 21:03:45 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f9843fT29793; Mon, 8 Oct 2001 00:03:41 -0400 (EDT) (envelope-from wollman) Date: Mon, 8 Oct 2001 00:03:41 -0400 (EDT) From: Garrett Wollman Message-Id: <200110080403.f9843fT29793@khavrinen.lcs.mit.edu> To: Bruce Evans Cc: Subject: Re: panic: blockable sleep lock (sx) allproc @ /usr/local/src/sys/kern/kern_proc.c:212 In-Reply-To: <20011007142123.A6012-100000@delplex.bde.org> References: <3BBF6540.AF950344@DougBarton.net> <20011007142123.A6012-100000@delplex.bde.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: > Is using xconsole significantly better than "tail -f /var/log/messages"? I don't know. I think `xterm -C' is better than either one, if it can be made to work properly. (I have held off on updating to latest -current in the hope that this might be resolved one way or the other.) -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Oct 7 21:25:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id AB8CD37B405 for ; Sun, 7 Oct 2001 21:25:48 -0700 (PDT) Received: from mindspring.com (dialup-209.247.143.125.Dial1.SanJose1.Level3.net [209.247.143.125]) by scaup.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id VAA08549; Sun, 7 Oct 2001 21:25:38 -0700 (PDT) Message-ID: <3BC12AF4.3189CA@mindspring.com> Date: Sun, 07 Oct 2001 21:26:28 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Giorgos Keramidas Cc: current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit References: <20011006200417.B86A13808@overcee.netplex.com.au> <3BC000AE.405057F9@mindspring.com> <20011007093231.A91417@troutmask.apl.washington.edu> <3BC0BEF1.1D2725CE@mindspring.com> <20011008010733.C73967@hades.hell.gr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Giorgos Keramidas wrote: > > Terry Lambert wrote: > > Steve Kargl wrote: > > > > > > man send-pr > > > > Yeah; I'd prefer it if "send-pr" ran under Windows, or of > > FreeBSD would support WinModems. > > What fails to work for you in the Web Interface at > http://www.FreeBSD.org/send-pr.html ? Attaching patches. It does not support the HTTP drop target for upload, so a cut and paste will change tabs into spaces, so the patch won't apply cleanly. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 1: 6:14 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [216.145.48.34]) by hub.freebsd.org (Postfix) with ESMTP id 1F08F37B405 for ; Mon, 8 Oct 2001 01:06:10 -0700 (PDT) Received: from DougBarton.net (db-cvad-2-tmp.yahoo.com [216.145.48.243]) by mail-relay1.yahoo.com (Postfix) with ESMTP id 36EB58B5B9; Mon, 8 Oct 2001 01:06:09 -0700 (PDT) Message-ID: <3BC15E76.727448F@DougBarton.net> Date: Mon, 08 Oct 2001 01:06:14 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: tlambert2@mindspring.com Cc: Giorgos Keramidas , current@FreeBSD.ORG Subject: Re: PATCHES for Kris Kennaway to commit References: <20011006200417.B86A13808@overcee.netplex.com.au> <3BC000AE.405057F9@mindspring.com> <20011007093231.A91417@troutmask.apl.washington.edu> <3BC0BEF1.1D2725CE@mindspring.com> <20011008010733.C73967@hades.hell.gr> <3BC12AF4.3189CA@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Giorgos Keramidas wrote: > > > > Terry Lambert wrote: > > > Steve Kargl wrote: > > > > > > > > man send-pr > > > > > > Yeah; I'd prefer it if "send-pr" ran under Windows, or of > > > FreeBSD would support WinModems. > > > > What fails to work for you in the Web Interface at > > http://www.FreeBSD.org/send-pr.html ? > > Attaching patches. It does not support the HTTP drop > target for upload, so a cut and paste will change tabs > into spaces, so the patch won't apply cleanly. I find that the --ignore-whitespace option to patch usually handles this nicely. -- "We will not tire, we will not falter, and we will not fail." - George W. Bush, President of the United States September 20, 2001 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 1: 7:39 2001 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 3EB2B37B401 for ; Mon, 8 Oct 2001 01:07:35 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id SAA05133; Mon, 8 Oct 2001 18:07:15 +1000 Date: Mon, 8 Oct 2001 18:06:33 +1000 (EST) From: Bruce Evans X-X-Sender: To: Dmitry Karasik Cc: Subject: Re: /dev/cuaa broken ? In-Reply-To: Message-ID: <20011008163346.C14481-100000@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 3 Oct 2001, Dmitry Karasik wrote: > After upgrade to 3.5 to 4.3-stable we encoutered a problem > with our custom device connected to com-port. The device > accepts command strings and returns strings in response, > but under 4.3 it strangely does not respond to commands > that are longer than 15 bytes ( 16 with \r). > > The device is controlled by a code, which, if stripped to > functional minimum is as such: > > open F, "+< /dev/cuaa0" or die "Cannot:$!\n"; > system "/bin/stty -f /dev/cuaa0 gfmt1:ispeed=19200:ospeed=19200 cstopb"; > print F "123\r"; # <- works under both 3.5 and 4.3 > # print F "1234567890123456\r" # <- doesn't work under 4.3 > print "|$_|\n" while ; > close F; This works for me under -current, but it stops working if the while statement is removed and dtrwait is set to 0 (not the default) on /dev/cuaa0. Waiting for output to drain is broken. close() waits for output to drain and then waits another dtrwait/100 seconds before dropping carrier. Problems occur when carrier is dropped while there is still data in the output fifo. The data gets transmitted normally but tends to be discarded by the reciver when it arrives arfter carrier drop. > One more strange effect is, that under cu(1) it works. That makes cu(1) works better because it ignores carrier drop, so it doesn't notice when the sender drops carrier prematurely. > us assume that the programming technique used into our program > is inappropriate - but it seems pretty straightforward and > we are just clueless about what implicit 16-byte buffers > might be involved here. My suspicion is that it's the device driver bug, > but unfortunately we cannot afford tracking the exact commit that caused > the malfunction. The relevant magic number is actually 14 for the size of the input fifo on the receiver. The receiver tends to see input in 14-byte chunks. When it sees carrier drop and is not ignoring carrier drop, it discards any further input. I haven't found the bug yet. It was first fixed relatively recently in rev.1.152 (1996/11/30) of sio.c. Until then, you had to have waits in your program or dtrwait large enough to avoid loss of data on close. But dtrwait didn't help for the ioctls that need to wait for output to drain. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 2:16:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id A112E37B408 for ; Mon, 8 Oct 2001 02:16:22 -0700 (PDT) Received: (from root@localhost) by plab.ku.dk (8.11.3/8.9.3) id f989GHG35873 for freebsd-current@FreeBSD.ORG.AVP; Mon, 8 Oct 2001 11:16:17 +0200 (CEST) (envelope-from postmaster@plab.ku.dk) Received: from raven.plab.ku.dk (raven.plab.ku.dk [130.225.105.67]) by plab.ku.dk (8.11.3/8.9.3) with ESMTP id f989GGv35857; Mon, 8 Oct 2001 11:16:16 +0200 (CEST) (envelope-from postmaster@plab.ku.dk) In-Reply-To: Bruce Evans's message of "Mon, 8 Oct 2001 18:06:33 +1000 (EST)" Subject: Re: /dev/cuaa broken ? Content-Transfer-Encoding: 8bit References: <20011008163346.C14481-100000@delplex.bde.org> To: Bruce Evans From: Dmitry Karasik Cc: Keywords: 2001334874 X-Comment-To: Bruce Evans Content-Type: text/plain; charset="koi8-r" Lines: 39 Mime-Version: 1.0 Date: 08 Oct 2001 11:17:15 +0200 X-Mailer: Mail::Mailer[v1.18] Net::SMTP[v2.13] Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Bruce! On 08 Oct 01 at 18:06, "Bruce" (Bruce Evans) wrote: Thanks Bruce Further investigation revealed the following fact, which might be relevant. If a write of 1 byte is issued, everything is O.K - contrary to when more than 1 byte is written, there is a problem. It was noticed first with cu, when I typed a command from keyboard and copy-pasted it after and received different results. As for now, we have fixed our code in such a fashion that now it writes commands by 1 byte - but since the exact problem cause is unknown, be it dtr state or something else, it might be still a hack, that wouldn't work in different circumstances, on a faster machine for example. If that bug makes a particular interest to you, I can make an account for you on that box. Bruce> I haven't found the bug yet. It was first fixed relatively Bruce> recently in rev.1.152 (1996/11/30) of sio.c. Until then, you had Bruce> to have waits in your program or dtrwait large enough to avoid loss Bruce> of data on close. But dtrwait didn't help for the ioctls that need Bruce> to wait for output to drain. Bruce> Bruce -- Sincerely, Dmitry --- www.karasik.eu.org --- Life ain't fair, but the root password helps. - BOFH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 4:14:49 2001 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 F0B1037B406 for ; Mon, 8 Oct 2001 04:14:39 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA20901; Mon, 8 Oct 2001 21:14:31 +1000 Date: Mon, 8 Oct 2001 21:13:48 +1000 (EST) From: Bruce Evans X-X-Sender: To: Dmitry Karasik Cc: Subject: Re: /dev/cuaa broken ? In-Reply-To: Message-ID: <20011008194257.B16343-100000@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 8 Oct 2001, Dmitry Karasik wrote: > Further investigation revealed the following fact, which > might be relevant. If a write of 1 byte is issued, everything > is O.K - contrary to when more than 1 byte is written, there > is a problem. It was noticed first with cu, when I typed > a command from keyboard and copy-pasted it after and received > different results. I can't explain why 1 byte works much better, but the problem (as I understand it) is very timing dependent. Multiples of the receiver fifo trigger level best because the timing is favorable then. > As for now, we have fixed our code in such a fashion > that now it writes commands by 1 byte - but since the > exact problem cause is unknown, be it dtr state or > something else, it might be still a hack, that wouldn't work > in different circumstances, on a faster machine for example. I was confused about DTR. It's carrier drop that is the problem (assuming you are closing the device after each command). dtrwait doesn't affect carrier. Carrier is dropped immediately after the output is drained in close(). Then DTR is held high for dtrwait/100 seconds, and further opens are blocked until then. dtrwait normally doesn't matter much, but should be quite large for safety (the default is 3 seconds). However, if you want send a lot of commands and close the file after each, then you don't want it large. My current understanding of the bug is that it is caused by interrupt handling for the receiver working too well :-). If there were no delays except the ones for the receiver fifo (input is not normally seen unless the fifo is nearly full or 4 character times have elapsed since a byte was received), then the last few bytes for "write(); close();" would always be lost since they would be received concurrently with the carrier drop, and on carrier drop the device goes into "zombie" state in which all reads on it return EOF. In practice there are some delays, so they last few bytes are not always lost. Fixes: - senders should probably wait a bit before closing. - the zombie state probably shouldn't affect returning previously received input to userland. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 4:36:59 2001 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 04AF237B40B for ; Mon, 8 Oct 2001 04:36:57 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA22506; Mon, 8 Oct 2001 21:36:51 +1000 Date: Mon, 8 Oct 2001 21:36:08 +1000 (EST) From: Bruce Evans X-X-Sender: To: Garrett Wollman Cc: Subject: Re: panic: blockable sleep lock (sx) allproc @ /usr/local/src/sys/kern/kern_proc.c:212 In-Reply-To: <200110080403.f9843fT29793@khavrinen.lcs.mit.edu> Message-ID: <20011008213351.X17039-100000@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 8 Oct 2001, Garrett Wollman wrote: > < said: > > > Is using xconsole significantly better than "tail -f /var/log/messages"? > > I don't know. I think `xterm -C' is better than either one, if it can > be made to work properly. (I have held off on updating to latest > -current in the hope that this might be resolved one way or the > other.) I take this as a hint that we can't just remove TIOCCONS :-). (xterm -C uses it too.) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 5:24:28 2001 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 0B32A37B405 for ; Mon, 8 Oct 2001 05:24:25 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA26143; Mon, 8 Oct 2001 22:24:15 +1000 Date: Mon, 8 Oct 2001 22:23:32 +1000 (EST) From: Bruce Evans X-X-Sender: To: Ian Dowse Cc: Subject: Re: Missing stack frames in kgdb/ddb traces In-Reply-To: <200110072132.aa77889@salmon.maths.tcd.ie> Message-ID: <20011008214808.S17093-100000@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 7 Oct 2001, Ian Dowse wrote: > I noticed recently two problems with gdb/ddb traces that involve an > interrupt frame (both of these are in i386-specific code, but maybe > similar issues exist on other architectures): > > The first is that kgdb sometimes messes up a stack frame that > includes an interrupt, e.g in the trace below, the cpu_idle() frame > is corrupted. > > #7 0xc0325246 in siointr1 (com=0xc092a400) at machine/cpufunc.h:63 > #8 0xc0325137 in siointr (arg=0xc092a400) at ../../../isa/sio.c:1859 > #9 0x8 in ?? () > #10 0xc01ff391 in idle_proc (dummy=0x0) at ../../../kern/kern_idle.c:99 > #11 0xc01ff210 in fork_exit (callout=0xc01ff370 , arg=0x0, > frame=0xc40ffd48) at ../../../kern/kern_fork.c:785 > > This is because gdb was never updated when cpl was removed from the > interrupt frame (ddb was changed in i386/i386/db_trace.c rev 1.37). > The following patch seems to fix it: Seems reasonable. > Secondly, fast interrupts do not have an XresumeN style of symbol, > so neither gdb nor ddb treat their frames as interrupt frames. > This causes the frame listed as XfastintrN to gobble up the frame > that was executing at the time of the interrupt, which is especially > annoying when a serial console is being used to debug an infinite > loop in the kernel. BTW, I think parts of the keyboard interrupt handler need to be fast interrupts again so that the keyboard can be used to debug infinite loops in the kernel like it used to be able to. Now the debugger hotkey always takes you to an uninteresting place in the keyboard ithread even if it is not blocked. > The following patch adds an XresumefastN to fast interrupt handlers, > which allows gdb and ddb to correctly see the missing frame. The > name Xresumefast is chosen because it involves no ddb or gdb changes > (they just check for a name beginning with "Xresume"). I think debuggers should be taught about the main entry points Xintr* and Xfastintr* instead. The current Xresume* labels are not used except by debuggers. These labels are only used by debuggers because they hide the labels for the main entry points of the interrupt handlers. Note that Xsyscall is already handled like this. I think support for it was broken in gdb by the evil syscall_with_err_pushed changes. I still use the old non-bloated frame for fast interrupt handlers so I would need special support for this frame type. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 6: 8: 3 2001 Delivered-To: freebsd-current@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id 2A4E137B407 for ; Mon, 8 Oct 2001 06:07:44 -0700 (PDT) Received: from vega.vega.com (h28.228.dialup.iptcom.net [212.9.228.28]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id QAA28545; Mon, 8 Oct 2001 16:07:21 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.6/8.11.3) with ESMTP id f98D6RU13637; Mon, 8 Oct 2001 16:06:27 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3BC1A54A.6ABF09B1@FreeBSD.org> Date: Mon, 08 Oct 2001 16:08:26 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: tlambert2@mindspring.com Cc: kris@obsecurity.org, nate@yogotech.com, lyndon@atg.aciworldwide.com, ticso@mail.cicely.de, current@FreeBSD.org Subject: Re: uucp @ sourceforge References: <200110061123.OAA47907@ipcard.iptcom.net> <3BBF540E.BD325B70@mindspring.com> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > Maxim Sobolev wrote: > > I agree with Kris. These days it is not a big problem, especially for > > an opensource project, such as UUCP. Most obvious possibility is a > > Sourceforge - it provides all what is necessary (i.e. cvs repo, bug > > tracking database, mailing lists, www space, ftp space etc) at zero > > cost. And in my view it is even better option than /usr/src, because > > it is much easier to allow interested people to have r/w access to > > that private repo. > > Sourceforge is based on the premise that you can create an > Open Source project by declaring one, which is untrue. If > you want my opnions in detail, check the -chat and -advocacy > archives. I am not sure how this could defeat the fact that you can get a necessary ftp/www/cvs/etc space easily. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 6:23:27 2001 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 54DD337B403 for ; Mon, 8 Oct 2001 06:23:20 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Oct 2001 14:23:15 +0100 (BST) To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: Missing stack frames in kgdb/ddb traces In-Reply-To: Your message of "Mon, 08 Oct 2001 22:23:32 +1000." <20011008214808.S17093-100000@delplex.bde.org> Date: Mon, 08 Oct 2001 14:23:12 +0100 From: Ian Dowse Message-ID: <200110081423.aa55254@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011008214808.S17093-100000@delplex.bde.org>, Bruce Evans writes: > >BTW, I think parts of the keyboard interrupt handler need to be fast >interrupts again so that the keyboard can be used to debug infinite >loops in the kernel like it used to be able to. Now the debugger >hotkey always takes you to an uninteresting place in the keyboard >ithread even if it is not blocked. Yeah, this was an annoying side-effect of the ithread changes. I was delighted to discover that the serial console case still gives a useful trace. >I think debuggers should be taught about the main entry points Xintr* >and Xfastintr* instead. The current Xresume* labels are not used >except by debuggers. These labels are only used by debuggers because >they hide the labels for the main entry points of the interrupt handlers. >Note that Xsyscall is already handled like this. I think support for >it was broken in gdb by the evil syscall_with_err_pushed changes. Ah, I missed why the Xresume labels were there originally. Below is a patch that removes the Xresume labels, and makes gdb and ddb check for the Xintr/Xfastintr labels instead. Ian Index: sys/i386/i386/db_trace.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/i386/i386/db_trace.c,v retrieving revision 1.43 diff -u -r1.43 db_trace.c --- sys/i386/i386/db_trace.c 12 Sep 2001 08:37:29 -0000 1.43 +++ sys/i386/i386/db_trace.c 8 Oct 2001 12:34:32 -0000 @@ -223,7 +223,8 @@ if (name != NULL) { if (!strcmp(name, "calltrap")) { frame_type = TRAP; - } else if (!strncmp(name, "Xresume", 7)) { + } else if (!strncmp(name, "Xintr", 5) || + !strncmp(name, "Xfastintr", 9)) { frame_type = INTERRUPT; } else if (!strcmp(name, "syscall_with_err_pushed")) { frame_type = SYSCALL; Index: gnu/usr.bin/binutils/gdb/i386/kvm-fbsd.c =================================================================== RCS file: /dump/FreeBSD-CVS/src/gnu/usr.bin/binutils/gdb/i386/kvm-fbsd.c,v retrieving revision 1.27 diff -u -r1.27 kvm-fbsd.c --- gnu/usr.bin/binutils/gdb/i386/kvm-fbsd.c 19 Sep 2001 18:42:19 -0000 1.27 +++ gnu/usr.bin/binutils/gdb/i386/kvm-fbsd.c 8 Oct 2001 13:08:58 -0000 @@ -125,7 +125,8 @@ * Symbol names of kernel entry points. Use special frames. */ #define KSYM_TRAP "calltrap" -#define KSYM_INTERRUPT "Xresume" +#define KSYM_INTR "Xintr" +#define KSYM_FASTINTR "Xfastintr" #define KSYM_SYSCALL "Xsyscall" /* @@ -160,7 +161,9 @@ if (sym != NULL) { if (strcmp (SYMBOL_NAME(sym), KSYM_TRAP) == 0) frametype = tf_trap; - else if (strncmp (SYMBOL_NAME(sym), KSYM_INTERRUPT, 7) == 0) + else if (strncmp (SYMBOL_NAME(sym), KSYM_INTR, + strlen(KSYM_INTR)) == 0 || strncmp (SYMBOL_NAME(sym), + KSYM_FASTINTR, strlen(KSYM_FASTINTR)) == 0) frametype = tf_interrupt; else if (strcmp (SYMBOL_NAME(sym), KSYM_SYSCALL) == 0) frametype = tf_syscall; Index: sys/i386/isa/apic_vector.s =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/i386/isa/apic_vector.s,v retrieving revision 1.72 diff -u -r1.72 apic_vector.s --- sys/i386/isa/apic_vector.s 12 Sep 2001 08:37:33 -0000 1.72 +++ sys/i386/isa/apic_vector.s 8 Oct 2001 12:35:12 -0000 @@ -155,8 +155,6 @@ movl PCPU(CURTHREAD),%ebx ; \ incl TD_INTR_NESTING_LEVEL(%ebx) ; \ ; \ - /* entry point used by doreti_unpend for HWIs. */ \ -__CONCAT(Xresume,irq_num): ; \ FAKE_MCOUNT(13*4(%esp)) ; /* XXX avoid dbl cnt */ \ pushl $irq_num; /* pass the IRQ */ \ call sched_ithd ; \ Index: sys/i386/isa/icu_vector.s =================================================================== RCS file: /dump/FreeBSD-CVS/src/sys/i386/isa/icu_vector.s,v retrieving revision 1.29 diff -u -r1.29 icu_vector.s --- sys/i386/isa/icu_vector.s 12 Sep 2001 08:37:34 -0000 1.29 +++ sys/i386/isa/icu_vector.s 8 Oct 2001 12:35:22 -0000 @@ -106,7 +106,6 @@ enable_icus ; \ movl PCPU(CURTHREAD),%ebx ; \ incl TD_INTR_NESTING_LEVEL(%ebx) ; \ -__CONCAT(Xresume,irq_num): ; \ FAKE_MCOUNT(13*4(%esp)) ; /* XXX late to avoid double count */ \ pushl $irq_num; /* pass the IRQ */ \ call sched_ithd ; \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 9:46: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 78EC037B408 for ; Mon, 8 Oct 2001 09:45:51 -0700 (PDT) Received: (qmail 73694 invoked from network); 8 Oct 2001 16:45:50 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Oct 2001 16:45:50 -0000 Message-ID: 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: <3BC00E08.1F800907@mindspring.com> Date: Mon, 08 Oct 2001 09:45:22 -0700 (PDT) From: John Baldwin To: Terry Lambert Subject: Re: PATCHES for Kris Kennaway to commit Cc: current@FreeBSD.ORG, Kris Kennaway Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 07-Oct-01 Terry Lambert wrote: > As to the work itself, I have been avoiding it, since we have > a new person at ClickArray whose "trial by fire" is building > an updated "developer workstation release CDROM" based on the > FreeBSD 4.3-RELEASE plus our heavily modified kernel code, > and our distribution package for our current release product > (i.e. a CDROM that can be used to install engineering desktop > machines, and can also be used as a "golden master" for the > release engineering process). > > As soon as he has successfully been mentored through this > process (which involves many local patches, some of which I > posted to you, and which must be manually integrated, since > the FreeBSD "add patches during ``make release''" doesn't > work if you are patching the top level release Makefile), I > will be able to turn my attention to it without stepping on > his toes or his learning process. Actually, while that is painful, it's not that hard to work around. You need your big honkin' patch file that you list in LOCAL_PATCHES and then you need to patch src/release/Makefile manually before you kick off the release. The only extra step is patching src/release/Makefile manually, and there isn't a good way to workaround that, since you always have to bootstrap from something. I've used this approach many times myself in testing release Makefile changes. It's not that hard. :-P -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Mon Oct 8 9:46: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id 73CDD37B40A for ; Mon, 8 Oct 2001 09:45:52 -0700 (PDT) Received: (qmail 73714 invoked from network); 8 Oct 2001 16:45:51 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Oct 2001 16:45:51 -0000 Message-ID: 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: <200110081423.aa55254@salmon.maths.tcd.ie> Date: Mon, 08 Oct 2001 09:45:23 -0700 (PDT) From: John Baldwin To: Ian Dowse Subject: Re: Missing stack frames in kgdb/ddb traces Cc: current@FreeBSD.ORG, Bruce Evans Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 08-Oct-01 Ian Dowse wrote: > In message <20011008214808.S17093-100000@delplex.bde.org>, Bruce Evans > writes: >> >>BTW, I think parts of the keyboard interrupt handler need to be fast >>interrupts again so that the keyboard can be used to debug infinite >>loops in the kernel like it used to be able to. Now the debugger >>hotkey always takes you to an uninteresting place in the keyboard >>ithread even if it is not blocked. > > Yeah, this was an annoying side-effect of the ithread changes. I > was delighted to discover that the serial console case still gives > a useful trace. Note that you can trace an arbitrart process (but figuring out which process to trace might be a pain) by doing 'trace ' such as 'trace 23' to trace process 23. Your patches look good to me though. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/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 Mon Oct 8 10:55:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 3FBEB37B403 for ; Mon, 8 Oct 2001 10:55:40 -0700 (PDT) Received: from mindspring.com (dialup-209.245.132.185.Dial1.SanJose1.Level3.net [209.245.132.185]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id KAA25865; Mon, 8 Oct 2001 10:55:27 -0700 (PDT) Message-ID: <3BC1E8C0.2C409E3C@mindspring.com> Date: Mon, 08 Oct 2001 10:56:16 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: Dmitry Karasik , freebsd-current@FreeBSD.ORG Subject: Re: /dev/cuaa broken ? References: <20011008163346.C14481-100000@delplex.bde.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bruce Evans wrote: > I haven't found the bug yet. It was first fixed relatively recently > in rev.1.152 (1996/11/30) of sio.c. Until then, you had to have waits > in your program or dtrwait large enough to avoid loss of data on close. > But dtrwait didn't help for the ioctls that need to wait for output to > drain. Shouldn't he just disable the FIFO for this usage? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 11: 3:42 2001 Delivered-To: freebsd-current@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id A4AA237B401 for ; Mon, 8 Oct 2001 11:03:37 -0700 (PDT) Received: from mindspring.com (dialup-209.245.132.185.Dial1.SanJose1.Level3.net [209.245.132.185]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id LAA07206; Mon, 8 Oct 2001 11:03:30 -0700 (PDT) Message-ID: <3BC1EAA4.DE4F914F@mindspring.com> Date: Mon, 08 Oct 2001 11:04:20 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Evans Cc: Dmitry Karasik , freebsd-current@FreeBSD.ORG Subject: Re: /dev/cuaa broken ? References: <20011008194257.B16343-100000@delplex.bde.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bruce Evans wrote: > > On 8 Oct 2001, Dmitry Karasik wrote: > > > Further investigation revealed the following fact, which > > might be relevant. If a write of 1 byte is issued, everything > > is O.K - contrary to when more than 1 byte is written, there > > is a problem. It was noticed first with cu, when I typed > > a command from keyboard and copy-pasted it after and received > > different results. > > I can't explain why 1 byte works much better, but the problem (as I > understand it) is very timing dependent. Multiples of the receiver > fifo trigger level best because the timing is favorable then. He's using perl, which is slow. So by the time he gets around to writing another byte, the FIFO timeout has been fired, so he's writing a byte at a time. I think the UART tries to bunch up "bursty" data, on the theory that it might be triggering a line turnaround on a link that needs it, so it wants to gather the write. This means that it will treat one byte and n bytes (n>1) differentially. > I was confused about DTR. It's carrier drop that is the problem > (assuming you are closing the device after each command). dtrwait > doesn't affect carrier. Carrier is dropped immediately after the > output is drained in close(). Then DTR is held high for dtrwait/100 > seconds, and further opens are blocked until then. dtrwait normally > doesn't matter much, but should be quite large for safety (the default > is 3 seconds). However, if you want send a lot of commands and close > the file after each, then you don't want it large. He could simply nanosleep before the close... > My current understanding of the bug is that it is caused by interrupt > handling for the receiver working too well :-). If there were no > delays except the ones for the receiver fifo (input is not normally > seen unless the fifo is nearly full or 4 character times have elapsed > since a byte was received), then the last few bytes for "write(); > close();" would always be lost since they would be received concurrently > with the carrier drop, and on carrier drop the device goes into "zombie" > state in which all reads on it return EOF. In practice there are some > delays, so they last few bytes are not always lost. > > Fixes: > - senders should probably wait a bit before closing. Yep; I don't know if perl exposes nanosleep, so this may have to be a second. That's ugly. > - the zombie state probably shouldn't affect returning previously received > input to userland. I remember that the mouse line discipline used to disable the FIFO... is there any chance he could disable the FIFO? He dosn't need it to be fast, or he wouldn't be using perl, he'd be using a compiled language instead. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 11: 8:22 2001 Delivered-To: freebsd-current@freebsd.org Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id 7CE4337B407; Mon, 8 Oct 2001 11:08:20 -0700 (PDT) Received: from dialup-209.245.132.185.dial1.sanjose1.level3.net ([209.245.132.185] helo=mindspring.com) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.32 #2) id 15qep9-00049U-00; Mon, 08 Oct 2001 11:08:19 -0700 Message-ID: <3BC1EBC2.11538589@mindspring.com> Date: Mon, 08 Oct 2001 11:09:06 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Maxim Sobolev Cc: kris@obsecurity.org, nate@yogotech.com, lyndon@atg.aciworldwide.com, ticso@mail.cicely.de, current@FreeBSD.org Subject: Re: uucp @ sourceforge References: <200110061123.OAA47907@ipcard.iptcom.net> <3BBF540E.BD325B70@mindspring.com> <3BC1A54A.6ABF09B1@FreeBSD.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Maxim Sobolev wrote: > > Sourceforge is based on the premise that you can create an > > Open Source project by declaring one, which is untrue. If > > you want my opnions in detail, check the -chat and -advocacy > > archives. > > I am not sure how this could defeat the fact that you can get a necessary > ftp/www/cvs/etc space easily. It doesn't defeat that. It only defeats the project living on after I am run over by a bus, since the project will be unable to attract outside participation if it is hosted at SourceForge. You can't cookie-cutter Open Source projects, at least not the way they are trying to do it. As I said before, you need to read my objections in the -current and -advocacy lists. Realize that I have participated in the genesis of no less than 5 open source projects, 4 of which are still going. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Oct 8 11:41:55 2001 Delivered-To: freebsd-current@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 848E537B401 for ; Mon, 8 Oct 2001 11:41:44 -0700 (PDT) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f98IfiM73865 for ; Mon, 8 Oct 2001 11:41:44 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 3FCD6380F for ; Mon, 8 Oct 2001 11:41:44 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: current@freebsd.org Subject: For your amusement.. Date: Mon, 08 Oct 2001 11:41:44 -0700 From: Peter Wemm Message-Id: <20011008184144.3FCD6380F@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just a FYI to people not on the ia64 list... All bow before Doug Rabson, the mighty! :-) peter@overcee[11:23am]~src/sys/ia64/compile/SMALL-203# telnet -K ia64 Trying 10.0.0.21... Connected to ia64.wemm.org. Escape character is '^]'. FreeBSD/ia64 (ia64.wemm.org) (ttyp0) login: peter Password: Last login: Thu Oct 4 12:26:02 from overcee Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT (SMALL) #1: Mon Oct 8 10:33:33 PDT 2001 Welcome to FreeBSD! $ uname -a FreeBSD ia64.wemm.org 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Mon Oct 8 10:33:33 PDT 2001 peter@overcee.netplex.com.au:/home/src/sys/ia64/compile/SMALL ia64 $ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da1a 254063 124581 109157 53% / devfs 1 1 0 100% /dev procfs 8 8 0 100% /proc $ ps -axl UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 0 0 0 0 -16 0 0 5 sched DLs ?? 0:00.00 (swapper) 0 1 0 0 8 0 1312 23 wait ILs ?? 0:00.01 (init) 0 2 0 0 -16 0 0 5 psleep DL ?? 0:00.00 (pagedaemon) 0 3 0 0 20 0 0 5 psleep DL ?? 0:00.00 (vmdaemon) 0 4 0 0 20 0 0 5 pgzero DL ?? 0:00.00 (pagezero) 0 5 0 0 -16 0 0 5 psleep DL ?? 0:00.01 (bufdaemon) 0 6 0 0 20 0 0 5 syncer DL ?? 0:00.03 (syncer) 0 10 0 48 -16 0 0 5 - RL ?? 7:59.29 (idle) 0 11 0 0 -44 0 0 5 - WL ?? 0:00.02 (swi1: net) 0 12 0 0 -48 0 0 5 - WL ?? 0:01.11 (swi6: tty:sio clock) 0 13 0 0 -32 0 0 5 - WL ?? 0:00.00 (swi4: vm) 0 14 0 0 76 0 0 5 sleep DL ?? 0:00.04 (random) 0 15 0 0 -28 0 0 5 - WL ?? 0:00.00 (swi5: task queue) 0 16 0 0 -40 0 0 5 - WL ?? 0:00.00 (swi2: camnet) 0 17 0 0 -8 0 0 5 - WL ?? 0:00.03 (swi3: cambio) 0 18 0 0 -52 0 0 5 - WL ?? 0:00.00 (intr: acpi0) 0 19 0 0 -68 0 0 5 - WL ?? 0:00.01 (intr: fxp0) 0 20 0 0 -64 0 0 5 - WL ?? 0:00.00 (intr: ata0) 0 21 0 0 -64 0 0 5 - WL ?? 0:00.00 (intr: ata1) 0 22 0 0 -64 0 0 5 - WL ?? 0:00.00 (intr: uhci0) 0 23 0 0 8 0 0 5 usbevt DL ?? 0:00.00 (usb0) 0 24 0 0 -60 0 0 5 - WL ?? 0:00.00 (intr: atkbd0) 0 25 0 0 -48 0 0 5 - WL ?? 0:00.01 (swi0: tty:sio) 0 26 0 0 -60 0 0 5 - WL ?? 0:00.00 (intr: sio0) 0 27 0 0 -64 0 0 5 - WL ?? 0:00.04 (intr: isp0) 0 66 1 0 96 0 1408 123 select Is ?? 0:00.02 (inetd) 0 90 66 1 96 0 1528 159 select Ss ?? 0:00.05 (telnetd) 0 91 90 0 8 0 1552 167 wait Is p0 0:00.05 (login) 433 92 91 0 8 0 1944 172 wait S p0 0:00.03 (sh) 433 96 92 1 96 0 1320 113 - R+ p0 0:00.00 (ps) 0 7 1 0 5 0 1944 113 ttyin Is+ d0 0:00.07 (sh) $ ls -l total 18 -r--r--r-- 1 root wheel 4735 Oct 6 10:06 COPYRIGHT drwxr-xr-x 2 root wheel 1024 Oct 8 09:55 bin drwxr-xr-x 6 root wheel 512 Oct 7 22:04 boot drwxr-xr-x 3 root wheel 0 Oct 4 12:22 dev drwxr-xr-x 17 root wheel 2560 Oct 4 12:25 etc drwxr-xr-x 2 root wheel 512 Oct 5 19:22 mnt dr-xr-xr-x 1 root wheel 512 Oct 4 12:45 proc drwxr-xr-x 2 root wheel 512 Oct 6 10:06 root drwxr-xr-x 2 root wheel 2048 Oct 8 09:47 sbin lrwxr-xr-x 1 root wheel 12 Oct 8 18:00 sys -> /usr/src/sys drwxr-xr-t 2 root wheel 512 Oct 4 12:28 tmp drwxr-xr-x 13 root wheel 512 Oct 8 09:30 usr drwxr-xr-x 19 root wheel 512 Oct 5 19:22 var $ Yes, this is running on real hardware, not a simulator. There is still lots to do, but there is definate progress! The loader interface looks like this (I have deliberately disabled all automatic startup features, so it's a tad rough): EFI Boot Manager ver 1.02 [12.38] Please select a boot option shell Leenucks Boot option maintenance menu Use ^ and v to change option(s). Use Enter to select an option Loading.: shell EFI Shell version 1.02 [12.38] Device mapping table fs0 : VenHw(Unknown Device:80)/HD(Part1,Sig00000000) blk0 : Acpi(PNP0A03,0)/Pci(3|1)/Ata(Primary,Master) blk1 : VenHw(Unknown Device:80) blk2 : VenHw(Unknown Device:80)/HD(Part1,Sig00000000) blk3 : VenHw(Unknown Device:80)/HD(Part2,Sig00000000) blk4 : VenHw(Unknown Device:80)/HD(Part3,Sig00000000) blk5 : VenHw(Unknown Device:80)/HD(Part3,Sig00000000)/HD(Part1,Sig00000000) blk6 : VenHw(Unknown Device:81) blk7 : Acpi(PNP0A03,0)/Pci(3|1)/Ata(Secondary,Master) Shell> fs0: fs0:\> loader Console: EFI console FreeBSD/ia64 EFI boot, Revision 0.1 (peter@daintree.yahoo.com, Wed Oct 3 17:30:10 PDT 2001) Type '?' for a list of commands, 'help' for more detailed help. ok load /kernel.0810 /kernel.0810 data=0x580800+0x97be8 syms=[0x8+0x40a28+0x8+0x34dda] ok boot -sa Entering /kernel.0810 at 0xe00000000050a000... ACPI debug layer 0x0 debug level 0x0 Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Mon Oct 8 10:33:33 PDT 2001 peter@overcee.netplex.com.au:/home/src/sys/ia64/compile/SMALL CPU: Itanium (733.36-Mhz) Origin = "GenuineIntel" Model = 0 Revision = 4 Features = 0x0 real memory = 1056210944 (1031456K bytes) avail memory = 1023123456 (999144K bytes) Preloaded elf kernel "/kernel.0810" at 0xe000000000b90000. acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI" frequency 3579545 Hz acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_pcib0: port 0xcf8-0xcff on acpi0 pci0: on acpi_pcib0 pci0: at device 0.0 (no driver attached) pci0: at device 1.0 (no driver attached) fxp0: port 0x1140-0x117f mem 0xf7e00000-0xf7efffff,0xf7cc9000-0xf7cc9fff irq 39 at device 2.0 on pci0 fxp0: Ethernet address 00:d0:b7:af:cb:3b inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 3.0 on pci0 isa0: on isab0 atapci0: port 0x11b0-0x11bf at device 3.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x1180-0x119f irq 47 at device 3.2 on pci0 uhci0: (New UHCI DeviceId=0x76028086) usb0: on uhci0 usb0: USB revision 1.0 uhub0: (0x76028086) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub1: vendor 0x0424 product 0x2020, class 9/0, rev 1.10/0.00, addr 2 device_probe_and_attach: uhub1 attach returned 6 uhub1: vendor 0x0424 product 0x2020, class 9/0, rev 1.10/0.00, addr 2 device_probe_and_attach: uhub1 attach returned 6 pci0: at device 3.3 (no driver attached) pci0: at device 4.0 (no driver attached) pci0: at device 16.0 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console acpi_pcib1: on acpi0 pci1: on acpi_pcib1 pci1: at device 15.0 (no driver attached) acpi_pcib2: on acpi0 pci2: on acpi_pcib2 isp0: port 0x2000-0x20ff mem 0xeffdf000-0xeffdffff irq 27 at device 0.0 on pci2 pci2: at device 15.0 (no driver attached) acpi_pcib3: on acpi0 pci3: on acpi_pcib3 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xa08-0xa0b on acpi0 orm0: