From owner-freebsd-current Sun Sep 17 2:34:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id E9D5237B42C for ; Sun, 17 Sep 2000 02:34:01 -0700 (PDT) Received: from [194.97.50.138] (helo=mx0.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #20) id 13aapk-0003RP-00; Sun, 17 Sep 2000 11:34:00 +0200 Received: from a36a6.pppool.de ([213.6.54.166] helo=Magelan.Leidinger.net) by mx0.freenet.de with esmtp (Exim 3.16 #20) id 13aapj-0003pp-00; Sun, 17 Sep 2000 11:34:00 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8H9XQn01830; Sun, 17 Sep 2000 11:33:27 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009170933.e8H9XQn01830@Magelan.Leidinger.net> Date: Sun, 17 Sep 2000 11:33:25 +0200 (CEST) From: Alexander Leidinger Subject: Re: 100% system time? (SMPng on UP system) To: jhb@pike.osd.bsdi.com Cc: current@freebsd.org In-Reply-To: <200009161636.JAA19603@pike.osd.bsdi.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Sep, John Baldwin wrote: > None of the CPU states from vmmeter are close to accurate on UP x86 > systems at the moment because statclock() doesn't have a valid stack > frame to work with. SMP is slightly more accurate as we get all the > stats on the other CPU's correct. This is on the todo list to fix, > but it is merely cosmetic, so it is farther down on the list than, say, > finishing up threading interrupts on the alpha. :) It wasn't mentioned in the known bugs list, so I thought it wasn't known. BTW: Good work, keep going on. Bye, Alexander. -- Intel: where Quality is job number 0.9998782345! http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 2:34:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 1027337B43C; Sun, 17 Sep 2000 02:34:02 -0700 (PDT) Received: from [194.97.50.138] (helo=mx0.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #20) id 13aapl-0003Pj-00; Sun, 17 Sep 2000 11:34:01 +0200 Received: from a36a6.pppool.de ([213.6.54.166] helo=Magelan.Leidinger.net) by mx0.freenet.de with esmtp (Exim 3.16 #20) id 13aapk-0003pp-00; Sun, 17 Sep 2000 11:34:00 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8H9TZn01194; Sun, 17 Sep 2000 11:29:36 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009170929.e8H9TZn01194@Magelan.Leidinger.net> Date: Sun, 17 Sep 2000 11:29:34 +0200 (CEST) From: Alexander Leidinger Subject: Re: patch for openssh To: kris@FreeBSD.ORG Cc: current@FreeBSD.ORG In-Reply-To: <200009161607.e8GG7en02911@Magelan.Leidinger.net> MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="0-1804289383-969182979=:1190" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0-1804289383-969182979=:1190 Content-Type: TEXT/plain; charset=us-ascii On 16 Sep, To: kris@FreeBSD.ORG wrote: > But I think I found some other bugs, please have a look at the attached > diff. Oops, sorry, wrong diff. Bye, Alexander. -- To boldly go where I surely don't belong. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E --0-1804289383-969182979=:1190 Content-Type: TEXT/plain; CHARSET=US-ASCII Content-Disposition: attachment; filename="openssh.diff" Index: authfd.c =================================================================== RCS file: /big/FreeBSD-CVS/src/crypto/openssh/authfd.c,v retrieving revision 1.6 diff -u -r1.6 authfd.c --- authfd.c 2000/09/10 09:35:37 1.6 +++ authfd.c 2000/09/16 15:27:25 @@ -178,7 +178,7 @@ if (sock < 0) return NULL; - auth = xmalloc(sizeof(*auth)); + auth = xmalloc(sizeof(AuthenticationConnection)); auth->fd = sock; buffer_init(&auth->identities); auth->howmany = 0; Index: ssh-agent.c =================================================================== RCS file: /big/FreeBSD-CVS/src/crypto/openssh/ssh-agent.c,v retrieving revision 1.7 diff -u -r1.7 ssh-agent.c --- ssh-agent.c 2000/09/10 09:35:38 1.7 +++ ssh-agent.c 2000/09/17 09:24:21 @@ -577,6 +577,8 @@ perror("accept from AUTH_SOCKET"); break; } + slen -= sizeof(sunaddr.sun_len) + sizeof(sunaddr.sun_family); + sunaddr.sun_path[slen] = 0; new_socket(AUTH_CONNECTION, sock); } break; @@ -741,7 +743,8 @@ memset(&sunaddr, 0, sizeof(sunaddr)); sunaddr.sun_family = AF_UNIX; strlcpy(sunaddr.sun_path, socket_name, sizeof(sunaddr.sun_path)); - if (bind(sock, (struct sockaddr *) & sunaddr, sizeof(sunaddr)) < 0) { + sunaddr.sun_len = SUN_LEN(&sunaddr)+1; + if (bind(sock, (struct sockaddr *) & sunaddr, sunaddr.sun_len) < 0) { perror("bind"); cleanup_exit(1); } --0-1804289383-969182979=:1190-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 2:56:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 4FA4037B423 for ; Sun, 17 Sep 2000 02:56:20 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8H9uB608172; Sun, 17 Sep 2000 02:56:11 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: mike ryan Cc: freebsd-current@FreeBSD.ORG Subject: Re: fxp suspend/resume hangs In-Reply-To: Message from mike ryan of "Sun, 17 Sep 2000 00:27:33 EDT." <20000917002733.A37043@medianstrip.net> Date: Sun, 17 Sep 2000 02:56:11 -0700 Message-ID: <8168.969184571@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > in summary: PR kern/18756 contains a patch (against -stable, alas, This PR has been explicitly assigned to David Greenman and should be handled by him. As I pointed out in another message, nobody but he is likely to touch the fxp driver under any circumstances so it basically comes down to either him or nobody. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 5:33:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 8EF2337B422; Sun, 17 Sep 2000 05:33:31 -0700 (PDT) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #20) id 13addP-0006Eo-00; Sun, 17 Sep 2000 14:33:27 +0200 Received: from a2cd9.pppool.de ([213.6.44.217] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.16 #21) id 13addO-0006JB-00; Sun, 17 Sep 2000 14:33:27 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8H9van02062; Sun, 17 Sep 2000 11:57:37 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009170957.e8H9van02062@Magelan.Leidinger.net> Date: Sun, 17 Sep 2000 11:57:35 +0200 (CEST) From: Alexander Leidinger Subject: Re: 100% system time? (SMPng on UP system) To: bde@zeta.org.au Cc: current@FreeBSD.ORG, jhb@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Sep, Bruce Evans wrote: >> dnetc runns with idprio 31, system cvsupped around Sep 16, 11 CEST from >> a german mirror (it contains the idle fixes: src/sys/kern/kern_idle.c,v >> 1.4), complete build{world,kernel}. >> >> ---snip--- >> last pid: 1666; load averages: 1.10, 1.11, 1.03 up 0+00:51:21 16:54:14 > > Perhaps it really is a system process :-[. idprio on a pure cpu hog prevents > other user processes from running like a system process might do: > > idprio 31 sh -c "while :; do :; done" > > System processes actually hang the entire system until they complete: Are you mixing idprio with rtprio or did I not understand what you explain? Bye, Alexander. -- There's no place like ~ http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 5:35:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 5811D37B424 for ; Sun, 17 Sep 2000 05:35:21 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id FAA26513; Sun, 17 Sep 2000 05:31:45 -0700 (PDT) Message-Id: <200009171231.FAA26513@implode.root.com> To: mike ryan Cc: freebsd-current@FreeBSD.ORG Subject: Re: fxp suspend/resume hangs In-reply-to: Your message of "Sun, 17 Sep 2000 00:27:33 EDT." <20000917002733.A37043@medianstrip.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 17 Sep 2000 05:31:45 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >appended below is an excerpt from a message sent to -stable earlier >tonight, containing content of a type which kris kenneway correctly >suggested would find a more suitable audience on -current. > >in summary: PR kern/18756 contains a patch (against -stable, alas, >sorry) which fixes kernel hangs in the fxp driver on some laptops >after a resume from suspend. while quite a few people appear to be >using this patch successfully, it hasn't been committed -- david >greenman had an entirely reasonable objection to one aspect of the >patch's behavior. > >unfortunately, my knowledge of the kernel isn't sufficient to >adequately address david's concerns, and though i've mailed him to >ask for guidance twice over the past 4 months, i haven't received a >response. that's probably my fault, i probably should have been >mailing -current to being with. I can only find the 5/22 email regarding this, so I seem to have missed your second message. With over a thousand emails a day coming into my inbox, this shouldn't be too surprising. My response to the 5/22 message was this: ... This could be a problem. If an interrupt occurs, it must be acknowledged otherwise you'll be stuck in an infinit loop - PCI interrupts are level sensitive and must be cleared in the ISR. ... In short, while it may fix a hang in your laptop case, it opens the driver up to a hang if an unexpected interrupt occurs while IFF_RUNNING is clear. I think this is dangerous enough that I don't think the code should not be compiled as part of the standard driver. One just cannot ignore level- sensitive PCI interrupts. >if anybody can offer any suggestions as to how to move forward with >getting this patch to the point where it can be committed, i'd >certainly appreciate it. alternately, any feedback on whether the >patch is necessary and/or functional on your machine, laptop or no, >would be interesting. >> i wouldn't be at all surprised if there were a better approach than >> simply ignoring interrupts when the device isn't running, but it's >> not clear to me what that would be. if anybody has any suggestions >> as to how to clean this up, i'm all ears. alternately, if any >> committers want to take this on, that'd be swell too. Someone needs to find out what the laptop is doing to the STATACK register that causes a hang when it is accessed. Failing any better resolution, I guess that the objected-to change could be committed with an ifdef. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 6:19:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 9B7E237B422 for ; Sun, 17 Sep 2000 06:19:16 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id GAA26649; Sun, 17 Sep 2000 06:15:45 -0700 (PDT) Message-Id: <200009171315.GAA26649@implode.root.com> To: mike ryan Cc: freebsd-current@FreeBSD.ORG Subject: Re: fxp suspend/resume hangs In-reply-to: Your message of "Sun, 17 Sep 2000 00:27:33 EDT." <20000917002733.A37043@medianstrip.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 17 Sep 2000 06:15:45 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've made a few changes to the patches which should address my primary concerns. Instead of using IFF_RUNNING, I added a new softc variable to track the suspended condition. Only the APM stuff should call suspend/resume, so the interrupt logic should be uneffected in non-APM machines. Please try these patches out and let me know if they work as expected. They should apply and work with both -stable and -current. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. Index: if_fxp.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v retrieving revision 1.77.2.3 diff -c -r1.77.2.3 if_fxp.c *** if_fxp.c 2000/06/19 00:54:30 1.77.2.3 --- if_fxp.c 2000/09/17 13:15:33 *************** *** 125,135 **** --- 125,139 ---- fxp_lwcopy(src, dst) volatile u_int32_t *src, *dst; { + #ifdef __i386__ + *dst = *src; + #else volatile u_int16_t *a = (volatile u_int16_t *)src; volatile u_int16_t *b = (volatile u_int16_t *)dst; b[0] = a[0]; b[1] = a[1]; + #endif } /* *************** *** 215,220 **** --- 219,225 ---- static void fxp_mediastatus __P((struct ifnet *, struct ifmediareq *)); static void fxp_set_media __P((struct fxp_softc *, int)); static __inline void fxp_scb_wait __P((struct fxp_softc *)); + static __inline void fxp_dma_wait __P((volatile u_int16_t *, struct fxp_softc *sc)); static FXP_INTR_TYPE fxp_intr __P((void *)); static void fxp_start __P((struct ifnet *)); static int fxp_ioctl __P((struct ifnet *, *************** *** 283,290 **** struct fxp_softc *sc; { int i = 10000; ! while (CSR_READ_1(sc, FXP_CSR_SCB_COMMAND) && --i); } /************************************************************* --- 288,311 ---- struct fxp_softc *sc; { int i = 10000; + + while (CSR_READ_1(sc, FXP_CSR_SCB_COMMAND) && --i) + DELAY(2); + if (i == 0) + printf(FXP_FORMAT ": SCB timeout\n", FXP_ARGS(sc)); + } + + static __inline void + fxp_dma_wait(status, sc) + volatile u_int16_t *status; + struct fxp_softc *sc; + { + int i = 10000; ! while (!(*status & FXP_CB_STATUS_C) && --i) ! DELAY(2); ! if (i == 0) ! printf(FXP_FORMAT ": DMA timeout\n", FXP_ARGS(sc)); } /************************************************************* *************** *** 679,690 **** --- 700,784 ---- return 0; } + /* + * Device suspend routine. Stop the interface and save some PCI + * settings in case the BIOS doesn't restore them properly on + * resume. + */ + static int + fxp_suspend(device_t dev) + { + struct fxp_softc *sc = device_get_softc(dev); + int i, s; + + s = splimp(); + + fxp_stop(sc); + + for (i=0; i<5; i++) + sc->saved_maps[i] = pci_read_config(dev, PCIR_MAPS + i*4, 4); + sc->saved_biosaddr = pci_read_config(dev, PCIR_BIOS, 4); + sc->saved_intline = pci_read_config(dev, PCIR_INTLINE, 1); + sc->saved_cachelnsz = pci_read_config(dev, PCIR_CACHELNSZ, 1); + sc->saved_lattimer = pci_read_config(dev, PCIR_LATTIMER, 1); + + sc->suspended = 1; + + splx(s); + + return 0; + } + + /* + * Device resume routine. Restore some PCI settings in case the BIOS + * doesn't, re-enable busmastering, and restart the interface if + * appropriate. + */ + static int + fxp_resume(device_t dev) + { + struct fxp_softc *sc = device_get_softc(dev); + struct ifnet *ifp = &sc->sc_if; + u_int16_t pci_command; + int i, s; + + s = splimp(); + + /* better way to do this? */ + for (i=0; i<5; i++) + pci_write_config(dev, PCIR_MAPS + i*4, sc->saved_maps[i], 4); + pci_write_config(dev, PCIR_BIOS, sc->saved_biosaddr, 4); + pci_write_config(dev, PCIR_INTLINE, sc->saved_intline, 1); + pci_write_config(dev, PCIR_CACHELNSZ, sc->saved_cachelnsz, 1); + pci_write_config(dev, PCIR_LATTIMER, sc->saved_lattimer, 1); + + /* reenable busmastering */ + pci_command = pci_read_config(dev, PCIR_COMMAND, 2); + pci_command |= (PCIM_CMD_MEMEN|PCIM_CMD_BUSMASTEREN); + pci_write_config(dev, PCIR_COMMAND, pci_command, 2); + + CSR_WRITE_4(sc, FXP_CSR_PORT, FXP_PORT_SELECTIVE_RESET); + DELAY(10); + + /* reinitialize interface if necessary */ + if (ifp->if_flags & IFF_UP) + fxp_init(sc); + + sc->suspended = 0; + + splx(s); + + return 0; + } + static device_method_t fxp_methods[] = { /* Device interface */ DEVMETHOD(device_probe, fxp_probe), DEVMETHOD(device_attach, fxp_attach), DEVMETHOD(device_detach, fxp_detach), DEVMETHOD(device_shutdown, fxp_shutdown), + DEVMETHOD(device_suspend, fxp_suspend), + DEVMETHOD(device_resume, fxp_resume), { 0, 0 } }; *************** *** 1095,1101 **** int claimed = 0; #endif ! while ((statack = CSR_READ_1(sc, FXP_CSR_SCB_STATACK)) != 0) { #if defined(__NetBSD__) claimed = 1; #endif --- 1189,1195 ---- int claimed = 0; #endif ! while (!sc->suspended && (statack = CSR_READ_1(sc, FXP_CSR_SCB_STATACK)) != 0) { #if defined(__NetBSD__) claimed = 1; #endif *************** *** 1158,1164 **** */ if (fxp_add_rfabuf(sc, m) == 0) { struct ether_header *eh; ! u_int16_t total_len; total_len = rfa->actual_size & (MCLBYTES - 1); --- 1252,1258 ---- */ if (fxp_add_rfabuf(sc, m) == 0) { struct ether_header *eh; ! int total_len; total_len = rfa->actual_size & (MCLBYTES - 1); *************** *** 1317,1322 **** --- 1411,1419 ---- struct fxp_cb_tx *txp; int i; + ifp->if_flags &= ~(IFF_RUNNING | IFF_OACTIVE); + ifp->if_timer = 0; + /* * Cancel stats updater. */ *************** *** 1359,1367 **** panic("fxp_stop: no buffers!"); } } - - ifp->if_flags &= ~(IFF_RUNNING | IFF_OACTIVE); - ifp->if_timer = 0; } /* --- 1456,1461 ---- *************** *** 1474,1480 **** CSR_WRITE_4(sc, FXP_CSR_SCB_GENERAL, vtophys(&cbp->cb_status)); CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); /* ...and wait for it to complete. */ ! while (!(cbp->cb_status & FXP_CB_STATUS_C)); /* * Now initialize the station address. Temporarily use the TxCB --- 1568,1574 ---- CSR_WRITE_4(sc, FXP_CSR_SCB_GENERAL, vtophys(&cbp->cb_status)); CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); /* ...and wait for it to complete. */ ! fxp_dma_wait(&cbp->cb_status, sc); /* * Now initialize the station address. Temporarily use the TxCB *************** *** 1497,1503 **** fxp_scb_wait(sc); CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); /* ...and wait for it to complete. */ ! while (!(cb_ias->cb_status & FXP_CB_STATUS_C)); /* * Initialize transmit control block (TxCB) list. --- 1591,1597 ---- fxp_scb_wait(sc); CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); /* ...and wait for it to complete. */ ! fxp_dma_wait(&cb_ias->cb_status, sc); /* * Initialize transmit control block (TxCB) list. *************** *** 1936,1941 **** --- 2030,2036 ---- struct ifnet *ifp = &sc->sc_if; struct ifmultiaddr *ifma; int nmcasts; + int count; /* * If there are queued commands, we must wait until they are all *************** *** 2017,2024 **** * Wait until command unit is not active. This should never * be the case when nothing is queued, but make sure anyway. */ while ((CSR_READ_1(sc, FXP_CSR_SCB_RUSCUS) >> 6) == ! FXP_SCB_CUS_ACTIVE) ; /* * Start the multicast setup command. --- 2112,2125 ---- * Wait until command unit is not active. This should never * be the case when nothing is queued, but make sure anyway. */ + count = 100; while ((CSR_READ_1(sc, FXP_CSR_SCB_RUSCUS) >> 6) == ! FXP_SCB_CUS_ACTIVE && --count) ! DELAY(10); ! if (count == 0) { ! printf(FXP_FORMAT ": command queue timeout\n", FXP_ARGS(sc)); ! return; ! } /* * Start the multicast setup command. Index: if_fxpvar.h =================================================================== RCS file: /home/ncvs/src/sys/pci/if_fxpvar.h,v retrieving revision 1.9.2.1 diff -c -r1.9.2.1 if_fxpvar.h *** if_fxpvar.h 2000/03/29 02:02:39 1.9.2.1 --- if_fxpvar.h 2000/09/17 13:15:33 *************** *** 68,73 **** --- 68,79 ---- int phy_primary_device; /* device type of primary PHY */ int phy_10Mbps_only; /* PHY is 10Mbps-only device */ int eeprom_size; /* size of serial EEPROM */ + int suspended; /* 0 = normal 1 = suspended (APM) */ + u_int32_t saved_maps[5]; /* pci data */ + u_int32_t saved_biosaddr; + u_int8_t saved_intline; + u_int8_t saved_cachelnsz; + u_int8_t saved_lattimer; }; /* Macros to ease CSR access. */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 6:30:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id 8423137B422; Sun, 17 Sep 2000 06:30:15 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id PAA01098; Sun, 17 Sep 2000 15:29:54 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.0/8.8.8) with ESMTP id e8HETkm00847; Sun, 17 Sep 2000 16:29:46 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sun, 17 Sep 2000 16:29:41 +0200 (CEST) From: Michael Reifenberger To: Greg Lehey Cc: FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io In-Reply-To: <20000917102824.C42114@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, ... > The frames above are what the system went to as the result of your > debugger request. I'd also be interested to see the output of the > 'icnt' macro (if this is UP machine) or 'icnt1' (if it's SMP), and > 'ps' (the macro I promised above). (kgdb) icnt 1215544* 566* 0 0* 0 0 1 0 1555964* 0* 0* 0* 0 0* 22636* 11 1 0 0 0 0 0 441031 imen: 6f0b (kgdb) ps pid proc addr uid pri ppid pgrp flag stat comm wchan 37 c7874a00 c9665000 0 32 6 36 004086 3 tar piperd c9663f20 36 c7874bc0 c960a000 0 32 6 36 004006 3 tar FFS node c02f4220 35 c7874d80 c9607000 0 32 6 35 004006 3 tar inode c1d2fa00 6 c7874f40 c9604000 0 32 1 6 004086 3 sh wait c7874f40 5 c7875100 c8295000 0 4 0 0 000204 3 syncer syncer c03236e8 4 c78752c0 c8293000 0 4 0 0 100204 3 bufdaemon psleep c03072f0 3 c7875480 c8291000 0 4 0 0 000204 3 vmdaemon psleep c0317a00 2 c7875640 c828f000 0 4 0 0 100204 3 pagedaemon psleep c02f5938 21 c7875800 c78d4000 0 1* 0 0 000204 2 irq8: rtc 20 c78759c0 c78d2000 0 1* 0 0 000204 2 irq0: clk 19 c7875b80 c78b0000 0 7* 0 0 000204 6 irq5: pcm0 18 c7875d40 c788e000 0 7* 0 0 000204 6 irq7: ppc0 17 c7875f00 c788c000 0 7* 0 0 000204 6 irq12: psm0 16 c78760c0 c788a000 0 7* 0 0 000204 2 irq1: atkbd0 15 c7876280 c7887000 0 6* 0 0 000204 6 irq6: fdc0 14 c7876440 c7885000 0 6* 0 0 000204 6 irq15: ata1 13 c7876600 c7883000 0 6* 0 0 000204 2 irq14: ata0 12 c78767c0 c7881000 0 4 0 0 000204 3 random rndslp c0322934 11 c7876980 c787f000 0 15* 0 0 008204 6 softinterrupt 10 c7876b40 c787d000 0 4 0 0 008204 2 idle 1 c7876d00 c787b000 0 4 0 1 004284 3 init wait c7876d00 0 c0322960 c03c0000 0 4 0 0 000204 3 swapper sched c0322960 ... > handler. At this point, it would be very interesting to see the value > of p->p_comm, which is the process name at the end of the ps listing. > > > (kgdb) proc 35 > > Why are you interested in this process? It was one of the tar's which I grabbed by hand (without your ps macro) ... Whats next to show :-) Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 6:44:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from medianstrip.net (medianstrip.net [206.113.38.30]) by hub.freebsd.org (Postfix) with ESMTP id DD82837B423 for ; Sun, 17 Sep 2000 06:44:15 -0700 (PDT) Received: by medianstrip.net (Postfix, from userid 1000) id 0608158E5; Sun, 17 Sep 2000 09:44:10 -0400 (EDT) Date: Sun, 17 Sep 2000 09:44:10 -0400 From: mike ryan To: David Greenman Cc: freebsd-current@FreeBSD.ORG Subject: Re: fxp suspend/resume hangs Message-ID: <20000917094410.A57878@medianstrip.net> Mail-Followup-To: David Greenman , freebsd-current@FreeBSD.ORG References: <20000917002733.A37043@medianstrip.net> <200009171315.GAA26649@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200009171315.GAA26649@implode.root.com>; from dg@root.com on Sun, Sep 17, 2000 at 06:15:45AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 17, 2000 at 06:15:45AM -0700, David Greenman wrote: > I've made a few changes to the patches which should address my primary > concerns. Instead of using IFF_RUNNING, I added a new softc variable to > track the suspended condition. Only the APM stuff should call suspend/resume, > so the interrupt logic should be uneffected in non-APM machines. Please try > these patches out and let me know if they work as expected. They should apply > and work with both -stable and -current. yup, suspend/resume still works fine with this new patch. thanks, and sorry i've been such a pest about this... > -DG > > David Greenman > Co-founder, The FreeBSD Project - http://www.freebsd.org > President, TeraSolutions, Inc. - http://www.terasolutions.com > Pave the road of life with opportunities. > > Index: if_fxp.c > =================================================================== > RCS file: /home/ncvs/src/sys/pci/if_fxp.c,v > retrieving revision 1.77.2.3 > diff -c -r1.77.2.3 if_fxp.c > *** if_fxp.c 2000/06/19 00:54:30 1.77.2.3 > --- if_fxp.c 2000/09/17 13:15:33 > *************** > *** 125,135 **** > --- 125,139 ---- > fxp_lwcopy(src, dst) > volatile u_int32_t *src, *dst; > { > + #ifdef __i386__ > + *dst = *src; > + #else > volatile u_int16_t *a = (volatile u_int16_t *)src; > volatile u_int16_t *b = (volatile u_int16_t *)dst; > > b[0] = a[0]; > b[1] = a[1]; > + #endif > } > > /* > *************** > *** 215,220 **** > --- 219,225 ---- > static void fxp_mediastatus __P((struct ifnet *, struct ifmediareq *)); > static void fxp_set_media __P((struct fxp_softc *, int)); > static __inline void fxp_scb_wait __P((struct fxp_softc *)); > + static __inline void fxp_dma_wait __P((volatile u_int16_t *, struct fxp_softc *sc)); > static FXP_INTR_TYPE fxp_intr __P((void *)); > static void fxp_start __P((struct ifnet *)); > static int fxp_ioctl __P((struct ifnet *, > *************** > *** 283,290 **** > struct fxp_softc *sc; > { > int i = 10000; > > ! while (CSR_READ_1(sc, FXP_CSR_SCB_COMMAND) && --i); > } > > /************************************************************* > --- 288,311 ---- > struct fxp_softc *sc; > { > int i = 10000; > + > + while (CSR_READ_1(sc, FXP_CSR_SCB_COMMAND) && --i) > + DELAY(2); > + if (i == 0) > + printf(FXP_FORMAT ": SCB timeout\n", FXP_ARGS(sc)); > + } > + > + static __inline void > + fxp_dma_wait(status, sc) > + volatile u_int16_t *status; > + struct fxp_softc *sc; > + { > + int i = 10000; > > ! while (!(*status & FXP_CB_STATUS_C) && --i) > ! DELAY(2); > ! if (i == 0) > ! printf(FXP_FORMAT ": DMA timeout\n", FXP_ARGS(sc)); > } > > /************************************************************* > *************** > *** 679,690 **** > --- 700,784 ---- > return 0; > } > > + /* > + * Device suspend routine. Stop the interface and save some PCI > + * settings in case the BIOS doesn't restore them properly on > + * resume. > + */ > + static int > + fxp_suspend(device_t dev) > + { > + struct fxp_softc *sc = device_get_softc(dev); > + int i, s; > + > + s = splimp(); > + > + fxp_stop(sc); > + > + for (i=0; i<5; i++) > + sc->saved_maps[i] = pci_read_config(dev, PCIR_MAPS + i*4, 4); > + sc->saved_biosaddr = pci_read_config(dev, PCIR_BIOS, 4); > + sc->saved_intline = pci_read_config(dev, PCIR_INTLINE, 1); > + sc->saved_cachelnsz = pci_read_config(dev, PCIR_CACHELNSZ, 1); > + sc->saved_lattimer = pci_read_config(dev, PCIR_LATTIMER, 1); > + > + sc->suspended = 1; > + > + splx(s); > + > + return 0; > + } > + > + /* > + * Device resume routine. Restore some PCI settings in case the BIOS > + * doesn't, re-enable busmastering, and restart the interface if > + * appropriate. > + */ > + static int > + fxp_resume(device_t dev) > + { > + struct fxp_softc *sc = device_get_softc(dev); > + struct ifnet *ifp = &sc->sc_if; > + u_int16_t pci_command; > + int i, s; > + > + s = splimp(); > + > + /* better way to do this? */ > + for (i=0; i<5; i++) > + pci_write_config(dev, PCIR_MAPS + i*4, sc->saved_maps[i], 4); > + pci_write_config(dev, PCIR_BIOS, sc->saved_biosaddr, 4); > + pci_write_config(dev, PCIR_INTLINE, sc->saved_intline, 1); > + pci_write_config(dev, PCIR_CACHELNSZ, sc->saved_cachelnsz, 1); > + pci_write_config(dev, PCIR_LATTIMER, sc->saved_lattimer, 1); > + > + /* reenable busmastering */ > + pci_command = pci_read_config(dev, PCIR_COMMAND, 2); > + pci_command |= (PCIM_CMD_MEMEN|PCIM_CMD_BUSMASTEREN); > + pci_write_config(dev, PCIR_COMMAND, pci_command, 2); > + > + CSR_WRITE_4(sc, FXP_CSR_PORT, FXP_PORT_SELECTIVE_RESET); > + DELAY(10); > + > + /* reinitialize interface if necessary */ > + if (ifp->if_flags & IFF_UP) > + fxp_init(sc); > + > + sc->suspended = 0; > + > + splx(s); > + > + return 0; > + } > + > static device_method_t fxp_methods[] = { > /* Device interface */ > DEVMETHOD(device_probe, fxp_probe), > DEVMETHOD(device_attach, fxp_attach), > DEVMETHOD(device_detach, fxp_detach), > DEVMETHOD(device_shutdown, fxp_shutdown), > + DEVMETHOD(device_suspend, fxp_suspend), > + DEVMETHOD(device_resume, fxp_resume), > > { 0, 0 } > }; > *************** > *** 1095,1101 **** > int claimed = 0; > #endif > > ! while ((statack = CSR_READ_1(sc, FXP_CSR_SCB_STATACK)) != 0) { > #if defined(__NetBSD__) > claimed = 1; > #endif > --- 1189,1195 ---- > int claimed = 0; > #endif > > ! while (!sc->suspended && (statack = CSR_READ_1(sc, FXP_CSR_SCB_STATACK)) != 0) { > #if defined(__NetBSD__) > claimed = 1; > #endif > *************** > *** 1158,1164 **** > */ > if (fxp_add_rfabuf(sc, m) == 0) { > struct ether_header *eh; > ! u_int16_t total_len; > > total_len = rfa->actual_size & > (MCLBYTES - 1); > --- 1252,1258 ---- > */ > if (fxp_add_rfabuf(sc, m) == 0) { > struct ether_header *eh; > ! int total_len; > > total_len = rfa->actual_size & > (MCLBYTES - 1); > *************** > *** 1317,1322 **** > --- 1411,1419 ---- > struct fxp_cb_tx *txp; > int i; > > + ifp->if_flags &= ~(IFF_RUNNING | IFF_OACTIVE); > + ifp->if_timer = 0; > + > /* > * Cancel stats updater. > */ > *************** > *** 1359,1367 **** > panic("fxp_stop: no buffers!"); > } > } > - > - ifp->if_flags &= ~(IFF_RUNNING | IFF_OACTIVE); > - ifp->if_timer = 0; > } > > /* > --- 1456,1461 ---- > *************** > *** 1474,1480 **** > CSR_WRITE_4(sc, FXP_CSR_SCB_GENERAL, vtophys(&cbp->cb_status)); > CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); > /* ...and wait for it to complete. */ > ! while (!(cbp->cb_status & FXP_CB_STATUS_C)); > > /* > * Now initialize the station address. Temporarily use the TxCB > --- 1568,1574 ---- > CSR_WRITE_4(sc, FXP_CSR_SCB_GENERAL, vtophys(&cbp->cb_status)); > CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); > /* ...and wait for it to complete. */ > ! fxp_dma_wait(&cbp->cb_status, sc); > > /* > * Now initialize the station address. Temporarily use the TxCB > *************** > *** 1497,1503 **** > fxp_scb_wait(sc); > CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); > /* ...and wait for it to complete. */ > ! while (!(cb_ias->cb_status & FXP_CB_STATUS_C)); > > /* > * Initialize transmit control block (TxCB) list. > --- 1591,1597 ---- > fxp_scb_wait(sc); > CSR_WRITE_1(sc, FXP_CSR_SCB_COMMAND, FXP_SCB_COMMAND_CU_START); > /* ...and wait for it to complete. */ > ! fxp_dma_wait(&cb_ias->cb_status, sc); > > /* > * Initialize transmit control block (TxCB) list. > *************** > *** 1936,1941 **** > --- 2030,2036 ---- > struct ifnet *ifp = &sc->sc_if; > struct ifmultiaddr *ifma; > int nmcasts; > + int count; > > /* > * If there are queued commands, we must wait until they are all > *************** > *** 2017,2024 **** > * Wait until command unit is not active. This should never > * be the case when nothing is queued, but make sure anyway. > */ > while ((CSR_READ_1(sc, FXP_CSR_SCB_RUSCUS) >> 6) == > ! FXP_SCB_CUS_ACTIVE) ; > > /* > * Start the multicast setup command. > --- 2112,2125 ---- > * Wait until command unit is not active. This should never > * be the case when nothing is queued, but make sure anyway. > */ > + count = 100; > while ((CSR_READ_1(sc, FXP_CSR_SCB_RUSCUS) >> 6) == > ! FXP_SCB_CUS_ACTIVE && --count) > ! DELAY(10); > ! if (count == 0) { > ! printf(FXP_FORMAT ": command queue timeout\n", FXP_ARGS(sc)); > ! return; > ! } > > /* > * Start the multicast setup command. > Index: if_fxpvar.h > =================================================================== > RCS file: /home/ncvs/src/sys/pci/if_fxpvar.h,v > retrieving revision 1.9.2.1 > diff -c -r1.9.2.1 if_fxpvar.h > *** if_fxpvar.h 2000/03/29 02:02:39 1.9.2.1 > --- if_fxpvar.h 2000/09/17 13:15:33 > *************** > *** 68,73 **** > --- 68,79 ---- > int phy_primary_device; /* device type of primary PHY */ > int phy_10Mbps_only; /* PHY is 10Mbps-only device */ > int eeprom_size; /* size of serial EEPROM */ > + int suspended; /* 0 = normal 1 = suspended (APM) */ > + u_int32_t saved_maps[5]; /* pci data */ > + u_int32_t saved_biosaddr; > + u_int8_t saved_intline; > + u_int8_t saved_cachelnsz; > + u_int8_t saved_lattimer; > }; > > /* Macros to ease CSR access. */ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 6:53:24 2000 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 4394B37B422; Sun, 17 Sep 2000 06:53:15 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id AAA05747; Mon, 18 Sep 2000 00:52:44 +1100 Date: Mon, 18 Sep 2000 00:52:41 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Alexander Leidinger Cc: current@FreeBSD.ORG, jhb@FreeBSD.ORG Subject: Re: 100% system time? (SMPng on UP system) In-Reply-To: <200009170957.e8H9van02062@Magelan.Leidinger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Sep 2000, Alexander Leidinger wrote: > On 17 Sep, Bruce Evans wrote: > > >> dnetc runns with idprio 31, system cvsupped around Sep 16, 11 CEST from > >> a german mirror (it contains the idle fixes: src/sys/kern/kern_idle.c,v > >> 1.4), complete build{world,kernel}. > >> > >> ---snip--- > >> last pid: 1666; load averages: 1.10, 1.11, 1.03 up 0+00:51:21 16:54:14 > > > > Perhaps it really is a system process :-[. idprio on a pure cpu hog prevents > > other user processes from running like a system process might do: > > > > idprio 31 sh -c "while :; do :; done" > > > > System processes actually hang the entire system until they complete: > > Are you mixing idprio with rtprio or did I not understand what you > explain? You didn't understand :-). Try the example. It only uses idprio. rtprio certainly causes system hangs, and the supergiant lock may increase the problem. Before SMPng, rtprio processes prevented all non-rtprio processes including important daemons (and I think even kernel processes) from running. Starting an infinite loop at rtprio while remotely logged in was fatal because a ^C (character, not signal) to kill the process couldn't be delivered. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 6:57:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id D6BC037B423; Sun, 17 Sep 2000 06:57:30 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8HDvIN78781; Sun, 17 Sep 2000 15:57:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: Alexander Leidinger , current@FreeBSD.ORG, jhb@FreeBSD.ORG Subject: Re: 100% system time? (SMPng on UP system) In-Reply-To: Your message of "Mon, 18 Sep 2000 00:52:41 +1100." Date: Sun, 17 Sep 2000 15:57:18 +0200 Message-ID: <78779.969199038@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bruce Ev ans writes: >> > Perhaps it really is a system process :-[. idprio on a pure cpu hog prevents >> > other user processes from running like a system process might do: >> > >> > idprio 31 sh -c "while :; do :; done" >> > >> > System processes actually hang the entire system until they complete: >> >> Are you mixing idprio with rtprio or did I not understand what you >> explain? > >You didn't understand :-). Try the example. It only uses idprio. > >rtprio certainly causes system hangs, and the supergiant lock may >increase the problem. Before SMPng, rtprio processes prevented all >non-rtprio processes including important daemons (and I think even kernel processes) from running. Starting an infinite loop at rtprio >while remotely logged in was fatal because a ^C (character, not signal) >to kill the process couldn't be delivered. I can confirm this one, ntpd has for a long time pointlessly raised it's priority to the absolute maximum, and if during debugging it went into a spin it would freeze the system. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 7: 4:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailout1.hananet.net (mailout1.hananet.net [210.220.163.34]) by hub.freebsd.org (Postfix) with ESMTP id 2980637B423 for ; Sun, 17 Sep 2000 07:03:59 -0700 (PDT) Received: from gnomaniac.myhome ([210.205.34.245]) by mailout1.hananet.net (Netscape Messaging Server 4.15) with ESMTP id G11B2E02.5DM; Sun, 17 Sep 2000 23:03:50 +0900 Received: (from cjh@localhost) by gnomaniac.myhome (8.11.0/8.11.0) id e8HE1rI10324; Sun, 17 Sep 2000 23:01:53 +0900 (KST) (envelope-from cjh@kr.FreeBSD.org) X-Authentication-Warning: gnomaniac.myhome: cjh set sender to cjh@kr.FreeBSD.org using -f To: Steve Kargl Cc: FreeBSD Current Subject: Re: aic7xxx breaks kernel build References: <200009170509.WAA07882@troutmask.apl.washington.edu> From: CHOI Junho Date: 17 Sep 2000 23:01:52 +0900 In-Reply-To: Steve Kargl's message of "Sat, 16 Sep 2000 22:09:29 -0700 (PDT)" Message-ID: <86aed7i0bz.fsf@gnomaniac.myhome> Lines: 15 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "SK" == Steve Kargl writes: SK> I get the following with sources cvsup'd for cvsup5.freebsd.org SK> at 10:00 pm PST on 16 Sep 00. SK> make: cannot open /usr/src/sys/dev/aic7xxx/Makefile. Yes, me too. It seems that the file have removed after last commit on aic7xxx drivers... -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI Junho KFUG Web Data Bank FreeBSD, GNU/Linux Developer http://people.FreeBSD.org/~cjh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 7:23:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id F31DA37B422 for ; Sun, 17 Sep 2000 07:23:22 -0700 (PDT) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.11.0/8.11.0) with ESMTP id e8HENG108215; Sun, 17 Sep 2000 07:23:16 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.11.0/8.11.0) id e8HENnb30899; Sun, 17 Sep 2000 07:23:49 -0700 (PDT) (envelope-from frank) From: Frank Mayhar Message-Id: <200009171423.e8HENnb30899@realtime.exit.com> Subject: Re: fxp suspend/resume hangs In-Reply-To: <8168.969184571@winston.osd.bsdi.com> from Jordan Hubbard at "Sep 17, 2000 02:56:11 am" To: Jordan Hubbard Date: Sun, 17 Sep 2000 07:23:49 -0700 (PDT) Cc: mike ryan , freebsd-current@FreeBSD.ORG Reply-To: frank@exit.com Organization: Exit Consulting X-Copyright0: Copyright 2000 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > > in summary: PR kern/18756 contains a patch (against -stable, alas, > This PR has been explicitly assigned to David Greenman and should be > handled by him. As I pointed out in another message, nobody but he is > likely to touch the fxp driver under any circumstances so it basically > comes down to either him or nobody. So I suspect that either blackmail or bribery is now in order. :-) (Hey, it worked for me with Cameron and the SBLive driver!) -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 7:30:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id E972137B422; Sun, 17 Sep 2000 07:30:14 -0700 (PDT) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #20) id 13afSN-0004nl-00; Sun, 17 Sep 2000 16:30:11 +0200 Received: from ae0d0.pppool.de ([213.6.224.208] helo=Magelan.Leidinger.net) by mx2.freenet.de with esmtp (Exim 3.16 #20) id 13afSM-0002V2-00; Sun, 17 Sep 2000 16:30:10 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8HERFn34982; Sun, 17 Sep 2000 16:27:16 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009171427.e8HERFn34982@Magelan.Leidinger.net> Date: Sun, 17 Sep 2000 16:27:12 +0200 (CEST) From: Alexander Leidinger Subject: Re: 100% system time? (SMPng on UP system) To: bde@zeta.org.au Cc: current@FreeBSD.ORG, jhb@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Sep, Bruce Evans wrote: >> >> dnetc runns with idprio 31, system cvsupped around Sep 16, 11 CEST from >> >> a german mirror (it contains the idle fixes: src/sys/kern/kern_idle.c,v >> >> 1.4), complete build{world,kernel}. >> >> >> >> ---snip--- >> >> last pid: 1666; load averages: 1.10, 1.11, 1.03 up 0+00:51:21 16:54:14 >> > >> > Perhaps it really is a system process :-[. idprio on a pure cpu hog prevents >> > other user processes from running like a system process might do: >> > >> > idprio 31 sh -c "while :; do :; done" >> > >> > System processes actually hang the entire system until they complete: >> >> Are you mixing idprio with rtprio or did I not understand what you >> explain? > > You didn't understand :-). Try the example. It only uses idprio. I have dnetc still running with idprio 31 and it didn't hang the entire system (I'm able to write this mail and compiling a port in the background while dnetc is running). As I understand this: - The man-page of idprio says it allows processes only to run if the system is idle. - You say, in my case (dnetc is a cpu hog, isn't it?) idprio prevents other processes from running (the opposide of what I want). - I say, dnetc is running in the background with idprio 31 and I'm able to do usefull work while it is running. Confused, Alexander. -- Reboot America. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 7:45:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 1A5D537B42C for ; Sun, 17 Sep 2000 07:45:19 -0700 (PDT) Received: (qmail 13751 invoked from network); 17 Sep 2000 14:45:14 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 17 Sep 2000 14:45:14 -0000 Date: Mon, 18 Sep 2000 01:45:10 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Alexander Leidinger Cc: current@FreeBSD.ORG, jhb@FreeBSD.ORG Subject: Re: 100% system time? (SMPng on UP system) In-Reply-To: <200009171427.e8HERFn34982@Magelan.Leidinger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Sep 2000, Alexander Leidinger wrote: > On 18 Sep, Bruce Evans wrote: > > >> >> dnetc runns with idprio 31, system cvsupped around Sep 16, 11 CEST from > >> >> a german mirror (it contains the idle fixes: src/sys/kern/kern_idle.c,v > >> >> 1.4), complete build{world,kernel}. > >> >> > >> >> ---snip--- > >> >> last pid: 1666; load averages: 1.10, 1.11, 1.03 up 0+00:51:21 16:54:14 > >> > > >> > Perhaps it really is a system process :-[. idprio on a pure cpu hog prevents > >> > other user processes from running like a system process might do: > >> > > >> > idprio 31 sh -c "while :; do :; done" > >> > > >> > System processes actually hang the entire system until they complete: > >> > >> Are you mixing idprio with rtprio or did I not understand what you > >> explain? > > > > You didn't understand :-). Try the example. It only uses idprio. > > I have dnetc still running with idprio 31 and it didn't hang the entire > system (I'm able to write this mail and compiling a port in the > background while dnetc is running). dnetc presumably blocks occasionally, giving other processes a chance to run. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 8:19:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id 7C20537B424; Sun, 17 Sep 2000 08:19:09 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id RAA01381; Sun, 17 Sep 2000 17:18:46 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.0/8.8.8) with ESMTP id e8HGIiF01053; Sun, 17 Sep 2000 18:18:44 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sun, 17 Sep 2000 18:18:39 +0200 (CEST) From: Michael Reifenberger To: Greg Lehey Cc: FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io In-Reply-To: <20000917102824.C42114@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, if the order of the ps macro is correct, here the backtraces of the procs 35,36,37: Copyright (c) 1992-2000 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 #0: Sat Sep 16 19:32:53 CEST 2000 root@nihil.plaut.de:/usr/obj/usr/src/sys/nihil Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 266615847 Hz CPU: Pentium II/Pentium II Xeon/Celeron (266.62-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 268369920 (262080K bytes) config> #flags wdc0 0xa0ffa0ff Invalid command or syntax. Type `?' for help. config> #flags wdc1 0xa0ffa0ff Invalid command or syntax. Type `?' for help. config> #iosiz npx0 196608 Invalid command or syntax. Type `?' for help. config> #irq pcic0 11 Invalid command or syntax. Type `?' for help. config> quit avail memory = 257589248 (251552K bytes) Preloaded elf kernel "kernel.ko" at 0xc03ad000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03ad0ac. Preloaded elf module "linux.ko" at 0xc03ad0fc. Preloaded elf module "linprocfs.ko" at 0xc03ad19c. Pentium Pro MTRR support enabled VESA: v2.0, 2496k memory, flags:0x0, mode table:0xc031ee42 (1000022) VESA: MagicGraph 256 AV 44K PRELIMINARY npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 4.0 irq 11 isab0: at device 5.0 on pci0 isa0: on isab0 atapci0: port 0xfe60-0xfe6f at device 5.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 5.2 irq 11 pci0: at 5.3 pci0: at 9.0 irq 11 pcic-pci0: at device 11.0 on pci0 pcic-pci1: at device 11.1 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 pps0: on ppbus0 pcic0: at port 0x3e0-0x3e1 on isa0 pcic0: Polling mode pccard0: on pcic0 pccard1: on pcic0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources pcm0: at port 0x220-0x233,0x530-0x537,0x388-0x38f,0x330-0x333,0x538-0x539 irq 5 drq 1,0 on isa0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited to 100 packets/entry by default IPsec: Initialized Security Association Processing. ad0: 24207MB [49184/16/63] at ata0-master using UDMA33 ad1: 6194MB [13424/15/63] at ata1-master using UDMA33 Mounting root from ufs:/dev/ad0s1a pccard: card inserted, slot 0 panic: from debugger syncing disks... done Uptime: 3h22m40s dumping to dev #ad/0x20001, offset 2547840 dump ata0: resetting devices .. done 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:475 475 dumppcb.pcb_cr3 = rcr3(); (kgdb) proc 37 (kgdb) bt #0 mi_switch () at /usr/src/sys/kern/kern_synch.c:953 #1 0xc017e2f0 in msleep (ident=0xc9663f20, mtx=0x0, priority=0x110, wmesg=0xc028b101 "piperd", timo=0x0) at /usr/src/sys/kern/kern_synch.c:506 #2 0xc018e5bc in pipe_read (fp=0xc1258cc0, uio=0xc9666ec4, cred=0xc0ea9f80, flags=0x0, p=0xc7874a00) at /usr/src/sys/kern/sys_pipe.c:445 #3 0xc018d01e in dofileread (p=0xc7874a00, fp=0xc1258cc0, fd=0x0, buf=0x80ac000, nbyte=0x2800, offset=0xffffffffffffffff, flags=0x0) at /usr/src/sys/sys/file.h:141 #4 0xc018cf47 in read (p=0xc7874a00, uap=0xc9666f80) at /usr/src/sys/kern/sys_generic.c:110 #5 0xc0261aec in syscall2 (frame={tf_fs = 0x2f, tf_es = 0x80b002f, tf_ds = 0xbfbf002f, tf_edi = 0xbfbffd60, tf_esi = 0x1, tf_ebp = 0xbfbffc6c, tf_isp = 0xc9666fd4, tf_ebx = 0x1, tf_edx = 0x2800, tf_ecx = 0x80ae600, tf_eax = 0x3, tf_trapno = 0x7, tf_err = 0x2, tf_eip = 0x8089494, tf_cs = 0x1f, tf_eflags = 0x297, tf_esp = 0xbfbffc40, tf_ss = 0x2f}) at /usr/src/sys/i386/i386/trap.c:1136 #6 0xc0255b0f in Xint0x80_syscall () #7 0x80499e5 in ?? () #8 0x80481fd in ?? () #9 0x8050976 in ?? () #10 0x80505db in ?? () #11 0x80528f6 in ?? () #12 0x8048135 in ?? () (kgdb) proc 36 (kgdb) bt #0 mi_switch () at /usr/src/sys/kern/kern_synch.c:953 #1 0xc017e2f0 in msleep (ident=0xc02f4220, mtx=0xc0322fc0, priority=0x2, wmesg=0xc02a2b00 "FFS node", timo=0x0) at /usr/src/sys/kern/kern_synch.c:506 #2 0xc01762bc in malloc (size=0x104, type=0xc02f4220, flags=0x0) at /usr/src/sys/kern/kern_malloc.c:171 #3 0xc021fecb in ffs_vget (mp=0xc1070000, ino=0x1dddba, vpp=0xc960bd40) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1045 #4 0xc0223575 in ufs_lookup (ap=0xc960bd98) at /usr/src/sys/ufs/ufs/ufs_lookup.c:551 #5 0xc0227bd1 in ufs_vnoperate (ap=0xc960bd98) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2263 #6 0xc01a6df3 in vfs_cache_lookup (ap=0xc960bdf0) at vnode_if.h:77 #7 0xc0227bd1 in ufs_vnoperate (ap=0xc960bdf0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2263 #8 0xc01a9f44 in lookup (ndp=0xc960be6c) at vnode_if.h:52 #9 0xc01a9968 in namei (ndp=0xc960be6c) at /usr/src/sys/kern/vfs_lookup.c:153 #10 0xc01afaa9 in lstat (p=0xc7874bc0, uap=0xc960bf80) at /usr/src/sys/kern/vfs_syscalls.c:1787 #11 0xc0261aec in syscall2 (frame={tf_fs = 0x2f, tf_es = 0x80a002f, tf_ds = 0xbfbf002f, tf_edi = 0x80b8030, tf_esi = 0x80b802c, tf_ebp = 0xbfbffa74, tf_isp = 0xc960bfd4, tf_ebx = 0x14, tf_edx = 0x80af200, tf_ecx = 0x80af200, tf_eax = 0xbe, tf_trapno = 0x7, tf_err = 0x2, tf_eip = 0x805e354, tf_cs = 0x1f, tf_eflags = 0x293, tf_esp = 0xbfbff9e8, tf_ss = 0x2f}) at /usr/src/sys/i386/i386/trap.c:1136 #12 0xc0255b0f in Xint0x80_syscall () #13 0x804b0cd in ?? () #14 0x804b0cd in ?? () #15 0x804b0cd in ?? () #16 0x804b0cd in ?? () #17 0x804a431 in ?? () #18 0x8052801 in ?? () #19 0x8048135 in ?? () (kgdb) proc 35 (kgdb) bt #0 mi_switch () at /usr/src/sys/kern/kern_synch.c:953 #1 0xc017e2f0 in msleep (ident=0xc1d2fa00, mtx=0x0, priority=0x8, wmesg=0xc02a2c62 "inode", timo=0x0) at /usr/src/sys/kern/kern_synch.c:506 #2 0xc01750f2 in acquire (lkp=0xc1d2fa00, extflags=0x1000040, wanted=0x600) at /usr/src/sys/kern/kern_lock.c:147 #3 0xc017537c in lockmgr (lkp=0xc1d2fa00, flags=0x1010002, interlkp=0xc9b371ec, p=0xc7874d80) at /usr/src/sys/kern/kern_lock.c:354 #4 0xc01a8ba8 in vop_stdlock (ap=0xc9608d34) at /usr/src/sys/kern/vfs_default.c:243 #5 0xc0227bd1 in ufs_vnoperate (ap=0xc9608d34) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2263 #6 0xc01b35e3 in vn_lock (vp=0xc9b37180, flags=0x10002, p=0xc7874d80) at vnode_if.h:840 #7 0xc01abc8b in vget (vp=0xc9b37180, flags=0x2, p=0xc7874d80) at /usr/src/sys/kern/vfs_subr.c:1393 #8 0xc01a6d18 in vfs_cache_lookup (ap=0xc9608df0) at /usr/src/sys/kern/vfs_cache.c:470 #9 0xc0227bd1 in ufs_vnoperate (ap=0xc9608df0) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2263 #10 0xc01a9f44 in lookup (ndp=0xc9608e6c) at vnode_if.h:52 #11 0xc01a9968 in namei (ndp=0xc9608e6c) at /usr/src/sys/kern/vfs_lookup.c:153 #12 0xc01afaa9 in lstat (p=0xc7874d80, uap=0xc9608f80) at /usr/src/sys/kern/vfs_syscalls.c:1787 #13 0xc0261aec in syscall2 (frame={tf_fs = 0xc025002f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x80b8030, tf_esi = 0x80b802c, tf_ebp = 0xbfbffa6c, tf_isp = 0xc9608fd4, tf_ebx = 0x14, tf_edx = 0x80af200, tf_ecx = 0x80af200, tf_eax = 0xbe, tf_trapno = 0x7, tf_err = 0x2, tf_eip = 0x805e354, tf_cs = 0x1f, tf_eflags = 0x283, tf_esp = 0xbfbff9e0, tf_ss = 0x2f}) at /usr/src/sys/i386/i386/trap.c:1136 #14 0xc0255b0f in Xint0x80_syscall () #15 0x804b0cd in ?? () #16 0x804b0cd in ?? () #17 0x804b0cd in ?? () #18 0x804b0cd in ?? () #19 0x804a431 in ?? () #20 0x8052801 in ?? () #21 0x8048135 in ?? () (kgdb) quit Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 8:19:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 2EA9737B424 for ; Sun, 17 Sep 2000 08:19:39 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13agMK-0000Vf-00; Sun, 17 Sep 2000 09:28:00 -0600 Message-ID: <39C4E300.242244E9@softweyr.com> Date: Sun, 17 Sep 2000 09:28:00 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: SMPNG kernel on UP References: <200009142042.QAA15287@khavrinen.lcs.mit.edu> <200009141941.MAA86101@pike.osd.bsdi.com> <200009141946.NAA98535@harmony.village.org> <200009142044.OAA99073@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <200009142042.QAA15287@khavrinen.lcs.mit.edu> Garrett Wollman writes: > : < said: > : > Hmmm, they look good to me. Maybe Mark's system doesn't have group > : > operator at gid 5. That's one bad thing about the new DEVFS: it > : > appears to enshrine things like this in the kernel... > : > : It would only take a small amount of Makefile magic to fix > : this... something like: > : > : PASSWD?= /etc/passwd > : GROUP?= /etc/group > : > : uidgid.h: ${PASSWD} ${GROUP} > : perl -ne 'split(/:/); print ("#define\tUID_", uc($_[0]), "\t", \ > : $_[2], "\n");' ${PASSWD} >${.TARGET} > : perl -ne 'split(/:/); print ("#define\tGID_", uc($_[0]), "\t", \ > : $_[2], "\n");' ${GROUP} >>${.TARGET} > : > : ...add this to and include "uidgid.h" as necessary in > : source files. > > Hmmm, I like it... But it does suffer from one problem that we > already have enough of in our tree. The build on one system, install > on another problem. It would be better than the current situtation. Add ${DESTDIR} to PASSWD and GROUP? That will help. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 8:37: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 710EF37B422; Sun, 17 Sep 2000 08:37:06 -0700 (PDT) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #20) id 13agV2-00009S-00; Sun, 17 Sep 2000 17:37:00 +0200 Received: from a2c48.pppool.de ([213.6.44.72] helo=Magelan.Leidinger.net) by mx2.freenet.de with esmtp (Exim 3.16 #20) id 13agV2-0003lU-00; Sun, 17 Sep 2000 17:37:00 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8HFPun36463; Sun, 17 Sep 2000 17:25:57 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009171525.e8HFPun36463@Magelan.Leidinger.net> Date: Sun, 17 Sep 2000 17:25:54 +0200 (CEST) From: Alexander Leidinger Subject: Re: 100% system time? (SMPng on UP system) To: bde@zeta.org.au Cc: current@FreeBSD.ORG, jhb@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Sep, Bruce Evans wrote: > dnetc presumably blocks occasionally, giving other processes a chance to > run. I've started dnetc without idprio (with build in "nice"), it also displays 100% system. And with a closer look (stopped dnetc): 0% user, 0% nice... ? ---snip--- last pid: 36437; load averages: 0.68, 1.44, 1.41 up 0+06:53:18 17:23:03 73 processes: 1 running, 70 sleeping, 1 stopped, 1 zombie CPU states: 0.0% user, 0.0% nice, 30.2% system, 5.2% interrupt, 64.6% idle Mem: 63M Active, 13M Inact, 33M Wired, 5644K Cache, 22M Buf, 6580K Free Swap: 266M Total, 43M Used, 223M Free, 15% Inuse, 8K In kill PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 35709 netchild 2 0 10956K 6736K poll 1:48 8.94% 8.94% xmms 732 netchild 2 0 3224K 1048K select 0:05 5.81% 5.81% xterm 658 root 2 0 80016K 33516K select 10:48 4.98% 4.98% XF86_SVGA 457 netchild -6 0 2856K 512K pcmwr 0:46 2.49% 2.49% esd ---snip--- Bye, Alexander. -- I believe the technical term is "Oops!" http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 8:48:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from hip4.hip-web.com (hip4.hip-web.com [216.173.203.178]) by hub.freebsd.org (Postfix) with SMTP id CCB8F37B422 for ; Sun, 17 Sep 2000 08:48:44 -0700 (PDT) Received: (qmail 10932 invoked by uid 511); 17 Sep 2000 15:42:59 -0000 Message-ID: <20000917154237.10896.qmail@hip4.hip-web.com> Cc: recipient list not shown: ; From: yohko@ha.bekkoame.ne.jp Reply-To: yohko@ha.bekkoame.ne.jp Subject: =?ISO-2022-JP?B?GyRCM2QkaiQtJEMkPyQqSVUkLTlnJCQkNyReJDskcyQrISkbKEI=?= Date: Mon, 18 Sep 2000 00:42:37 +0900 Error-To: yohko@ha.bekkoame.ne.jp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $B$3$N>pJs$,ITI,MW$JJ}$O:o=|$J$5$C$F2<$5$$!#(B $B$^$?!"K|$,0l=w@-$NJ}$KFO$$$?>l9g$b?=$7$o$1$"$j$^$;$s$,:o=|$J$5$C$F2<$5$$!#(B ====================================================================== $B!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!(BDi$B$M$C$H$O!%!%!%(B $B!!!!!!I^7,R2p$5$l$^$7$?!#(B $B!!!!!!E4?MR2p$5$l$F$$$^$9!*(B ====================================================================== $B3'$5$s$h$/7G<(HD$J$I$rMxMQ$7$F3d$j@Z$C$?8r:]4uK>=w@-$rJg=8$5$l$F$$$^$9$,!"(B $B@.2L$N$[$I$O$$$+$,$G$7$g$&$+!)(B $B!V%;%C%/%9%U%l%s%I$,$G$-$?!W!"$H$$$&J}$b$$$i$C$7$c$k$h$&$G$9$,!";d$I$b$N(B $B%j%5!<%A$K$h$k$H!"#3#0#0?M$K#1?M$$$k$+$$$J$$$+$0$i$$$G$7$+$J$$$h$&$G$9!#(B $B$=$NB>$NJ}!9$O$4B8$8$N$H$*$j!"7G<(!"%a!<%kBT$A!"%a!<%kAwIU!"7G<(!"(B $B%a!<%kBT$A!"%a!<%kAwIU$NF2!9=d$j$N$h$&$G$9!#(B $B!!!!!!$J$<$@$+$o$+$j$^$9$+!)(B $B!!(B $BEz$($O4JC1$G$9!##1BP#1$G%3%_%e%K%1!<%7%g%s$rR2p$7$F$$$^$9!#(B $B%M%C%H%J%s%QI,>!K!$,$"$l$P#1BP#1$N%3%_%e%K%1!<%7%g%s$OEv$?$jA0$K$J$j$^$9!#(B $B!V(BDi$B$M$C$H!W$N%M%C%H%J%s%QI,>!K!$G%M%C%H%J%s%Q;U$,$>$/$>$/CB@8Cf$G$9!#(B $B9XF~7G:\Cf$G$9!*(B $B$^$?!"%M%C%H%J%s%Q$NBe9T6HL3$b9T$C$F$$$^$9!#(B $B!!(B $B!!!!!!#2G/$G#5#0?M0J>e$r?)$C$?%M%C%H%J%s%Q;U$H$7$F!"(B $B!!!!!!!V#S#P#A!*#2#0#0#0G/#5!?#3#1F|9f!W(B $B!!!!!!E4?MR2p$5$l$^$7$?!#(B $B!V(BDi$B$M$C$H!W$G$O!"%N%&%O%&9XF~$*$h$S!"%J%s%QBe9T$rR2p$7$F$b$i$C$?$"$H!"(B $B$I$&$9$l$P=w@-$,<+J,@lMQ$N0&?M$K$J$k$+!"$H$+!"(B $B$J$+$J$+O"Mm$,Mh$J$$=w@-$r4JC1$K?6$j8~$+$;$kJ}K!$J$I!"(B $B;d$NBN83$r$^$8$($F>R2p$7$^$9!#(B $B$3$N%a!<%k%^%,%8%s$OHs2q0wMM$OM-NA$H$J$j$^$9!#(B $B%J%s%QI,>!K!$N9XF~$*$h$S%J%s%QBe9T$r\$7$/$O!V(BDi$B$M$C$H!W$N%[!<%`%Z!<%8$^$G$*1[$72<$5$$!#(B $B!!!!!!LLGr$$$h$&$K=w@-$,$R$C$+$+$kJ}K!$rEA!'(B $B!V(B Di$B$M$C$H!W(B $B""(BWEB $B!!!'!!(Bhttp://www5a.biglobe.ne.jp/~di-net/index4.htm ====================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 9:14:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from lavender.sanpei.org (ppp116.dialup.st.keio.ac.jp [131.113.27.116]) by hub.freebsd.org (Postfix) with ESMTP id 7DCC937B423 for ; Sun, 17 Sep 2000 09:14:37 -0700 (PDT) Received: (from sanpei@localhost) by lavender.sanpei.org (8.11.0/3.7W) id e8HFsJe02816; Mon, 18 Sep 2000 00:54:19 +0900 (JST) Message-Id: <200009171554.e8HFsJe02816@lavender.sanpei.org> To: current@FreeBSD.org Subject: Please review: small change in sys/i386/isa/clock.c and sys/alpha/alpha/clock.c for PC-Card melody beep code. From: sanpei@FreeBSD.org X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 18 Sep 2000 00:54:19 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. FreeBSD developers. I have a plan to commit PC-Card melody beep code into 5-current(/sys/pccard/pccard_beep.c) from PAO3. But it needs to call sysbeepstop@sys/${ARCH}/${BUS}/clock.c function from pccard_beep.c. May I commit below small changes to sys/i386/isa/clock.c and sys/alpha/alpha/clock.c? MAIN POINT: static void sysbeepstop --> void sysbeepstop. Full PC-Card melody patch is in below URL. http://people.FreeBSD.org/~sanpei/5-current/sys-pccard-pccard_beep_melody-20000917.diff --- MIHIRA, Sanpei Yoshiro Yokohama, Japan. --- sys/i386/isa/clock.c.org Tue May 9 10:16:31 2000 +++ sys/i386/isa/clock.c Sat May 6 00:50:11 2000 @@ -510,7 +510,7 @@ #endif } -static void +void sysbeepstop(void *chan) { outb(IO_PPI, inb(IO_PPI)&0xFC); /* disable counter2 output to speaker */ --- sys/alpha/alpha/clock.c.org Fri Sep 15 18:05:23 2000 +++ sys/alpha/alpha/clock.c Fri Sep 15 18:05:52 2000 @@ -626,7 +626,7 @@ return (0); } -static void +void sysbeepstop(void *chan) { outb(IO_PPI, inb(IO_PPI)&0xFC); /* disable counter2 output to speaker */ --- sys/i386/include/clock.h.org Fri Sep 15 18:07:58 2000 +++ sys/i386/include/clock.h Fri Sep 15 18:09:19 2000 @@ -44,6 +44,7 @@ int release_timer1 __P((void)); #endif int sysbeep __P((int pitch, int period)); +void sysbeepstop __P((void *chan)); void i8254_restore __P((void)); #endif /* _KERNEL */ --- sys/alpha/include/clock.h.org Mon Sep 18 00:38:54 2000 +++ sys/alpha/include/clock.h Mon Sep 18 00:39:12 2000 @@ -17,6 +17,7 @@ void DELAY __P((int usec)); int sysbeep __P((int pitch, int period)); +void sysbeepstop __P((void *chan)); int acquire_timer2 __P((int mode)); int release_timer2 __P((void)); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 9:27:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from spock.org (cm-24-92-52-10.nycap.rr.com [24.92.52.10]) by hub.freebsd.org (Postfix) with ESMTP id EBAD837B422 for ; Sun, 17 Sep 2000 09:27:36 -0700 (PDT) Received: (from jon@localhost) by spock.org serial EF600Q3T-B7F; Sun, 17 Sep 2000 12:27:08 -0400 (EDT) (envelope-from jon) Date: Sun, 17 Sep 2000 12:27:08 -0400 From: Jonathan Chen To: David Greenman Cc: mike ryan , freebsd-current@FreeBSD.ORG Subject: Re: fxp suspend/resume hangs Message-ID: <20000917122707.A67786@spock.org> References: <20000917002733.A37043@medianstrip.net> <200009171231.FAA26513@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: telnet/1.1x In-Reply-To: <200009171231.FAA26513@implode.root.com>; from dg@root.com on Sun, Sep 17, 2000 at 05:31:45AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 17, 2000 at 05:31:45AM -0700, David Greenman wrote: > >in summary: PR kern/18756 contains a patch (against -stable, alas, > >sorry) which fixes kernel hangs in the fxp driver on some laptops > >after a resume from suspend. while quite a few people appear to be > >using this patch successfully, it hasn't been committed -- david > >greenman had an entirely reasonable objection to one aspect of the > >patch's behavior. > > > >unfortunately, my knowledge of the kernel isn't sufficient to > >adequately address david's concerns, and though i've mailed him to > >ask for guidance twice over the past 4 months, i haven't received a > >response. that's probably my fault, i probably should have been > >mailing -current to being with. > > I can only find the 5/22 email regarding this, so I seem to have missed > your second message. With over a thousand emails a day coming into my inbox, > this shouldn't be too surprising. My response to the 5/22 message was this: > > ... > This could be a problem. If an interrupt occurs, it must be acknowledged > otherwise you'll be stuck in an infinit loop - PCI interrupts are level > sensitive and must be cleared in the ISR. > ... > > In short, while it may fix a hang in your laptop case, it opens the driver > up to a hang if an unexpected interrupt occurs while IFF_RUNNING is clear. I > think this is dangerous enough that I don't think the code should not be > compiled as part of the standard driver. One just cannot ignore level- > sensitive PCI interrupts. While programming for cardbus under FreeBSD, I ran into similar issues that when cards were powere down or removed where they would go into an infinite loop reading status registers. What actually happens is the register returns 0xffffffff whenever it is read, and the resolution I used was to check whether it is equal to 0xffff and do appropiate measures when it is found to be true. It looks from reading the PR that this might be a similar issue here -- that the card is powered down during suspend and of wakeup the reads to FXP_CSR_SCB_STATACK and cbp->cb_status returns 0xff. I believe this issue can be resolved by checking whether what was read equals 0xffffffff and abort the loop. This should be fairly safe as interrups shouldn't happen during powerdown (and can't be ack'ed anyway)... -- (o_ 1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2 _o) \\\_\ Jonathan Chen jon@spock.org /_/// <____) No electrons were harmed during production of this message (____> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 11:33:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0355C37B423; Sun, 17 Sep 2000 11:33:12 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA86725; Sun, 17 Sep 2000 12:33:10 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA24037; Sun, 17 Sep 2000 12:33:03 -0600 (MDT) Message-Id: <200009171833.MAA24037@harmony.village.org> To: Mike Meyer Subject: Re: Kernel builds to wrong location? Cc: Ben Smithurst , current@FreeBSD.ORG In-reply-to: Your message of "Sat, 16 Sep 2000 23:27:34 CDT." <14788.18486.789541.682547@guru.mired.org> References: <14788.18486.789541.682547@guru.mired.org> <14788.16494.26893.660078@guru.mired.org> <20000917051648.I56185@strontium.scientia.demon.co.uk> Date: Sun, 17 Sep 2000 12:33:02 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14788.18486.789541.682547@guru.mired.org> Mike Meyer writes: : Is needing to have a new loader installed to boot worth a mention in : UPDATING? Nah. People should be forced to puzzle it out for themselves ;-) Warner P.S. An entry will be committed shortly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 11:38:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id F32B837B422; Sun, 17 Sep 2000 11:38:32 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA86755; Sun, 17 Sep 2000 12:38:31 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA24081; Sun, 17 Sep 2000 12:38:24 -0600 (MDT) Message-Id: <200009171838.MAA24081@harmony.village.org> To: sanpei@FreeBSD.ORG Subject: Re: Please review: small change in sys/i386/isa/clock.c and sys/alpha/alpha/clock.c for PC-Card melody beep code. Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 18 Sep 2000 00:54:19 +0900." <200009171554.e8HFsJe02816@lavender.sanpei.org> References: <200009171554.e8HFsJe02816@lavender.sanpei.org> Date: Sun, 17 Sep 2000 12:38:24 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've seen these patches many times and think that it is a good idea. This interface needs to be exported so that the pccard system sounds don't interfere with normal systme sounds. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 11:45:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from dataloss.net (massive.dataloss.net [212.189.232.193]) by hub.freebsd.org (Postfix) with SMTP id B14D137B43C for ; Sun, 17 Sep 2000 11:45:02 -0700 (PDT) Received: (qmail 11597 invoked by uid 1000); 17 Sep 2000 18:36:16 -0000 Date: Sun, 17 Sep 2000 20:36:16 +0200 From: Peter van Dijk To: current@FreeBSD.ORG Subject: Re: superduperopen(3) (was: Fdescfs updates--coming to a devfs near you!) Message-ID: <20000917203616.B11424@dataloss.net> Mail-Followup-To: current@FreeBSD.ORG References: <200009160249.e8G2n3n02415@hak.lan.Awfulhak.org> <20000916100447.I27034@speedy.gsinet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000916100447.I27034@speedy.gsinet>; from Gerhard.Sittig@gmx.net on Sat, Sep 16, 2000 at 10:04:47AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 16, 2000 at 10:04:47AM +0200, Gerhard Sittig wrote: > > > How much sense does it make to think about implementing tee and > select methods this way? Like "open file1 and file2 and write to > both of them whatever I give to you" and "give me data coming in > from whatever file is in this set"? The only problem is to > determine available characters to separate these names. '+' as > well as ':', ',' and ';' are perfectly valid characters for > constructing filenames. '&' seems to be too, but could be used > rarely enough. And the split upon these new separators actually > should be done only when the appropriate SDO_ flags are passed. > > e.g. > superduperopen("file1&file2", "a+", SDO_TEEFILES) > superduperopen("file1&file2", "r" , SDO_SELECT) FILE *superduperopen(char *files[], char *type, int flags); [snip] > parameters) have to pass certain checks. Nobody should try to > read from "|command". And I cannot see any use for "write to > whatever descriptor is ready to write to first" as would result > from "w" and SDO_SELECT. But they should be able to read from "command|", ofcourse. That feature should be in there too :) I do see a use to "write to whatever descriptor is ready first". It could be used for a very simple multithreading-like implementation. Spawn 8 child processes, attach them to one stream with superduperopen(), and pass single-byte commands to one that is waiting to handle one. If all 8 are busy, you block, or return something like EAGAIN. This description is very pseudo-something, btw :) > Feel free to correct the flag's data type. I have the feeling > not all int's have 32bits. :) Some other means of storage might int works for open, I doubt whether we need more options than open does :) > be more appropriate while still being easy to combine and to pass > to the function. But I feel strings like "STD,PIPE,TEE" are There's no reason for that. We have a compiler that can parse *unquoted* strings like STD | PIPE | TEE and create single int's out of that. Ain't it wonderful :) > harder to parse and single character notation like the "wt" mode > flags are harder to find (think of) and to read (in terms of > eyeballing the source code) for the sdo case. I do think the "w+" 'n stuff notation in popen sucks. This is our chance to turn those into bitflags too, for superduperopen anyway. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 13:39:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 02C0337B422 for ; Sun, 17 Sep 2000 13:39:24 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id NAA26894; Sun, 17 Sep 2000 13:39:02 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id NAA12052; Sun, 17 Sep 2000 13:39:01 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Sun, 17 Sep 2000 13:39:01 -0700 (PDT) Message-Id: <200009172039.NAA12052@vashon.polstra.com> To: current@freebsd.org Cc: Alexander@Leidinger.net Subject: Re: patch for openssh In-Reply-To: <200009170929.e8H9TZn01194@Magelan.Leidinger.net> References: <200009170929.e8H9TZn01194@Magelan.Leidinger.net> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009170929.e8H9TZn01194@Magelan.Leidinger.net>, Alexander Leidinger wrote: > > Index: authfd.c > =================================================================== > RCS file: /big/FreeBSD-CVS/src/crypto/openssh/authfd.c,v > retrieving revision 1.6 > diff -u -r1.6 authfd.c > --- authfd.c 2000/09/10 09:35:37 1.6 > +++ authfd.c 2000/09/16 15:27:25 > @@ -178,7 +178,7 @@ > if (sock < 0) > return NULL; > > - auth = xmalloc(sizeof(*auth)); > + auth = xmalloc(sizeof(AuthenticationConnection)); > auth->fd = sock; > buffer_init(&auth->identities); > auth->howmany = 0; What is the point of that change? Functionally it makes no difference at all, since "*auth" is an AuthenticationConnection. It makes the code harder to maintain in case the type of "auth" is changed in the future. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 14:18:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [209.145.74.241]) by hub.freebsd.org (Postfix) with ESMTP id 25DE837B422; Sun, 17 Sep 2000 14:18:38 -0700 (PDT) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.9.3/8.8.8) with ESMTP id RAA24394; Sun, 17 Sep 2000 17:18:34 -0400 (EDT) (envelope-from adrian@ubergeeks.com) Date: Sun, 17 Sep 2000 17:18:34 -0400 (EDT) From: Adrian Filipi-Martin Reply-To: Adrian Filipi-Martin To: Ben Smithurst Cc: Poul-Henning Kamp , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: <20000914115342.I77593@strontium.scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 14 Sep 2000, Ben Smithurst wrote: > Poul-Henning Kamp wrote: > > > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > > is bogus. It looks like something which happened "because we can" more > > than something which has a legitimate need. > > You think adding a hack to every program to support "-" to mean > stdout/stdin is better? It seems to be that saying "/dev/stdin" when > you mean stdin is better than saying "-" and hoping the application > handles that correctly. Of course many programs will read stdin by > default, and write stdout by default, but that doesn't help when you > want to read more than one file, one of which is stdin. > > > If anything I would propose we ditch it... > > And break loads of scripts at the same time? I recently ran into revelant problem with /dev/stdout, while working on some software under linux that expected /dev/stdout as an argument instead of using stdout. Using the device file breaks, if the process is suid to a non-root user. This is because it cannot open /dev/stdout, which is owned by your UID and not the EUID of the process to which the device was passed. My solution was to add the "-" hack and use the existing open descriptor. Still, I don't think /dev/stdout and friends are such bad things that they should be abandoned. They are present in other OS's and it does help avoid making named pipes and the such when you need the behavior the special devices provide. I think it would simple create minor poratability issues for third party software. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 15:10:14 2000 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 59F2237B423 for ; Sun, 17 Sep 2000 15:10:12 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id PAA11090 for freebsd-current@freebsd.org; Sun, 17 Sep 2000 15:15:24 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200009172215.PAA11090@troutmask.apl.washington.edu> Subject: aic7xxx changes break kernel builds To: FreeBSD Current Date: Sun, 17 Sep 2000 15:15:24 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hotrats:root[211] setenv KERNEL HOTRATS hotrats:root[212] make buildkernel -------------------------------------------------------------- >>> Rebuilding kernel(s) -------------------------------------------------------------- ===> HOTRATS mkdir -p /usr/obj/usr/src/sys cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -r -d /usr/obj/usr/src/sys/HOTRATS HOTRATS Don't forget to do a ``make depend'' Kernel build directory is /usr/obj/usr/src/sys/HOTRATS cd /usr/obj/usr/src/sys/HOTRATS; MAKESRCPATH=/usr/src/sys/dev/aic7xxx make -f /usr/src/sys/dev/aic7xxx/Makefile make: cannot open /usr/src/sys/dev/aic7xxx/Makefile. *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. It has been this way since last night 10pm PST. Anyone have a tip on generating the missing Makefile? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 15:10:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id CC32F37B423; Sun, 17 Sep 2000 15:10:32 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8HMAMk93586; Mon, 18 Sep 2000 07:40:22 +0930 (CST) (envelope-from grog) Date: Mon, 18 Sep 2000 07:40:22 +0930 From: Greg Lehey To: Michael Reifenberger Cc: FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io Message-ID: <20000918074021.E67912@wantadilla.lemis.com> References: <20000917102824.C42114@wantadilla.lemis.com> <20000917102824.C42114@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from root@nihil.plaut.de on Sun, Sep 17, 2000 at 04:29:41PM +0200 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 17 September 2000 at 16:29:41 +0200, Michael Reifenberger wrote: > Hi, > ... >> The frames above are what the system went to as the result of your >> debugger request. I'd also be interested to see the output of the >> 'icnt' macro (if this is UP machine) or 'icnt1' (if it's SMP), and >> 'ps' (the macro I promised above). > (kgdb) icnt > 1215544* 566* 0 0* 0 0 1 0 > 1555964* 0* 0* 0* 0 0* 22636* 11 > 1 0 0 0 0 0 441031 > imen: 6f0b > (kgdb) ps > pid proc addr uid pri ppid pgrp flag stat comm wchan > 37 c7874a00 c9665000 0 32 6 36 004086 3 tar piperd c9663f20 > 36 c7874bc0 c960a000 0 32 6 36 004006 3 tar FFS node c02f4220 > 35 c7874d80 c9607000 0 32 6 35 004006 3 tar inode c1d2fa00 > 6 c7874f40 c9604000 0 32 1 6 004086 3 sh wait c7874f40 > 5 c7875100 c8295000 0 4 0 0 000204 3 syncer syncer c03236e8 > 4 c78752c0 c8293000 0 4 0 0 100204 3 bufdaemon psleep c03072f0 > 3 c7875480 c8291000 0 4 0 0 000204 3 vmdaemon psleep c0317a00 > 2 c7875640 c828f000 0 4 0 0 100204 3 pagedaemon psleep c02f5938 > 21 c7875800 c78d4000 0 1* 0 0 000204 2 irq8: rtc > 20 c78759c0 c78d2000 0 1* 0 0 000204 2 irq0: clk > 19 c7875b80 c78b0000 0 7* 0 0 000204 6 irq5: pcm0 > 18 c7875d40 c788e000 0 7* 0 0 000204 6 irq7: ppc0 > 17 c7875f00 c788c000 0 7* 0 0 000204 6 irq12: psm0 > 16 c78760c0 c788a000 0 7* 0 0 000204 2 irq1: atkbd0 > 15 c7876280 c7887000 0 6* 0 0 000204 6 irq6: fdc0 > 14 c7876440 c7885000 0 6* 0 0 000204 6 irq15: ata1 > 13 c7876600 c7883000 0 6* 0 0 000204 2 irq14: ata0 > 12 c78767c0 c7881000 0 4 0 0 000204 3 random rndslp c0322934 > 11 c7876980 c787f000 0 15* 0 0 008204 6 softinterrupt > 10 c7876b40 c787d000 0 4 0 0 008204 2 idle > 1 c7876d00 c787b000 0 4 0 1 004284 3 init wait c7876d00 > 0 c0322960 c03c0000 0 4 0 0 000204 3 swapper sched c0322960 > ... >> handler. At this point, it would be very interesting to see the value >> of p->p_comm, which is the process name at the end of the ps listing. >> >>> (kgdb) proc 35 >> >> Why are you interested in this process? > It was one of the tar's which I grabbed by hand (without your ps macro) > ... > > Whats next to show :-) To quote: >> At this point, it would be very interesting to see the value of >> p->p_comm, which is the process name at the end of the ps listing. You could also show the content of p->p_pid. If you don't have a p pointer in the frame you're looking at, use ((struct *proc)gd_curproc)->p_pid and ((struct *proc)gd_curproc)->p_comm. We need to know what is hanging. I'm probably going on holiday for the rest of the week; somebody else should pick this one up. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 15:13: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id 6DC5137B422 for ; Sun, 17 Sep 2000 15:12:57 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e8HMC1i55864; Sun, 17 Sep 2000 19:12:01 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 17 Sep 2000 19:12:01 -0300 (ADT) From: The Hermit Hacker To: Steve Kargl Cc: FreeBSD Current Subject: Re: aic7xxx changes break kernel builds In-Reply-To: <200009172215.PAA11090@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Sep 2000, Steve Kargl wrote: > hotrats:root[211] setenv KERNEL HOTRATS > hotrats:root[212] make buildkernel > > -------------------------------------------------------------- > >>> Rebuilding kernel(s) > -------------------------------------------------------------- > ===> HOTRATS > mkdir -p /usr/obj/usr/src/sys > cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -r -d /usr/obj/usr/src/sys/HOTRATS HOTRATS > Don't forget to do a ``make depend'' > Kernel build directory is /usr/obj/usr/src/sys/HOTRATS > cd /usr/obj/usr/src/sys/HOTRATS; MAKESRCPATH=/usr/src/sys/dev/aic7xxx make -f /usr/src/sys/dev/aic7xxx/Makefile > make: cannot open /usr/src/sys/dev/aic7xxx/Makefile. > *** Error code 2 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > > It has been this way since last night 10pm PST. Anyone > have a tip on generating the missing Makefile? I hit the same, went into /sys/i386/conf and ran 'config' and built the kernel "the old fashioned way", and it went through perfectly ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 15:24: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id D06E037B422; Sun, 17 Sep 2000 15:23:56 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id AAA02625; Mon, 18 Sep 2000 00:23:36 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.0/8.8.8) with ESMTP id e8HNNZr01576; Mon, 18 Sep 2000 01:23:35 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Mon, 18 Sep 2000 01:23:30 +0200 (CEST) From: Michael Reifenberger To: Greg Lehey Cc: FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io In-Reply-To: <20000918074021.E67912@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Sep 2000, Greg Lehey wrote: ... > You could also show the content of p->p_pid. If you don't have a p > pointer in the frame you're looking at, use ((struct > *proc)gd_curproc)->p_pid and ((struct *proc)gd_curproc)->p_comm. We > need to know what is hanging. Sorry doesn't seem to work: (kgdb) p p->p_comm No symbol "p" in current context. (kgdb) p ((struct*proc)gd_curproc)->p_pid A syntax error in expression, near `proc)gd_curproc)->p_pid'. (kgdb) p ((struct *proc)gd_curproc)->p_comm A syntax error in expression, near `proc)gd_curproc)->p_comm'. (kgdb) p gd_curproc $1 = 0xc78760c0 Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 15:25:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7A55B37B422; Sun, 17 Sep 2000 15:25:26 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8HMPI000981; Mon, 18 Sep 2000 07:55:18 +0930 (CST) (envelope-from grog) Date: Mon, 18 Sep 2000 07:55:18 +0930 From: Greg Lehey To: Michael Reifenberger Cc: FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io Message-ID: <20000918075518.H67912@wantadilla.lemis.com> References: <20000918074021.E67912@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from root@nihil.plaut.de on Mon, Sep 18, 2000 at 01:23:30AM +0200 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 18 September 2000 at 1:23:30 +0200, Michael Reifenberger wrote: > On Mon, 18 Sep 2000, Greg Lehey wrote: > ... >> You could also show the content of p->p_pid. If you don't have a p >> pointer in the frame you're looking at, use ((struct >> *proc)gd_curproc)->p_pid and ((struct *proc)gd_curproc)->p_comm. We >> need to know what is hanging. > Sorry doesn't seem to work: > (kgdb) p p->p_comm > No symbol "p" in current context. > (kgdb) p ((struct*proc)gd_curproc)->p_pid > A syntax error in expression, near `proc)gd_curproc)->p_pid'. > (kgdb) p ((struct *proc)gd_curproc)->p_comm > A syntax error in expression, near `proc)gd_curproc)->p_comm'. > (kgdb) p gd_curproc > $1 = 0xc78760c0 Oops, that's what comes of typing hurriedly early in the morning. p ((struct proc *)gd_curproc)->p_comm p ((struct proc *)gd_curproc)->p_pid Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 15:29:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id 7D8DA37B42C; Sun, 17 Sep 2000 15:29:53 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id AAA02659; Mon, 18 Sep 2000 00:29:34 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.0/8.8.8) with ESMTP id e8HNTZO01607; Mon, 18 Sep 2000 01:29:35 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Mon, 18 Sep 2000 01:29:34 +0200 (CEST) From: Michael Reifenberger To: Greg Lehey Cc: FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io In-Reply-To: <20000918075518.H67912@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Sep 2000, Greg Lehey wrote: ... > Oops, that's what comes of typing hurriedly early in the morning. > > p ((struct proc *)gd_curproc)->p_comm > p ((struct proc *)gd_curproc)->p_pid Works better: (kgdb) p ((struct proc *)gd_curproc)->p_comm $6 = "irq1: atkbd0\000\000\000\000" (kgdb) p ((struct proc *)gd_curproc)->p_pid $7 = 0x10 Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 15:36:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 7C81F37B424; Sun, 17 Sep 2000 15:36:10 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8HMZxs06146; Mon, 18 Sep 2000 08:05:59 +0930 (CST) (envelope-from grog) Date: Mon, 18 Sep 2000 08:05:59 +0930 From: Greg Lehey To: Michael Reifenberger Cc: FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io Message-ID: <20000918080559.J67912@wantadilla.lemis.com> References: <20000918075518.H67912@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from root@nihil.plaut.de on Mon, Sep 18, 2000 at 01:29:34AM +0200 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 18 September 2000 at 1:29:34 +0200, Michael Reifenberger wrote: > On Mon, 18 Sep 2000, Greg Lehey wrote: > ... >> Oops, that's what comes of typing hurriedly early in the morning. >> >> p ((struct proc *)gd_curproc)->p_comm >> p ((struct proc *)gd_curproc)->p_pid > Works better: > (kgdb) p ((struct proc *)gd_curproc)->p_comm > $6 = "irq1: atkbd0\000\000\000\000" > (kgdb) p ((struct proc *)gd_curproc)->p_pid > $7 = 0x10 Hmm. I suppose that's reasonable, since you've just pressed a key. We obviously have a problem here, but I'm not going to be able to look at it myself until Friday or Saturday. Anybody else want to take a look? There's also the possibility that a problem I had seen and not investigated could in fact be the same problem: I got it tarring and untarring across an NFS connection. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 18:45:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 075D137B422; Sun, 17 Sep 2000 18:45:38 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id SAA52872; Sun, 17 Sep 2000 18:44:39 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009180144.SAA52872@pike.osd.bsdi.com> Subject: Re: Debugging -current SMPNG HANG on heavy disk-io In-Reply-To: <20000918080559.J67912@wantadilla.lemis.com> from Greg Lehey at "Sep 18, 2000 08:05:59 am" To: Greg Lehey Date: Sun, 17 Sep 2000 18:44:39 -0700 (PDT) Cc: Michael Reifenberger , FreeBSD-Current , FreeBSD-SMP X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Monday, 18 September 2000 at 1:29:34 +0200, Michael Reifenberger wrote: > > On Mon, 18 Sep 2000, Greg Lehey wrote: > > ... > >> Oops, that's what comes of typing hurriedly early in the morning. > >> > >> p ((struct proc *)gd_curproc)->p_comm > >> p ((struct proc *)gd_curproc)->p_pid > > Works better: > > (kgdb) p ((struct proc *)gd_curproc)->p_comm > > $6 = "irq1: atkbd0\000\000\000\000" > > (kgdb) p ((struct proc *)gd_curproc)->p_pid > > $7 = 0x10 > > Hmm. I suppose that's reasonable, since you've just pressed a key. > > We obviously have a problem here, but I'm not going to be able to look > at it myself until Friday or Saturday. Anybody else want to take a > look? There's also the possibility that a problem I had seen and not > investigated could in fact be the same problem: I got it tarring and > untarring across an NFS connection. Hmm, could it be lockmgr() related? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "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 Sun Sep 17 19: 4:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 22AD437B424 for ; Sun, 17 Sep 2000 19:04:37 -0700 (PDT) Received: (qmail 51200 invoked by uid 1142); 18 Sep 2000 02:04:32 -0000 Date: 17 Sep 2000 19:04:32 -0700 Date: Sun, 17 Sep 2000 19:04:23 -0700 From: Jason Evans To: Konstantin Chuguev Cc: Udo Schweigert , freebsd-current@FreeBSD.ORG Subject: Re: ssh and scp fail connecting to a root account Message-ID: <20000917190423.A28269@canonware.com> References: <20000915163344.A79462@alaska.cert.siemens.de> <39C234CC.668195B@dante.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39C234CC.668195B@dante.org.uk>; from Konstantin.Chuguev@dante.org.uk on Fri, Sep 15, 2000 at 03:40:12PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 15, 2000 at 03:40:12PM +0100, Konstantin Chuguev wrote: > Udo Schweigert wrote: > > > after a fresh build of -current openssh does not work if connecting to the > > root-user. For example (tested from a -stable machine, but the same from > > 4.1-RELEASE): > > Yes, I've been seeing the same thing since the checkout of the SMPng stuff... > No idea why it's happening. I've seen similar things intermittently over the past 10 days, and specifically the same problem for the past three days or so. I'm pretty sure that the problems have been associated with the random device rather than the SMP work specifically. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 19: 7: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id CD56E37B422; Sun, 17 Sep 2000 19:06:58 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id TAA24987; Sun, 17 Sep 2000 19:06:58 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 17 Sep 2000 19:06:58 -0700 (PDT) From: Kris Kennaway To: Jason Evans Cc: Konstantin Chuguev , Udo Schweigert , freebsd-current@FreeBSD.ORG Subject: Re: ssh and scp fail connecting to a root account In-Reply-To: <20000917190423.A28269@canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Sep 2000, Jason Evans wrote: > On Fri, Sep 15, 2000 at 03:40:12PM +0100, Konstantin Chuguev wrote: > > Udo Schweigert wrote: > > > > > after a fresh build of -current openssh does not work if connecting to the > > > root-user. For example (tested from a -stable machine, but the same from > > > 4.1-RELEASE): > > > > Yes, I've been seeing the same thing since the checkout of the SMPng stuff... > > No idea why it's happening. > > I've seen similar things intermittently over the past 10 days, and > specifically the same problem for the past three days or so. I'm pretty > sure that the problems have been associated with the random device rather > than the SMP work specifically. Well, the crash is apparently due to malloc flags - remove the /etc/malloc.conf link and it may work better. I've only seen this once, and when I tried to run sshd under gdb it went away, and now I can't reproduce it again. :-( Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 19:15:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id E47A337B423 for ; Sun, 17 Sep 2000 19:15:42 -0700 (PDT) Received: (qmail 23498 invoked by uid 0); 18 Sep 2000 02:15:41 -0000 Received: from p3ee21667.dip.t-dialin.net (HELO speedy.gsinet) (62.226.22.103) by mail.gmx.net with SMTP; 18 Sep 2000 02:15:41 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id WAA00728 for current@FreeBSD.ORG; Sun, 17 Sep 2000 22:17:59 +0200 Date: Sun, 17 Sep 2000 22:17:59 +0200 From: Gerhard Sittig To: current@FreeBSD.ORG Subject: Re: superduperopen(3) (was: Fdescfs updates--coming to a devfs near you!) Message-ID: <20000917221759.B187@speedy.gsinet> Mail-Followup-To: current@FreeBSD.ORG References: <200009160249.e8G2n3n02415@hak.lan.Awfulhak.org> <20000916100447.I27034@speedy.gsinet> <20000917203616.B11424@dataloss.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000917203616.B11424@dataloss.net>; from peter@dataloss.net on Sun, Sep 17, 2000 at 08:36:16PM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 17, 2000 at 20:36 +0200, Peter van Dijk wrote: > On Sat, Sep 16, 2000 at 10:04:47AM +0200, Gerhard Sittig wrote: > > > > > > [ ... how to find separating chars not used in filenames ... ] > > > > e.g. > > superduperopen("file1&file2", "a+", SDO_TEEFILES) > > superduperopen("file1&file2", "r" , SDO_SELECT) > > FILE *superduperopen(char *files[], char *type, int flags); Of course it would be the cleanest thing to do, and I was aware of this possibility. But that's when the interface is _very_ much different from fopen(3). That's where I'm reluctant to introduce this hard a change. :) In addition it was not quite clear how appropriate this semantics would be, at all. Unless one sees this (yet to be renamed accordingly:) function as something very different from fopen and "easy adaption of existing utilities" is not so much of a concern, I still hesitate to put this much more burdon on the programmer: opening single files like fopen(3) did before would now mean to handle a "list of one filenames" instead of passing whatever was there before -- just to have the lib handle stdin recognition. I could suggest something even more ugly than the above "x&y" for those who want easy adaption: superduperopen(char *fn, char *mode, int flags, ...); with the \dots being zero or more filenames, only evaluated when the flags suggest to do so. But it tears the first and any other filename apart. The other solution was to provide two functions: one fopen like plus the flags for when only one filename is needed and another with a filename list, mode, and flags; being the first a wrapper for the second (much as IPC::Open2 and IPC::Open3 are). This would allow for a simple fixsized two element array handled in the wrapper without the app's need to care about anything more but the SDO_ flags for STD in the existing cases we mainly talk about (cat(1) and the like). After all I'm still not sure how useful this kind of extension would be. It all started out with the wish for knowing "-" and "|cmd" / "cmd|" where an interface like superduperopen(char *fn, char *mode, int flags); is sufficient. > [snip] > > parameters) have to pass certain checks. Nobody should try > > to read from "|command". And I cannot see any use for "write > > to whatever descriptor is ready to write to first" as would > > result from "w" and SDO_SELECT. > > But they should be able to read from "command|", ofcourse. That > feature should be in there too :) That's obvious (isn't it?). But there are definitely combinations which aren't really useful. And some even shouldn't be allowed at all. Which brings me to a completely different topic: How much sense does it make being able to read(2) directories? Shouldn't be other functions (like stat, chdir, opendir & friends) sufficient and shouldn't read fail with EISDIR or something similar? I've been bitten quite often from the garbled output of "head *" with damaged terminal fonts afterwards. I know Linux had this before but has been fixed for several years now. I'm aware this could be a religious topic, but I feel it should have been discussed before. It's just that I think searching for "read" or "directory" in the list's archive is not very useful. Where can I find more information on the reasons to still allow for this misfeature (it's how I judge this short of knowing any advantages). > I do see a use to "write to whatever descriptor is ready > first". It could be used for a very simple multithreading-like > implementation. Spawn 8 child processes, attach them to one > stream with superduperopen(), and pass single-byte commands to > one that is waiting to handle one. Yes, but the same restriction as to "read from whatever is ready first" apply: The type of data has to be "fixed size and without problems splittable" or "not really produced in parallel but more alternatively" as one byte commands are or keystrokes could be. That's where I see only limited use for these. It heavily depends on the applications' environments. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Sep 17 20: 5:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41]) by hub.freebsd.org (Postfix) with ESMTP id 3EB5437B422 for ; Sun, 17 Sep 2000 20:05:33 -0700 (PDT) Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net) by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7) id 13arFM-0001IU-00; Mon, 18 Sep 2000 03:05:32 +0000 Received: from [204.1.90.43] (helo=power) by dfw-mmp4.email.verio.net with smtp (Exim 3.15 #4) id 13arFM-0005ih-00; Mon, 18 Sep 2000 03:05:32 +0000 From: "Tony Johnson" To: "Gerhard Sittig" , Subject: RE: superduperopen(3) (was: Fdescfs updates--coming to a devfs near you!) Date: Sun, 17 Sep 2000 22:05:31 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20000917221759.B187@speedy.gsinet> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think this thread needs to be killed. Whipping a horse that was dead 3 days ago is way too much. People have expressed thier opposition to PHK's post and so it should end there. For the love of cgi scripts, please keep /dev/stdin && out so that peoples web work can be sent to && from the masses. This is posted on NetBSD's web page, "Solutions and not hacks" Stop trying to hack up a broken idea in order to kinda-sorta make it work and produce a "Solution" -----Original Message----- From: owner-freebsd-current@FreeBSD.ORG [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Gerhard Sittig Sent: Sunday, September 17, 2000 3:18 PM To: current@FreeBSD.ORG Subject: Re: superduperopen(3) (was: Fdescfs updates--coming to a devfs near you!) On Sun, Sep 17, 2000 at 20:36 +0200, Peter van Dijk wrote: > On Sat, Sep 16, 2000 at 10:04:47AM +0200, Gerhard Sittig wrote: > > > > > > [ ... how to find separating chars not used in filenames ... ] > > > > e.g. > > superduperopen("file1&file2", "a+", SDO_TEEFILES) > > superduperopen("file1&file2", "r" , SDO_SELECT) > > FILE *superduperopen(char *files[], char *type, int flags); Of course it would be the cleanest thing to do, and I was aware of this possibility. But that's when the interface is _very_ much different from fopen(3). That's where I'm reluctant to introduce this hard a change. :) In addition it was not quite clear how appropriate this semantics would be, at all. Unless one sees this (yet to be renamed accordingly:) function as something very different from fopen and "easy adaption of existing utilities" is not so much of a concern, I still hesitate to put this much more burdon on the programmer: opening single files like fopen(3) did before would now mean to handle a "list of one filenames" instead of passing whatever was there before -- just to have the lib handle stdin recognition. I could suggest something even more ugly than the above "x&y" for those who want easy adaption: superduperopen(char *fn, char *mode, int flags, ...); with the \dots being zero or more filenames, only evaluated when the flags suggest to do so. But it tears the first and any other filename apart. The other solution was to provide two functions: one fopen like plus the flags for when only one filename is needed and another with a filename list, mode, and flags; being the first a wrapper for the second (much as IPC::Open2 and IPC::Open3 are). This would allow for a simple fixsized two element array handled in the wrapper without the app's need to care about anything more but the SDO_ flags for STD in the existing cases we mainly talk about (cat(1) and the like). After all I'm still not sure how useful this kind of extension would be. It all started out with the wish for knowing "-" and "|cmd" / "cmd|" where an interface like superduperopen(char *fn, char *mode, int flags); is sufficient. > [snip] > > parameters) have to pass certain checks. Nobody should try > > to read from "|command". And I cannot see any use for "write > > to whatever descriptor is ready to write to first" as would > > result from "w" and SDO_SELECT. > > But they should be able to read from "command|", ofcourse. That > feature should be in there too :) That's obvious (isn't it?). But there are definitely combinations which aren't really useful. And some even shouldn't be allowed at all. Which brings me to a completely different topic: How much sense does it make being able to read(2) directories? Shouldn't be other functions (like stat, chdir, opendir & friends) sufficient and shouldn't read fail with EISDIR or something similar? I've been bitten quite often from the garbled output of "head *" with damaged terminal fonts afterwards. I know Linux had this before but has been fixed for several years now. I'm aware this could be a religious topic, but I feel it should have been discussed before. It's just that I think searching for "read" or "directory" in the list's archive is not very useful. Where can I find more information on the reasons to still allow for this misfeature (it's how I judge this short of knowing any advantages). > I do see a use to "write to whatever descriptor is ready > first". It could be used for a very simple multithreading-like > implementation. Spawn 8 child processes, attach them to one > stream with superduperopen(), and pass single-byte commands to > one that is waiting to handle one. Yes, but the same restriction as to "read from whatever is ready first" apply: The type of data has to be "fixed size and without problems splittable" or "not really produced in parallel but more alternatively" as one byte commands are or keystrokes could be. That's where I see only limited use for these. It heavily depends on the applications' environments. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. 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 Sep 17 21: 5:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id D130A37B422 for ; Sun, 17 Sep 2000 21:05:12 -0700 (PDT) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA62095 for ; Sun, 17 Sep 2000 21:05:12 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39C59477.D02978BD@gorean.org> Date: Sun, 17 Sep 2000 21:05:11 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-091 i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Can't build a kernel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I use the buildkernel target I get the following: make: cannot open /usr/amd/realmounts/slave/usr/current/src/sys/dev/aic7xxx/Makefile. *** Error code 2 Stop in /usr/amd/realmounts/slave/usr/current/src. *** Error code 1 If I use the old way, I get errors about a pointer with an incomplete type in aac (whatever that is). Doug -- "The dead cannot be seduced." - Kai, "Lexx" 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 Sep 18 1: 3:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.66]) by hub.freebsd.org (Postfix) with ESMTP id 9BC2B37B423 for ; Mon, 18 Sep 2000 01:03:05 -0700 (PDT) Received: from jarrow.dev.nanoteq.co.za (jarrow [196.37.91.33]) by oskar.nanoteq.co.za (8.9.3/8.9.0) with ESMTP id KAA06334; Mon, 18 Sep 2000 10:04:49 +0200 (SAT) 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: <19651.969165128@coconut.itojun.org> Date: Mon, 18 Sep 2000 10:00:53 +0200 (SAST) Reply-To: rbezuide@oskar.nanoteq.co.za From: Reinier Bezuidenhout To: itojun@iijlab.net Subject: Re: (KAME-snap 3327) Re: Panic on current (12 Sept) Cc: freebsd-current@FreeBSD.ORG, snap-users@kame.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As far as I recall ... the first kernel was before any of the SMP commits ... but in case it was not ... how do I go about going back to a "coarse grain lock" kernel ... can I set something in the config file or do I have to checkout old sources ?? Reinier On 17-Sep-00 itojun@iijlab.net wrote: > >>> I'm running a current machine of 12 Sept although this problem >>> also occured on a current of a few days earlier ... > > "current machine" meaning FreeBSD-current? if so, are there any > locking behavior changes due to the introduction of fine grain locks? > what happens if you go back to coarse grain lock kernel? > > itojun > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ################################################################### # # # R.N. Bezuidenhout NetSeq Firewall # # rbezuide@oskar.nanoteq.co.za http://www.nanoteq.co.za # # # ################################################################### ---------------------------------- Date: 18-Sep-00 Time: 09:59:11 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 1: 6:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id 740E937B440; Mon, 18 Sep 2000 01:06:53 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id KAA05062; Mon, 18 Sep 2000 10:06:01 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.0/8.8.8) with ESMTP id e8I93No00378; Mon, 18 Sep 2000 11:03:23 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Mon, 18 Sep 2000 11:03:17 +0200 (CEST) From: Michael Reifenberger To: John Baldwin Cc: Greg Lehey , FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io In-Reply-To: <200009180144.SAA52872@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Sep 2000, John Baldwin wrote: ... > Hmm, could it be lockmgr() related? How can I proof? Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 1: 9:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from oskar.nanoteq.co.za (oskar.nanoteq.co.za [196.37.91.66]) by hub.freebsd.org (Postfix) with ESMTP id 18C8837B423 for ; Mon, 18 Sep 2000 01:08:45 -0700 (PDT) Received: from jarrow.dev.nanoteq.co.za (jarrow [196.37.91.33]) by oskar.nanoteq.co.za (8.9.3/8.9.0) with ESMTP id KAA06384; Mon, 18 Sep 2000 10:09:49 +0200 (SAT) 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: <20000916202011C.sakane@ydc.co.jp> Date: Mon, 18 Sep 2000 10:05:53 +0200 (SAST) Reply-To: rbezuide@oskar.nanoteq.co.za From: Reinier Bezuidenhout To: snap-users@kame.net Subject: RE: (KAME-snap 3327) Re: Panic on current (12 Sept) Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... Without starting the racoon daemon and doing a secure connect everything works fine without a problem. If I start racoon, do a tunnel connection and then run daily, the machine panics .. Reinier On 16-Sep-00 Shoichi 'Ne' Sakane wrote: >> I'm running a current machine of 12 Sept although this problem >> also occured on a current of a few days earlier ... >> >> This only happens when using the IPv6 IPSec code during the day, >> it is readily reproduceable. >> >> If during the day I load the racoon daemon and load keys and >> establish a IPSec tunnel connection everything works fine till >> 2:00 am when the daily script runs OR if I run the daily script >> by hand ... I generated the following dump and backtrace ... >> >> It seems to crash in a makedev routine using FOREACH list macro's. >> >> The problem doesn't seem to be with the list or the makedev function >> in kern_conf.c. It seems to me that something in the kernel >> corrupts the static list dev_hash when using the IPSec code. >> >> Summary - when ising IPSec ... machine panics during daily >> script execution. > > I think IPsec is not relative to this issue. To make sure, > does your machine run healthy without IPsec ? > Please try the following. > case 1) with option IPSEC, but no SPD entry. > case 2) without option IPSEC ################################################################### # # # R.N. Bezuidenhout NetSeq Firewall # # rbezuide@oskar.nanoteq.co.za http://www.nanoteq.co.za # # # ################################################################### ---------------------------------- Date: 18-Sep-00 Time: 10:04:59 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 3:17: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from worldclass.jolt.nu (lgh637b.hn-krukan.AC [212.217.139.112]) by hub.freebsd.org (Postfix) with ESMTP id C56F537B422 for ; Mon, 18 Sep 2000 03:16:50 -0700 (PDT) Received: from localhost (root@localhost) by worldclass.jolt.nu (8.11.0/8.11.0) with ESMTP id e8ICGHx41221 for ; Mon, 18 Sep 2000 12:16:18 GMT (envelope-from root@worldclass.jolt.nu) Date: Mon, 18 Sep 2000 12:16:15 +0000 (GMT) From: Administrator To: freebsd-current@freebsd.org Subject: make world fails errors in libedit? Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-83113638-969279375=:41209" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-83113638-969279375=:41209 Content-Type: TEXT/PLAIN; charset=US-ASCII Updated around 3 am (CET) and tryed to build the world but if fails miserably on libedit. --0-83113638-969279375=:41209 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="make.world.output" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="make.world.output" U2NyaXB0IHN0YXJ0ZWQgb24gTW9uIFNlcCAxOCAwNjoxODo0OCAyMDAwDQoo cm9vdEB3b3JsZGNsYXNzOi91c3Ivc3JjKSBtYWtlIHdvcmxkDQ0KLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0NDQo+Pj4gZWxmIG1ha2Ugd29ybGQgc3RhcnRlZCBvbiBN b24gU2VwIDE4IDA2OjE4OjUyIEdNVCAyMDAwDQ0KLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0NDQoNDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0NCj4+PiBSZWJ1aWxkaW5nIHRo ZSB0ZW1wb3JhcnkgYnVpbGQgdHJlZQ0NCi0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQ0K cm0gLXJmIC91c3Ivb2JqL3Vzci9zcmMvaTM4Ng0NCi4uLi4NCi4uLi4NCj09 PT4gbGliZWRpdA0NCmNjIC1PMiAtcGlwZSAtSS4gLUkvdXNyL3NyYy9saWIv bGliZWRpdCAgIC1JL3Vzci9vYmovdXNyL3NyYy9pMzg2L3Vzci9pbmNsdWRl IC1jIGVkaXRsaW5lLmMgLW8gZWRpdGxpbmUubw0NCkluIGZpbGUgaW5jbHVk ZWQgZnJvbSAvdXNyL3NyYy9saWIvbGliZWRpdC9jaGFyZWQuaDoxMzAsDQ0K ICAgICAgICAgICAgICAgICBmcm9tIC91c3Ivc3JjL2xpYi9saWJlZGl0L2Vs Lmg6OTcsDQ0KICAgICAgICAgICAgICAgICBmcm9tIC91c3Ivc3JjL2xpYi9s aWJlZGl0L2NoYXJlZC5jOjQ3LA0NCiAgICAgICAgICAgICAgICAgZnJvbSBl ZGl0bGluZS5jOjQ6DQ0KY29tbW9uLmg6Mjogd2FybmluZzogZ2FyYmFnZSBh dCBlbmQgb2YgYCNpZm5kZWYnIGFyZ3VtZW50DQ0KY29tbW9uLmg6Mzogd2Fy bmluZzogbWlzc2luZyB3aGl0ZSBzcGFjZSBhZnRlciBgI2RlZmluZSBfaF8n DQ0KSW4gZmlsZSBpbmNsdWRlZCBmcm9tIC91c3Ivc3JjL2xpYi9saWJlZGl0 L2NoYXJlZC5oOjEzMSwNDQogICAgICAgICAgICAgICAgIGZyb20gL3Vzci9z cmMvbGliL2xpYmVkaXQvZWwuaDo5NywNDQogICAgICAgICAgICAgICAgIGZy b20gL3Vzci9zcmMvbGliL2xpYmVkaXQvY2hhcmVkLmM6NDcsDQ0KICAgICAg ICAgICAgICAgICBmcm9tIGVkaXRsaW5lLmM6NDoNDQp2aS5oOjI6IHdhcm5p bmc6IGdhcmJhZ2UgYXQgZW5kIG9mIGAjaWZuZGVmJyBhcmd1bWVudA0NCklu IGZpbGUgaW5jbHVkZWQgZnJvbSAvdXNyL3NyYy9saWIvbGliZWRpdC9jaGFy ZWQuaDoxMzIsDQ0KICAgICAgICAgICAgICAgICBmcm9tIC91c3Ivc3JjL2xp Yi9saWJlZGl0L2VsLmg6OTcsDQ0KICAgICAgICAgICAgICAgICBmcm9tIC91 c3Ivc3JjL2xpYi9saWJlZGl0L2NoYXJlZC5jOjQ3LA0NCiAgICAgICAgICAg ICAgICAgZnJvbSBlZGl0bGluZS5jOjQ6DQ0KZW1hY3MuaDoyOiB3YXJuaW5n OiBnYXJiYWdlIGF0IGVuZCBvZiBgI2lmbmRlZicgYXJndW1lbnQNDQpJbiBm aWxlIGluY2x1ZGVkIGZyb20gZWRpdGxpbmUuYzo4Og0NCmZjbnMuYzozMjog YHZpX2FkZCcgdW5kZWNsYXJlZCBoZXJlIChub3QgaW4gYSBmdW5jdGlvbikN DQpmY25zLmM6MzI6IGluaXRpYWxpemVyIGVsZW1lbnQgaXMgbm90IGNvbnN0 YW50DQ0KZmNucy5jOjMyOiAobmVhciBpbml0aWFsaXphdGlvbiBmb3IgYGVs X2Z1bmNbNTRdJykNDQpmY25zLmM6MzI6IGB2aV9hZGRfYXRfZW9sJyB1bmRl Y2xhcmVkIGhlcmUgKG5vdCBpbiBhIGZ1bmN0aW9uKQ0NCmZjbnMuYzozMjog aW5pdGlhbGl6ZXIgZWxlbWVudCBpcyBub3QgY29uc3RhbnQNDQpmY25zLmM6 MzI6IChuZWFyIGluaXRpYWxpemF0aW9uIGZvciBgZWxfZnVuY1s1NV0nKQ0N CmZjbnMuYzozMzogYHZpX2NoYW5nZV9jYXNlJyB1bmRlY2xhcmVkIGhlcmUg KG5vdCBpbiBhIGZ1bmN0aW9uKQ0NCmZjbnMuYzozMzogaW5pdGlhbGl6ZXIg ZWxlbWVudCBpcyBub3QgY29uc3RhbnQNDQpmY25zLmM6MzM6IChuZWFyIGlu aXRpYWxpemF0aW9uIGZvciBgZWxfZnVuY1s1Nl0nKQ0NCmZjbnMuYzozMzog YHZpX2NoYW5nZV9tZXRhJyB1bmRlY2xhcmVkIGhlcmUgKG5vdCBpbiBhIGZ1 bmN0aW9uKQ0NCmZjbnMuYzozMzogaW5pdGlhbGl6ZXIgZWxlbWVudCBpcyBu b3QgY29uc3RhbnQNDQpmY25zLmM6MzM6IChuZWFyIGluaXRpYWxpemF0aW9u IGZvciBgZWxfZnVuY1s1N10nKQ0NCmZjbnMuYzozNDogYHZpX2NoYW5nZV90 b19lb2wnIHVuZGVjbGFyZWQgaGVyZSAobm90IGluIGEgZnVuY3Rpb24pDQ0K ZmNucy5jOjM0OiBpbml0aWFsaXplciBlbGVtZW50IGlzIG5vdCBjb25zdGFu dA0NCmZjbnMuYzozNDogKG5lYXIgaW5pdGlhbGl6YXRpb24gZm9yIGBlbF9m dW5jWzU4XScpDQ0KZmNucy5jOjM0OiBgdmlfY29tbWFuZF9tb2RlJyB1bmRl Y2xhcmVkIGhlcmUgKG5vdCBpbiBhIGZ1bmN0aW9uKQ0NCmZjbnMuYzozNDog aW5pdGlhbGl6ZXIgZWxlbWVudCBpcyBub3QgY29uc3RhbnQNDQpmY25zLmM6 MzQ6IChuZWFyIGluaXRpYWxpemF0aW9uIGZvciBgZWxfZnVuY1s1OV0nKQ0N CmZjbnMuYzozNTogYHZpX2RlbGV0ZV9tZXRhJyB1bmRlY2xhcmVkIGhlcmUg KG5vdCBpbiBhIGZ1bmN0aW9uKQ0NCmZjbnMuYzozNTogaW5pdGlhbGl6ZXIg ZWxlbWVudCBpcyBub3QgY29uc3RhbnQNDQpmY25zLmM6MzU6IChuZWFyIGlu aXRpYWxpemF0aW9uIGZvciBgZWxfZnVuY1s2MF0nKQ0NCmZjbnMuYzozNTog YHZpX2RlbGV0ZV9wcmV2X2NoYXInIHVuZGVjbGFyZWQgaGVyZSAobm90IGlu IGEgZnVuY3Rpb24pDQ0KZmNucy5jOjM1OiBpbml0aWFsaXplciBlbGVtZW50 IGlzIG5vdCBjb25zdGFudA0NCmZjbnMuYzozNTogKG5lYXIgaW5pdGlhbGl6 YXRpb24gZm9yIGBlbF9mdW5jWzYxXScpDQ0KZmNucy5jOjM2OiBgdmlfZW5k X3dvcmQnIHVuZGVjbGFyZWQgaGVyZSAobm90IGluIGEgZnVuY3Rpb24pDQ0K ZmNucy5jOjM2OiBpbml0aWFsaXplciBlbGVtZW50IGlzIG5vdCBjb25zdGFu dA0NCmZjbnMuYzozNjogKG5lYXIgaW5pdGlhbGl6YXRpb24gZm9yIGBlbF9m dW5jWzYyXScpDQ0KZmNucy5jOjM2OiBgdmlfaW5zZXJ0JyB1bmRlY2xhcmVk IGhlcmUgKG5vdCBpbiBhIGZ1bmN0aW9uKQ0NCmZjbnMuYzozNjogaW5pdGlh bGl6ZXIgZWxlbWVudCBpcyBub3QgY29uc3RhbnQNDQpmY25zLmM6MzY6IChu ZWFyIGluaXRpYWxpemF0aW9uIGZvciBgZWxfZnVuY1s2M10nKQ0NCmZjbnMu YzozNzogYHZpX2luc2VydF9hdF9ib2wnIHVuZGVjbGFyZWQgaGVyZSAobm90 IGluIGEgZnVuY3Rpb24pDQ0KZmNucy5jOjM3OiBpbml0aWFsaXplciBlbGVt ZW50IGlzIG5vdCBjb25zdGFudA0NCmZjbnMuYzozNzogKG5lYXIgaW5pdGlh bGl6YXRpb24gZm9yIGBlbF9mdW5jWzY0XScpDQ0KZmNucy5jOjM3OiBgdmlf a2lsbF9saW5lX3ByZXYnIHVuZGVjbGFyZWQgaGVyZSAobm90IGluIGEgZnVu Y3Rpb24pDQ0KZmNucy5jOjM3OiBpbml0aWFsaXplciBlbGVtZW50IGlzIG5v dCBjb25zdGFudA0NCmZjbnMuYzozNzogKG5lYXIgaW5pdGlhbGl6YXRpb24g Zm9yIGBlbF9mdW5jWzY1XScpDQ0KZmNucy5jOjM4OiBgdmlfbGlzdF9vcl9l b2YnIHVuZGVjbGFyZWQgaGVyZSAobm90IGluIGEgZnVuY3Rpb24pDQ0KZmNu cy5jOjM4OiBpbml0aWFsaXplciBlbGVtZW50IGlzIG5vdCBjb25zdGFudA0N CmZjbnMuYzozODogKG5lYXIgaW5pdGlhbGl6YXRpb24gZm9yIGBlbF9mdW5j WzY2XScpDQ0KZmNucy5jOjM4OiBgdmlfbmV4dF9jaGFyJyB1bmRlY2xhcmVk IGhlcmUgKG5vdCBpbiBhIGZ1bmN0aW9uKQ0NCmZjbnMuYzozODogaW5pdGlh bGl6ZXIgZWxlbWVudCBpcyBub3QgY29uc3RhbnQNDQpmY25zLmM6Mzg6IChu ZWFyIGluaXRpYWxpemF0aW9uIGZvciBgZWxfZnVuY1s2N10nKQ0NCmZjbnMu YzozOTogYHZpX25leHRfc3BhY2Vfd29yZCcgdW5kZWNsYXJlZCBoZXJlIChu b3QgaW4gYSBmdW5jdGlvbikNDQpmY25zLmM6Mzk6IGluaXRpYWxpemVyIGVs ZW1lbnQgaXMgbm90IGNvbnN0YW50DQ0KZmNucy5jOjM5OiAobmVhciBpbml0 aWFsaXphdGlvbiBmb3IgYGVsX2Z1bmNbNjhdJykNDQpmY25zLmM6Mzk6IGB2 aV9uZXh0X3dvcmQnIHVuZGVjbGFyZWQgaGVyZSAobm90IGluIGEgZnVuY3Rp b24pDQ0KZmNucy5jOjM5OiBpbml0aWFsaXplciBlbGVtZW50IGlzIG5vdCBj b25zdGFudA0NCmZjbnMuYzozOTogKG5lYXIgaW5pdGlhbGl6YXRpb24gZm9y IGBlbF9mdW5jWzY5XScpDQ0KZmNucy5jOjQwOiBgdmlfcGFzdGVfbmV4dCcg dW5kZWNsYXJlZCBoZXJlIChub3QgaW4gYSBmdW5jdGlvbikNDQpmY25zLmM6 NDA6IGluaXRpYWxpemVyIGVsZW1lbnQgaXMgbm90IGNvbnN0YW50DQ0KZmNu cy5jOjQwOiAobmVhciBpbml0aWFsaXphdGlvbiBmb3IgYGVsX2Z1bmNbNzBd JykNDQpmY25zLmM6NDA6IGB2aV9wYXN0ZV9wcmV2JyB1bmRlY2xhcmVkIGhl cmUgKG5vdCBpbiBhIGZ1bmN0aW9uKQ0NCmZjbnMuYzo0MDogaW5pdGlhbGl6 ZXIgZWxlbWVudCBpcyBub3QgY29uc3RhbnQNDQpmY25zLmM6NDA6IChuZWFy IGluaXRpYWxpemF0aW9uIGZvciBgZWxfZnVuY1s3MV0nKQ0NCmZjbnMuYzo0 MTogYHZpX3ByZXZfY2hhcicgdW5kZWNsYXJlZCBoZXJlIChub3QgaW4gYSBm dW5jdGlvbikNDQpmY25zLmM6NDE6IGluaXRpYWxpemVyIGVsZW1lbnQgaXMg bm90IGNvbnN0YW50DQ0KZmNucy5jOjQxOiAobmVhciBpbml0aWFsaXphdGlv biBmb3IgYGVsX2Z1bmNbNzJdJykNDQpmY25zLmM6NDE6IGB2aV9wcmV2X3Nw YWNlX3dvcmQnIHVuZGVjbGFyZWQgaGVyZSAobm90IGluIGEgZnVuY3Rpb24p DQ0KZmNucy5jOjQxOiBpbml0aWFsaXplciBlbGVtZW50IGlzIG5vdCBjb25z dGFudA0NCmZjbnMuYzo0MTogKG5lYXIgaW5pdGlhbGl6YXRpb24gZm9yIGBl bF9mdW5jWzczXScpDQ0KZmNucy5jOjQyOiBgdmlfcHJldl93b3JkJyB1bmRl Y2xhcmVkIGhlcmUgKG5vdCBpbiBhIGZ1bmN0aW9uKQ0NCmZjbnMuYzo0Mjog aW5pdGlhbGl6ZXIgZWxlbWVudCBpcyBub3QgY29uc3RhbnQNDQpmY25zLmM6 NDI6IChuZWFyIGluaXRpYWxpemF0aW9uIGZvciBgZWxfZnVuY1s3NF0nKQ0N CmZjbnMuYzo0MjogYHZpX3JlcGVhdF9uZXh0X2NoYXInIHVuZGVjbGFyZWQg aGVyZSAobm90IGluIGEgZnVuY3Rpb24pDQ0KZmNucy5jOjQyOiBpbml0aWFs aXplciBlbGVtZW50IGlzIG5vdCBjb25zdGFudA0NCmZjbnMuYzo0MjogKG5l YXIgaW5pdGlhbGl6YXRpb24gZm9yIGBlbF9mdW5jWzc1XScpDQ0KZmNucy5j OjQzOiBgdmlfcmVwZWF0X3ByZXZfY2hhcicgdW5kZWNsYXJlZCBoZXJlIChu b3QgaW4gYSBmdW5jdGlvbikNDQpmY25zLmM6NDM6IGluaXRpYWxpemVyIGVs ZW1lbnQgaXMgbm90IGNvbnN0YW50DQ0KZmNucy5jOjQzOiAobmVhciBpbml0 aWFsaXphdGlvbiBmb3IgYGVsX2Z1bmNbNzZdJykNDQpmY25zLmM6NDM6IGB2 aV9yZXBlYXRfc2VhcmNoX25leHQnIHVuZGVjbGFyZWQgaGVyZSAobm90IGlu IGEgZnVuY3Rpb24pDQ0KZmNucy5jOjQzOiBpbml0aWFsaXplciBlbGVtZW50 IGlzIG5vdCBjb25zdGFudA0NCmZjbnMuYzo0MzogKG5lYXIgaW5pdGlhbGl6 YXRpb24gZm9yIGBlbF9mdW5jWzc3XScpDQ0KZmNucy5jOjQ0OiBgdmlfcmVw ZWF0X3NlYXJjaF9wcmV2JyB1bmRlY2xhcmVkIGhlcmUgKG5vdCBpbiBhIGZ1 bmN0aW9uKQ0NCmZjbnMuYzo0NDogaW5pdGlhbGl6ZXIgZWxlbWVudCBpcyBu b3QgY29uc3RhbnQNDQpmY25zLmM6NDQ6IChuZWFyIGluaXRpYWxpemF0aW9u IGZvciBgZWxfZnVuY1s3OF0nKQ0NCmZjbnMuYzo0NDogYHZpX3JlcGxhY2Vf Y2hhcicgdW5kZWNsYXJlZCBoZXJlIChub3QgaW4gYSBmdW5jdGlvbikNDQpm Y25zLmM6NDQ6IGluaXRpYWxpemVyIGVsZW1lbnQgaXMgbm90IGNvbnN0YW50 DQ0KZmNucy5jOjQ0OiAobmVhciBpbml0aWFsaXphdGlvbiBmb3IgYGVsX2Z1 bmNbNzldJykNDQpmY25zLmM6NDU6IGB2aV9yZXBsYWNlX21vZGUnIHVuZGVj bGFyZWQgaGVyZSAobm90IGluIGEgZnVuY3Rpb24pDQ0KZmNucy5jOjQ1OiBp bml0aWFsaXplciBlbGVtZW50IGlzIG5vdCBjb25zdGFudA0NCmZjbnMuYzo0 NTogKG5lYXIgaW5pdGlhbGl6YXRpb24gZm9yIGBlbF9mdW5jWzgwXScpDQ0K ZmNucy5jOjQ1OiBgdmlfc2VhcmNoX25leHQnIHVuZGVjbGFyZWQgaGVyZSAo bm90IGluIGEgZnVuY3Rpb24pDQ0KZmNucy5jOjQ1OiBpbml0aWFsaXplciBl bGVtZW50IGlzIG5vdCBjb25zdGFudA0NCmZjbnMuYzo0NTogKG5lYXIgaW5p dGlhbGl6YXRpb24gZm9yIGBlbF9mdW5jWzgxXScpDQ0KZmNucy5jOjQ2OiBg dmlfc2VhcmNoX3ByZXYnIHVuZGVjbGFyZWQgaGVyZSAobm90IGluIGEgZnVu Y3Rpb24pDQ0KZmNucy5jOjQ2OiBpbml0aWFsaXplciBlbGVtZW50IGlzIG5v dCBjb25zdGFudA0NCmZjbnMuYzo0NjogKG5lYXIgaW5pdGlhbGl6YXRpb24g Zm9yIGBlbF9mdW5jWzgyXScpDQ0KZmNucy5jOjQ2OiBgdmlfc3Vic3RpdHV0 ZV9jaGFyJyB1bmRlY2xhcmVkIGhlcmUgKG5vdCBpbiBhIGZ1bmN0aW9uKQ0N CmZjbnMuYzo0NjogaW5pdGlhbGl6ZXIgZWxlbWVudCBpcyBub3QgY29uc3Rh bnQNDQpmY25zLmM6NDY6IChuZWFyIGluaXRpYWxpemF0aW9uIGZvciBgZWxf ZnVuY1s4M10nKQ0NCmZjbnMuYzo0NzogYHZpX3N1YnN0aXR1dGVfbGluZScg dW5kZWNsYXJlZCBoZXJlIChub3QgaW4gYSBmdW5jdGlvbikNDQpmY25zLmM6 NDc6IGluaXRpYWxpemVyIGVsZW1lbnQgaXMgbm90IGNvbnN0YW50DQ0KZmNu cy5jOjQ3OiAobmVhciBpbml0aWFsaXphdGlvbiBmb3IgYGVsX2Z1bmNbODRd JykNDQpmY25zLmM6NDc6IGB2aV90b19lbmRfd29yZCcgdW5kZWNsYXJlZCBo ZXJlIChub3QgaW4gYSBmdW5jdGlvbikNDQpmY25zLmM6NDc6IGluaXRpYWxp emVyIGVsZW1lbnQgaXMgbm90IGNvbnN0YW50DQ0KZmNucy5jOjQ3OiAobmVh ciBpbml0aWFsaXphdGlvbiBmb3IgYGVsX2Z1bmNbODVdJykNDQpmY25zLmM6 NDg6IGB2aV90b19uZXh0X2NoYXInIHVuZGVjbGFyZWQgaGVyZSAobm90IGlu IGEgZnVuY3Rpb24pDQ0KZmNucy5jOjQ4OiBpbml0aWFsaXplciBlbGVtZW50 IGlzIG5vdCBjb25zdGFudA0NCmZjbnMuYzo0ODogKG5lYXIgaW5pdGlhbGl6 YXRpb24gZm9yIGBlbF9mdW5jWzg2XScpDQ0KZmNucy5jOjQ4OiBgdmlfdG9f cHJldl9jaGFyJyB1bmRlY2xhcmVkIGhlcmUgKG5vdCBpbiBhIGZ1bmN0aW9u KQ0NCmZjbnMuYzo0ODogaW5pdGlhbGl6ZXIgZWxlbWVudCBpcyBub3QgY29u c3RhbnQNDQpmY25zLmM6NDg6IChuZWFyIGluaXRpYWxpemF0aW9uIGZvciBg ZWxfZnVuY1s4N10nKQ0NCmZjbnMuYzo0OTogYHZpX3VuZG8nIHVuZGVjbGFy ZWQgaGVyZSAobm90IGluIGEgZnVuY3Rpb24pDQ0KZmNucy5jOjQ5OiBpbml0 aWFsaXplciBlbGVtZW50IGlzIG5vdCBjb25zdGFudA0NCmZjbnMuYzo0OTog KG5lYXIgaW5pdGlhbGl6YXRpb24gZm9yIGBlbF9mdW5jWzg4XScpDQ0KZmNu cy5jOjQ5OiBgdmlfdW5kb19saW5lJyB1bmRlY2xhcmVkIGhlcmUgKG5vdCBp biBhIGZ1bmN0aW9uKQ0NCmZjbnMuYzo0OTogaW5pdGlhbGl6ZXIgZWxlbWVu dCBpcyBub3QgY29uc3RhbnQNDQpmY25zLmM6NDk6IChuZWFyIGluaXRpYWxp emF0aW9uIGZvciBgZWxfZnVuY1s4OV0nKQ0NCmZjbnMuYzo1MDogYHZpX3pl cm8nIHVuZGVjbGFyZWQgaGVyZSAobm90IGluIGEgZnVuY3Rpb24pDQ0KZmNu cy5jOjUwOiBpbml0aWFsaXplciBlbGVtZW50IGlzIG5vdCBjb25zdGFudA0N CmZjbnMuYzo1MDogKG5lYXIgaW5pdGlhbGl6YXRpb24gZm9yIGBlbF9mdW5j WzkwXScpDQ0KSW4gZmlsZSBpbmNsdWRlZCBmcm9tIGVkaXRsaW5lLmM6MjE6 DQ0KL3Vzci9zcmMvbGliL2xpYmVkaXQvdmkuYzo2OTA6IHdhcm5pbmc6IGB2 aV9jb21tYW5kX21vZGUnIHdhcyBkZWNsYXJlZCBpbXBsaWNpdGx5IGBleHRl cm4nIGFuZCBsYXRlciBgc3RhdGljJw0NCi91c3Ivc3JjL2xpYi9saWJlZGl0 L2NvbW1vbi5jOjExNzogd2FybmluZzogcHJldmlvdXMgZGVjbGFyYXRpb24g b2YgYHZpX2NvbW1hbmRfbW9kZScNDQovdXNyL3NyYy9saWIvbGliZWRpdC92 aS5jOjY5MDogd2FybmluZzogdHlwZSBtaXNtYXRjaCB3aXRoIHByZXZpb3Vz IGltcGxpY2l0IGRlY2xhcmF0aW9uDQ0KL3Vzci9zcmMvbGliL2xpYmVkaXQv Y29tbW9uLmM6MTE3OiB3YXJuaW5nOiBwcmV2aW91cyBpbXBsaWNpdCBkZWNs YXJhdGlvbiBvZiBgdmlfY29tbWFuZF9tb2RlJw0NCi91c3Ivc3JjL2xpYi9s aWJlZGl0L3ZpLmM6NjkwOiB3YXJuaW5nOiBgdmlfY29tbWFuZF9tb2RlJyB3 YXMgcHJldmlvdXNseSBpbXBsaWNpdGx5IGRlY2xhcmVkIHRvIHJldHVybiBg aW50Jw0NCioqKiBFcnJvciBjb2RlIDENDQoNDQpTdG9wIGluIC91c3Ivc3Jj L2xpYi9saWJlZGl0Lg0NCioqKiBFcnJvciBjb2RlIDENDQoNDQpTdG9wIGlu IC91c3Ivc3JjL2xpYi4NDQoqKiogRXJyb3IgY29kZSAxDQ0KDQ0KU3RvcCBp biAvdXNyL3NyYy4NDQoqKiogRXJyb3IgY29kZSAxDQ0KDQ0KU3RvcCBpbiAv dXNyL3NyYy4NDQoqKiogRXJyb3IgY29kZSAxDQ0KDQ0KU3RvcCBpbiAvdXNy L3NyYy4NDQoocm9vdEB3b3JsZGNsYXNzOi91c3Ivc3JjKSBleGl0DQ0KDQpT Y3JpcHQgZG9uZSBvbiBNb24gU2VwIDE4IDEyOjEyOjQxIDIwMDANCg== --0-83113638-969279375=:41209-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 3:54: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id F21EB37B423 for ; Mon, 18 Sep 2000 03:53:52 -0700 (PDT) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #20) id 13ayYZ-0008Ms-00; Mon, 18 Sep 2000 12:53:51 +0200 Received: from a3309.pppool.de ([213.6.51.9] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.16 #20) id 13ayYY-00057A-00; Mon, 18 Sep 2000 12:53:50 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8I8xKn01498; Mon, 18 Sep 2000 10:59:21 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009180859.e8I8xKn01498@Magelan.Leidinger.net> Date: Mon, 18 Sep 2000 10:59:19 +0200 (CEST) From: Alexander Leidinger Subject: Re: patch for openssh To: jdp@polstra.com Cc: current@freebsd.org In-Reply-To: <200009172039.NAA12052@vashon.polstra.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Sep, John Polstra wrote: > What is the point of that change? Functionally it makes no difference > at all, since "*auth" is an AuthenticationConnection. It makes the I was a little bit confused at that time. Yes, it's more of a bikeshed decision, IMHO it makes it less difficult to read (you didn't have to search for the type). > code harder to maintain in case the type of "auth" is changed in the > future. This depends on the type of change someone makes. If you didn't change the typedef of "AuthenticationConnection" but the type of "auth", you normaly have to go through the code and ensure every invariant is still valid (I classify this as a major code change, but this is a bikeshed argument too). Bye, Alexander. -- The three Rs of Microsoft support: Retry, Reboot, Reinstall. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 5:48: 9 2000 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 0692837B42C; Mon, 18 Sep 2000 05:48:05 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id XAA19037; Mon, 18 Sep 2000 23:47:52 +1100 Date: Mon, 18 Sep 2000 23:47:49 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: sanpei@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Please review: small change in sys/i386/isa/clock.c and sys/alpha/alpha/clock.c for PC-Card melody beep code. In-Reply-To: <200009171838.MAA24081@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Sep 2000, Warner Losh wrote: > I've seen these patches many times and think that it is a good idea. > This interface needs to be exported so that the pccard system sounds > don't interfere with normal systme sounds. It needs locking changes to be exportable: 1) splhigh()/splx(), at least in RELENG_4 where there is no giant lock and spl*() has a non-null effect, so that callers don't need to know that it must be called at splsoftclock() or higher. 2) Honor the current locking protocol acquire_timer2()/release_timer2() -- don't do anything if (!beeping). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 5:59:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 3660837B43E; Mon, 18 Sep 2000 05:59:19 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.0/8.11.0) id e8I9jZ770342; Mon, 18 Sep 2000 10:45:35 +0100 (BST) (envelope-from nik) Date: Mon, 18 Sep 2000 10:45:30 +0100 From: Nik Clayton To: Reinier Bezuidenhout Cc: nik@freebsd.org, current@freebsd.org Subject: Re: VMWare on -current, how fast should I expect it to be? Message-ID: <20000918104530.A70310@canyon.nothing-going-on.org> References: <200009121444.QAA15707@oskar.nanoteq.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009121444.QAA15707@oskar.nanoteq.co.za>; from rbezuide@oskar.nanoteq.co.za on Tue, Sep 12, 2000 at 04:44:41PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 12, 2000 at 04:44:41PM +0200, Reinier Bezuidenhout wrote: > Let me first ask ... do you use the "suspend/resume" option?? Yep. > This caused the same "lockup" every few seconds on my machine too - > a much slower 400 PII. As soon as I "shutdown" Win9X and rebooted > it worked fine. I tried that. The pauses are still there :-( Thanks for the suggestion. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 6:39:39 2000 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 D8A6337B423; Mon, 18 Sep 2000 06:39:30 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id AAA21762; Tue, 19 Sep 2000 00:39:11 +1100 Date: Tue, 19 Sep 2000 00:39:08 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Adrian Filipi-Martin Cc: Ben Smithurst , Poul-Henning Kamp , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Sep 2000, Adrian Filipi-Martin wrote: > I recently ran into revelant problem with /dev/stdout, while > working on some software under linux that expected /dev/stdout as an > argument instead of using stdout. > > Using the device file breaks, if the process is suid to a non-root > user. This is because it cannot open /dev/stdout, which is owned by your > UID and not the EUID of the process to which the device was passed. My > solution was to add the "-" hack and use the existing open descriptor. Um, open on fdesc devices doesn't check either uid. It just checks the access mode. Perhaps the software expected /dev/stdout to for read-write like a tty would be. Then opening /dev/stdout would fail for normal shell output redirection which only opens for writing. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 6:58:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id DF6F837B424; Mon, 18 Sep 2000 06:58:08 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.0/8.9.3) id e8IDvf206856; Mon, 18 Sep 2000 15:57:41 +0200 (CEST) (envelope-from asmodai) Date: Mon, 18 Sep 2000 15:57:41 +0200 From: Jeroen Ruigrok van der Werven To: Alexander Leidinger Cc: current@FreeBSD.ORG, kris@FreeBSD.ORG Subject: Re: updated OpenSSH & pam_ssh, the old bug is back Message-ID: <20000918155741.K4858@lucifer.bart.nl> References: <200009161449.e8GEnCn01662@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009161449.e8GEnCn01662@Magelan.Leidinger.net>; from Alexander@Leidinger.net on Sat, Sep 16, 2000 at 04:49:10PM +0200 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000916 17:10], Alexander Leidinger (Alexander@Leidinger.net) wrote: >after the update of OpenSSH xdm crashes if I enable pam_ssh in pam.conf. >I fixed this in the old version, but it seems the bug is back. > >I have a look at it and try to produce a patch again. You mean that bug which you reported and produced a patch and which I subsequently committed? The malloc.conf -> AJ resulted coredump one? -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Grant me the serenity to accept the things I cannot change, courage to change the things I can, and wisdom to know the difference... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 7: 1:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from lychee.itojun.org (ny-ppp015.iij-us.net [216.98.99.15]) by hub.freebsd.org (Postfix) with ESMTP id A8BE437B422 for ; Mon, 18 Sep 2000 07:01:22 -0700 (PDT) Received: from kiwi.itojun.org (localhost [127.0.0.1]) by itojun.org (8.10.0/3.7W) with ESMTP id e8IE0q302036; Mon, 18 Sep 2000 23:00:52 +0900 (JST) Message-Id: <200009181400.e8IE0q302036@itojun.org> To: rbezuide@oskar.nanoteq.co.za Cc: freebsd-current@freebsd.org, snap-users@kame.net In-reply-to: rbezuide's message of Mon, 18 Sep 2000 10:00:53 +0200. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: (KAME-snap 3338) Re: Panic on current (12 Sept) From: Jun-ichiro itojun Hagino Date: Mon, 18 Sep 2000 23:00:52 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> "current machine" meaning FreeBSD-current? if so, are there any >> locking behavior changes due to the introduction of fine grain locks? >> what happens if you go back to coarse grain lock kernel? >As far as I recall ... the first kernel was before any of the SMP >commits ... but in case it was not ... how do I go about >going back to a "coarse grain lock" kernel ... can I set >something in the config file or do I have to checkout old >sources ?? for this part (how to get a source before fine grain SMP) I'm totally unsure. sorry itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 7: 1:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from lychee.itojun.org (ny-ppp015.iij-us.net [216.98.99.15]) by hub.freebsd.org (Postfix) with ESMTP id AB26737B423 for ; Mon, 18 Sep 2000 07:01:49 -0700 (PDT) Received: from kiwi.itojun.org (localhost [127.0.0.1]) by itojun.org (8.10.0/3.7W) with ESMTP id e8IE1U302050; Mon, 18 Sep 2000 23:01:30 +0900 (JST) Message-Id: <200009181401.e8IE1U302050@itojun.org> To: rbezuide@oskar.nanoteq.co.za Cc: snap-users@kame.net, freebsd-current@freebsd.org In-reply-to: rbezuide's message of Mon, 18 Sep 2000 10:05:53 +0200. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: (KAME-snap 3337) RE: Panic on current (12 Sept) From: Jun-ichiro itojun Hagino Date: Mon, 18 Sep 2000 23:01:30 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Without starting the racoon daemon and doing a secure connect >everything works fine without a problem. If I start racoon, >do a tunnel connection and then run daily, the machine panics .. I bet you can panic the kernel with setkey(8) in that case. am I correct? if so, something is not friendly with fine grain SMP, under sys/netkey. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 7:18:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id B6B4237B422; Mon, 18 Sep 2000 07:18:07 -0700 (PDT) Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #20) id 13b1kE-0000Pu-00; Mon, 18 Sep 2000 16:18:06 +0200 Received: from a35e6.pppool.de ([213.6.53.230] helo=Magelan.Leidinger.net) by mx3.freenet.de with esmtp (Exim 3.16 #21) id 13b1kB-00057Z-00; Mon, 18 Sep 2000 16:18:06 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8IEHOV04422; Mon, 18 Sep 2000 16:17:25 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009181417.e8IEHOV04422@Magelan.Leidinger.net> Date: Mon, 18 Sep 2000 16:17:22 +0200 (CEST) From: Alexander Leidinger Subject: Re: updated OpenSSH & pam_ssh, the old bug is back To: jruigrok@via-net-works.nl Cc: current@FreeBSD.ORG, kris@FreeBSD.ORG In-Reply-To: <20000918155741.K4858@lucifer.bart.nl> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Sep, Jeroen Ruigrok van der Werven wrote: >>after the update of OpenSSH xdm crashes if I enable pam_ssh in pam.conf. >>I fixed this in the old version, but it seems the bug is back. >> >>I have a look at it and try to produce a patch again. > > You mean that bug which you reported and produced a patch and which I > subsequently committed? The malloc.conf -> AJ resulted coredump one? Initially yes, but at the moment I'm under the impression it's another bug (I don't know where it is and how to fix it), the old one seems to be fixed. Bye, Alexander. -- ...and that is how we know the Earth to be banana-shaped. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 7:21:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 940C237B422; Mon, 18 Sep 2000 07:21:35 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.0/8.9.3) id e8IELG407224; Mon, 18 Sep 2000 16:21:16 +0200 (CEST) (envelope-from asmodai) Date: Mon, 18 Sep 2000 16:21:15 +0200 From: Jeroen Ruigrok van der Werven To: Alexander Leidinger Cc: current@FreeBSD.ORG, kris@FreeBSD.ORG Subject: Re: updated OpenSSH & pam_ssh, the old bug is back Message-ID: <20000918162115.A7126@lucifer.bart.nl> References: <20000918155741.K4858@lucifer.bart.nl> <200009181417.e8IEHOV04422@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009181417.e8IEHOV04422@Magelan.Leidinger.net>; from Alexander@leidinger.net on Mon, Sep 18, 2000 at 04:17:22PM +0200 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000918 16:20], Alexander Leidinger (Alexander@leidinger.net) wrote: >On 18 Sep, Jeroen Ruigrok van der Werven wrote: > >> You mean that bug which you reported and produced a patch and which I >> subsequently committed? The malloc.conf -> AJ resulted coredump one? > >Initially yes, but at the moment I'm under the impression it's another >bug (I don't know where it is and how to fix it), the old one seems to >be fixed. Is it a malloc.conf -> AJ related bug again? =) Anyway, if you find it, don't hesitate to let me know, so I can apply it. Cheers, -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Grant me the serenity to accept the things I cannot change, courage to change the things I can, and wisdom to know the difference... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 7:54:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 3143A37B424 for ; Mon, 18 Sep 2000 07:54:16 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13b2Gz-000E37-00 for current@FreeBSD.org; Mon, 18 Sep 2000 15:51:57 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id PAA16851 for current@FreeBSD.org; Mon, 18 Sep 2000 15:51:57 +0100 (BST) (envelope-from ben) Date: Mon, 18 Sep 2000 15:51:57 +0100 From: Ben Smithurst To: current@FreeBSD.org Subject: "No buffer space available" errors Message-ID: <20000918155157.X56185@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have any clue what could cause errors like this? I've been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure there's more information I should be giving, so just let me know what to find. dmesg is at the end. Sep 18 07:56:01 lithium last message repeated 17 times Sep 18 07:56:10 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 07:56:11 lithium dhclient: send_packet: No buffer space available Sep 18 07:56:29 lithium dhclient: send_packet: No buffer space available Sep 18 07:57:55 lithium last message repeated 4 times Sep 18 08:06:30 lithium last message repeated 14 times Sep 18 08:09:16 lithium dhclient: send_packet: No buffer space available Sep 18 08:09:39 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 08:10:49 lithium dhclient: send_packet: No buffer space available Sep 18 08:11:26 lithium last message repeated 4 times Sep 18 08:13:32 lithium last message repeated 4 times Sep 18 08:18:13 lithium last message repeated 3 times Sep 18 08:23:08 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 08:23:09 lithium dhclient: send_packet: No buffer space available Sep 18 08:23:30 lithium last message repeated 2 times Sep 18 08:24:31 lithium last message repeated 2 times Sep 18 08:31:00 lithium last message repeated 2 times Sep 18 08:36:37 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 08:37:10 lithium dhclient: send_packet: No buffer space available Sep 18 08:39:00 lithium dhclient: send_packet: No buffer space available Sep 18 08:41:10 lithium last message repeated 2 times Sep 18 08:50:01 lithium last message repeated 15 times Sep 18 08:50:06 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 08:50:34 lithium dhclient: send_packet: No buffer space available Sep 18 08:51:12 lithium last message repeated 2 times Sep 18 08:53:00 lithium last message repeated 7 times Sep 18 09:03:03 lithium last message repeated 18 times Sep 18 09:03:35 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 09:04:27 lithium dhclient: send_packet: No buffer space available Sep 18 09:04:57 lithium last message repeated 3 times Sep 18 09:06:50 lithium last message repeated 4 times Sep 18 09:15:35 lithium last message repeated 4 times Sep 18 09:17:04 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 09:17:20 lithium dhclient: send_packet: No buffer space available Sep 18 09:19:14 lithium dhclient: send_packet: No buffer space available Sep 18 09:21:01 lithium last message repeated 3 times Sep 18 09:30:04 lithium last message repeated 8 times Sep 18 09:30:33 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 09:32:33 lithium dhclient: send_packet: No buffer space available Sep 18 09:34:36 lithium dhclient: send_packet: No buffer space available Sep 18 09:35:31 lithium dhclient: send_packet: No buffer space available Sep 18 09:42:40 lithium last message repeated 7 times Sep 18 09:44:02 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 09:45:57 lithium dhclient: send_packet: No buffer space available Sep 18 09:47:17 lithium dhclient: send_packet: No buffer space available Sep 18 09:48:24 lithium last message repeated 3 times Sep 18 09:57:31 lithium last message repeated 25 times Sep 18 09:57:31 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 09:57:51 lithium dhclient: send_packet: No buffer space available Sep 18 09:58:35 lithium last message repeated 2 times Sep 18 10:00:43 lithium last message repeated 3 times Sep 18 10:07:45 lithium last message repeated 4 times Sep 18 10:11:00 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 10:12:49 lithium dhclient: send_packet: No buffer space available Sep 18 10:21:14 lithium dhclient: send_packet: No buffer space available Sep 18 10:24:29 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 10:37:58 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 10:41:39 lithium dhclient: send_packet: No buffer space available Sep 18 10:46:54 lithium dhclient: send_packet: No buffer space available Sep 18 10:51:27 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 10:51:38 lithium dhclient: send_packet: No buffer space available Sep 18 10:54:45 lithium dhclient: send_packet: No buffer space available Sep 18 10:58:42 lithium dhclient: send_packet: No buffer space available Sep 18 11:03:24 lithium last message repeated 2 times Sep 18 11:04:56 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 11:05:11 lithium dhclient: send_packet: No buffer space available Sep 18 11:05:49 lithium dhclient: send_packet: No buffer space available Sep 18 11:06:54 lithium dhclient: send_packet: No buffer space available Sep 18 11:17:31 lithium last message repeated 15 times Sep 18 11:18:25 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 11:18:57 lithium dhclient: send_packet: No buffer space available Sep 18 11:21:25 lithium dhclient: send_packet: No buffer space available Sep 18 11:25:03 lithium dhclient: send_packet: No buffer space available Sep 18 11:31:11 lithium last message repeated 12 times Sep 18 11:31:54 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 11:32:03 lithium dhclient: send_packet: No buffer space available Sep 18 11:33:26 lithium dhclient: send_packet: No buffer space available Sep 18 11:35:29 lithium last message repeated 5 times Sep 18 11:44:40 lithium last message repeated 17 times Sep 18 11:45:23 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 11:45:24 lithium dhclient: send_packet: No buffer space available Sep 18 11:46:11 lithium dhclient: send_packet: No buffer space available Sep 18 11:48:17 lithium last message repeated 6 times Sep 18 11:57:44 lithium last message repeated 22 times Sep 18 11:58:25 lithium dhclient: send_packet: No buffer space available Sep 18 11:58:52 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 11:59:35 lithium dhclient: send_packet: No buffer space available Sep 18 12:01:59 lithium dhclient: send_packet: No buffer space available Sep 18 12:05:31 lithium dhclient: send_packet: No buffer space available Sep 18 12:09:04 lithium dhclient: send_packet: No buffer space available Sep 18 12:12:21 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 12:15:27 lithium dhclient: send_packet: No buffer space available Sep 18 12:22:31 lithium dhclient: send_packet: No buffer space available Sep 18 12:25:27 lithium /boot/kernel/kernel: stray irq 7 Sep 18 12:25:30 lithium /boot/kernel/kernel: stray irq 7 Sep 18 12:25:30 lithium dhclient: New IP Address(ep0): 192.168.91.35 Sep 18 12:25:31 lithium dhclient: New Subnet Mask (ep0): 255.255.255.240 Sep 18 12:25:31 lithium dhclient: New Broadcast Address(ep0): 192.168.91.47 Sep 18 12:25:31 lithium dhclient: New Routers: 192.168.91.33 Sep 18 12:25:52 lithium timed[27809]: slave to scientia.demon.co.uk Copyright (c) 1992-2000 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 #0: Sun Sep 17 13:02:24 BST 2000 ben@lithium.scientia.demon.co.uk:/current/obj/current/src/sys/LITHIUM Timecounter "i8254" frequency 1193182 Hz CPU: AMD Enhanced Am486DX4 Write-Through (486-class CPU) Origin = "AuthenticAMD" Id = 0x484 Stepping = 4 Features=0x1 real memory = 16777216 (16384K bytes) avail memory = 13979648 (13652K bytes) Preloaded elf kernel "kernel" at 0xc029b000. Preloaded elf module "random.ko" at 0xc029b09c. npx0: on motherboard npx0: INT 16 interface isa0: on motherboard ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16450 sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 sio1: type 16450 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ep0: <3Com 3C509-Combo EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep0: Ethernet address 00:a0:24:eb:f4:a2 ad0: 407MB [898/15/62] at ata0-master using BIOSPIO Mounting root from ufs:/dev/ad0s1a -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 8:43:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id BDFE337B424; Mon, 18 Sep 2000 08:43:16 -0700 (PDT) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #20) id 13b34a-0000Pq-00; Mon, 18 Sep 2000 17:43:12 +0200 Received: from a315e.pppool.de ([213.6.49.94] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.16 #20) id 13b34Z-0007rT-00; Mon, 18 Sep 2000 17:43:12 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8IFRaV05004; Mon, 18 Sep 2000 17:27:37 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009181527.e8IFRaV05004@Magelan.Leidinger.net> Date: Mon, 18 Sep 2000 17:27:35 +0200 (CEST) From: Alexander Leidinger Subject: Re: updated OpenSSH & pam_ssh, the old bug is back To: jruigrok@via-net-works.nl Cc: current@FreeBSD.ORG, kris@FreeBSD.ORG In-Reply-To: <20000918162115.A7126@lucifer.bart.nl> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Sep, Jeroen Ruigrok van der Werven wrote: >>> You mean that bug which you reported and produced a patch and which I >>> subsequently committed? The malloc.conf -> AJ resulted coredump one? >> >>Initially yes, but at the moment I'm under the impression it's another >>bug (I don't know where it is and how to fix it), the old one seems to >>be fixed. > > Is it a malloc.conf -> AJ related bug again? =) No, I'm at malloc.conf -> aj now. > Anyway, if you find it, don't hesitate to let me know, so I can apply > it. I don't know where to look. The only usefull information I have so far is: ---snip--(from /lib/X11/xdm/xdm-error)- xdm error (pid 2530): Unknown session exit code 2816 from process 2727 ---snip--- I assume (from looking at the openssh source) proc 2727 is ssh-agent. I'm not that familiar with the internals of xdm, pam or ssh to know where to look further. A helping hand would be fine. :) Bye, Alexander. -- The three Rs of Microsoft support: Retry, Reboot, Reinstall. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 8:52:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from light.imasy.or.jp (light.imasy.or.jp [202.227.24.4]) by hub.freebsd.org (Postfix) with ESMTP id 193DE37B43C for ; Mon, 18 Sep 2000 08:52:07 -0700 (PDT) Received: (from uucp@localhost) by light.imasy.or.jp (8.11.0+3.3W/3.7W-light) with UUCP id e8IFnJu14564; Tue, 19 Sep 2000 00:49:19 +0900 (JST) (envelope-from ume@mahoroba.org) Received: from localhost (peace.mahoroba.org [3ffe:505:2:0:200:f8ff:fe05:3eae]) by mail.mahoroba.org (8.11.0/8.11.0/chaos) with ESMTP/inet6 id e8IFflX09438; Tue, 19 Sep 2000 00:41:47 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Tue, 19 Sep 2000 00:41:47 +0900 (JST) Message-Id: <20000919.004147.92586170.ume@mahoroba.org> To: rbezuide@oskar.nanoteq.co.za Cc: freebsd-current@freebsd.org, snap-users@kame.net Subject: Re: (KAME-snap 3338) Re: Panic on current (12 Sept) From: Hajimu UMEMOTO In-Reply-To: References: <19651.969165128@coconut.itojun.org> X-Mailer: xcite1.20> Mew version 1.95b38 on Emacs 20.7 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Mon, 18 Sep 2000 10:00:53 +0200 (SAST) >>>>> Reinier Bezuidenhout said: rbezuide> As far as I recall ... the first kernel was before any of the SMP rbezuide> commits ... but in case it was not ... how do I go about rbezuide> going back to a "coarse grain lock" kernel ... can I set rbezuide> something in the config file or do I have to checkout old rbezuide> sources ?? There is a tag just before SMPNG merge. You can do cvsup with: src-all tag=PRE_SMPNG -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 9:42:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id D6E0737B422; Mon, 18 Sep 2000 09:42:08 -0700 (PDT) Received: from vic.sabbo.net (root@[193.193.218.94]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id TAA12604; Mon, 18 Sep 2000 19:42:03 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.0/8.9.3) with ESMTP id e8IGg4U56407; Mon, 18 Sep 2000 19:42:04 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <39C645D8.ED66330A@FreeBSD.org> Date: Mon, 18 Sep 2000 19:42:00 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@FreeBSD.org Cc: jlemon@FreeBSD.org, jasone@FreeBSD.org Subject: Thread-safe version of fpathconf(2) syscall missed from libc_r [patch for review] Content-Type: multipart/mixed; boundary="------------F173C57EA66A1E2470B9EBFC" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------F173C57EA66A1E2470B9EBFC Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Hi, It seems that due to unknown for me reasons, thread-safe wrapper for fpathconf(2) syscall is missed from the libc_r, while fpathconf listed in the list of syscalls for which thread-safe wrappers are to be provided (src/lib/libc_r/Makefile:31). The following short example exposes the bug: fpath.c: #include #include int main() { return fpathconf(1, 3); } $ cc -pthread fpath.c /tmp/ccF56334.o: In function `main': /tmp/ccF56334.o(.text+0xe): undefined reference to `fpathconf' Attached patch expected to fix the problem. -Maxim --------------F173C57EA66A1E2470B9EBFC Content-Type: text/plain; charset=koi8-r; name="libc_r-fpathconf.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="libc_r-fpathconf.diff" diff -druN libc_r.orig/uthread/Makefile.inc libc_r/uthread/Makefile.inc --- libc_r.orig/uthread/Makefile.inc Fri Aug 11 14:49:15 2000 +++ libc_r/uthread/Makefile.inc Mon Sep 18 18:28:49 2000 @@ -49,6 +49,7 @@ uthread_find_thread.c \ uthread_flock.c \ uthread_fork.c \ + uthread_fpathconf.c \ uthread_fstat.c \ uthread_fstatfs.c \ uthread_fsync.c \ diff -druN libc_r.orig/uthread/pthread_private.h libc_r/uthread/pthread_private.h --- libc_r.orig/uthread/pthread_private.h Fri Aug 11 14:49:15 2000 +++ libc_r/uthread/pthread_private.h Mon Sep 18 19:10:00 2000 @@ -1204,6 +1204,7 @@ int _thread_sys_pause(void); int _thread_sys_pipe(int *); int _thread_sys_select(int, fd_set *, fd_set *, fd_set *, struct timeval *); +long _thread_sys_fpathconf(int, int); off_t _thread_sys_lseek(int, off_t, int); pid_t _thread_sys_fork(void); pid_t _thread_sys_tcgetpgrp(int); diff -druN libc_r.orig/uthread/uthread_fpathconf.c libc_r/uthread/uthread_fpathconf.c --- libc_r.orig/uthread/uthread_fpathconf.c Thu Jan 1 03:00:00 1970 +++ libc_r/uthread/uthread_fpathconf.c Mon Sep 18 19:24:14 2000 @@ -0,0 +1,46 @@ +/* + * Copyright (c) 2000 Maxim Sobolev + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * + * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + * $FreeBSD$ + */ +#include +#ifdef _THREAD_SAFE +#include +#include "pthread_private.h" + +long +_fpathconf(int fd, int name) +{ + long ret; + + if ((ret = _FD_LOCK(fd, FD_READ, NULL)) == 0) { + ret = _thread_sys_fpathconf(fd, name); + _FD_UNLOCK(fd, FD_READ); + } + return ret; +} + +__strong_reference(_fpathconf, fpathconf); +#endif --------------F173C57EA66A1E2470B9EBFC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 9:57:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 8A3B937B424; Mon, 18 Sep 2000 09:57:05 -0700 (PDT) Received: from modemcable136.203-201-24.mtl.mc.videotron.ca ([24.201.203.136]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G1300634DOG96@field.videotron.net>; Mon, 18 Sep 2000 12:55:28 -0400 (EDT) Date: Mon, 18 Sep 2000 12:59:05 -0400 (EDT) From: Bosko Milekic Subject: Re: "No buffer space available" errors In-reply-to: <20000918155157.X56185@strontium.scientia.demon.co.uk> X-Sender: bmilekic@jehovah.technokratis.com To: Ben Smithurst Cc: current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Sep 2000, Ben Smithurst wrote: > Does anyone have any clue what could cause errors like this? I've > been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure > there's more information I should be giving, so just let me know what to > find. dmesg is at the end. This looks an awful lot like something I was seeing during early testing while adding locking to the mbuf system. Try `netstat -m' to see how many mbuf clusters are allocated. I would guess that the system is unable to allocate clusters reliably. In my case, at the time, I had forgotten to change a pointer dereference to meet the new structure, and thus it just worked out that after allocating the initial amount of clusters, nothing more was possible to allocate. I haven't seen this problem after fixing my mistake, nor before introducing it. None of the work I mentionned has been committed at any point in time (yet), so the problem can only be similar, at best (in any case, a `netstat -m' should offer a clue). Regards, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 10: 9:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 7270837B423; Mon, 18 Sep 2000 10:09:43 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id NAA54584; Mon, 18 Sep 2000 13:09:42 -0400 (EDT) Date: Mon, 18 Sep 2000 13:09:42 -0400 (EDT) From: "Matthew N. Dodd" To: Ben Smithurst Cc: current@FreeBSD.ORG Subject: Re: "No buffer space available" errors In-Reply-To: <20000918155157.X56185@strontium.scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 18 Sep 2000, Ben Smithurst wrote: > Does anyone have any clue what could cause errors like this? I've > been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure > there's more information I should be giving, so just let me know what > to find. dmesg is at the end. ... > ep0: <3Com 3C509-Combo EtherLink III> at port 0x300-0x30f irq 10 on isa0 > ep0: Ethernet address 00:a0:24:eb:f4:a2 Run 'netstat -m' when you encounter the problem and email me the results. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 10:27:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from parodius.com (pentarou.parodius.com [205.149.163.62]) by hub.freebsd.org (Postfix) with ESMTP id 2B35237B422 for ; Mon, 18 Sep 2000 10:27:31 -0700 (PDT) Received: from localhost (dpk@localhost) by parodius.com (8.11.0/8.11.0) with ESMTP id e8IHRIK72912 for ; Mon, 18 Sep 2000 10:27:19 -0700 (PDT) (envelope-from dpk@parodius.com) Date: Mon, 18 Sep 2000 10:27:18 -0700 (PDT) From: David Kirchner To: freebsd-current@freebsd.org Subject: Re: Strange procfs bug(?) 3.2-RELEASE In-Reply-To: <20000911130912.N12231@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone know if the patch indicated below was committed to fix this FreeBSD 3.2 bug? I can't upgrade to a later release yet, but if this patch is it, I can hack it in. On Mon, 11 Sep 2000, Alfred Perlstein wrote: > * David Kirchner [000911 12:19] wrote: > > > > > Yes, there's a problem with procfs in 3.2 when you stress it heavily > > > like that, my suggestion is to get 4-stable running, or at least try > > > to get 3.5.1 up and running, but I'm unsure if it's fixed in 3.5.1. > > > > > > -Alfred > > > > Is this related? : > > > > "Don't call calcru() on a swapped-out process. calcru() access p_stats, > > which is in U-area." > > > > That's from CVSweb at file procfs_status.c, revision 1.14 > > I'm not really a procfs guru, I only know about your reported problem, > I've never heard of that message though. > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 11:36:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 62A4E37B620 for ; Mon, 18 Sep 2000 11:36:39 -0700 (PDT) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA11064 for ; Mon, 18 Sep 2000 14:36:27 -0400 (EDT) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id OAA27196 for ; Mon, 18 Sep 2000 14:36:27 -0400 (EDT) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA27186 for ; Mon, 18 Sep 2000 14:36:26 -0400 (EDT) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Mon, 18 Sep 2000 14:36:25 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: SMPng feedback Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alright, I've been using -CURRENT with the SMPng changes for a few days and wanted to give some feedback. Overall everything works, although I have been experienceing a few problems which may or may not be related. 1) When I'm playing music (mp3), and I move the mouse or move a window in X, the sound stutters and I get a pcm0: hwptr went backwards x -> y (where x and y are different numbers). 2) the mouse is quite jumpy in X, especially while there is high cpu usage. I have tried to use both the usb mouse and the psm mouse (I have a usb to psm adapter) and the behaviour is the same with all mice I've tried. ( a logitec optical mouse, and a ms intellimouse with the ball, not optical) These have been the only noticable changes to my system since the update... I have built the world with the changes in the kernel without problems so they seem stable enough, just kinda slow. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 11:42:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom1-253.telepath.com [216.14.1.253]) by hub.freebsd.org (Postfix) with SMTP id 74E8C37B424 for ; Mon, 18 Sep 2000 11:42:28 -0700 (PDT) Received: (qmail 50482 invoked by uid 100); 18 Sep 2000 18:41:51 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14790.25071.254295.658898@guru.mired.org> Date: Mon, 18 Sep 2000 13:41:51 -0500 (CDT) To: current@freebsd.org Subject: periodic no longer usable by users? X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that recent (the last two weeks?) changes to periodic have changed things so that non-root users of it no longer get any output. A simple fix would be to change the default output to $USER (not yet tested). However, having a user-specific periodic.conf would be a lot more useful. But I wanted to see what others thought of it before trying it. Reply-To: Adrian Filipi-Martin To: Bruce Evans Cc: Ben Smithurst , Poul-Henning Kamp , Peter Pentchev , Julian Elischer , Chris Costello , hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Fdescfs updates--coming to a devfs near you! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Sep 2000, Bruce Evans wrote: > On Sun, 17 Sep 2000, Adrian Filipi-Martin wrote: > > > I recently ran into revelant problem with /dev/stdout, while > > working on some software under linux that expected /dev/stdout as an > > argument instead of using stdout. > > > > Using the device file breaks, if the process is suid to a non-root > > user. This is because it cannot open /dev/stdout, which is owned by your > > UID and not the EUID of the process to which the device was passed. My > > solution was to add the "-" hack and use the existing open descriptor. > > Um, open on fdesc devices doesn't check either uid. It just checks > the access mode. > > Perhaps the software expected /dev/stdout to for read-write like a > tty would be. Then opening /dev/stdout would fail for normal shell > output redirection which only opens for writing. No, it wasn't a RW/W issue. I dug a little deeper. It looks like the BSD implmentation of /dev/stdout is smarter than the linux version. Linux's is a symlink into /proc and the device ownership is determined by the UID of the invoking user. I guess I wouldn't have have had a problem under BSD. no suprise here. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 14:11: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 51EF337B424 for ; Mon, 18 Sep 2000 14:11:01 -0700 (PDT) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA08080 for ; Mon, 18 Sep 2000 14:11:00 -0700 (PDT) (envelope-from DougB@gorean.org) Date: Mon, 18 Sep 2000 14:11:00 -0700 (PDT) From: Doug Barton X-Sender: doug@dt051n37.san.rr.com To: current@freebsd.org Subject: Re: kernel breakage in aac.c (Was: Can't build a kernel) In-Reply-To: <39C59477.D02978BD@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 17 Sep 2000, Doug Barton wrote: > If I use the buildkernel target I get the following: > > make: cannot open > /usr/amd/realmounts/slave/usr/current/src/sys/dev/aic7xxx/Makefile. > *** Error code 2 > > Stop in /usr/amd/realmounts/slave/usr/current/src. > *** Error code 1 This is fixed now. > If I use the old way, I get errors about a pointer with an incomplete > type in aac (whatever that is). This is still broken: ===> aac cc -O -pipe -DAAC_COMPAT_LINUX -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c /usr/amd/realmounts/slave/usr/current/src/sys/modules/aac/../../dev/aac/aac.c /usr/amd/realmounts/slave/usr/current/src/sys/modules/aac/../../dev/aac/aac.c: In function `aac_linux_ioctl': /usr/amd/realmounts/slave/usr/current/src/sys/modules/aac/../../dev/aac/aac.c:1815: dereferencing pointer to incomplete type Doug -- "The dead cannot be seduced." - Kai, "Lexx" 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 Sep 18 14:14:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 289C237B422 for ; Mon, 18 Sep 2000 14:14:37 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id OAA01170; Mon, 18 Sep 2000 14:10:52 -0700 (PDT) Message-Id: <200009182110.OAA01170@implode.root.com> To: Doug Barton Cc: current@FreeBSD.ORG Subject: Re: kernel breakage in aac.c (Was: Can't build a kernel) In-reply-to: Your message of "Mon, 18 Sep 2000 14:11:00 PDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 18 Sep 2000 14:10:52 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is still broken: > >===> aac >cc -O -pipe -DAAC_COMPAT_LINUX -D_KERNEL -Wall -Wredundant-decls >-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith >-Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- >-I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c >/usr/amd/realmounts/slave/usr/current/src/sys/modules/aac/../../dev/aac/aac.c >/usr/amd/realmounts/slave/usr/current/src/sys/modules/aac/../../dev/aac/aac.c: In >function `aac_linux_ioctl': >/usr/amd/realmounts/slave/usr/current/src/sys/modules/aac/../../dev/aac/aac.c:1815: dereferencing >pointer to incomplete type Here is a fix. Hopefully Mike will commit it soon. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. Index: aac.c =================================================================== RCS file: /home/ncvs/src/sys/dev/aac/aac.c,v retrieving revision 1.1 diff -c -r1.1 aac.c *** aac.c 2000/09/13 03:20:34 1.1 --- aac.c 2000/09/18 08:45:08 *************** *** 35,40 **** --- 35,41 ---- #include #include #include + #include #include To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 14:56:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 141FD37B42C for ; Mon, 18 Sep 2000 14:56:53 -0700 (PDT) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id OAA08422; Mon, 18 Sep 2000 14:56:49 -0700 (PDT) (envelope-from DougB@gorean.org) Date: Mon, 18 Sep 2000 14:56:48 -0700 (PDT) From: Doug Barton X-Sender: doug@dt051n37.san.rr.com To: David Greenman Cc: current@FreeBSD.ORG Subject: Re: kernel breakage in aac.c (Was: Can't build a kernel) In-Reply-To: <200009182110.OAA01170@implode.root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Et voila. Thanks, Doug On Mon, 18 Sep 2000, David Greenman wrote: > Here is a fix. Hopefully Mike will commit it soon. > > -DG > > David Greenman > Co-founder, The FreeBSD Project - http://www.freebsd.org > President, TeraSolutions, Inc. - http://www.terasolutions.com > Pave the road of life with opportunities. > > Index: aac.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/aac/aac.c,v > retrieving revision 1.1 > diff -c -r1.1 aac.c > *** aac.c 2000/09/13 03:20:34 1.1 > --- aac.c 2000/09/18 08:45:08 > *************** > *** 35,40 **** > --- 35,41 ---- > #include > #include > #include > + #include > > #include > > -- "The dead cannot be seduced." - Kai, "Lexx" 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 Sep 18 16:45:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from lavender.sanpei.org (ppp138.dialup.st.keio.ac.jp [131.113.27.138]) by hub.freebsd.org (Postfix) with ESMTP id 3D29537B423 for ; Mon, 18 Sep 2000 16:44:57 -0700 (PDT) Received: (from sanpei@localhost) by lavender.sanpei.org (8.11.0/3.7W) id e8ICGpH01788; Mon, 18 Sep 2000 21:16:51 +0900 (JST) Message-Id: <200009181216.e8ICGpH01788@lavender.sanpei.org> To: imp@village.org Cc: current@FreeBSD.ORG From: sanpei@FreeBSD.ORG Subject: Re: Please review: small change in sys/i386/isa/clock.c and sys/alpha/alpha/clock.c for PC-Card melody beep code. In-Reply-To: Your message of "Sun, 17 Sep 2000 12:38:24 -0600" References: <200009171838.MAA24081@harmony.village.org> X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 18 Sep 2000 21:16:50 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I've seen these patches many times and think that it is a good idea. >This interface needs to be exported so that the pccard system sounds >don't interfere with normal systme sounds. Thanks for your response. OK, I will commit this patch the next weekend. ---------- By the way, we also need to change in sys/pc98/pc98/clock.c. --- MIHIRA, Sanpei Yoshiro Yokohama, Japan. --- sys/pc98/pc98/clock.c.org Mon Sep 18 21:13:55 2000 +++ sys/pc98/pc98/clock.c Fri Sep 15 14:42:42 2000 @@ -583,7 +583,7 @@ #endif } -void +static void sysbeepstop(void *chan) { #ifdef PC98 /* PC98 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 16:51:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6598137B422; Mon, 18 Sep 2000 16:51:11 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA92469; Mon, 18 Sep 2000 17:51:10 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA34404; Mon, 18 Sep 2000 17:50:58 -0600 (MDT) Message-Id: <200009182350.RAA34404@harmony.village.org> To: sanpei@FreeBSD.ORG Subject: Re: Please review: small change in sys/i386/isa/clock.c and sys/alpha/alpha/clock.c for PC-Card melody beep code. Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 18 Sep 2000 21:16:50 +0900." <200009181216.e8ICGpH01788@lavender.sanpei.org> References: <200009181216.e8ICGpH01788@lavender.sanpei.org> <200009171838.MAA24081@harmony.village.org> Date: Mon, 18 Sep 2000 17:50:58 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009181216.e8ICGpH01788@lavender.sanpei.org> sanpei@FreeBSD.ORG writes: : >I've seen these patches many times and think that it is a good idea. : >This interface needs to be exported so that the pccard system sounds : >don't interfere with normal systme sounds. : : Thanks for your response. OK, I will commit this patch the next : weekend. : ---------- : By the way, we also need to change in sys/pc98/pc98/clock.c. mihira-san, Did you see bruce's commentso n the change? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 21:40: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from lavender.sanpei.org (lavender.yy.ics.keio.ac.jp [131.113.47.22]) by hub.freebsd.org (Postfix) with ESMTP id 5C1D237B423 for ; Mon, 18 Sep 2000 21:39:56 -0700 (PDT) Received: (from sanpei@localhost) by lavender.sanpei.org (8.11.0/3.7W) id e8J4csH00439; Tue, 19 Sep 2000 13:38:54 +0900 (JST) Message-Id: <200009190438.e8J4csH00439@lavender.sanpei.org> To: imp@village.org Cc: current@FreeBSD.ORG From: sanpei@FreeBSD.ORG Subject: Re: Please review: small change in sys/i386/isa/clock.c and sys/alpha/alpha/clock.c for PC-Card melody beep code. In-Reply-To: Your message of "Mon, 18 Sep 2000 17:50:58 -0600" References: <200009182350.RAA34404@harmony.village.org> X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Sep 2000 13:38:53 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner-san wrote: >In message <200009181216.e8ICGpH01788@lavender.sanpei.org> sanpei@FreeBSD.ORG writes: >: >I've seen these patches many times and think that it is a good idea. >: >This interface needs to be exported so that the pccard system sounds >: >don't interfere with normal systme sounds. >: >: Thanks for your response. OK, I will commit this patch the next >: weekend. >: ---------- >: By the way, we also need to change in sys/pc98/pc98/clock.c. > >mihira-san, > Did you see bruce's commentso n the change? I wrote replay mail before I read Bruce's mail.... I will re-write code with bruce's suggestion. Thank you, Bruce and Warner. --- MIHIRA, Sanpei Yoshiro Yokohama, Japan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Sep 18 23:46:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id F209337B423 for ; Mon, 18 Sep 2000 23:46:25 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13bHAa-000H5K-00; Tue, 19 Sep 2000 08:46:21 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8J6gbn03428; Tue, 19 Sep 2000 08:42:38 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009190642.e8J6gbn03428@grimreaper.grondar.za> To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMPng feedback References: In-Reply-To: ; from Kenneth Wayne Culver "Mon, 18 Sep 2000 14:36:25 -0400." Date: Tue, 19 Sep 2000 08:42:36 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1) When I'm playing music (mp3), and I move the mouse or move a window in > X, the sound stutters and I get a pcm0: hwptr went backwards x -> y (where > x and y are different numbers). > > 2) the mouse is quite jumpy in X, especially while there is high cpu > usage. I have tried to use both the usb mouse and the psm mouse (I have a > usb to psm adapter) and the behaviour is the same with all mice I've > tried. ( a logitec optical mouse, and a ms intellimouse with the ball, > not optical) How old is your build? Do you have the kthreaded /dev/random driver? (do a top -S and look for a process called "random" when you wiggle your mouse). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 0:26:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 3B08137B423 for ; Tue, 19 Sep 2000 00:26:44 -0700 (PDT) Received: (qmail 8158 invoked from network); 19 Sep 2000 07:26:38 -0000 Received: from acs-63-85-133-215.cvzoom.net (HELO cvzoom.net) (63.85.133.215) by ns.cvzoom.net with SMTP; 19 Sep 2000 07:26:38 -0000 Message-ID: <39C71528.DEED8617@cvzoom.net> Date: Tue, 19 Sep 2000 03:26:32 -0400 From: Donn Miller X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: buildkernel problems Content-Type: multipart/mixed; boundary="------------D31AD8CBC7411C061B309A58" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------D31AD8CBC7411C061B309A58 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Here's problems I'm having with the latest (as of now) cvsup'd sources. - Donn --------------D31AD8CBC7411C061B309A58 Content-Type: text/plain; charset=us-ascii; name="make.log" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="make.log" perl @/kern/makeobjops.pl -h @/kern/bus_if.m perl @/kern/makeobjops.pl -h @/pci/pci_if.m perl @/kern/makeobjops.pl -h @/dev/mii/miibus_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/sis/../../pci/if_sis.c ===> sk @ -> /usr/src/sys machine -> /usr/src/sys/i386/include touch opt_bdg.h perl @/kern/makeobjops.pl -h @/kern/device_if.m perl @/kern/makeobjops.pl -h @/kern/bus_if.m perl @/kern/makeobjops.pl -h @/pci/pci_if.m perl @/kern/makeobjops.pl -h @/dev/mii/miibus_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/sk/../../pci/if_sk.c ===> sn @ -> /usr/src/sys machine -> /usr/src/sys/i386/include perl @/kern/makeobjops.pl -h @/kern/device_if.m perl @/kern/makeobjops.pl -h @/kern/bus_if.m perl @/kern/makeobjops.pl -h @/isa/isa_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/sn/../../dev/sn/if_sn.c /usr/src/sys/modules/sn/../../dev/sn/if_sn_isa.c /usr/src/sys/modules/sn/../../dev/sn/if_sn_pccard.c /usr/src/sys/modules/sn/../../dev/sn/if_sn_pccard.c:60: card_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/sn. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/CUSTOM. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --------------D31AD8CBC7411C061B309A58-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 1: 0:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 55C3537B423 for ; Tue, 19 Sep 2000 01:00:27 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8J80H623791 for ; Tue, 19 Sep 2000 01:00:17 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: current@freebsd.org Subject: USW2 Root: -current build report for Tue Sep 19 02:07:44 CDT 2000 Date: Tue, 19 Sep 2000 01:00:17 -0700 Message-ID: <23788.969350417@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG current current, who broke current. :) ------- Forwarded Message Return-Path: root@usw2.freebsd.org Delivery-Date: Tue Sep 19 00:12:20 2000 Return-Path: Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8J7CJ622964 for ; Tue, 19 Sep 2000 00:12:19 -0700 (PDT) (envelope-from root@usw2.freebsd.org) Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F7766E2B76 for ; Tue, 19 Sep 2000 00:12:28 -0700 (PDT) Received: by hub.freebsd.org (Postfix) id 8178737B42C; Tue, 19 Sep 2000 00:12:28 -0700 (PDT) Delivered-To: jkh@freebsd.org Received: from usw2.freebsd.org (usw2.freebsd.org [209.180.6.226]) by hub.freebsd.org (Postfix) with ESMTP id 3756F37B424 for ; Tue, 19 Sep 2000 00:12:28 -0700 (PDT) Received: (from root@localhost) by usw2.freebsd.org (8.11.0/8.11.0) id e8J7CRC99426 for build-reports@freebsd.org; Tue, 19 Sep 2000 02:12:27 -0500 (CDT) (envelope-from root) Date: Tue, 19 Sep 2000 02:12:27 -0500 (CDT) From: USW2 Root Message-Id: <200009190712.e8J7CRC99426@usw2.freebsd.org> To: build-reports@freebsd.org Subject: -current build report for Tue Sep 19 02:07:44 CDT 2000 Doing nightly build attempt for 5.0-20000919-CURRENT at Tue Sep 19 02:07:44 CDT 2000 Updating source tree... Making release... Release build of 5.0-20000919-CURRENT was an abject failure. ln -fs ../la_LN.DIS_8859-15/LC_CTYPE /vol2/5.0-current-chrootdir/usr/share/locale/nl_NL.DIS_8859-15/LC_CTYPE ln -fs ../la_LN.DIS_8859-15/LC_CTYPE /vol2/5.0-current-chrootdir/usr/share/locale/no_NO.DIS_8859-15/LC_CTYPE ln -fs ../la_LN.DIS_8859-15/LC_CTYPE /vol2/5.0-current-chrootdir/usr/share/locale/pt_PT.DIS_8859-15/LC_CTYPE ln -fs ../la_LN.DIS_8859-15/LC_CTYPE /vol2/5.0-current-chrootdir/usr/share/locale/sv_SE.DIS_8859-15/LC_CTYPE ln -fs ../la_LN.ISO_8859-2/LC_CTYPE /vol2/5.0-current-chrootdir/usr/share/locale/cs_CZ.ISO_8859-2/LC_CTYPE ln -fs ../la_LN.ISO_8859-2/LC_CTYPE /vol2/5.0-current-chrootdir/usr/share/locale/hr_HR.ISO_8859-2/LC_CTYPE ln -fs ../la_LN.ISO_8859-2/LC_CTYPE /vol2/5.0-current-chrootdir/usr/share/locale/hu_HU.ISO_8859-2/LC_CTYPE ln -fs ../la_LN.ISO_8859-2/LC_CTYPE /vol2/5.0-current-chrootdir/usr/share/locale/pl_PL.ISO_8859-2/LC_CTYPE ln -fs ../la_LN.ISO_8859-2/LC_CTYPE /vol2/5.0-current-chrootdir/usr/share/locale/sl_SI.ISO_8859-2/LC_CTYPE ln -fs ../la_LN.ISO_8859-4/LC_CTYPE /vol2/5.0-current-chrootdir/usr/share/locale/lt_LT.ISO_8859-4/LC_CTYPE ln -fs ../ja_JP.SJIS/LC_CTYPE /vol2/5.0-current-chrootdir/usr/share/locale/ja_JP.Shift_JIS/LC_CTYPE ===> share/skel install -c -o root -g wheel -m 0644 dot.cshrc dot.login dot.login_conf dot.mailrc dot.profile dot.shrc /vol2/5.0-current-chrootdir/usr/share/skel install -c -o root -g wheel -m 0600 dot.mail_aliases dot.rhosts /vol2/5.0-current-chrootdir/usr/share/skel ===> share/syscons ===> share/syscons/fonts install -c -o root -g wheel -m 444 cp437-8x8.fnt cp437-8x14.fnt cp437-8x16.fnt cp437-thin-8x8.fnt cp437-thin-8x16.fnt cp850-8x8.fnt cp850-8x14.fnt cp850-8x16.fnt cp850-thin-8x8.fnt cp850-thin-8x16.fnt cp865-8x8.fnt cp865-8x14.fnt cp865-8x16.fnt cp865-thin-8x8.fnt cp865-thin-8x16.fnt cp866-8x8.fnt cp866-8x14.fnt cp866-8x16.fnt cp866b-8x16.fnt cp866c-8x16.fnt cp1251-8x8.fnt cp1251-8x14.fnt cp1251-8x16.fnt iso-8x8.fnt iso-8x14.fnt iso-8x16.fnt iso02-8x8.fnt iso02-8x14.fnt iso02-8x16.fnt iso04-8x8.fnt iso04-8x14.fnt iso04-8x16.fnt iso04-wide-8x16.fnt iso04-vga9-8x8.fnt iso04-vga9-8x14.fnt iso04-vga9-8x16.fnt iso04-vga9-wide-8x16.fnt iso08-8x8.fnt iso08-8x14.fnt iso08-8x16.fnt iso09-8x16.fnt iso15-8x8.fnt iso15-8x14.fnt iso15-8x16.fnt iso-thin-8x16.fnt iso15-thin-8x16.fnt koi8-r-8x8.fnt koi8-r-8x14.fnt koi8-r-8x16.fnt koi8-rb-8x16.fnt koi8-rc-8x16.fnt swiss-8x16.fnt swiss-8x8.fnt INDEX.fonts /vol2/5.0-current-chrootdir/usr/share/syscons/fonts ===> share/syscons/keymaps install -c -o root -g wheel -m 444 INDEX.keymaps be.iso.kbd be.iso.acc.kbd bg.bds.ctrlcaps.kbd bg.phonetic.ctrlcaps.kbd br275.iso.kbd br275.iso.acc.kbd br275.cp850.kbd ce.iso2.kbd cs.latin2.qwertz.kbd cz.iso2.kbd danish.iso.kbd danish.cp865.kbd finnish.iso.kbd finnish.cp850.kbd estonian.iso.kbd estonian.iso15.kbd estonian.cp850.kbd fr.iso.kbd fr.iso.acc.kbd fr_CA.iso.acc.kbd german.iso.kbd german.cp850.kbd hr.iso.kbd hu.iso2.101keys.kbd hu.iso2.102keys.kbd icelandic.iso.kbd icelandic.iso.acc.kbd it.iso.kbd iw.iso8.kbd jp.106.kbd jp.106x.kbd lat-amer.kbd lt.iso4.kbd norwegian.iso.kbd pl_PL.ISO_8859-2.kbd pt.iso.kbd pt.iso.acc.kbd ru.koi8-r.kbd ru.koi8-r.shift.kbd ru.cp866.kbd si.iso.kbd sk.iso2.kbd spanish.iso.kbd spanish.iso.acc.kbd spanish.iso15.acc.kbd swedish.iso.kbd swedish.cp850.kbd swissfrench.iso.kbd swissfrench.iso.acc.kbd swissfrench.cp850.kbd swissgerman.iso.kbd swissgerman.iso.acc.kbd swissgerman.cp850.kbd tr.iso9.q.kbd ua.koi8-u.kbd uk.iso.kbd uk.iso-ctrl.kbd uk.! cp850.kbd uk.cp850-ctrl.kbd us.iso .kbd us.dvorak.kbd us.dvorakx.kbd us.emacs.kbd us.pc-ctrl.kbd us.unix.kbd /vol2/5.0-current-chrootdir/usr/share/syscons/keymaps ===> share/syscons/scrnmaps install -c -o root -g wheel -m 444 koi8-r2cp866.scm iso-8859-1_to_cp437.scm iso-8859-4_to_cp437.scm /vol2/5.0-current-chrootdir/usr/share/syscons/scrnmaps ===> share/tabset install -c -o root -g wheel -m 444 3101 9837 aa aed512 beehive diablo dtc382 hp700-wy ibm3101 std stdcrt tandem653 teleray vt100 vt100-w wyse-adds xerox1720 xerox1730 xerox1730-lm zenith29 /vol2/5.0-current-chrootdir/usr/share/tabset ===> share/termcap install -c -o root -g wheel -m 444 termcap termcap.db /vol2/5.0-current-chrootdir/usr/share/misc install -c -o root -g wheel -m 444 /usr/src/share/termcap/map3270 /vol2/5.0-current-chrootdir/usr/share/misc ===> share/timedef for l in cs_CZ.ISO_8859-2 da_DK.ISO_8859-1 de_AT.ISO_8859-1 de_DE.ISO_8859-1 en_GB.ISO_8859-1 en_US.ISO_8859-1 es_ES.ISO_8859-1 fi_FI.ISO_8859-1 fr_FR.ISO_8859-1 hr_HR.ISO_8859-2 hu_HU.ISO_8859-2 is_IS.ISO_8859-1 ja_JP.EUC ja_JP.SJIS it_IT.ISO_8859-1 ko_KR.EUC la_LN.ISO_8859-1 lt_LT.ISO_8859-4 nl_NL.ISO_8859-1 no_NO.ISO_8859-1 pl_PL.ISO_8859-2 pt_PT.ISO_8859-1 ru_SU.CP866 ru_SU.ISO_8859-5 ru_SU.KOI8-R sl_SI.ISO_8859-2 sv_SE.ISO_8859-1 tr_TR.ISO_8859-9 uk_UA.KOI8-U zh_CN.EUC zh_TW.Big5; do install -c -m 644 -o root -g wheel $l.out /vol2/5.0-current-chrootdir/usr/share/locale/$l/LC_TIME; done install: tr_TR.ISO_8859-9.out: No such file or directory *** Error code 71 Stop in /usr/src/share/timedef. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 1:45:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 8B55E37B422 for ; Tue, 19 Sep 2000 01:45:10 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e8J8ir718868; Tue, 19 Sep 2000 12:44:53 +0400 (MSD) (envelope-from ache) Date: Tue, 19 Sep 2000 12:44:49 +0400 From: "Andrey A. Chernov" To: Jordan Hubbard Cc: current@FreeBSD.ORG Subject: Re: USW2 Root: -current build report for Tue Sep 19 02:07:44 CDT 2000 Message-ID: <20000919124448.A17572@nagual.pp.ru> References: <23788.969350417@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <23788.969350417@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Tue, Sep 19, 2000 at 01:00:17AM -0700 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 19, 2000 at 01:00:17AM -0700, Jordan Hubbard wrote: > current current, who broke current. :) > ===> share/timedef > for l in cs_CZ.ISO_8859-2 da_DK.ISO_8859-1 de_AT.ISO_8859-1 de_DE.ISO_8859-1 en_GB.ISO_8859-1 en_US.ISO_8859-1 es_ES.ISO_8859-1 fi_FI.ISO_8859-1 fr_FR.ISO_8859-1 hr_HR.ISO_8859-2 hu_HU.ISO_8859-2 is_IS.ISO_8859-1 ja_JP.EUC ja_JP.SJIS it_IT.ISO_8859-1 ko_KR.EUC la_LN.ISO_8859-1 lt_LT.ISO_8859-4 nl_NL.ISO_8859-1 no_NO.ISO_8859-1 pl_PL.ISO_8859-2 pt_PT.ISO_8859-1 ru_SU.CP866 ru_SU.ISO_8859-5 ru_SU.KOI8-R sl_SI.ISO_8859-2 sv_SE.ISO_8859-1 tr_TR.ISO_8859-9 uk_UA.KOI8-U zh_CN.EUC zh_TW.Big5; do install -c -m 644 -o root -g wheel $l.out /vol2/5.0-current-chrootdir/usr/share/locale/$l/LC_TIME; done > install: tr_TR.ISO_8859-9.out: No such file or directory > *** Error code 71 It seems that your share/timedef/Makefile isn't updated properly - tr_TR.ISO_8859-9 _is_ there. I just test it on my local -current and not find the problem. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 1:52:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 8989337B424 for ; Tue, 19 Sep 2000 01:52:27 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e8J8qH919727; Tue, 19 Sep 2000 12:52:17 +0400 (MSD) (envelope-from ache) Date: Tue, 19 Sep 2000 12:52:16 +0400 From: "Andrey A. Chernov" To: Jordan Hubbard Cc: current@FreeBSD.ORG Subject: Re: USW2 Root: -current build report for Tue Sep 19 02:07:44 CDT 2000 Message-ID: <20000919125216.A19506@nagual.pp.ru> References: <23788.969350417@winston.osd.bsdi.com> <20000919124448.A17572@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000919124448.A17572@nagual.pp.ru>; from ache@nagual.pp.ru on Tue, Sep 19, 2000 at 12:44:49PM +0400 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 19, 2000 at 12:44:49PM +0400, Andrey A. Chernov wrote: > On Tue, Sep 19, 2000 at 01:00:17AM -0700, Jordan Hubbard wrote: > > current current, who broke current. :) > > > ===> share/timedef > > for l in cs_CZ.ISO_8859-2 da_DK.ISO_8859-1 de_AT.ISO_8859-1 de_DE.ISO_8859-1 en_GB.ISO_8859-1 en_US.ISO_8859-1 es_ES.ISO_8859-1 fi_FI.ISO_8859-1 fr_FR.ISO_8859-1 hr_HR.ISO_8859-2 hu_HU.ISO_8859-2 is_IS.ISO_8859-1 ja_JP.EUC ja_JP.SJIS it_IT.ISO_8859-1 ko_KR.EUC la_LN.ISO_8859-1 lt_LT.ISO_8859-4 nl_NL.ISO_8859-1 no_NO.ISO_8859-1 pl_PL.ISO_8859-2 pt_PT.ISO_8859-1 ru_SU.CP866 ru_SU.ISO_8859-5 ru_SU.KOI8-R sl_SI.ISO_8859-2 sv_SE.ISO_8859-1 tr_TR.ISO_8859-9 uk_UA.KOI8-U zh_CN.EUC zh_TW.Big5; do install -c -m 644 -o root -g wheel $l.out /vol2/5.0-current-chrootdir/usr/share/locale/$l/LC_TIME; done > > install: tr_TR.ISO_8859-9.out: No such file or directory > > *** Error code 71 > > It seems that your share/timedef/Makefile isn't updated properly - > tr_TR.ISO_8859-9 _is_ there. I just test it on my local -current and not > find the problem. Another possible place is your BSD.usr.dist isn't updated properly and tr_TR.ISO_8859-9 directory isn't there -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 1:56: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 290E737B422 for ; Tue, 19 Sep 2000 01:56:07 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8J8to624262; Tue, 19 Sep 2000 01:55:50 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: USW2 Root: -current build report for Tue Sep 19 02:07:44 CDT 2000 In-Reply-To: Message from "Andrey A. Chernov" of "Tue, 19 Sep 2000 12:52:16 +0400." <20000919125216.A19506@nagual.pp.ru> Date: Tue, 19 Sep 2000 01:55:50 -0700 Message-ID: <24258.969353750@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Another possible place is your BSD.usr.dist isn't updated properly and > tr_TR.ISO_8859-9 directory isn't there I'll try a quick update of current.freebsd.org and get back to you. Thanks for the quick response. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 2: 3:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id 1B78037B423 for ; Tue, 19 Sep 2000 02:03:07 -0700 (PDT) Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #20) id 13bJIv-0004Ym-00; Tue, 19 Sep 2000 11:03:05 +0200 Received: from a36d6.pppool.de ([213.6.54.214] helo=Magelan.Leidinger.net) by mx2.freenet.de with esmtp (Exim 3.16 #20) id 13bJIv-0007HH-00; Tue, 19 Sep 2000 11:03:05 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.0/8.11.0) with ESMTP id e8J8n8n01782; Tue, 19 Sep 2000 10:49:09 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200009190849.e8J8n8n01782@Magelan.Leidinger.net> Date: Tue, 19 Sep 2000 10:49:07 +0200 (CEST) From: Alexander Leidinger Subject: Re: SMPng feedback To: culverk@wam.umd.edu Cc: freebsd-current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Sep, Kenneth Wayne Culver wrote: > 1) When I'm playing music (mp3), and I move the mouse or move a window in > X, the sound stutters and I get a pcm0: hwptr went backwards x -> y (where > x and y are different numbers). I see this too. If I use xmms instead of mpg123 I didn't need to move the mouse. Perhaps something interrupt related. I see alot (more than usual) of interrupts in top (if the displayed information is correct). But perhaps this is just an "I want to see something different" experience, I have no similiar system to compare with. Bye, Alexander. -- The best things in life are free, but the expensive ones are still worth a look. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 6: 4:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from waterblue.imgsrc.co.jp (waterblue.imgsrc.co.jp [210.226.20.160]) by hub.freebsd.org (Postfix) with ESMTP id 381C037B422; Tue, 19 Sep 2000 06:04:42 -0700 (PDT) Received: from waterblue.imgsrc.co.jp (localhost [127.0.0.1]) by waterblue.imgsrc.co.jp (8.11.0/8.11.0) with ESMTP id e8JD37G81061; Tue, 19 Sep 2000 22:03:08 +0900 (JST) Date: Tue, 19 Sep 2000 22:03:07 +0900 Message-ID: <7m7l885yb8.wl@waterblue.imgsrc.co.jp> From: Jun Kuriyama To: imp@FreeBSD.org Cc: Current Subject: Re: cvs commit: src/sys/dev/pccard card_if.m pccard.c pccardvar.h src/sys/dev/ep if_ep_pccard.c src/sys/dev/sn if_sn.c if_sn_isa.c if_sn_pccard.c src/sys/pccard pccard_nbk.c In-Reply-To: In your message of "Mon, 18 Sep 2000 21:39:20 -0700 (PDT)" <200009190439.VAA18340@freefall.freebsd.org> References: <200009190439.VAA18340@freefall.freebsd.org> User-Agent: Wanderlust/1.1.1 (Purple Rain) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 12) (Channel Islands) (i386--freebsd) 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 X-Loop: FreeBSD.ORG At Mon, 18 Sep 2000 21:39:20 -0700 (PDT), Warner Losh wrote: > sn driver updated more than minorly. Add module dependencies to allow > module to load. Also change name to if_sn. Add some debugging code. > attempt to fix the cannot allocate memory problem I'd been seeing. > Minor formatting nits. After this commit, I cannot "make depend" for GENERIC configuration. % config GENERIC; cd ../../compile/GENERIC; make depend ... ===> sn @ -> /home/kuriyama/ncvs/src/sys machine -> /home/kuriyama/ncvs/src/sys/i386/include perl @/kern/makeobjops.pl -h @/kern/device_if.m perl @/kern/makeobjops.pl -h @/kern/bus_if.m perl @/kern/makeobjops.pl -h @/isa/isa_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/include /home/kuriyama/ncvs/src/sys/modules/sn/../../dev/sn/if_sn.c /home/kuriyama/ncvs/src/sys/modules/sn/../../dev/sn/if_sn_isa.c /home/kuriyama/ncvs/src/sys/modules/sn/../../dev/sn/if_sn_pccard.c /home/kuriyama/ncvs/src/sys/modules/sn/../../dev/sn/if_sn_pccard.c:60: card_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /home/kuriyama/ncvs/src/sys/modules/sn. *** Error code 1 Stop in /home/kuriyama/ncvs/src/sys/modules. *** Error code 1 Stop in /home/kuriyama/ncvs/src/sys/compile/GENERIC. -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 6: 7:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 066D237B43C for ; Tue, 19 Sep 2000 06:07:10 -0700 (PDT) Received: (qmail 903 invoked from network); 19 Sep 2000 13:07:09 -0000 Received: from acs-63-85-133-215.cvzoom.net (63.85.133.215) by ns.cvzoom.net with SMTP; 19 Sep 2000 13:07:09 -0000 Date: Tue, 19 Sep 2000 09:07:08 -0400 (EDT) From: Donn Miller To: Jun Kuriyama Cc: imp@FreeBSD.org, Current Subject: Re: cvs commit: src/sys/dev/pccard card_if.m pccard.c pccardvar.h src/sys/dev/ep if_ep_pccard.c src/sys/dev/sn if_sn.c if_sn_isa.c if_sn_pccard.c src/sys/pccard pccard_nbk.c In-Reply-To: <7m7l885yb8.wl@waterblue.imgsrc.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Sep 2000, Jun Kuriyama wrote: > At Mon, 18 Sep 2000 21:39:20 -0700 (PDT), > Warner Losh wrote: > > sn driver updated more than minorly. Add module dependencies to allow > > module to load. Also change name to if_sn. Add some debugging code. > > attempt to fix the cannot allocate memory problem I'd been seeing. > > Minor formatting nits. > > After this commit, I cannot "make depend" for GENERIC configuration. > > % config GENERIC; cd ../../compile/GENERIC; make depend > /home/kuriyama/ncvs/src/sys/modules/sn/../../dev/sn/if_sn_pccard.c:60: card_if.h: No such file or directory > mkdep: compile failed > *** Error code 1 I get the same error. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 6:40:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id 46F1937B424 for ; Tue, 19 Sep 2000 06:40:01 -0700 (PDT) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 90C522CE38; Tue, 19 Sep 2000 15:39:50 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.0/8.11.0) id e8JDdLw16061; Tue, 19 Sep 2000 15:39:21 +0200 (EET) (envelope-from vallo) Date: Tue, 19 Sep 2000 15:39:20 +0200 From: Vallo Kallaste To: Mike Meyer Cc: "Brandon D. Valentine" , current@FreeBSD.ORG Subject: Re: PRE_SMPNG snap Message-ID: <20000919153920.A16013@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <200009161725.KAA20319@pike.osd.bsdi.com> <14787.53656.382549.966793@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14787.53656.382549.966793@guru.mired.org>; from mwm@mired.org on Sat, Sep 16, 2000 at 03:01:28PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 16, 2000 at 03:01:28PM -0500, Mike Meyer wrote: > > I've had a ton of experience with ahc lately, as those of you who follow > > -questions, -stable, or -scsi know. r1.48 of aic7xxx.c is horribly > > broken. I can't get current snaps after that revision was committed to > > even boot on machines which use aic7892 or 29160 controllers. > > How about 7890 controllers? I was about to step from PRE_SMPNG back to > -current, but you've just made me nervous! My SMP system with onboard AIC-7896 wedges every night after some amount of nfs traffic. Buildworlds are usually successful as mentioned before, but heavy nfs traffic on 100Mbit/s segment seems to do it. I'm running pre-smpng because of that. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 7:25:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9A79637B424 for ; Tue, 19 Sep 2000 07:25:26 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id IAA94986; Tue, 19 Sep 2000 08:25:25 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id IAA38133; Tue, 19 Sep 2000 08:25:11 -0600 (MDT) Message-Id: <200009191425.IAA38133@harmony.village.org> To: Jun Kuriyama Subject: Re: cvs commit: src/sys/dev/pccard card_if.m pccard.c pccardvar.h src/sys/dev/ep if_ep_pccard.c src/sys/dev/sn if_sn.c if_sn_isa.c if_sn_pccard.c src/sys/pccard pccard_nbk.c Cc: Current In-reply-to: Your message of "Tue, 19 Sep 2000 22:03:07 +0900." <7m7l885yb8.wl@waterblue.imgsrc.co.jp> References: <7m7l885yb8.wl@waterblue.imgsrc.co.jp> <200009190439.VAA18340@freefall.freebsd.org> Date: Tue, 19 Sep 2000 08:25:11 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <7m7l885yb8.wl@waterblue.imgsrc.co.jp> Jun Kuriyama writes: : After this commit, I cannot "make depend" for GENERIC configuration. Thanks. CVS didn't commit the makefile change and then lost it :-(. I've fixed it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 7:40:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id E5A6937B422 for ; Tue, 19 Sep 2000 07:40:44 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e8JEehc00473 for current@freebsd.org; Tue, 19 Sep 2000 18:40:43 +0400 (MSD) (envelope-from ache) Date: Tue, 19 Sep 2000 18:40:43 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: recent kernel, microuptime went backwards Message-ID: <20000919184043.A346@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With very latest kernel I got lots of microuptime() went backwards (1.3624050 -> 1.998840) messages just before Mounting root from ufs:/dev/da0s1a -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 7:45: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta05.mail.mel.aone.net.au (mta05.mail.au.uu.net [203.2.192.85]) by hub.freebsd.org (Postfix) with ESMTP id E0E7737B43E for ; Tue, 19 Sep 2000 07:44:57 -0700 (PDT) Received: from camtech.net.au ([203.55.242.163]) by mta05.mail.mel.aone.net.au with ESMTP id <20000919144455.FORN413.mta05.mail.mel.aone.net.au@camtech.net.au> for ; Wed, 20 Sep 2000 00:44:55 +1000 Message-ID: <39C77C5F.1DEEA429@camtech.net.au> Date: Wed, 20 Sep 2000 00:16:55 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: CURRENT kernel make depend fails in sn module Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just synced my repo with cvsup4 and find that make depend fails. This is after "config -r MATT". "make includes" in /usr/src doesn't fix it either. ===> sn @ -> /usr/src/sys machine -> /usr/src/sys/i386/include perl @/kern/makeobjops.pl -h @/kern/device_if.m perl @/kern/makeobjops.pl -h @/kern/bus_if.m perl @/kern/makeobjops.pl -h @/isa/isa_if.m rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../include -I/usr/include /usr/src/sys/modules/sn/../../dev/sn/if_sn.c /usr/src/sys/modules/sn/../../dev/sn/if_sn_isa.c /usr/src/sys/modules/sn/../../dev/sn/if_sn_pccard.c /usr/src/sys/modules/sn/../../dev/sn/if_sn_pccard.c:60: card_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/sn. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys/compile/MATT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 8:27:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id EEF4D37B423 for ; Tue, 19 Sep 2000 08:27:22 -0700 (PDT) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id LAA10810; Tue, 19 Sep 2000 11:27:04 -0400 (EDT) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id LAA26875; Tue, 19 Sep 2000 11:27:03 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id LAA26871; Tue, 19 Sep 2000 11:27:03 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Tue, 19 Sep 2000 11:27:03 -0400 (EDT) From: Kenneth Wayne Culver To: Mark Murray Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMPng feedback In-Reply-To: <200009190642.e8J6gbn03428@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG IT's new as of last night. There is a random there, but it's not doing anything when I move the mouse. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 19 Sep 2000, Mark Murray wrote: > > 1) When I'm playing music (mp3), and I move the mouse or move a window in > > X, the sound stutters and I get a pcm0: hwptr went backwards x -> y (where > > x and y are different numbers). > > > > 2) the mouse is quite jumpy in X, especially while there is high cpu > > usage. I have tried to use both the usb mouse and the psm mouse (I have a > > usb to psm adapter) and the behaviour is the same with all mice I've > > tried. ( a logitec optical mouse, and a ms intellimouse with the ball, > > not optical) > > How old is your build? Do you have the kthreaded /dev/random driver? > (do a top -S and look for a process called "random" when you wiggle > your mouse). > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 8:28:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 88D4537B424 for ; Tue, 19 Sep 2000 08:28:42 -0700 (PDT) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id LAA10913; Tue, 19 Sep 2000 11:28:23 -0400 (EDT) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id LAA27305; Tue, 19 Sep 2000 11:28:23 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id LAA27300; Tue, 19 Sep 2000 11:28:23 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Tue, 19 Sep 2000 11:28:23 -0400 (EDT) From: Kenneth Wayne Culver To: Alexander Leidinger Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMPng feedback In-Reply-To: <200009190849.e8J8n8n01782@Magelan.Leidinger.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Personally, the whole system seems a bit sluggish with the SMPng stuff there... I'm assuming this will be fixed later. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Tue, 19 Sep 2000, Alexander Leidinger wrote: > On 18 Sep, Kenneth Wayne Culver wrote: > > > 1) When I'm playing music (mp3), and I move the mouse or move a window in > > X, the sound stutters and I get a pcm0: hwptr went backwards x -> y (where > > x and y are different numbers). > > I see this too. > > If I use xmms instead of mpg123 I didn't need to move the mouse. Perhaps > something interrupt related. I see alot (more than usual) of interrupts > in top (if the displayed information is correct). But perhaps this is > just an "I want to see something different" experience, I have no > similiar system to compare with. > > Bye, > Alexander. > > -- > The best things in life are free, but the > expensive ones are still worth a look. > > http://www.Leidinger.net Alexander @ Leidinger.net > GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 8:51:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta04.mail.mel.aone.net.au (mta04.mail.au.uu.net [203.2.192.84]) by hub.freebsd.org (Postfix) with ESMTP id EF45B37B423 for ; Tue, 19 Sep 2000 08:51:44 -0700 (PDT) Received: from camtech.net.au ([203.55.243.199]) by mta04.mail.mel.aone.net.au with ESMTP id <20000919155142.HTHX374.mta04.mail.mel.aone.net.au@camtech.net.au>; Wed, 20 Sep 2000 01:51:42 +1000 Message-ID: <39C78C08.4D98F0C3@camtech.net.au> Date: Wed, 20 Sep 2000 01:23:44 +0930 From: Matthew Thyer X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Donn Miller Cc: current@freebsd.org Subject: Re: CURRENT kernel make depend fails in sn module References: <39C77C5F.1DEEA429@camtech.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Thyer wrote: > mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ > -I@/../include -I/usr/include > /usr/src/sys/modules/sn/../../dev/sn/if_sn.c > /usr/src/sys/modules/sn/../../dev/sn/if_sn_isa.c > /usr/src/sys/modules/sn/../../dev/sn/if_sn_pccard.c > /usr/src/sys/modules/sn/../../dev/sn/if_sn_pccard.c:60: card_if.h: No > such file or directory > mkdep: compile failed > *** Error code 1 > > Stop in /usr/src/sys/modules/sn. Warner's fixed this so update again To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 9: 3:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8A26337B422 for ; Tue, 19 Sep 2000 09:03:22 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA95591; Tue, 19 Sep 2000 10:03:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA38891; Tue, 19 Sep 2000 10:03:03 -0600 (MDT) Message-Id: <200009191603.KAA38891@harmony.village.org> To: Donn Miller Subject: Re: buildkernel problems Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 19 Sep 2000 03:26:32 EDT." <39C71528.DEED8617@cvzoom.net> References: <39C71528.DEED8617@cvzoom.net> Date: Tue, 19 Sep 2000 10:03:03 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39C71528.DEED8617@cvzoom.net> Donn Miller writes: : Here's problems I'm having with the latest (as of now) cvsup'd sources. I fixed this as of 8:35am MDT today. Sorry about any inconveince my incomplete checkin caused. This is one reason I don't like the modules/foo dev/foo split we have today. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 9: 4:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 328F637B422 for ; Tue, 19 Sep 2000 09:04:31 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA95603; Tue, 19 Sep 2000 10:04:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA38918; Tue, 19 Sep 2000 10:04:12 -0600 (MDT) Message-Id: <200009191604.KAA38918@harmony.village.org> To: Jordan Hubbard Subject: Re: USW2 Root: -current build report for Tue Sep 19 02:07:44 CDT 2000 Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 19 Sep 2000 01:00:17 PDT." <23788.969350417@winston.osd.bsdi.com> References: <23788.969350417@winston.osd.bsdi.com> Date: Tue, 19 Sep 2000 10:04:12 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <23788.969350417@winston.osd.bsdi.com> Jordan Hubbard writes: : current current, who broke current. :) Hmmm. Someone else broke it too! We're sadly having a run on conical hats. Good thing I didn't throw mine away from the last time. My breakage was later, the one in sys/modules/sn. : install: tr_TR.ISO_8859-9.out: No such file or directory Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 9: 5:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2CC1037B424 for ; Tue, 19 Sep 2000 09:05:12 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA95615; Tue, 19 Sep 2000 10:05:11 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA38938; Tue, 19 Sep 2000 10:04:56 -0600 (MDT) Message-Id: <200009191604.KAA38938@harmony.village.org> Subject: Re: cvs commit: src/sys/dev/pccard card_if.m pccard.c pccardvar.h src/sys/dev/ep if_ep_pccard.c src/sys/dev/sn if_sn.c if_sn_isa.c if_sn_pccard.c src/sys/pccard pccard_nbk.c Cc: Jun Kuriyama , Current In-reply-to: Your message of "Tue, 19 Sep 2000 08:25:11 MDT." <200009191425.IAA38133@harmony.village.org> References: <200009191425.IAA38133@harmony.village.org> <7m7l885yb8.wl@waterblue.imgsrc.co.jp> <200009190439.VAA18340@freefall.freebsd.org> Date: Tue, 19 Sep 2000 10:04:56 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009191425.IAA38133@harmony.village.org> Warner Losh writes: : Thanks. CVS didn't commit the makefile change and then lost it :-(. : I've fixed it. Actually, CVS didn't eat the change, I just forgot to commit it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 10:43:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id AB9B737B43C for ; Tue, 19 Sep 2000 10:43:26 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13bRQQ-000F8v-00; Tue, 19 Sep 2000 19:43:23 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8JHden00622; Tue, 19 Sep 2000 19:39:42 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009191739.e8JHden00622@grimreaper.grondar.za> To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMPng feedback References: In-Reply-To: ; from Kenneth Wayne Culver "Tue, 19 Sep 2000 11:27:03 -0400." Date: Tue, 19 Sep 2000 19:39:40 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > IT's new as of last night. There is a random there, but it's not doing > anything when I move the mouse. OK - its not my random driver, then :-). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 11:23:30 2000 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 E506237B422 for ; Tue, 19 Sep 2000 11:23:23 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id FAA23924; Wed, 20 Sep 2000 05:23:07 +1100 Date: Wed, 20 Sep 2000 05:23:03 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards In-Reply-To: <20000919184043.A346@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Sep 2000, Andrey A. Chernov wrote: > With very latest kernel I got lots of > > microuptime() went backwards (1.3624050 -> 1.998840) > > messages just before > > Mounting root from ufs:/dev/da0s1a It really does go backwards. This is caused by the giant lock preventing the clock interrupt task from running soon enough. The giant lock can also prevent the clock interrupt task from running often enough even after booting. E.g., "dd if=/dev/random of=/dev/null bs=large" does several bad things. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 11:29:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id 0CC4837B423; Tue, 19 Sep 2000 11:29:34 -0700 (PDT) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id UAA68967; Tue, 19 Sep 2000 20:29:19 +0200 (CEST) Message-Id: <200009191829.UAA68967@midten.fast.no> To: root@nihil.plaut.de Cc: grog@lemis.com, current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: Debugging -current SMPNG HANG on heavy disk-io From: Tor.Egge@fast.no In-Reply-To: Your message of "Sun, 17 Sep 2000 16:29:41 +0200 (CEST)" References: X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Sep 2000 20:29:18 +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (kgdb) ps > pid proc addr uid pri ppid pgrp flag stat comm wchan > 37 c7874a00 c9665000 0 32 6 36 004086 3 tar piperd c9663f20 > 36 c7874bc0 c960a000 0 32 6 36 004006 3 tar FFS node c02f4220 This looks like you've hit the limit for the FFS node memory type. vmstat -m will indicate if this is correct. If you see somethinig like Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) [....] FFS node262144 65536K 65536K 65536K 2024460 0 6 256 [....] Memory Totals: In Use Free Requests 93897K 608K 9482590 (i.e. MemUse == Limit), then you've hit the limit. The process allocating a FFS node normally holds a vnode lock, resulting in a cascade of vnode locks and a frozen system. Increasing the kmem_map size (by setting a loader variable (kern.vm.kmem.size) or defining VM_KMEM_SIZE and VM_KMEM_SIZE_MAX in the kernel config file) should help. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 11:30:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id B5BD637B422 for ; Tue, 19 Sep 2000 11:30:39 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8JIUPN92162; Tue, 19 Sep 2000 20:30:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards In-Reply-To: Your message of "Wed, 20 Sep 2000 05:23:03 +1100." Date: Tue, 19 Sep 2000 20:30:25 +0200 Message-ID: <92160.969388225@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bruce Eva ns writes: >On Tue, 19 Sep 2000, Andrey A. Chernov wrote: > >> With very latest kernel I got lots of >> >> microuptime() went backwards (1.3624050 -> 1.998840) >> >> messages just before >> >> Mounting root from ufs:/dev/da0s1a > >It really does go backwards. This is caused by the giant lock preventing >the clock interrupt task from running soon enough. The giant lock can >also prevent the clock interrupt task from running often enough even >after booting. E.g., "dd if=/dev/random of=/dev/null bs=large" does >several bad things. Yes, we are royally hosed right now with respect to interrupt service. It's a testimony to the robustness of the majority of our drivers that they don't explode more often than they do. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 11:36: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from cosrel2.hp.com (cosrel2.hp.com [156.153.255.162]) by hub.freebsd.org (Postfix) with ESMTP id 418F637B423; Tue, 19 Sep 2000 11:36:01 -0700 (PDT) Received: from udlkern.fc.hp.com (udlkern.fc.hp.com [15.1.52.48]) by cosrel2.hp.com (Postfix) with ESMTP id B3B619DF; Tue, 19 Sep 2000 12:34:54 -0600 (MDT) Received: from udlkern.fc.hp.com (erdos.fc.hp.com [15.1.54.169]) by udlkern.fc.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 SMKit7.0) id MAA19602; Tue, 19 Sep 2000 12:35:08 -0600 (MDT) Message-ID: <39C7B1DC.632CC701@udlkern.fc.hp.com> Date: Tue, 19 Sep 2000 12:35:08 -0600 From: "Andrew M. Miklic" X-Mailer: Mozilla 4.72 [en] (X11; U; HP-UX B.11.00 9000/785) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: bus_space_subregion()? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All, I'm trying to port the TGA/TGA2 driver from NetBSD to FreeBSD, and there is a function used throughout the code (bus_space_subregion()) that has a prototype defined in FreeBSD, but no code associated with it--does anyone know if there is a functional equivalent? Andrew Miklic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 11:55:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (zoom0-062.telepath.com [216.14.0.62]) by hub.freebsd.org (Postfix) with SMTP id 5D67837B422 for ; Tue, 19 Sep 2000 11:55:48 -0700 (PDT) Received: (qmail 20408 invoked by uid 100); 19 Sep 2000 18:55:34 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14791.46758.482319.577085@guru.mired.org> Date: Tue, 19 Sep 2000 13:55:34 -0500 (CDT) To: vallo@matti.ee Cc: "Brandon D. Valentine" , current@FreeBSD.ORG Subject: Re: PRE_SMPNG snap In-Reply-To: <20000919153920.A16013@myhakas.matti.ee> References: <200009161725.KAA20319@pike.osd.bsdi.com> <14787.53656.382549.966793@guru.mired.org> <20000919153920.A16013@myhakas.matti.ee> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vallo Kallaste writes: > On Sat, Sep 16, 2000 at 03:01:28PM -0500, Mike Meyer wrote: > > > > I've had a ton of experience with ahc lately, as those of you who follow > > > -questions, -stable, or -scsi know. r1.48 of aic7xxx.c is horribly > > > broken. I can't get current snaps after that revision was committed to > > > even boot on machines which use aic7892 or 29160 controllers. > > How about 7890 controllers? I was about to step from PRE_SMPNG back to > > -current, but you've just made me nervous! > My SMP system with onboard AIC-7896 wedges every night after some > amount of nfs traffic. Buildworlds are usually successful as > mentioned before, but heavy nfs traffic on 100Mbit/s segment seems > to do it. I'm running pre-smpng because of that. Since it's still coming up, my SMP system with onboard AIC-7890 boots and runs fine. However, it's not very heavily loaded. To: Tor.Egge@fast.no Cc: root@nihil.plaut.de, grog@lemis.com, FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io In-Reply-To: <200009191829.UAA68967@midten.fast.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Sep 2000 Tor.Egge@fast.no wrote: ... > This looks like you've hit the limit for the FFS node memory type. > > vmstat -m will indicate if this is correct. > ... > Increasing the kmem_map size (by setting a loader variable > (kern.vm.kmem.size) or defining VM_KMEM_SIZE and VM_KMEM_SIZE_MAX in > the kernel config file) should help. I'll try. Thanks for the hint! BTW: Is it possible to dynamically adjust the limit of the node mem? The system shouldn't freeze anyway. Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 12:51:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id D53A337B424; Tue, 19 Sep 2000 12:51:39 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id VAA20806; Tue, 19 Sep 2000 21:50:45 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.0/8.8.8) with ESMTP id e8JKnm000329; Tue, 19 Sep 2000 22:49:48 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Tue, 19 Sep 2000 22:49:47 +0200 (CEST) From: Michael Reifenberger To: Tor.Egge@fast.no Cc: grog@lemis.com, FreeBSD-Current , FreeBSD-SMP Subject: Re: Debugging -current SMPNG HANG on heavy disk-io In-Reply-To: <200009191829.UAA68967@midten.fast.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, 19 Sep 2000 Tor.Egge@fast.no wrote: ... > This looks like you've hit the limit for the FFS node memory type. BINGO! > FFS node262144 65536K 65536K 65536K 2024460 0 6 256 So the symptom is clear. But the cause? With pre SMPng I had the default kmem sizes (which is 12MB I think). Now I bumped kern.vm.kmem.size 4 times to 40960000 (which leads to 20k max-mem for FFS node) and still can't tar /usr/ports to /dev/null! Where comes the increased memory consumption from ?!? BTW: What is the KMEM exactly: Kernel real memory? Kernel virtual memory? Thanks anyway for your answer and your efforts! Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 12:54: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from area51.slashnet.org (area51.slashnet.org [208.222.214.95]) by hub.freebsd.org (Postfix) with ESMTP id CF76C37B423; Tue, 19 Sep 2000 12:54:03 -0700 (PDT) Received: from edgemaster.zombie.org (edgemaster.creighton.edu [147.134.107.69]) by area51.slashnet.org (Postfix) with ESMTP id B07AD14D544; Tue, 19 Sep 2000 15:54:01 -0400 (EDT) Received: by edgemaster.zombie.org (Postfix, from userid 1001) id B9D7698F5; Tue, 19 Sep 2000 14:53:49 -0500 (CDT) Date: Tue, 19 Sep 2000 14:53:49 -0500 From: Sean Kelly To: stable@freebsd.org, current@freebsd.org Subject: 'host' command with CNAMEs Message-ID: <20000919145349.A28511@edgemaster.zombie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got two machines here, one running 4.1-STABLE (from Aug 3) and a 5.0-CURRENT (from Aug 10) and both of them show the same issue. When you use the 'host' command to resolve a CNAME, it will show all the A records twice: (7) smkelly@edgemaster:~$ host www.microsoft.com www.microsoft.com is a nickname for microsoft.com microsoft.com has address 207.46.130.45 microsoft.com has address 207.46.230.218 microsoft.com has address 207.46.230.219 microsoft.com has address 207.46.230.218 microsoft.com has address 207.46.230.219 microsoft.com has address 207.46.130.45 The host command never used to behave in this way and I'm not sure if it is a bug with the program itself or the resolver. -- Sean Kelly or PGP KeyID: 4AC781C7 http://www.sean-kelly.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 13:42:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B260537B422; Tue, 19 Sep 2000 13:42:46 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA96925; Tue, 19 Sep 2000 14:42:45 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA41378; Tue, 19 Sep 2000 14:42:30 -0600 (MDT) Message-Id: <200009192042.OAA41378@harmony.village.org> To: "Andrew M. Miklic" Subject: Re: bus_space_subregion()? Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 19 Sep 2000 12:35:08 MDT." <39C7B1DC.632CC701@udlkern.fc.hp.com> References: <39C7B1DC.632CC701@udlkern.fc.hp.com> Date: Tue, 19 Sep 2000 14:42:30 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39C7B1DC.632CC701@udlkern.fc.hp.com> "Andrew M. Miklic" writes: : is a function used throughout the code (bus_space_subregion()) that has : a prototype defined in FreeBSD, but no code associated with it--does : anyone know if there is a functional equivalent? No. I'm fairly sure that there's no equivalent. These interfaces post date the import from NetBSD of the bus_space interface. We should likely add them, as they are useful. They are trivial to implement on i386 and alpha given that bus_space_handle_t is basically an int. On pc98 these will be harder to implement, but shouldn't be too bad. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 14:26:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 0223037B422 for ; Tue, 19 Sep 2000 14:26:52 -0700 (PDT) Received: (qmail 7001 invoked from network); 19 Sep 2000 21:26:51 -0000 Received: from acs-24-154-11-27.zoominternet.net (24.154.11.27) by scully.zoominternet.net with SMTP; 19 Sep 2000 21:26:51 -0000 Date: Tue, 19 Sep 2000 17:26:50 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-11-27.zoominternet.net To: Bruce Evans Cc: "Andrey A. Chernov" , current@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Sep 2000, Bruce Evans wrote: > On Tue, 19 Sep 2000, Andrey A. Chernov wrote: > > > microuptime() went backwards (1.3624050 -> 1.998840) > It really does go backwards. This is caused by the giant lock preventing > the clock interrupt task from running soon enough. The giant lock can > also prevent the clock interrupt task from running often enough even > after booting. E.g., "dd if=/dev/random of=/dev/null bs=large" does > several bad things. I've noticed that, every time I do ntpdate, my clock loses about 5-11 seconds per hour. At first I thought it may have been my CMOS battery, but maybe it's that microuptime() thing that's causing it. (I've got a UP machine.) - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 14:47:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 386BF37B422; Tue, 19 Sep 2000 14:47:44 -0700 (PDT) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=root) by scientia.demon.co.uk with esmtp (Exim 3.16 #1) id 13bVAe-000IC6-00; Tue, 19 Sep 2000 22:43:20 +0100 Received: (from ben@localhost) by strontium.scientia.demon.co.uk (8.9.3/8.9.3) id WAA88217; Tue, 19 Sep 2000 22:43:19 +0100 (BST) (envelope-from ben) Date: Tue, 19 Sep 2000 22:43:19 +0100 From: Ben Smithurst To: Sean Kelly Cc: stable@freebsd.org, current@freebsd.org Subject: Re: 'host' command with CNAMEs Message-ID: <20000919224319.E30774@strontium.scientia.demon.co.uk> References: <20000919145349.A28511@edgemaster.zombie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000919145349.A28511@edgemaster.zombie.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Kelly wrote: > I've got two machines here, one running 4.1-STABLE (from Aug 3) and a > 5.0-CURRENT (from Aug 10) and both of them show the same issue. When > you use the 'host' command to resolve a CNAME, it will show all the A > records twice: The problem is older than that: ben@magnesium:~$ host www www.scientia.demon.co.uk is a nickname for magnesium.scientia.demon.co.uk magnesium.scientia.demon.co.uk has address 192.168.91.34 magnesium.scientia.demon.co.uk has address 192.168.91.34 ben@magnesium:~$ uname -rsm FreeBSD 3.4-STABLE i386 ISTR when the problem first cropped up it was briefly mentioned, but evidently no-one could be bothered to fix it at the time. -- Ben Smithurst / ben@FreeBSD.org / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 15:22:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 3BBB037B422; Tue, 19 Sep 2000 15:22:47 -0700 (PDT) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id PAA29581; Tue, 19 Sep 2000 15:22:44 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200009192222.PAA29581@freeway.dcfinc.com> Subject: Re: 'host' command with CNAMEs In-Reply-To: <20000919145349.A28511@edgemaster.zombie.org> from Sean Kelly at "Sep 19, 0 02:53:49 pm" To: smkelly@zombie.org (Sean Kelly) Date: Tue, 19 Sep 2000 15:22:43 -0700 (MST) Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Sean Kelly wrote: > I've got two machines here, one running 4.1-STABLE (from Aug 3) and a > 5.0-CURRENT (from Aug 10) and both of them show the same issue. When > you use the 'host' command to resolve a CNAME, it will show all the A > records twice: > > (7) smkelly@edgemaster:~$ host www.microsoft.com > www.microsoft.com is a nickname for microsoft.com > microsoft.com has address 207.46.130.45 > microsoft.com has address 207.46.230.218 > microsoft.com has address 207.46.230.219 > microsoft.com has address 207.46.230.218 > microsoft.com has address 207.46.230.219 > microsoft.com has address 207.46.130.45 > > The host command never used to behave in this way and I'm not sure if > it is a bug with the program itself or the resolver. From a 2.2.8-STABLE system: chad@freeway> host www.microsoft.com www.microsoft.com is a nickname for microsoft.com microsoft.com has address 207.46.230.219 microsoft.com has address 207.46.130.45 microsoft.com has address 207.46.230.218 microsoft.com mail is handled (pri=10) by mail2.microsoft.com microsoft.com mail is handled (pri=10) by mail3.microsoft.com microsoft.com mail is handled (pri=10) by mail4.microsoft.com microsoft.com mail is handled (pri=10) by mail5.microsoft.com microsoft.com mail is handled (pri=10) by mail1.microsoft.com -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 16:56:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 6DA9A37B422 for ; Tue, 19 Sep 2000 16:56:37 -0700 (PDT) Received: from rac1.wam.umd.edu (IDENT:root@rac1.wam.umd.edu [128.8.10.141]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA02283; Tue, 19 Sep 2000 19:56:24 -0400 (EDT) Received: from rac1.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id TAA04218; Tue, 19 Sep 2000 19:56:23 -0400 (EDT) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA04214; Tue, 19 Sep 2000 19:56:23 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Tue, 19 Sep 2000 19:56:22 -0400 (EDT) From: Kenneth Wayne Culver To: Mark Murray Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMPng feedback In-Reply-To: <200009191739.e8JHden00622@grimreaper.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK - its not my random driver, then :-). > Well, unless your random driver is not attached to the ums device... It does something when I use the mouse attached to the psm device... and the mouse is still jumpy. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 20: 7:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id DAC6737B422; Tue, 19 Sep 2000 20:07:51 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8K37lv57098; Wed, 20 Sep 2000 04:07:47 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8K36Os12846; Wed, 20 Sep 2000 04:06:24 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009200306.e8K36Os12846@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kris Kennaway Cc: Jason Evans , Konstantin Chuguev , Udo Schweigert , freebsd-current@FreeBSD.org, brian@Awfulhak.org Subject: Re: ssh and scp fail connecting to a root account In-Reply-To: Message from Kris Kennaway of "Sun, 17 Sep 2000 19:06:58 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 04:06:24 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 17 Sep 2000, Jason Evans wrote: > > > On Fri, Sep 15, 2000 at 03:40:12PM +0100, Konstantin Chuguev wrote: > > > Udo Schweigert wrote: > > > > > > > after a fresh build of -current openssh does not work if connecting to the > > > > root-user. For example (tested from a -stable machine, but the same from > > > > 4.1-RELEASE): > > > > > > Yes, I've been seeing the same thing since the checkout of the SMPng stuff... > > > No idea why it's happening. > > > > I've seen similar things intermittently over the past 10 days, and > > specifically the same problem for the past three days or so. I'm pretty > > sure that the problems have been associated with the random device rather > > than the SMP work specifically. > > Well, the crash is apparently due to malloc flags - remove the > /etc/malloc.conf link and it may work better. I've only seen this once, > and when I tried to run sshd under gdb it went away, and now I can't > reproduce it again. :-( Got it ! See version 1.6 of src/lib/libc/stdlib/setenv.c. This took me all night - Up for work in two hours !!! :-( > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 22:39:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id F263E37B422 for ; Tue, 19 Sep 2000 22:39:19 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e8K5b5t06699; Wed, 20 Sep 2000 09:37:05 +0400 (MSD) (envelope-from ache) Date: Wed, 20 Sep 2000 09:37:03 +0400 From: "Andrey A. Chernov" To: Poul-Henning Kamp Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards Message-ID: <20000920093702.A6671@nagual.pp.ru> References: <92160.969388225@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <92160.969388225@critter>; from phk@critter.freebsd.dk on Tue, Sep 19, 2000 at 08:30:25PM +0200 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Sep 19, 2000 at 08:30:25PM +0200, Poul-Henning Kamp wrote: > In message , Bruce Eva > ns writes: > >On Tue, 19 Sep 2000, Andrey A. Chernov wrote: > > > >> With very latest kernel I got lots of > >> > >> microuptime() went backwards (1.3624050 -> 1.998840) > >> > >> messages just before > >> > >> Mounting root from ufs:/dev/da0s1a > > > >It really does go backwards. This is caused by the giant lock preventing > >the clock interrupt task from running soon enough. The giant lock can > >also prevent the clock interrupt task from running often enough even > >after booting. E.g., "dd if=/dev/random of=/dev/null bs=large" does > >several bad things. > > Yes, we are royally hosed right now with respect to interrupt service. > > It's a testimony to the robustness of the majority of our drivers that > they don't explode more often than they do. It seems it was SCSI driver in my case waiting for SCSI device settle (or in some another state, I am not sure). BTW, could you please summarize this diagnostic? I.e. istead of tons of messages effectively overflowing dmesg buffer and maybe cause backwards by time consumed by themselfs put only one message summarizing all of them, something like "went backwards N times". -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 23:51:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 8A31637B424 for ; Tue, 19 Sep 2000 23:51:01 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8K6p0N94806 for ; Wed, 20 Sep 2000 08:51:00 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: 1131 unneeded includes in the kernel... From: Poul-Henning Kamp Date: Wed, 20 Sep 2000 08:50:59 +0200 Message-ID: <94804.969432659@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG UNNEEDED #includes in the FreeBSD kernel agp_if.c cam/cam_periph.c cam/scsi/scsi_all.c cam/scsi/scsi_ch.c cam/scsi/scsi_pass.c cam/scsi/scsi_ses.c cam/scsi/scsi_targ_bh.c coda/coda_fbsd.c coda/coda_namecache.c coda/coda_psdev.c coda/coda_subr.c coda/coda_venus.c coda/coda_vnops.c compat/linux/linux_file.c compat/linux/linux_misc.c compat/svr4/svr4_fcntl.c compat/svr4/svr4_sysent.c compat/svr4/svr4_termios.c contrib/dev/fla/fla.c contrib/dev/oltr/if_oltr.c crypto/blowfish/bf_skey.c crypto/cast128/cast128.c crypto/sha1.c dev/aac/aac.c dev/aac/aac_disk.c dev/aac/aac_pci.c dev/acpi/aml/aml_evalobj.c dev/acpi/aml/aml_obj.c dev/acpi/aml/aml_parse.c dev/advansys/adv_isa.c dev/advansys/advansys.c dev/advansys/advlib.c dev/advansys/adwlib.c dev/aha/aha.c dev/aha/aha_mca.c dev/aic/aic.c dev/aic/aic_cbus.c dev/aic/aic_isa.c dev/aic/aic_pccard.c dev/amr/amr.c dev/amr/amr_disk.c dev/amr/amr_pci.c dev/an/if_an.c dev/an/if_an_isa.c dev/an/if_an_pccard.c dev/an/if_an_pci.c dev/asr/asr.c dev/ata/ata-all.c dev/ata/ata-disk.c dev/ata/ata-dma.c dev/ata/atapi-cd.c dev/ata/atapi-fd.c dev/awi/awi.c dev/awi/awi_wep.c dev/awi/awi_wicfg.c dev/awi/if_awi_pccard.c dev/bktr/bktr_audio.c dev/bktr/bktr_card.c dev/bktr/bktr_core.c dev/bktr/bktr_i2c.c dev/bktr/bktr_os.c dev/bktr/bktr_tuner.c dev/buslogic/bt.c dev/dpt/dpt_scsi.c dev/ed/if_ed.c dev/ed/if_ed_cbus.c dev/ed/if_ed_isa.c dev/ed/if_ed_pci.c dev/en/midway.c dev/ep/if_ep.c dev/ep/if_ep_isa.c dev/ep/if_ep_mca.c dev/ep/if_ep_pccard.c dev/ex/if_ex.c dev/ex/if_ex_isa.c dev/fb/fb.c dev/fb/splash.c dev/fb/vga.c dev/fe/if_fe.c dev/fe/if_fe_cbus.c dev/fe/if_fe_isa.c dev/fe/if_fe_pccard.c dev/ida/ida_disk.c dev/iicbus/if_ic.c dev/iicbus/iicbb.c dev/iicbus/iiconf.c dev/iicbus/iicsmb.c dev/isp/isp_target.c dev/ispfw/ispfw.c dev/kbd/atkbd.c dev/kbd/kbd.c dev/lnc/if_lnc_isa.c dev/lnc/if_lnc_pci.c dev/mca/mca_bus.c dev/mii/brgphy.c dev/mii/dcphy.c dev/mii/mii_physubr.c dev/mii/pnphy.c dev/mii/ukphy_subr.c dev/mii/xmphy.c dev/mlx/mlx_disk.c dev/mly/mly.c dev/mly/mly_pci.c dev/nulldev/nulldev.c dev/pdq/if_fpa.c dev/ppbus/immio.c dev/ppbus/lpbb.c dev/ppbus/pcfclock.c dev/ppbus/ppb_base.c dev/ppbus/ppb_msq.c dev/ppbus/ppi.c dev/ppbus/vpo.c dev/ppbus/vpoio.c dev/randomdev/harvest.c dev/randomdev/hash.c dev/randomdev/randomdev.c dev/randomdev/yarrow.c dev/rp/rp_isa.c dev/rp/rp_pci.c dev/si/si.c dev/si/si2_z280.c dev/si/si3_t225.c dev/si/si_eisa.c dev/si/si_pci.c dev/smbus/smb.c dev/smbus/smbconf.c dev/smbus/smbus.c dev/sn/if_sn.c dev/sn/if_sn_isa.c dev/sn/if_sn_pccard.c dev/sound/isa/gusc.c dev/sound/pci/csa.c dev/sound/pci/csapcm.c dev/sound/pci/via82c686.c dev/streams/streams.c dev/sym/sym_hipd.c dev/syscons/scterm-dumb.c dev/syscons/scterm.c dev/tdfx/tdfx_pci.c dev/twe/twe_disk.c dev/usb/if_aue.c dev/usb/if_cue.c dev/usb/if_kue.c dev/usb/ohci.c dev/usb/udbp.c dev/usb/ugen.c dev/usb/uhci.c dev/usb/uhid.c dev/usb/ukbd.c dev/usb/ulpt.c dev/usb/umass.c dev/usb/umodem.c dev/usb/ums.c dev/usb/urio.c dev/usb/usb.c dev/usb/usb_ethersubr.c dev/usb/usb_subr.c dev/usb/usbdi.c dev/vinum/vinum.c dev/vinum/vinumdaemon.c dev/vinum/vinuminterrupt.c dev/vinum/vinumio.c dev/vinum/vinumparser.c dev/vinum/vinumraid5.c dev/vinum/vinumrequest.c dev/vn/vn.c dev/xe/if_xe.c i386/apm/apm.c i386/i386/db_interface.c i386/i386/identcpu.c i386/i386/mem.c i386/i386/mpapic.c i386/i386/nexus.c i386/i386/procfs_machdep.c i386/i386/synch_machdep.c i386/i386/trap.c i386/i386/vm86.c i386/isa/bs/bs.c i386/isa/bs/bsif.c i386/isa/cronyx.c i386/isa/if_ar.c i386/isa/if_rdp.c i386/isa/if_sr.c i386/isa/if_wi.c i386/isa/ipl_funcs.c i386/isa/isa_compat.c i386/isa/ithread.c i386/isa/pcf.c i386/isa/pcvt/pcvt_drv.c i386/isa/prof_machdep.c i386/linux/linprocfs/linprocfs_misc.c i386/linux/linprocfs/linprocfs_vfsops.c i386/linux/linprocfs/linprocfs_vnops.c i386/linux/linux_sysvec.c i386/svr4/svr4_machdep.c i4b/driver/i4b_ctl.c i4b/driver/i4b_ipr.c i4b/driver/i4b_isppp.c i4b/driver/i4b_rbch.c i4b/driver/i4b_tel.c i4b/driver/i4b_trace.c i4b/layer1/i4b_avm_a1.c i4b/layer1/i4b_bchan.c i4b/layer1/i4b_ctx_s0P.c i4b/layer1/i4b_drn_ngo.c i4b/layer1/i4b_elsa_pcc16.c i4b/layer1/i4b_elsa_qs1i.c i4b/layer1/i4b_elsa_qs1p.c i4b/layer1/i4b_hscx.c i4b/layer1/i4b_isic.c i4b/layer1/i4b_isic_isa.c i4b/layer1/i4b_l1.c i4b/layer1/i4b_l1fsm.c i4b/layer1/i4b_siemens_isurf.c i4b/layer1/i4b_sws.c i4b/layer1/i4b_tel_s016.c i4b/layer1/i4b_tel_s0163.c i4b/layer1/i4b_tel_s08.c i4b/layer2/i4b_iframe.c i4b/layer2/i4b_l2.c i4b/layer2/i4b_l2fsm.c i4b/layer2/i4b_l2timer.c i4b/layer2/i4b_lme.c i4b/layer2/i4b_mbuf.c i4b/layer2/i4b_sframe.c i4b/layer2/i4b_tei.c i4b/layer2/i4b_uframe.c i4b/layer2/i4b_util.c i4b/layer3/i4b_l2if.c i4b/layer3/i4b_l3fsm.c i4b/layer3/i4b_l3timer.c i4b/layer3/i4b_l4if.c i4b/layer3/i4b_q931.c i4b/layer3/i4b_q932fac.c i4b/layer4/i4b_i4bdrv.c i4b/layer4/i4b_l4.c i4b/layer4/i4b_l4mgmt.c i4b/layer4/i4b_l4timer.c i4b/tina-dd/i4b_tina_dd.c isa/atkbd_isa.c isa/atkbdc_isa.c isa/isa_common.c isa/pnpparse.c isa/psm.c isa/vga_isa.c isofs/cd9660/cd9660_util.c isofs/cd9660/cd9660_vnops.c kern/imgact_aout.c kern/imgact_elf.c kern/init_main.c kern/kern_acl.c kern/kern_cap.c kern/kern_clock.c kern/kern_conf.c kern/kern_event.c kern/kern_exec.c kern/kern_idle.c kern/kern_kthread.c kern/kern_mutex.c kern/kern_prot.c kern/kern_time.c kern/link_elf.c kern/subr_blist.c kern/subr_diskslice.c kern/subr_kobj.c kern/sys_process.c kern/sysv_msg.c kern/uipc_accf.c kern/uipc_mbuf2.c kern/vfs_bio.c kern/vfs_conf.c kern/vfs_default.c kern/vfs_subr.c kern/vfs_syscalls.c libkern/arc4random.c miibus_if.c miscfs/fdesc/fdesc_vnops.c miscfs/kernfs/kernfs_vfsops.c miscfs/procfs/procfs_ctl.c miscfs/procfs/procfs_dbregs.c miscfs/procfs/procfs_fpregs.c miscfs/procfs/procfs_map.c miscfs/procfs/procfs_mem.c miscfs/procfs/procfs_regs.c miscfs/procfs/procfs_subr.c miscfs/procfs/procfs_vnops.c miscfs/union/union_vnops.c net/bridge.c net/bsd_comp.c net/if_atmsubr.c net/if_ef.c net/if_faith.c net/if_gif.c net/if_iso88025subr.c net/if_loop.c net/if_stf.c net/if_tap.c net/intrq.c net/net_osdep.c net/pfil.c net/ppp_deflate.c net/ppp_tty.c net/zlib.c netatalk/ddp_input.c netatm/atm_subr.c netgraph/ng_async.c netgraph/ng_mppc.c netgraph/ng_ppp.c netgraph/ng_pptpgre.c netgraph/ng_tty.c netinet/accf_data.c netinet/accf_http.c netinet/fil.c netinet/in_gif.c netinet/in_proto.c netinet/in_rmx.c netinet/ip_auth.c netinet/ip_dummynet.c netinet/ip_ecn.c netinet/ip_encap.c netinet/ip_fil.c netinet/ip_frag.c netinet/ip_fw.c netinet/ip_input.c netinet/ip_log.c netinet/ip_mroute.c netinet/ip_nat.c netinet/ip_output.c netinet/ip_proxy.c netinet/ip_state.c netinet/tcp_input.c netinet/udp_usrreq.c netinet6/ah_core.c netinet6/ah_input.c netinet6/ah_output.c netinet6/dest6.c netinet6/esp_core.c netinet6/esp_input.c netinet6/esp_output.c netinet6/frag6.c netinet6/icmp6.c netinet6/in6.c netinet6/in6_cksum.c netinet6/in6_gif.c netinet6/in6_ifattach.c netinet6/in6_pcb.c netinet6/in6_proto.c netinet6/in6_rmx.c netinet6/in6_src.c netinet6/ip6_forward.c netinet6/ip6_fw.c netinet6/ip6_input.c netinet6/ip6_mroute.c netinet6/ip6_output.c netinet6/ipcomp_core.c netinet6/ipcomp_input.c netinet6/ipcomp_output.c netinet6/ipsec.c netinet6/mld6.c netinet6/nd6_nbr.c netinet6/nd6_rtr.c netinet6/raw_ip6.c netinet6/route6.c netinet6/scope6.c netinet6/udp6_output.c netinet6/udp6_usrreq.c netipx/ipx_input.c netkey/key.c netkey/key_debug.c netkey/keydb.c netnatm/natm_proto.c netncp/ncp_crypt.c netncp/ncp_nls.c netncp/ncp_rq.c netncp/ncp_subr.c nfs/krpc_subr.c nfs/nfs_node.c nfs/nfs_serv.c nfs/nfs_srvcache.c nfs/nfs_subs.c nfs/nfs_vnops.c ntfs/ntfs_compr.c ntfs/ntfs_ihash.c ntfs/ntfs_subr.c ntfs/ntfs_vfsops.c ntfs/ntfs_vnops.c nwfs/nwfs_ioctl.c nwfs/nwfs_node.c pc98/i386/machdep.c pc98/pc98/isa_dma.c pc98/pc98/sio.c pc98/pc98/wd.c pccard/pccard.c pccard/pccard_nbk.c pccard/pcic.c pci/agp.c pci/agp_ali.c pci/agp_amd.c pci/agp_i810.c pci/agp_intel.c pci/agp_sis.c pci/agp_via.c pci/alpm.c pci/amd.c pci/cy_pci.c pci/if_de.c pci/if_sf.c pci/if_sis.c pci/if_sk.c pci/if_ste.c pci/if_ti.c pci/if_tx.c pci/if_vr.c pci/if_wb.c pci/if_xl.c pci/intpm.c pci/ncr.c pci/ohci_pci.c pci/pci.c pci/pci_compat.c pci/pcisupport.c pci/uhci_pci.c posix4/ksched.c posix4/p1003_1b.c ufs/ffs/ffs_alloc.c ufs/ffs/ffs_snapshot.c ufs/ffs/ffs_softdep.c ufs/ffs/ffs_vfsops.c ufs/mfs/mfs_vfsops.c ufs/ufs/ufs_lookup.c usb_if.c vm/phys_pager.c vm/swap_pager.c vm/vm_glue.c vm/vm_page.c vm/vm_pager.c vm/vm_swap.c -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 23:56: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BF40337B423; Tue, 19 Sep 2000 23:55:59 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id XAA03318; Tue, 19 Sep 2000 23:55:59 -0700 Date: Tue, 19 Sep 2000 23:55:57 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... In-Reply-To: <94804.969432659@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How did you manage to generate this list. You're smoking crack on this one > dev/isp/isp_target.c > > as the isp_OS_PLATFORM.h includes is the only include this file has. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Sep 19 23:56:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2857737B422; Tue, 19 Sep 2000 23:56:41 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id XAA03326; Tue, 19 Sep 2000 23:56:41 -0700 Date: Tue, 19 Sep 2000 23:56:38 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... In-Reply-To: <94804.969432659@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh- don't get me wrong. Valuable info. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 0: 9:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 3567A37B423; Wed, 20 Sep 2000 00:09:44 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id DAA96653; Wed, 20 Sep 2000 03:10:21 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Wed, 20 Sep 2000 03:10:21 -0400 (EDT) From: "Brandon D. Valentine" To: Matthew Jacob Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Sep 2000, Matthew Jacob wrote: > >Oh- don't get me wrong. Valuable info. Thanks. What would be very cool is to feed this into another script which strips these unnecesary includes out. Then do a test build of LINT in your local tree and if it succeeds commit a mass removal of them. The same concept could be applied to the greater source tree. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 0:10:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id C745537B422 for ; Wed, 20 Sep 2000 00:10:10 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8K7A5N94925; Wed, 20 Sep 2000 09:10:06 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... In-Reply-To: Your message of "Tue, 19 Sep 2000 23:55:57 PDT." Date: Wed, 20 Sep 2000 09:10:05 +0200 Message-ID: <94923.969433805@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew J acob writes: > >How did you manage to generate this list. You're smoking >crack on this one > >> dev/isp/isp_target.c >> >> > >as the isp_OS_PLATFORM.h includes is the only include this file has. Well, According to src/tools/tools/kerninclude that include is not even needed. I'm not claiming that every single line is dogmatically true, but at least it merits some amount of investigation... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 0:10:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3A36037B422; Wed, 20 Sep 2000 00:10:28 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id AAA80124; Wed, 20 Sep 2000 00:10:28 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 20 Sep 2000 00:10:28 -0700 (PDT) From: Kris Kennaway To: "Brandon D. Valentine" Cc: Matthew Jacob , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Sep 2000, Brandon D. Valentine wrote: > On Tue, 19 Sep 2000, Matthew Jacob wrote: > > > > >Oh- don't get me wrong. Valuable info. Thanks. > > What would be very cool is to feed this into another script which strips > these unnecesary includes out. Then do a test build of LINT in your > local tree and if it succeeds commit a mass removal of them. The same > concept could be applied to the greater source tree. ...except to the KAME bits, where we don't make gratuitous changes. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 0:10:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 8896237B424 for ; Wed, 20 Sep 2000 00:10:46 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8K7AhN94954; Wed, 20 Sep 2000 09:10:43 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... In-Reply-To: Your message of "Tue, 19 Sep 2000 23:55:57 PDT." Date: Wed, 20 Sep 2000 09:10:43 +0200 Message-ID: <94952.969433843@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew J acob writes: > >How did you manage to generate this list. You're smoking >crack on this one > >> dev/isp/isp_target.c >> >> > >as the isp_OS_PLATFORM.h includes is the only include this file has. Oh, forgot to say: it could also be indicative of options not excercised by NOTES/LINT... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 0:12: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DCAE337B423; Wed, 20 Sep 2000 00:12:05 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA03448; Wed, 20 Sep 2000 00:12:03 -0700 Date: Wed, 20 Sep 2000 00:12:00 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Brandon D. Valentine" Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, but no. Let the MAINTAINERS shoot their own lines. A script with nag mail is good though. On Wed, 20 Sep 2000, Brandon D. Valentine wrote: > On Tue, 19 Sep 2000, Matthew Jacob wrote: > > > > >Oh- don't get me wrong. Valuable info. Thanks. > > What would be very cool is to feed this into another script which strips > these unnecesary includes out. Then do a test build of LINT in your > local tree and if it succeeds commit a mass removal of them. The same > concept could be applied to the greater source tree. > > Brandon D. Valentine > -- > bandix at looksharp.net | bandix at structbio.vanderbilt.edu > "Truth suffers from too much analysis." -- Ancient Fremen Saying > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 0:12:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 1E8D037B423 for ; Wed, 20 Sep 2000 00:12:15 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8K7C6N94999; Wed, 20 Sep 2000 09:12:06 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Brandon D. Valentine" Cc: Matthew Jacob , current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... In-Reply-To: Your message of "Wed, 20 Sep 2000 03:10:21 EDT." Date: Wed, 20 Sep 2000 09:12:06 +0200 Message-ID: <94997.969433926@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Br andon D. Valentine" writes: >On Tue, 19 Sep 2000, Matthew Jacob wrote: > >> >>Oh- don't get me wrong. Valuable info. Thanks. > >What would be very cool is to feed this into another script which strips >these unnecesary includes out. Then do a test build of LINT in your >local tree and if it succeeds commit a mass removal of them. The same >concept could be applied to the greater source tree. This is found by compiling i386/conf/GENERIC, i386/conf/NOTES, pc98/conf/GENERIC and all modules, but I cannot test on alpha and there are various bogosities which can give false positives on this list. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 0:17:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B32CB37B42C for ; Wed, 20 Sep 2000 00:17:49 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA03468; Wed, 20 Sep 2000 00:14:30 -0700 Date: Wed, 20 Sep 2000 00:14:28 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... In-Reply-To: <94923.969433805@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Sep 2000, Poul-Henning Kamp wrote: > In message , Matthew J > acob writes: > > > >How did you manage to generate this list. You're smoking > >crack on this one > > > >> dev/isp/isp_target.c > >> > >> > > > >as the isp_OS_PLATFORM.h includes is the only include this file has. > > Well, > > According to src/tools/tools/kerninclude that include is not even > needed. > > I'm not claiming that every single line is dogmatically true, but > at least it merits some amount of investigation... Sure. But your tool did not try the ISP_TARGET_MODE kernel option, which is what would then cause this file to even be compiled. The compile would fail, since 99% of all defined values, as in CT_SENDSTATUS and so on, are in files brought in by that header. I think I see what it is. The includes are outside the #ifdef ISP_TARGET_MODE but still.... As you say- merited investigation. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 0:18:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D6A4337B423 for ; Wed, 20 Sep 2000 00:18:22 -0700 (PDT) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA03472; Wed, 20 Sep 2000 00:15:14 -0700 Date: Wed, 20 Sep 2000 00:15:12 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... In-Reply-To: <94952.969433843@critter> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Sep 2000, Poul-Henning Kamp wrote: > In message , Matthew J > acob writes: > > > >How did you manage to generate this list. You're smoking > >crack on this one > > > >> dev/isp/isp_target.c > >> > >> > > > >as the isp_OS_PLATFORM.h includes is the only include this file has. > > Oh, forgot to say: it could also be indicative of options not > excercised by NOTES/LINT... Yup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 0:46:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 4B9C937B424; Wed, 20 Sep 2000 00:46:51 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8K7kji66814; Wed, 20 Sep 2000 00:46:45 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8K7iPx93296; Wed, 20 Sep 2000 00:44:25 -0700 (PDT) (envelope-from jhb) 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: Date: Wed, 20 Sep 2000 00:44:24 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Bruce Evans Subject: Re: recent kernel, microuptime went backwards Cc: current@FreeBSD.ORG, "Andrey A. Chernov" , smp@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Sep-00 Bruce Evans wrote: > On Tue, 19 Sep 2000, Andrey A. Chernov wrote: > >> With very latest kernel I got lots of >> >> microuptime() went backwards (1.3624050 -> 1.998840) >> >> messages just before >> >> Mounting root from ufs:/dev/da0s1a > > It really does go backwards. This is caused by the giant lock preventing > the clock interrupt task from running soon enough. The giant lock can > also prevent the clock interrupt task from running often enough even > after booting. E.g., "dd if=/dev/random of=/dev/null bs=large" does > several bad things. It's not the Giant lock that is at fault. We give up Giant during mi_switch(). Then scheduling problem is in the way that the top-level scheduler runs. We decide to schedule another process due to the timeslice ending during the clk interrupt thread. In the past, this was not run as a thread, so it ran, set the AST_* constant for needing a resched and then exited. During doreti, we notice an AST is pending and call ast(). ast() calls userret() which notices that a resched is needed and calls mi_switch(). In the New World Order, when the clock interrupt occurs, we set the AST_* constant for every interrupt before returning from sched_ithd(). This results in the actual interrupt threads being schedule from ast(). However, when the clk ithread finishes, it simply calls mi_switch() to enter the next process in ithd_loop(). The need_resched() that it sets isn't handled until the next call to userret() either via a hardware interrupt or a syscall return. Thus, the problem isn't due to Giant, but rather to interrupt threads. As for the micruptime() messages on boot, they only occur here on a UP kernel. On an SMP kernel I don't get them. Also, they always occur during mi_switch() when an interrupt thread is finishing and going back to sleep. The first such thread to be run to generate thet error message is the irq0: clk ithread, so the clk ithread is running fine. > Bruce -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 1: 0:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 7A37B37B422; Wed, 20 Sep 2000 01:00:37 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8K80Wi67069; Wed, 20 Sep 2000 01:00:32 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8K7wDM93377; Wed, 20 Sep 2000 00:58:13 -0700 (PDT) (envelope-from jhb) 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: <94804.969432659@critter> Date: Wed, 20 Sep 2000 00:58:13 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Poul-Henning Kamp Subject: RE: 1131 unneeded includes in the kernel... Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Sep-00 Poul-Henning Kamp wrote: > > UNNEEDED #includes in the FreeBSD kernel Err, how exactly are you generating these? > i386/i386/db_interface.c > If you compile a kernel with KTR and DDB. *bewm* If you are using LINT for these tests, then it probably means that the KTR #define's aren't in NOTES, which I'll put on the todo list. > i386/i386/synch_machdep.c > Err, if DDB is defined, this file looks at db_active, which is declared in -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 1: 8: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from goliath.siemens.de (goliath2.siemens.de [192.35.17.28]) by hub.freebsd.org (Postfix) with ESMTP id 904DF37B424; Wed, 20 Sep 2000 01:07:56 -0700 (PDT) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de) Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e8K87k308835; Wed, 20 Sep 2000 10:07:46 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail3.siemens.de (8.11.0/8.11.0) with ESMTP id e8K87kN10936876; Wed, 20 Sep 2000 10:07:46 +0200 (MEST) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.11.0/8.11.0/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id e8K87j408262; Wed, 20 Sep 2000 10:07:45 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.11.0/8.11.0/alaska [ $Revision: 1.4 ]) id e8K87j148224; Wed, 20 Sep 2000 08:07:45 GMT (envelope-from ust) Date: Wed, 20 Sep 2000 10:07:45 +0200 From: Udo Schweigert To: Brian Somers Cc: Kris Kennaway , Jason Evans , Konstantin Chuguev , freebsd-current@FreeBSD.ORG Subject: Re: ssh and scp fail connecting to a root account Message-ID: <20000920100745.A48205@alaska.cert.siemens.de> Mail-Followup-To: Brian Somers , Kris Kennaway , Jason Evans , Konstantin Chuguev , freebsd-current@FreeBSD.ORG References: <200009200306.e8K36Os12846@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009200306.e8K36Os12846@hak.lan.Awfulhak.org>; from brian@Awfulhak.org on Wed, Sep 20, 2000 at 04:06:24AM +0100 X-Operating-System: FreeBSD 4.1-STABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 20, 2000 at 04:06:24 +0100, Brian Somers wrote: > > On 17 Sep 2000, Jason Evans wrote: > > > > > On Fri, Sep 15, 2000 at 03:40:12PM +0100, Konstantin Chuguev wrote: > > > > Udo Schweigert wrote: > > > > > > > > > after a fresh build of -current openssh does not work if connecting to the > > > > > root-user. For example (tested from a -stable machine, but the same from > > > > > 4.1-RELEASE): > > > > > > > > Yes, I've been seeing the same thing since the checkout of the SMPng stuff... > > > > No idea why it's happening. > > > > > > I've seen similar things intermittently over the past 10 days, and > > > specifically the same problem for the past three days or so. I'm pretty > > > sure that the problems have been associated with the random device rather > > > than the SMP work specifically. > > > > Well, the crash is apparently due to malloc flags - remove the > > /etc/malloc.conf link and it may work better. I've only seen this once, > > and when I tried to run sshd under gdb it went away, and now I can't > > reproduce it again. :-( > > Got it ! > > See version 1.6 of src/lib/libc/stdlib/setenv.c. This took me all > night - Up for work in two hours !!! :-( > Perfect! Now it also works for me. Thank you very much, Brian. Best regards. -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : ust@cert.siemens.de PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 1:40: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id A36BE37B423 for ; Wed, 20 Sep 2000 01:39:59 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13bfQ0-0005rk-00; Wed, 20 Sep 2000 10:39:52 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id KAA07772; Wed, 20 Sep 2000 10:39:53 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 7437; Wed Sep 20 10:38:50 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13bfP0-00067N-00; Wed, 20 Sep 2000 10:38:50 +0200 From: Sheldon Hearn To: "Andrey A. Chernov" Cc: current@freebsd.org Subject: Re: recent kernel, microuptime went backwards In-reply-to: Your message of "Tue, 19 Sep 2000 18:40:43 +0400." <20000919184043.A346@nagual.pp.ru> Date: Wed, 20 Sep 2000 10:38:49 +0200 Message-ID: <23515.969439129@axl.fw.uunet.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Sep 2000 18:40:43 +0400, "Andrey A. Chernov" wrote: > With very latest kernel I got lots of > > microuptime() went backwards (1.3624050 -> 1.998840) > > messages just before I've also seen them for the first time with today's kernel. Interestingly, today's kernel also seems to attribute more than 99% of CPU to system, in spite of some CPU-bound userland processes running. If that's already been noted on this list, my apologies. I certainly haven't seen it mentioned, but I may have been reading too fast. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 5:23:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id A8F1D37B422; Wed, 20 Sep 2000 05:23:35 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8KCNZo28998; Wed, 20 Sep 2000 05:23:35 -0700 (PDT) Date: Wed, 20 Sep 2000 05:23:35 -0700 From: Alfred Perlstein To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... Message-ID: <20000920052335.K9141@fw.wintelcom.net> References: <94804.969432659@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <94804.969432659@critter>; from phk@FreeBSD.ORG on Wed, Sep 20, 2000 at 08:50:59AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Poul-Henning Kamp [000919 23:51] wrote: > > UNNEEDED #includes in the FreeBSD kernel > > agp_if.c > > [snip] These reports would be a lot more useful if you included the last person to touch these files along with the first line of the Copyright. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 5:27: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 205E837B424 for ; Wed, 20 Sep 2000 05:26:59 -0700 (PDT) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.0/8.11.0) with ESMTP id e8KCQwF00424 for ; Wed, 20 Sep 2000 05:26:58 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <5.0.0.25.2.20000920052526.00a56520@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 20 Sep 2000 05:26:58 -0700 To: current@freebsd.org From: Manfred Antar Subject: Current periodic change Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG periodic is broken in current # /usr/sbin/periodic daily /usr/sbin/periodic: 43: Syntax error: ")" unexpected (expecting ";;") ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 5:57:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from gemma.TechFak.Uni-Bielefeld.DE (gemma.TechFak.Uni-Bielefeld.DE [129.70.136.103]) by hub.freebsd.org (Postfix) with ESMTP id A8CF637B42C for ; Wed, 20 Sep 2000 05:57:06 -0700 (PDT) Received: from frizzantino.TechFak.Uni-Bielefeld.DE (frizzantino.TechFak.Uni-Bielefeld.DE [129.70.133.65]) by gemma.TechFak.Uni-Bielefeld.DE (8.9.1/8.9.1/TechFak/pk+ro20000427) with SMTP id OAA08924 for ; Wed, 20 Sep 2000 14:57:03 +0200 (MET DST) From: Oliver Schonefeld Received: by frizzantino.TechFak.Uni-Bielefeld.DE (SMI-8.6/pk970604A) id OAA08752; Wed, 20 Sep 2000 14:57:03 +0200 Date: Wed, 20 Sep 2000 14:57:03 +0200 To: freebsd-current@freebsd.org Subject: 5.0-20000917 Snapshot and Gericom Notebook -> bad crash Message-ID: <20000920145703.A8641@frizzantino.TechFak.Uni-Bielefeld.DE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Zen: Oooommmmmmmmmmmmmmmmmmmmmmm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello freebsd-current! The loader or the kernel crashed badly on my Gericom Overdose II notebook. I was trying to boot from the bootdisk-set. The mfsroot image is successfuly loaded and the "bootcountdown" ist displayed. After that it looks like there are some cpu-registers dumped. unfortunalty everything scrolls too fast, i cannot really read anything. It any aditional information is needed, please contact me. Regards, Oliver -- -------------------------------------------------------- And remember: "To Infinity And Far Beyond ... Somehow?!" email: oschonef@techfak.uni-bielefeld.de olli@psychopathen.org -------------------------------------------------------- Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! <- Save this lifeform ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 6:59: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id ACACF37B443 for ; Wed, 20 Sep 2000 06:59:00 -0700 (PDT) Received: (qmail 23775 invoked from network); 20 Sep 2000 13:58:51 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 20 Sep 2000 13:58:51 -0000 Date: Thu, 21 Sep 2000 00:58:47 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: John Baldwin Cc: current@FreeBSD.ORG, "Andrey A. Chernov" , smp@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 20 Sep 2000, John Baldwin wrote: > On 19-Sep-00 Bruce Evans wrote: > > It really does go backwards. This is caused by the giant lock preventing > > the clock interrupt task from running soon enough. The giant lock can > > also prevent the clock interrupt task from running often enough even > > after booting. E.g., "dd if=/dev/random of=/dev/null bs=large" does > > several bad things. > > It's not the Giant lock that is at fault. We give up Giant during mi_switch(). > Then scheduling problem is in the way that the top-level scheduler runs. Then the scheduler is more broken than I thought :-). Initially there may be a locking problem as well as a scheduling problem. Giving up Giant in the first mi_switch() is a bit late. mi_switch() uses microuptime(), and the clock task needs to be run before then to finish initialization of the timecounter. > We > decide to schedule another process due to the timeslice ending during the clk > interrupt thread. How can this work? The timeslice accounting stuff doesn't get updated until the clock task runs. > In the past, this was not run as a thread, so it ran, set > the AST_* constant for needing a resched and then exited. During doreti, we > notice an AST is pending and call ast(). ast() calls userret() which notices > that a resched is needed and calls mi_switch(). In the New World Order, when > the clock interrupt occurs, we set the AST_* constant for every interrupt > before returning from sched_ithd(). This results in the actual interrupt > threads being schedule from ast(). What should happen is for ast() to normally schedule the clock interrupt (and other interrupts) immediately (unless they are blocked). This doesn't seem to be working, and I can't see how it can work, since there is nothing except the giant lock to tell us whether interrupts are blocked, and the giant lock is held most of the time in system mode. Previously, cpl told us, but cpl is no longer maintained. > However, when the clk ithread finishes, it > simply calls mi_switch() to enter the next process in ithd_loop(). The > need_resched() that it sets isn't handled until the next call to userret() > either via a hardware interrupt or a syscall return. Thus, the problem isn't > due to Giant, but rather to interrupt threads. I think this is a different problem. It is similar to a problem for scheduling netisrs from non-interrupt context. schednetisr() sets the AST flag and some other flags. Nothing looks at these flags until an interrupt occurs or the process sleeps. Previously, this was handled in splx(): s = splnet(); /* s == 0 in process context. */ queue_net_output(...); schednetisr(...); splx(s); /* Since s == 0, the netisr gets run here. */ Will this work again as soom as splx() is replaced by mtx_exit(), etc? We only have a few thousand spls to change :(. > As for the micruptime() > messages on boot, they only occur here on a UP kernel. On an SMP kernel I > don't get them. Also, they always occur during mi_switch() when an interrupt > thread is finishing and going back to sleep. The first such thread to be run > to generate thet error message is the irq0: clk ithread, so the clk ithread is > running fine. They are very timing dependent, and probably also very task-mix dependent. The primary cause of microuptime() going backwards is tv_nsec overflowing if the system takes longer than 2^32 nsec (about 4 seconds) between the initialization of the timecounter and the timecounter maintenance for the first clock interrupt. On one of my systems, the first thread to call mi_switch() is the generic thread (proc0?) that executes run_interrupt_driven_hooks(). mi_switch() is called for the first time when the ata hook goes to sleep. Things would be a little different for SMP. Hopefully another cpu handles the clock interrupt. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 7:13:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 2B8CC37B422; Wed, 20 Sep 2000 07:13:45 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8KD2HN96421; Wed, 20 Sep 2000 15:02:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: John Baldwin Cc: Bruce Evans , current@FreeBSD.ORG, "Andrey A. Chernov" , smp@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards In-Reply-To: Your message of "Wed, 20 Sep 2000 00:44:24 PDT." Date: Wed, 20 Sep 2000 15:02:17 +0200 Message-ID: <96419.969454937@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , John Baldwin writes: >As for the micruptime() >messages on boot, they only occur here on a UP kernel. On an SMP kernel I >don't get them. Also, they always occur during mi_switch() when an interrupt >thread is finishing and going back to sleep. The first such thread to be run >to generate thet error message is the irq0: clk ithread, so the clk ithread is >running fine. The microuptime() messages occur because the timecounters expect the i8254 clock interrupt to run "hz" times per second, and it doesn't. In particular it doesn't during then 10-20 seconds we probe/attach devices. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 7:28:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from gifw.genroco.com (genroco.com [205.254.195.202]) by hub.freebsd.org (Postfix) with ESMTP id 6FB5B37B43C; Wed, 20 Sep 2000 07:28:44 -0700 (PDT) Received: from gi2.genroco.com (gi2.genroco.com [192.133.120.3]) by gifw.genroco.com (8.9.3/8.9.3) with ESMTP id JAA12063; Wed, 20 Sep 2000 09:28:43 -0500 Received: from scot.genroco.com (scot.genroco.com [192.133.120.125]) by gi2.genroco.com (8.9.3/8.9.3) with SMTP id JAA13640; Wed, 20 Sep 2000 09:28:37 -0500 Message-ID: <00f901c0230f$14219280$7d7885c0@genroco.com> From: "Scot W. Hetzel" To: "Roman Shterenzon" , Cc: , References: Subject: Re: rpc.lockd Date: Wed, 20 Sep 2000 09:28:36 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Roman Shterenzon" > On Tue, 19 Sep 2000 andrew@ugh.net.au wrote: > > Yeah probably should...perhaps suggest it to -docs. Someone (from > > something.edu, perhaps rpi.edu) posted a URL to one of the lists of a > > working but untested rpc.lockd. You might like to try it...if it gets > > enough testing it should make it in for 4.2 (one hopes). > > > > Andrew > > > Thanks, I'm ready to give it a try, does anyone the URL? > I'll search the archives meanwhile. > (Was it ported from NetBSD?) > I kind of remember reading about it on the current mailing list. Current-Users: Has a working rpc.lockd been imported into CURRENT. If it has, is there a possibility of getting it MFC'd to STABLE. Thanks, Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 7:53:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id C8D7C37B422 for ; Wed, 20 Sep 2000 07:53:06 -0700 (PDT) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id QAA19133; Wed, 20 Sep 2000 16:53:37 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 13blF9-0004uU-00 for ; Wed, 20 Sep 2000 16:53:03 +0200 Date: Wed, 20 Sep 2000 16:53:03 +0200 From: Szilveszter Adam To: freebsd-current@freebsd.org Subject: Floppy does not work now Message-ID: <20000920165303.A17621@petra.hos.u-szeged.hu> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everybody! I have upgraded to this morning's (CEST) -CURRENT (must have been around 07:00 UTC). Build and installworld went fine, kernel built succesfully. I did not change anything in the kernel config from the previous run (which was on 15th September) but when I rebooted with the new kernel, the floppy drive was not probed, and the fdc simply said: fdc0: cannot reserve I/O port range Now, this is funny, I have never experienced anything like this on FreeBSD:-) I do not know if this is a known issue (if so, tell me to RTFM) but if not, maybe someone may have an idea... I certainly have device fdc in my kernel config and the appropriate hints in my hints file. Output of 'boot -v', kernel config and hints file are available and I shall be happy to include all info you might need but simply I am at a loss here... Datapoint: No other issues have been sighted here recently, certainly none of the 'microuptime() went back...' stuff. Thanks for your time! -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 7:54:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id DEBCD37B423; Wed, 20 Sep 2000 07:54:22 -0700 (PDT) Received: from localhost (trish@localhost) by superconductor.rush.net (8.9.3/8.9.3) with ESMTP id KAA18244; Wed, 20 Sep 2000 10:54:21 -0400 (EDT) Date: Wed, 20 Sep 2000 10:54:21 -0400 (EDT) From: Siobhan Patricia Lynch X-Sender: trish@superconductor.rush.net To: John Baldwin Cc: Bruce Evans , current@FreeBSD.ORG, "Andrey A. Chernov" , smp@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John, I get these on an SMP kernel, which locks up the box, I can't even figure out where exactly its happening. Maybe I'm just missing something in my kernel config file? I assumed (from UPDATING) that no real change was needed to the SMP options? The hardware is an Intel N440BX motherboard with two PII333 procs. I'm not opposed to the option that this is *my* error and not SMPNG's PRE_SMPNG is VERY stable on this box, however the constant crashes (mostly during high I/O periods, such as make world) have made it impossible to use the machine for any type of real development under SMPNG. (which if I had time since the promotion, I'd be a bit crazy right now) If theres is anything I can do to help debug this, let me know, you can email me privately. -Trish __ Trish Lynch FreeBSD - The Power to Serve trish@bsdunix.net Rush Networking trish@rush.net VA Linux Systems trish@valinux.com O|S|D|N trish@osdn.com --- "So if you ask me how do I fell inside I could honestly Tell you we've been taken on a very long ride And if my owners let me have some free time some day With all good intention I would probably run away Clutching the short straw" -Marillion, That Time of the Night To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 8:14:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id 6A64437B422; Wed, 20 Sep 2000 08:14:55 -0700 (PDT) Received: from localhost (trish@localhost) by superconductor.rush.net (8.9.3/8.9.3) with ESMTP id LAA27302; Wed, 20 Sep 2000 11:14:54 -0400 (EDT) Date: Wed, 20 Sep 2000 11:14:54 -0400 (EDT) From: Siobhan Patricia Lynch X-Sender: trish@superconductor.rush.net To: John Baldwin Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: recent kernel, microuptime went backwards In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG more info, the N440BX has a symbios scsi card on board and an fxp card onboard. I'm using relatively old scsi drives (4500 RPM seagates and HP drives) I have softupdates on, and I'm now using COMPAT_OLDPCI for now, although I only turned it back on after seeing that was the only real change I made to my kernel config pre and post SMPNG. -Trish __ Trish Lynch FreeBSD - The Power to Serve trish@bsdunix.net Rush Networking trish@rush.net VA Linux Systems trish@valinux.com O|S|D|N trish@osdn.com --- "what makes me think i could start clean slated the hardest to learn was the least complicated" -Indigo Girls, Least Complicated To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 8:24: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.online.ie (mail.online.ie [213.159.130.68]) by hub.freebsd.org (Postfix) with SMTP id 0CACE37B424 for ; Wed, 20 Sep 2000 08:24:03 -0700 (PDT) Received: (qmail 10600 invoked from network); 20 Sep 2000 15:23:55 -0000 Received: from eth3.web1.www.online.ie (HELO web1.www.online.ie) (10.10.3.32) by eth3.mail1.mail.online.ie with SMTP; 20 Sep 2000 15:23:55 -0000 Received: (from nobody@localhost) by web1.www.online.ie with id QAA30543 for current@freebsd.org; Wed, 20 Sep 2000 16:23:55 +0100 From: X-Authentication-Warning: web1.www.online.ie: nobody set sender to bofh@online.ie using -f Message-ID: <969463435.39c8d68bb971d@mail.online.ie> Date: Wed, 20 Sep 2000 16:23:55 +0100 To: Subject: Breakage in SYSV emulation? MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: online.ie webmail (IMP/PHP) X-Originating-IP: 194.125.130.115 X-Sent-By: http://mail.online.ie/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, since this morning, the SysVR4 modules appear to be broken: [...] ===> streams make: don't know how to make @/svr4/svr4_types.h. Stop *** Error code 2 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys/compile/BOFH. Anyone know how to fix this? TIA, s. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 8:29:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.telemere.net (mail.telemere.net [63.224.9.4]) by hub.freebsd.org (Postfix) with ESMTP id 929C637B424 for ; Wed, 20 Sep 2000 08:29:20 -0700 (PDT) Received: by mail.telemere.net (Postfix, from userid 1001) id D2E2A20F01; Wed, 20 Sep 2000 10:34:34 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.telemere.net (Postfix) with ESMTP id CF8871D101; Wed, 20 Sep 2000 10:34:34 -0500 (CDT) Date: Wed, 20 Sep 2000 10:34:31 -0500 (CDT) From: Visigoth To: Szilveszter Adam Cc: freebsd-current@freebsd.org Subject: Re: Floppy does not work now In-Reply-To: <20000920165303.A17621@petra.hos.u-szeged.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Sep 2000, Szilveszter Adam wrote: > floppy drive was not probed, and the fdc simply said: > > fdc0: cannot reserve I/O port range You don't happen to have a DPT raid card in that do you? Just wondering if on the off chance it is related to my PR kern/21378. If not, oh well, just shootin in the dark... Visigoth Damieon Stark Sr. Unix Systems Administrator visigoth@telemere.net PGP Public Key: www.telemere.net/~visigoth/visigoth.asc ____________________________________________________________________________ | M$ -Where do you want to go today? | Linux -Where do you want to go tomorrow?| FreeBSD - The POWER to serve Freebsd -Are you guys coming or what? | http://www.freebsd.org | | - ---------------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1i iQA/AwUBOcjK+jnmC/+RTnGeEQKslgCeOLgbvRtx8fOPV0icc5SG43SwOa4AoJI5 gElU9WYtQKptpTQR1g6AcWZg =6f7y -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 8:40:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 3305537B43F for ; Wed, 20 Sep 2000 08:40:44 -0700 (PDT) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id RAA23703; Wed, 20 Sep 2000 17:41:10 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 13blzA-00057k-00; Wed, 20 Sep 2000 17:40:36 +0200 Date: Wed, 20 Sep 2000 17:40:36 +0200 From: Adam Szilveszter To: Visigoth Cc: freebsd-current@freebsd.org Subject: Re: Floppy does not work now Message-ID: <20000920174036.C17621@petra.hos.u-szeged.hu> Mail-Followup-To: Visigoth , freebsd-current@freebsd.org References: <20000920165303.A17621@petra.hos.u-szeged.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: ; from visigoth@telemere.net on Wed, Sep 20, 2000 at 10:34:31AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 20, 2000 at 10:34:31AM -0500, Visigoth wrote: > On Wed, 20 Sep 2000, Szilveszter Adam wrote: > > floppy drive was not probed, and the fdc simply said: > > > > fdc0: cannot reserve I/O port range > > You don't happen to have a DPT raid card in that do you? Just > wondering if on the off chance it is related to my PR kern/21378. If not, > oh well, just shootin in the dark... Uhm, no:-) This is a simple workstation with only an IDE disk and an ATAPI CD-ROM both as masters. And the floppy has *always* worked up till today, including with a kernel & world after the SMPng commit (they were from Sept 15th.) That's why I thought I'd bring it up... maybe it rings a bell with somebody. The drive seems to be okay and is probed by the BIOS on startup, so I could boot from it, but is not usable on FreeBSD for the time being:-( -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 8:55:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.telemere.net (mail.telemere.net [63.224.9.4]) by hub.freebsd.org (Postfix) with ESMTP id 1868937B422 for ; Wed, 20 Sep 2000 08:55:39 -0700 (PDT) Received: by mail.telemere.net (Postfix, from userid 1001) id AB9A520F01; Wed, 20 Sep 2000 11:00:53 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.telemere.net (Postfix) with ESMTP id A1A091D101; Wed, 20 Sep 2000 11:00:53 -0500 (CDT) Date: Wed, 20 Sep 2000 11:00:50 -0500 (CDT) From: Visigoth To: Adam Szilveszter Cc: freebsd-current@freebsd.org Subject: Re: Floppy does not work now In-Reply-To: <20000920174036.C17621@petra.hos.u-szeged.hu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 20 Sep 2000, Adam Szilveszter wrote: > > Uhm, no:-) Oh well... *sigh* no end in sight... It was worth a try ;) Visigoth Damieon Stark Sr. Unix Systems Administrator visigoth@telemere.net PGP Public Key: www.telemere.net/~visigoth/visigoth.asc ____________________________________________________________________________ | M$ -Where do you want to go today? | Linux -Where do you want to go tomorrow?| FreeBSD - The POWER to serve Freebsd -Are you guys coming or what? | http://www.freebsd.org | | - ---------------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.1i iQA/AwUBOcjRJDnmC/+RTnGeEQIDYgCfbe01rm7/lrkZIQLUrjsPB4vx4iwAoMM5 bg9A/5CG7bj4u/6Ou+oXysXx =+5wJ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 9:23:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 93C9337B424; Wed, 20 Sep 2000 09:23:21 -0700 (PDT) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA26891; Wed, 20 Sep 2000 10:23:18 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id KAA13332; Wed, 20 Sep 2000 10:23:14 -0600 (MDT) (envelope-from nate) Date: Wed, 20 Sep 2000 10:23:14 -0600 (MDT) Message-Id: <200009201623.KAA13332@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Brian Somers Cc: Kris Kennaway , Jason Evans , Konstantin Chuguev , Udo Schweigert , freebsd-current@FreeBSD.ORG Subject: Re: ssh and scp fail connecting to a root account In-Reply-To: <200009200306.e8K36Os12846@hak.lan.Awfulhak.org> References: <200009200306.e8K36Os12846@hak.lan.Awfulhak.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ OpenSSH failure with particular malloc.conf flags ] > Got it ! > > See version 1.6 of src/lib/libc/stdlib/setenv.c. This took me all > night - Up for work in two hours !!! :-( Good catch! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 9:28:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (backplane-inc.SanFranciscosfd.cw.net [206.24.214.242]) by hub.freebsd.org (Postfix) with ESMTP id 5B50F37B423; Wed, 20 Sep 2000 09:28:43 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.0/8.9.3) id e8KGSha44044; Wed, 20 Sep 2000 09:28:43 -0700 (PDT) (envelope-from dillon) Date: Wed, 20 Sep 2000 09:28:43 -0700 (PDT) From: Matt Dillon Message-Id: <200009201628.e8KGSha44044@earth.backplane.com> To: FreeBSD-Current , FreeBSD-SMP Subject: Congrats on the SMPng work! References: <20000918075518.H67912@wantadilla.lemis.com> <20000918080559.J67912@wantadilla.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sniff! I feel so left out, I have so little time to play these days. You guys are all doing really exciting work, congratulations! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 10:11:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9BDB537B424; Wed, 20 Sep 2000 10:11:09 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8KHAvi79595; Wed, 20 Sep 2000 10:10:57 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8KH9Na15429; Wed, 20 Sep 2000 10:09:23 -0700 (PDT) (envelope-from jhb) 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: Date: Wed, 20 Sep 2000 10:09:23 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Siobhan Patricia Lynch Subject: Re: recent kernel, microuptime went backwards Cc: smp@FreeBSD.ORG, "Andrey A. Chernov" , current@FreeBSD.ORG, Bruce Evans Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Sep-00 Siobhan Patricia Lynch wrote: > John, > I get these on an SMP kernel, which locks up the box, I can't even > figure out where exactly its happening. Maybe I'm just missing something > in my kernel config file? I assumed (from UPDATING) that no real change > was > needed to the SMP options? No, it is probably a bug in the code with this scheduling mess. On the quad xeon here, very recent kernels are spinning during the acd0 probe with interrupts disabled, so there may be a few places where interrupts aren't being handled properly.  -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 12: 2:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 91FCC37B422 for ; Wed, 20 Sep 2000 12:02:29 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA01304; Wed, 20 Sep 2000 13:02:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA48386; Wed, 20 Sep 2000 13:02:10 -0600 (MDT) Message-Id: <200009201902.NAA48386@harmony.village.org> To: Poul-Henning Kamp Subject: Re: 1131 unneeded includes in the kernel... Cc: mjacob@feral.com, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 20 Sep 2000 09:10:43 +0200." <94952.969433843@critter> References: <94952.969433843@critter> Date: Wed, 20 Sep 2000 13:02:10 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <94952.969433843@critter> Poul-Henning Kamp writes: : Oh, forgot to say: it could also be indicative of options not : excercised by NOTES/LINT... There are a few NEWCARD/OLDCARD issues that you catch here.... I'll fix the rest. Thanks! Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 12:39:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 74BDB37B422 for ; Wed, 20 Sep 2000 12:39:30 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8KJdJN98560; Wed, 20 Sep 2000 21:39:19 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: mjacob@feral.com, current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... In-Reply-To: Your message of "Wed, 20 Sep 2000 13:02:10 MDT." <200009201902.NAA48386@harmony.village.org> Date: Wed, 20 Sep 2000 21:39:19 +0200 Message-ID: <98558.969478759@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009201902.NAA48386@harmony.village.org>, Warner Losh writes: >In message <94952.969433843@critter> Poul-Henning Kamp writes: >: Oh, forgot to say: it could also be indicative of options not >: excercised by NOTES/LINT... > >There are a few NEWCARD/OLDCARD issues that you catch here.... I'll >fix the rest. Thanks! Yeah, from time to time we have mutually exclusive options, it may be an idea to introduce an LINT2 kernel to contain the options which cannot co-exist in LINT. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 12:43:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id AD5BE37B423 for ; Wed, 20 Sep 2000 12:43:33 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA01535; Wed, 20 Sep 2000 13:43:32 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA48918; Wed, 20 Sep 2000 13:43:14 -0600 (MDT) Message-Id: <200009201943.NAA48918@harmony.village.org> To: Poul-Henning Kamp Subject: Re: 1131 unneeded includes in the kernel... Cc: mjacob@feral.com, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 20 Sep 2000 21:39:19 +0200." <98558.969478759@critter> References: <98558.969478759@critter> Date: Wed, 20 Sep 2000 13:43:14 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <98558.969478759@critter> Poul-Henning Kamp writes: : In message <200009201902.NAA48386@harmony.village.org>, Warner Losh writes: : >In message <94952.969433843@critter> Poul-Henning Kamp writes: : >: Oh, forgot to say: it could also be indicative of options not : >: excercised by NOTES/LINT... : > : >There are a few NEWCARD/OLDCARD issues that you catch here.... I'll : >fix the rest. Thanks! : : Yeah, from time to time we have mutually exclusive options, it may : be an idea to introduce an LINT2 kernel to contain the options : which cannot co-exist in LINT. I'd planned on doing that when I had a working NEWCARD. That should happen fairly soon, if I can ever thread the knot on the legacy interface. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 12:46: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [64.20.73.233]) by hub.freebsd.org (Postfix) with ESMTP id 4663437B422 for ; Wed, 20 Sep 2000 12:45:58 -0700 (PDT) Received: from boomer.forrie.com (dhcp-north-71-168.navipath.net [64.20.71.168]) by forrie.net with id e8KJjqH66384 for ; Wed, 20 Sep 2000 15:45:52 -0400 (EDT) Message-Id: <5.0.0.25.2.20000920153739.02040eb0@64.20.73.233> X-Sender: forrie@64.20.73.233 X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 20 Sep 2000 15:39:20 -0400 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Initial installation console Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can the configuration for bootup and initial installation be configured to detect (and configure) a serial console. This would be very useful for rackmount systems. Yes, I know it can be done manually after the installation is completed with a monitor; but this would save some time. If I'm missing something obvious, please let me know. I just tested it with a 2u system, booted up with a serial console, and it wasn't detected. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 12:50:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3C26837B424 for ; Wed, 20 Sep 2000 12:50:20 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8KJoIH12683; Wed, 20 Sep 2000 12:50:18 -0700 (PDT) Date: Wed, 20 Sep 2000 12:50:18 -0700 From: Alfred Perlstein To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: Initial installation console Message-ID: <20000920125017.E9141@fw.wintelcom.net> References: <5.0.0.25.2.20000920153739.02040eb0@64.20.73.233> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <5.0.0.25.2.20000920153739.02040eb0@64.20.73.233>; from forrie@forrie.com on Wed, Sep 20, 2000 at 03:39:20PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Forrest Aldrich [000920 12:46] wrote: > Can the configuration for bootup and initial installation be configured to > detect (and configure) a serial console. This would be very useful for > rackmount systems. Yes, I know it can be done manually after the > installation is completed with a monitor; but this would save some time. > > If I'm missing something obvious, please let me know. I just tested it > with a 2u system, booted up with a serial console, and it wasn't detected. If you boot without a keyboard attached and make sure you're using "Com1" then it should work. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 13: 0:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 3C7CE37B422 for ; Wed, 20 Sep 2000 13:00:40 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8KJtsv61564; Wed, 20 Sep 2000 20:55:54 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8KJrZs17729; Wed, 20 Sep 2000 20:53:35 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009201953.e8KJrZs17729@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Meyer Cc: current@freebsd.org, brian@Awfulhak.org Subject: Re: periodic no longer usable by users? In-Reply-To: Message from Mike Meyer of "Mon, 18 Sep 2000 13:41:51 CDT." <14790.25071.254295.658898@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 20:53:35 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems that recent (the last two weeks?) changes to periodic have > changed things so that non-root users of it no longer get any output. > > A simple fix would be to change the default output to $USER (not yet > tested). However, having a user-specific periodic.conf would be a lot > more useful. But I wanted to see what others thought of it before > trying it. I've tweaked things so that the default is to send output to stdout again, and so that it uses ${TMPDIR:-/tmp} for it's temporary files. Let me know if there are any further problems. > Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 13: 4:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id E8AB937B423 for ; Wed, 20 Sep 2000 13:04:28 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA05217; Wed, 20 Sep 2000 13:05:02 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009202005.NAA05217@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Forrest Aldrich Cc: freebsd-current@freebsd.org Subject: Re: Initial installation console In-reply-to: Your message of "Wed, 20 Sep 2000 15:39:20 EDT." <5.0.0.25.2.20000920153739.02040eb0@64.20.73.233> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 13:05:02 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can the configuration for bootup and initial installation be configured to > detect (and configure) a serial console. This would be very useful for > rackmount systems. Yes, I know it can be done manually after the > installation is completed with a monitor; but this would save some time. Not at the moment, unfortunately. Due to some stupidity in modern BIOS code, the automatic keyboard detection that we used to do no longer works and had to be removed. If you can deal with booting from floppies, you can create /boot.config on the first floppy containing just '-h' and you'll get a serial console. If you're building a CDROM install distribution, vnconfig/mount the boot.flp image and do the same there. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 13:25:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id F318337B424 for ; Wed, 20 Sep 2000 13:25:20 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8KKKmv61684; Wed, 20 Sep 2000 21:20:48 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8KKIHs18061; Wed, 20 Sep 2000 21:18:17 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009202018.e8KKIHs18061@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Manfred Antar Cc: current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: Current periodic change In-Reply-To: Message from Manfred Antar of "Wed, 20 Sep 2000 05:26:58 PDT." <5.0.0.25.2.20000920052526.00a56520@pozo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Sep 2000 21:18:17 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > periodic is broken in current > > # /usr/sbin/periodic daily > /usr/sbin/periodic: 43: Syntax error: ")" unexpected (expecting ";;") Oops, fixed. Thanks. > ================================== > || null@pozo.com || > || Ph. (415) 681-6235 || > ================================== -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 13:49:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 8034737B424 for ; Wed, 20 Sep 2000 13:49:26 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8KKn7617865; Wed, 20 Sep 2000 13:49:07 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: Initial installation console In-Reply-To: Message from Forrest Aldrich of "Wed, 20 Sep 2000 15:39:20 EDT." <5.0.0.25.2.20000920153739.02040eb0@64.20.73.233> Date: Wed, 20 Sep 2000 13:49:07 -0700 Message-ID: <17861.969482947@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can the configuration for bootup and initial installation be configured to > detect (and configure) a serial console. This would be very useful for The current installation "detects" serial console situations if you have a BIOS capable of properly instructing the loader about this or if you explicitly boot with -P at the first-stage loader. After that, sysinstall should properly fail to open /dev/ttyv0 and trundle on using the serial console instead of a graphics card. My question is simply what you mean by "configure" in this context. You want it to write an /etc/ttys entry out for a specific serial device? I suppose we could also just turn the console entry on as a wimp-out in such scenarios and get away with it. That's assuming, of course, I am clear on what you mean. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Sep 20 23:25:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 3E58037B424; Wed, 20 Sep 2000 23:25:18 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13bznG-000Apq-00; Thu, 21 Sep 2000 08:25:15 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8L6LWn03710; Thu, 21 Sep 2000 08:21:32 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009210621.e8L6LWn03710@grimreaper.grondar.za> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... References: <94804.969432659@critter> In-Reply-To: <94804.969432659@critter> ; from Poul-Henning Kamp "Wed, 20 Sep 2000 08:50:59 +0200." Date: Thu, 21 Sep 2000 08:21:32 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > UNNEEDED #includes in the FreeBSD kernel : : > dev/randomdev/harvest.c > > > > > dev/randomdev/hash.c > > > > dev/randomdev/randomdev.c > > > > dev/randomdev/yarrow.c > > ... Thanks! Dealt with. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 0:40:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 520F537B422 for ; Thu, 21 Sep 2000 00:40:41 -0700 (PDT) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id AAA78883 for ; Thu, 21 Sep 2000 00:42:39 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id AAA38613 for current@FreeBSD.org; Thu, 21 Sep 2000 00:42:03 -0700 (PDT) (envelope-from john) Message-Id: <200009210742.AAA38613@john.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 21 Sep 2000 00:42:03 -0700 (PDT) From: John Baldwin To: current@FreeBSD.org Subject: A SMPng suggestion.. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you are running -current with the SMPng code, it would probably be very production to stick the following options in your kernel config, especially if you are having crashes: SMP_DEBUG DIAGNOSTIC INVARIANTS INVARIANT_SUPPORT Using these allow for more useful error messages allowing the developers to track down bugs that you may run into more easily. Thanks. -- 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 Thu Sep 21 1:24: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (server.geekhouse.net [64.81.6.52]) by hub.freebsd.org (Postfix) with ESMTP id 5DEC837B43C for ; Thu, 21 Sep 2000 01:24:03 -0700 (PDT) Received: from john.baldwin.cx (root@john.baldwin.cx [192.168.1.18]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id BAA79007; Thu, 21 Sep 2000 01:25:57 -0700 (PDT) (envelope-from john@baldwin.cx) Received: (from john@localhost) by john.baldwin.cx (8.9.3/8.9.3) id BAA38736; Thu, 21 Sep 2000 01:25:20 -0700 (PDT) (envelope-from john) Message-Id: <200009210825.BAA38736@john.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000920125017.E9141@fw.wintelcom.net> Date: Thu, 21 Sep 2000 01:25:20 -0700 (PDT) From: John Baldwin To: Alfred Perlstein Subject: Re: Initial installation console Cc: freebsd-current@FreeBSD.ORG, Forrest Aldrich Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Sep-00 Alfred Perlstein wrote: > * Forrest Aldrich [000920 12:46] wrote: >> Can the configuration for bootup and initial installation be configured to >> detect (and configure) a serial console. This would be very useful for >> rackmount systems. Yes, I know it can be done manually after the >> installation is completed with a monitor; but this would save some time. >> >> If I'm missing something obvious, please let me know. I just tested it >> with a 2u system, booted up with a serial console, and it wasn't detected. > > If you boot without a keyboard attached and make sure you're using > "Com1" then it should work. No, it doesn't. :( The probe keyboard option is off in both -stable and -current due to all the broken K7 motherboards running around whose keyboards weren't being recognized. If we can get some better keyboard probing code in boot2, then we can reactivate the option. However, before installing, you can mount the kernel floppy, and type 'echo -P > /mnt/boot.config' and then unmount the floppy and boot from the floppies to get the old behavior. > -Alfred -- 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 Thu Sep 21 2: 5:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (gate.interxion.com [194.153.74.13]) by hub.freebsd.org (Postfix) with ESMTP id E1F7537B42C for ; Thu, 21 Sep 2000 02:05:43 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id eBMA8Ul00956; Fri, 22 Dec 2000 11:08:30 +0100 (CET) (envelope-from adrian) Date: Fri, 22 Dec 2000 11:08:29 +0100 From: Adrian Chadd To: Marius Bendiksen Cc: freebsd-current@freebsd.org Subject: Re: OpenBSD errata 008 also applies to FreeBSD Message-ID: <20001222110829.A929@roaming.cacheboy.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from mbendiks@eunet.no on Fri, Jul 07, 2000 at 08:22:48PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 07, 2000, Marius Bendiksen wrote: > It appears msdosfs is using a vnode after having released its reference on > it, which could lead to a bad things under high load. I've patched the > OpenBSD errata to apply cleanly to FreeBSD. Yes, I remember you bringing this up a while back. I don't see anything wrong with the patch, and the last time I applied it and tested it my box stopped panicing under a test. :) Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 5: 3:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id B421B37B422; Thu, 21 Sep 2000 05:03:10 -0700 (PDT) Received: from login-1.eunet.no (login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id OAA61117; Thu, 21 Sep 2000 14:03:09 +0200 (CEST) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id OAA38313; Thu, 21 Sep 2000 14:03:09 +0200 (CEST) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Thu, 21 Sep 2000 14:03:09 +0200 (CEST) From: Marius Bendiksen To: Adrian Chadd Cc: freebsd-current@freebsd.org Subject: Re: OpenBSD errata 008 also applies to FreeBSD In-Reply-To: <20001222110829.A929@roaming.cacheboy.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It appears msdosfs is using a vnode after having released its reference on > > it, which could lead to a bad things under high load. I've patched the > > OpenBSD errata to apply cleanly to FreeBSD. > > Yes, I remember you bringing this up a while back. I don't see anything > wrong with the patch, and the last time I applied it and tested it my > box stopped panicing under a test. :) ISTR having made it available from home.eunet.no/~mbendiks as well, together with some other patches. I was planning on submitting them to the PR system RSN. Marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 5:48:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id A799B37B422 for ; Thu, 21 Sep 2000 05:48:33 -0700 (PDT) Received: (qmail 31869 invoked from network); 21 Sep 2000 12:48:32 -0000 Received: from acs-24-154-25-35.zoominternet.net (24.154.25.35) by scully.zoominternet.net with SMTP; 21 Sep 2000 12:48:32 -0000 Date: Thu, 21 Sep 2000 08:48:30 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-25-35.zoominternet.net To: current@freebsd.org Subject: buildkernel broken? Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2016032685-969540510=:11686" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-2016032685-969540510=:11686 Content-Type: TEXT/PLAIN; charset=US-ASCII An example of what I get when I try to do a make buildkernel. I have set KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. - Donn --0-2016032685-969540510=:11686 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="make.log" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="make.log" e3N0YW5kYXJkIGlucHV0fToyMzQyOiBFcnJvcjogU3VidHJhY3Rpb24gb2Yg dHdvIHN5bWJvbHMgaW4gZGlmZmVyZW50IHNlY3Rpb25zICIuZGF0YSIgey5k YXRhIHNlY3Rpb259IC0gIktFUk5CQVNFIiB7KlVORCogc2VjdGlvbn0gYXQg ZmlsZSBhZGRyZXNzIDkyOC4NCntzdGFuZGFyZCBpbnB1dH06MjM0NDogRXJy b3I6IFN1YnRyYWN0aW9uIG9mIHR3byBzeW1ib2xzIGluIGRpZmZlcmVudCBz ZWN0aW9ucyAicHJvYzBwYWRkciIgey5kYXRhIHNlY3Rpb259IC0gIktFUk5C QVNFIiB7KlVORCogc2VjdGlvbn0gYXQgZmlsZSBhZGRyZXNzIDk0MC4NCntz dGFuZGFyZCBpbnB1dH06MjM0NjogRXJyb3I6IFN1YnRyYWN0aW9uIG9mIHR3 byBzeW1ib2xzIGluIGRpZmZlcmVudCBzZWN0aW9ucyAiLmRhdGEiIHsuZGF0 YSBzZWN0aW9ufSAtICJLRVJOQkFTRSIgeypVTkQqIHNlY3Rpb259IGF0IGZp bGUgYWRkcmVzcyA5NDYuDQp7c3RhbmRhcmQgaW5wdXR9OjIzNDY6IEVycm9y OiBTdWJ0cmFjdGlvbiBvZiB0d28gc3ltYm9scyBpbiBkaWZmZXJlbnQgc2Vj dGlvbnMgIi5kYXRhIiB7LmRhdGEgc2VjdGlvbn0gLSAiS0VSTkJBU0UiIHsq VU5EKiBzZWN0aW9ufSBhdCBmaWxlIGFkZHJlc3MgOTU4Lg0Ke3N0YW5kYXJk IGlucHV0fToyMzQ3OiBFcnJvcjogU3VidHJhY3Rpb24gb2YgdHdvIHN5bWJv bHMgaW4gZGlmZmVyZW50IHNlY3Rpb25zICIuZGF0YSIgey5kYXRhIHNlY3Rp b259IC0gIktFUk5CQVNFIiB7KlVORCogc2VjdGlvbn0gYXQgZmlsZSBhZGRy ZXNzIDk3Ni4NCntzdGFuZGFyZCBpbnB1dH06MjM0OTogRXJyb3I6IFN1YnRy YWN0aW9uIG9mIHR3byBzeW1ib2xzIGluIGRpZmZlcmVudCBzZWN0aW9ucyAi LmRhdGEiIHsuZGF0YSBzZWN0aW9ufSAtICJLRVJOQkFTRSIgeypVTkQqIHNl Y3Rpb259IGF0IGZpbGUgYWRkcmVzcyA5ODIuDQp7c3RhbmRhcmQgaW5wdXR9 OjIzNDk6IEVycm9yOiBTdWJ0cmFjdGlvbiBvZiB0d28gc3ltYm9scyBpbiBk aWZmZXJlbnQgc2VjdGlvbnMgIi5kYXRhIiB7LmRhdGEgc2VjdGlvbn0gLSAi S0VSTkJBU0UiIHsqVU5EKiBzZWN0aW9ufSBhdCBmaWxlIGFkZHJlc3MgOTk0 Lg0Ke3N0YW5kYXJkIGlucHV0fToyMzUwOiBFcnJvcjogU3VidHJhY3Rpb24g b2YgdHdvIHN5bWJvbHMgaW4gZGlmZmVyZW50IHNlY3Rpb25zICJ2bTg2cGEi IHsuZGF0YSBzZWN0aW9ufSAtICJLRVJOQkFTRSIgeypVTkQqIHNlY3Rpb259 IGF0IGZpbGUgYWRkcmVzcyAxMDEyLg0Ke3N0YW5kYXJkIGlucHV0fToyMzUy OiBFcnJvcjogU3VidHJhY3Rpb24gb2YgdHdvIHN5bWJvbHMgaW4gZGlmZmVy ZW50IHNlY3Rpb25zICJ2bTg2cGFkZHIiIHsuZGF0YSBzZWN0aW9ufSAtICJL RVJOQkFTRSIgeypVTkQqIHNlY3Rpb259IGF0IGZpbGUgYWRkcmVzcyAxMDI0 Lg0Ke3N0YW5kYXJkIGlucHV0fToyMzY3OiBFcnJvcjogU3VidHJhY3Rpb24g b2YgdHdvIHN5bWJvbHMgaW4gZGlmZmVyZW50IHNlY3Rpb25zICJjcHVfZmVh dHVyZSIgey5kYXRhIHNlY3Rpb259IC0gIktFUk5CQVNFIiB7KlVORCogc2Vj dGlvbn0gYXQgZmlsZSBhZGRyZXNzIDEwMzQuDQp7c3RhbmRhcmQgaW5wdXR9 OjIzNzI6IEVycm9yOiBTdWJ0cmFjdGlvbiBvZiB0d28gc3ltYm9scyBpbiBk aWZmZXJlbnQgc2VjdGlvbnMgImV0ZXh0IiB7KlVORCogc2VjdGlvbn0gLSAi S0VSTkJBU0UiIHsqVU5EKiBzZWN0aW9ufSBhdCBmaWxlIGFkZHJlc3MgMTA1 MS4NCntzdGFuZGFyZCBpbnB1dH06MjM3NTogRXJyb3I6IFN1YnRyYWN0aW9u IG9mIHR3byBzeW1ib2xzIGluIGRpZmZlcmVudCBzZWN0aW9ucyAiLmRhdGEi IHsuZGF0YSBzZWN0aW9ufSAtICJLRVJOQkFTRSIgeypVTkQqIHNlY3Rpb259 IGF0IGZpbGUgYWRkcmVzcyAxMDc0Lg0Ke3N0YW5kYXJkIGlucHV0fToyMzc4 OiBFcnJvcjogU3VidHJhY3Rpb24gb2YgdHdvIHN5bWJvbHMgaW4gZGlmZmVy ZW50IHNlY3Rpb25zICJldGV4dCIgeypVTkQqIHNlY3Rpb259IC0gIktFUk5C QVNFIiB7KlVORCogc2VjdGlvbn0gYXQgZmlsZSBhZGRyZXNzIDEwOTYuDQp7 c3RhbmRhcmQgaW5wdXR9OjIzODQ6IEVycm9yOiBTdWJ0cmFjdGlvbiBvZiB0 d28gc3ltYm9scyBpbiBkaWZmZXJlbnQgc2VjdGlvbnMgImNwdV9mZWF0dXJl IiB7LmRhdGEgc2VjdGlvbn0gLSAiS0VSTkJBU0UiIHsqVU5EKiBzZWN0aW9u fSBhdCBmaWxlIGFkZHJlc3MgMTExNy4NCntzdGFuZGFyZCBpbnB1dH06MjM4 OTogRXJyb3I6IFN1YnRyYWN0aW9uIG9mIHR3byBzeW1ib2xzIGluIGRpZmZl cmVudCBzZWN0aW9ucyAiLmRhdGEiIHsuZGF0YSBzZWN0aW9ufSAtICJLRVJO QkFTRSIgeypVTkQqIHNlY3Rpb259IGF0IGZpbGUgYWRkcmVzcyAxMTM1Lg0K e3N0YW5kYXJkIGlucHV0fToyMzkyOiBFcnJvcjogU3VidHJhY3Rpb24gb2Yg dHdvIHN5bWJvbHMgaW4gZGlmZmVyZW50IHNlY3Rpb25zICIuZGF0YSIgey5k YXRhIHNlY3Rpb259IC0gIktFUk5CQVNFIiB7KlVORCogc2VjdGlvbn0gYXQg ZmlsZSBhZGRyZXNzIDExNTQuDQp7c3RhbmRhcmQgaW5wdXR9OjIzOTU6IEVy cm9yOiBTdWJ0cmFjdGlvbiBvZiB0d28gc3ltYm9scyBpbiBkaWZmZXJlbnQg c2VjdGlvbnMgIklkbGVQVEQiIHsuZGF0YSBzZWN0aW9ufSAtICJLRVJOQkFT RSIgeypVTkQqIHNlY3Rpb259IGF0IGZpbGUgYWRkcmVzcyAxMTc2Lg0Ke3N0 YW5kYXJkIGlucHV0fToyMzk3OiBFcnJvcjogU3VidHJhY3Rpb24gb2YgdHdv IHN5bWJvbHMgaW4gZGlmZmVyZW50IHNlY3Rpb25zICIuZGF0YSIgey5kYXRh IHNlY3Rpb259IC0gIktFUk5CQVNFIiB7KlVORCogc2VjdGlvbn0gYXQgZmls ZSBhZGRyZXNzIDExOTUuDQp7c3RhbmRhcmQgaW5wdXR9OjI0MDA6IEVycm9y OiBTdWJ0cmFjdGlvbiBvZiB0d28gc3ltYm9scyBpbiBkaWZmZXJlbnQgc2Vj dGlvbnMgIi5kYXRhIiB7LmRhdGEgc2VjdGlvbn0gLSAiS0VSTkJBU0UiIHsq VU5EKiBzZWN0aW9ufSBhdCBmaWxlIGFkZHJlc3MgMTIxOC4NCntzdGFuZGFy ZCBpbnB1dH06MjQwMjogRXJyb3I6IFN1YnRyYWN0aW9uIG9mIHR3byBzeW1i b2xzIGluIGRpZmZlcmVudCBzZWN0aW9ucyAiLmRhdGEiIHsuZGF0YSBzZWN0 aW9ufSAtICJLRVJOQkFTRSIgeypVTkQqIHNlY3Rpb259IGF0IGZpbGUgYWRk cmVzcyAxMjM3Lg0Ke3N0YW5kYXJkIGlucHV0fToyNDA3OiBFcnJvcjogU3Vi dHJhY3Rpb24gb2YgdHdvIHN5bWJvbHMgaW4gZGlmZmVyZW50IHNlY3Rpb25z ICIuZGF0YSIgey5kYXRhIHNlY3Rpb259IC0gIktFUk5CQVNFIiB7KlVORCog c2VjdGlvbn0gYXQgZmlsZSBhZGRyZXNzIDEyNzkuDQp7c3RhbmRhcmQgaW5w dXR9OjI0MTA6IEVycm9yOiBTdWJ0cmFjdGlvbiBvZiB0d28gc3ltYm9scyBp biBkaWZmZXJlbnQgc2VjdGlvbnMgIi5kYXRhIiB7LmRhdGEgc2VjdGlvbn0g LSAiS0VSTkJBU0UiIHsqVU5EKiBzZWN0aW9ufSBhdCBmaWxlIGFkZHJlc3Mg MTMwMi4NCntzdGFuZGFyZCBpbnB1dH06MjQxMjogRXJyb3I6IFN1YnRyYWN0 aW9uIG9mIHR3byBzeW1ib2xzIGluIGRpZmZlcmVudCBzZWN0aW9ucyAiLmRh dGEiIHsuZGF0YSBzZWN0aW9ufSAtICJLRVJOQkFTRSIgeypVTkQqIHNlY3Rp b259IGF0IGZpbGUgYWRkcmVzcyAxMzIxLg0Ke3N0YW5kYXJkIGlucHV0fToy NDE4OiBFcnJvcjogU3VidHJhY3Rpb24gb2YgdHdvIHN5bWJvbHMgaW4gZGlm ZmVyZW50IHNlY3Rpb25zICJ2bTg2cGEiIHsuZGF0YSBzZWN0aW9ufSAtICJL RVJOQkFTRSIgeypVTkQqIHNlY3Rpb259IGF0IGZpbGUgYWRkcmVzcyAxMzYz Lg0Ke3N0YW5kYXJkIGlucHV0fToyNDI0OiBFcnJvcjogU3VidHJhY3Rpb24g b2YgdHdvIHN5bWJvbHMgaW4gZGlmZmVyZW50IHNlY3Rpb25zICJ2bTg2cGEi IHsuZGF0YSBzZWN0aW9ufSAtICJLRVJOQkFTRSIgeypVTkQqIHNlY3Rpb259 IGF0IGZpbGUgYWRkcmVzcyAxNDA1Lg0Ke3N0YW5kYXJkIGlucHV0fToyNDMw OiBFcnJvcjogU3VidHJhY3Rpb24gb2YgdHdvIHN5bWJvbHMgaW4gZGlmZmVy ZW50IHNlY3Rpb25zICIuZGF0YSIgey5kYXRhIHNlY3Rpb259IC0gIktFUk5C QVNFIiB7KlVORCogc2VjdGlvbn0gYXQgZmlsZSBhZGRyZXNzIDE0MjguDQp7 c3RhbmRhcmQgaW5wdXR9OjI0MzM6IEVycm9yOiBTdWJ0cmFjdGlvbiBvZiB0 d28gc3ltYm9scyBpbiBkaWZmZXJlbnQgc2VjdGlvbnMgIklkbGVQVEQiIHsu ZGF0YSBzZWN0aW9ufSAtICJLRVJOQkFTRSIgeypVTkQqIHNlY3Rpb259IGF0 IGZpbGUgYWRkcmVzcyAxNDQ0Lg0Ke3N0YW5kYXJkIGlucHV0fToyNDM2OiBF cnJvcjogU3VidHJhY3Rpb24gb2YgdHdvIHN5bWJvbHMgaW4gZGlmZmVyZW50 IHNlY3Rpb25zICIuZGF0YSIgey5kYXRhIHNlY3Rpb259IC0gIktFUk5CQVNF IiB7KlVORCogc2VjdGlvbn0gYXQgZmlsZSBhZGRyZXNzIDE0NjcuDQp7c3Rh bmRhcmQgaW5wdXR9OjI0Mzk6IEVycm9yOiBTdWJ0cmFjdGlvbiBvZiB0d28g c3ltYm9scyBpbiBkaWZmZXJlbnQgc2VjdGlvbnMgIklkbGVQVEQiIHsuZGF0 YSBzZWN0aW9ufSAtICJLRVJOQkFTRSIgeypVTkQqIHNlY3Rpb259IGF0IGZp bGUgYWRkcmVzcyAxNDg2Lg0Ke3N0YW5kYXJkIGlucHV0fToyNDQyOiBFcnJv cjogU3VidHJhY3Rpb24gb2YgdHdvIHN5bWJvbHMgaW4gZGlmZmVyZW50IHNl Y3Rpb25zICJJZGxlUFREIiB7LmRhdGEgc2VjdGlvbn0gLSAiS0VSTkJBU0Ui IHsqVU5EKiBzZWN0aW9ufSBhdCBmaWxlIGFkZHJlc3MgMTUwOS4NCntzdGFu ZGFyZCBpbnB1dH06MjQ0NTogRXJyb3I6IFN1YnRyYWN0aW9uIG9mIHR3byBz eW1ib2xzIGluIGRpZmZlcmVudCBzZWN0aW9ucyAiSWRsZVBURCIgey5kYXRh IHNlY3Rpb259IC0gIktFUk5CQVNFIiB7KlVORCogc2VjdGlvbn0gYXQgZmls ZSBhZGRyZXNzIDE1MjguDQoqKiogRXJyb3IgY29kZSAxDQoNClN0b3AgaW4g L3Vzci9vYmovdXNyL3NyYy9zeXMvQ1VTVE9NLg0KKioqIEVycm9yIGNvZGUg MQ0KDQpTdG9wIGluIC91c3Ivc3JjLg0KKioqIEVycm9yIGNvZGUgMQ0KDQpT dG9wIGluIC91c3Ivc3JjLg0K --0-2016032685-969540510=:11686-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 6:35:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (gate.interxion.com [194.153.74.13]) by hub.freebsd.org (Postfix) with ESMTP id 08CEB37B422 for ; Thu, 21 Sep 2000 06:35:35 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id eBMEc9c00218; Fri, 22 Dec 2000 15:38:09 +0100 (CET) (envelope-from adrian) Date: Fri, 22 Dec 2000 15:38:09 +0100 From: Adrian Chadd To: Donn Miller Cc: freebsd-current@freebsd.org Subject: Re: buildkernel broken? Message-ID: <20001222153808.A202@roaming.cacheboy.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from dmmiller@cvzoom.net on Thu, Sep 21, 2000 at 08:48:30AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 21, 2000, Donn Miller wrote: > An example of what I get when I try to do a make buildkernel. I have set > KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. > > - Donn > {standard input}:2342: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 928. I get that too on a source tree cvsupped about an hour or two ago. Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 7: 1:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 9FD2C37B43C for ; Thu, 21 Sep 2000 07:01:09 -0700 (PDT) Received: (qmail 23496 invoked from network); 21 Sep 2000 14:01:00 -0000 Received: from acs-24-154-25-35.zoominternet.net (24.154.25.35) by scully.zoominternet.net with SMTP; 21 Sep 2000 14:01:00 -0000 Date: Thu, 21 Sep 2000 10:00:59 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-25-35.zoominternet.net To: Neil Blakey-Milner Cc: current@freebsd.org Subject: Re: buildkernel broken? In-Reply-To: <20000921145439.A13769@mithrandr.moria.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 21 Sep 2000, Neil Blakey-Milner wrote: > On Thu 2000-09-21 (08:48), Donn Miller wrote: > > An example of what I get when I try to do a make buildkernel. I have set > > KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. > > > > > {standard input}:2342: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 928. > > Do you have a populated /usr/obj? (ie, with nm) I've been doing "make buildkernel installkernel" in /usr/src without doing a "make buildworld" first. Is this OK? I guess the buildkernel created a /usr/obj, but I deleted it and tried buildkernel again with the same results. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 7:27:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by hub.freebsd.org (Postfix) with ESMTP id A407C37B423; Thu, 21 Sep 2000 07:27:41 -0700 (PDT) Received: by pcwin002.win.tue.nl (Postfix, from userid 1001) id 2062F13472; Thu, 21 Sep 2000 16:27:15 +0200 (CEST) Date: Thu, 21 Sep 2000 16:27:14 +0200 From: Stijn Hoop To: Donn Miller Cc: Neil Blakey-Milner , current@freebsd.org, stable@freebsd.org Subject: Re: buildkernel broken? Message-ID: <20000921162714.A61894@pcwin002.win.tue.nl> References: <20000921145439.A13769@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dmmiller@cvzoom.net on Thu, Sep 21, 2000 at 10:00:59AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 21, 2000 at 10:00:59AM -0400, Donn Miller wrote: > On Thu, 21 Sep 2000, Neil Blakey-Milner wrote: > > > On Thu 2000-09-21 (08:48), Donn Miller wrote: > > > An example of what I get when I try to do a make buildkernel. I have set > > > KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. > > > > > > > > {standard input}:2342: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 928. > > > > Do you have a populated /usr/obj? (ie, with nm) > > I've been doing "make buildkernel installkernel" in /usr/src without doing > a "make buildworld" first. Is this OK? I guess the buildkernel created a > /usr/obj, but I deleted it and tried buildkernel again with the same > results. > > - Donn > FWIW, I have the same problem on 4.1-STABLE cvsupped 10 mins ago from cvsup.nl.freebsd.org. I noticed these lines in the build log: ... cd /usr/obj/usr/src/sys/PCWIN002; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin MACHINE=i386 make KERNEL=kernel depend cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/i386/i386/genassym.c sh /usr/src/sys/kern/genassym.sh genassym.o > assym.s nm: could not exec elf/nm in /usr/obj/usr/src/i386/usr/libexec: No such file or directory rm -f param.c cp /usr/src/sys/conf/param.c . perl5 /usr/src/sys/kern/vnode_if.pl -h /usr/src/sys/kern/vnode_if.src ... Especially: nm: could not exec elf/nm in /usr/obj/usr/src/i386/usr/libexec: No such file or directory Which is quite correct since I blew away /usr/obj after my last buildworld (FreeBSD 4.1-STABLE #0: Wed Sep 13 14:45:31 CEST 2000). Is this a problem? Should I have done a buildworld before a buildkernel now? --Stijn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 7:41:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from scully.zoominternet.net (scully.zoominternet.net [63.67.120.3]) by hub.freebsd.org (Postfix) with SMTP id 5818437B422 for ; Thu, 21 Sep 2000 07:41:23 -0700 (PDT) Received: (qmail 29419 invoked from network); 21 Sep 2000 14:31:15 -0000 Received: from acs-24-154-25-35.zoominternet.net (24.154.25.35) by scully.zoominternet.net with SMTP; 21 Sep 2000 14:31:15 -0000 Date: Thu, 21 Sep 2000 10:31:05 -0400 (EDT) From: Donn Miller X-Sender: dmmiller@acs-24-154-25-35.zoominternet.net To: current@freebsd.org Subject: kldload and alternate kernel locations... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Normally, kldload can only find .ko modules in /boot/kernel. What if you have KERNEL=MYKERNEL set in /etc/make.conf, for instance, which will result in a kernel installed in /boot/MYKERNEL? kldload doesn't find the modules then (because all the .ko's are in /boot/MYKERNEL). I've first noticed this problem at start-up, when I got the message: green_saver: not found or something to that extent. Basically, there's a line in /etc/rc.i386 which says: kldstat -v | grep -q _saver || kldload ${saver}_saver I think we should change it to something like kldstat -v | grep -q _saver || kldload /boot/${kernel}/${saver}_saver because kldload can't find modules not installed in /boot/kernel. I think /etc/rc.i386 should include /boot/loader.conf to determine the location of the .ko modules, since that's where $kernel is defined. Another solution (instead of modifying rc.i386) would be to modify kldload so that it somehow checks the value of $kernel set in /boot/loader.conf to check the location of kernel modules. I think this is a more elegant solution, but I don't know if it's necessarily easier. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 8:33: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from imapserver1.fnal.gov (imapserver1.fnal.gov [131.225.9.6]) by hub.freebsd.org (Postfix) with ESMTP id 6FD3537B424; Thu, 21 Sep 2000 08:33:01 -0700 (PDT) Received: from SMTP ([131.225.9.6]) by imapserver1.fnal.gov (Netscape Messaging Server 3.62) with SMTP id 821; Thu, 21 Sep 2000 10:33:00 -0500 Received: from nova.fnal.gov ([131.225.18.207]) by 131.225.9.6 (Norton AntiVirus for Internet Email Gateways 1.0) ; Thu, 21 Sep 2000 15:32:59 0000 (GMT) Received: from localhost (tez@localhost) by nova.fnal.gov (8.9.3+Sun/8.9.1) with ESMTP id KAA06067; Thu, 21 Sep 2000 10:32:59 -0500 (CDT) X-Authentication-Warning: nova.fnal.gov: tez owned process doing -bs Date: Thu, 21 Sep 2000 10:32:59 -0500 (CDT) From: Tim Zingelman X-Sender: tez@nova.fnal.gov To: stable@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: 'host' command with CNAMEs In-Reply-To: <200009192222.PAA29581@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As I recall, Sean Kelly wrote: > > I've got two machines here, one running 4.1-STABLE (from Aug 3) and a > > 5.0-CURRENT (from Aug 10) and both of them show the same issue. When > > you use the 'host' command to resolve a CNAME, it will show all the A > > records twice: > > > > (7) smkelly@edgemaster:~$ host www.microsoft.com > > www.microsoft.com is a nickname for microsoft.com > > microsoft.com has address 207.46.130.45 > > microsoft.com has address 207.46.230.218 > > microsoft.com has address 207.46.230.219 > > microsoft.com has address 207.46.230.218 > > microsoft.com has address 207.46.230.219 > > microsoft.com has address 207.46.130.45 It is more complicated than that... the bug only shows up if you specify an alias name... $ host releng4.freebsd.org releng4.freebsd.org is a nickname for usw3.FreeBSD.org usw3.FreeBSD.org has address 209.180.6.227 usw3.FreeBSD.org has address 209.180.6.227 $ $ host usw3.freebsd.org usw3.freebsd.org has address 209.180.6.227 $ - Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 8:36:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from liam.london.sparza.com (liam.london.sparza.com [212.135.72.25]) by hub.freebsd.org (Postfix) with ESMTP id 67FA937B422; Thu, 21 Sep 2000 08:36:23 -0700 (PDT) Received: from hagop.london.sparza.com ([212.135.72.28]) by liam.london.sparza.com with esmtp (Exim 3.14 #3) id 13c8On-00038Z-00; Thu, 21 Sep 2000 16:36:33 +0100 Received: from localhost (scot@localhost) by hagop.london.sparza.com (8.9.3/8.9.3) with ESMTP id QAA03567; Thu, 21 Sep 2000 16:36:17 +0100 (BST) (envelope-from scot@london.sparza.com) Date: Thu, 21 Sep 2000 16:36:16 +0100 (BST) From: Scot Elliott To: Tim Zingelman Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 'host' command with CNAMEs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think this is a bug in that version of Bind as it also happens on my Solaris machine here on which I compiled up bind v8.2.2 recently... Scot On Thu, 21 Sep 2000, Tim Zingelman wrote: > > As I recall, Sean Kelly wrote: > > > I've got two machines here, one running 4.1-STABLE (from Aug 3) and a > > > 5.0-CURRENT (from Aug 10) and both of them show the same issue. When > > > you use the 'host' command to resolve a CNAME, it will show all the A > > > records twice: > > > > > > (7) smkelly@edgemaster:~$ host www.microsoft.com > > > www.microsoft.com is a nickname for microsoft.com > > > microsoft.com has address 207.46.130.45 > > > microsoft.com has address 207.46.230.218 > > > microsoft.com has address 207.46.230.219 > > > microsoft.com has address 207.46.230.218 > > > microsoft.com has address 207.46.230.219 > > > microsoft.com has address 207.46.130.45 > > It is more complicated than that... the bug only shows up if you specify > an alias name... > > $ host releng4.freebsd.org > releng4.freebsd.org is a nickname for usw3.FreeBSD.org > usw3.FreeBSD.org has address 209.180.6.227 > usw3.FreeBSD.org has address 209.180.6.227 > $ > $ host usw3.freebsd.org > usw3.freebsd.org has address 209.180.6.227 > $ > > - Tim > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" 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 Thu Sep 21 8:52:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id A105C37B422 for ; Thu, 21 Sep 2000 08:52:23 -0700 (PDT) Received: from v-ger.we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id RAA08377 for ; Thu, 21 Sep 2000 17:52:13 +0200 (MET DST) Received: from we.lc.ehu.es (localhost [127.0.0.1]) by v-ger.we.lc.ehu.es (8.9.3/8.9.3) with ESMTP id RAA00833 for ; Thu, 21 Sep 2000 17:39:08 +0200 (CEST) (envelope-from jose@we.lc.ehu.es) Message-ID: <39CA2B9C.DB675E0D@we.lc.ehu.es> Date: Thu, 21 Sep 2000 17:39:08 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: current@FreeBSD.org Subject: processes only consume system time ???? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This happens with freshly built -CURRENT, on an uniprocessor machine: $ cat loop.c main() { while (1); } $ time ./loop [ wait for ten seconds... ] ^C real 0m9.982s user 0m0.000s sys 0m5.689s Uh? Other utilities, such as top(1) and systat(1) show that 100% of time is accounted to the system. I imagine that this is related to SMPng... Any clues? Cheers, -- JMA ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 9: 1:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id B3A5637B43E for ; Thu, 21 Sep 2000 09:01:11 -0700 (PDT) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.3) with ESMTP id BAA73354 for ; Fri, 22 Sep 2000 01:31:08 +0930 (CST) (envelope-from darius@guppy.dons.net.au) Received: (from darius@localhost) by guppy.dons.net.au (8.11.0/8.11.0) id e8LG17P00409 for freebsd-current@freebsd.org; Fri, 22 Sep 2000 01:31:07 +0930 (CST) (envelope-from darius) Message-Id: <200009211601.e8LG17P00409@guppy.dons.net.au> 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 Date: Fri, 22 Sep 2000 01:31:07 +0930 (CST) From: "Daniel J. O'Connor" To: freebsd-current@freebsd.org Subject: SMPng panic message Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, When I boot an SMP kernel (updated 2 days ago) I get the following panic message -> panic: cpu_switch: chooseproc returned NULL cpuid = 0; lapic_id = 00000000 db> tr Debugger(..) panic(..) sw0_3(2,c03876f8,0,0,0) at sw0_3 msleep(c038f958,0,30,c03890dc,64) at msleep+0x235 random_kthread(c038a37c) at random_kthread+0x79 Without the random dev KLD I get the same panic message so I didn't bother with a trace.. (I can get one if its needed :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 9:10:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 459C337B43C for ; Thu, 21 Sep 2000 09:09:56 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13c7N7-0003t7-00; Thu, 21 Sep 2000 16:30:45 +0200 Date: Thu, 21 Sep 2000 16:30:45 +0200 From: Neil Blakey-Milner To: Stijn Hoop Cc: Donn Miller , current@freebsd.org, stable@freebsd.org, marcel@FreeBSD.org Subject: Re: buildkernel broken? Message-ID: <20000921163045.A14925@mithrandr.moria.org> References: <20000921145439.A13769@mithrandr.moria.org> <20000921162714.A61894@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000921162714.A61894@pcwin002.win.tue.nl>; from stijn@win.tue.nl on Thu, Sep 21, 2000 at 04:27:14PM +0200 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu 2000-09-21 (16:27), Stijn Hoop wrote: > nm: could not exec elf/nm in /usr/obj/usr/src/i386/usr/libexec: No such file or directory Yep, this is the problem. > Which is quite correct since I blew away /usr/obj after my last buildworld > (FreeBSD 4.1-STABLE #0: Wed Sep 13 14:45:31 CEST 2000). Is this a problem? Yep. > Should I have done a buildworld before a buildkernel now? I'm trying to convince Marcel that since we already let you use gcc from out the tree, there's no reason we should prevent people from running 'nm' from out the tree. Since he knows more about this sort of thing, and says there may be a problem, I'll leave it to him. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 9:10:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 752C237B505 for ; Thu, 21 Sep 2000 09:10:02 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13c5s7-0003aU-00; Thu, 21 Sep 2000 14:54:39 +0200 Date: Thu, 21 Sep 2000 14:54:39 +0200 From: Neil Blakey-Milner To: Donn Miller Cc: current@freebsd.org Subject: Re: buildkernel broken? Message-ID: <20000921145439.A13769@mithrandr.moria.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dmmiller@cvzoom.net on Thu, Sep 21, 2000 at 08:48:30AM -0400 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu 2000-09-21 (08:48), Donn Miller wrote: > An example of what I get when I try to do a make buildkernel. I have set > KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. > > {standard input}:2342: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 928. Do you have a populated /usr/obj? (ie, with nm) Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 9:10:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id E307437B626 for ; Thu, 21 Sep 2000 09:10:04 -0700 (PDT) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 13c6xO-0003oi-00; Thu, 21 Sep 2000 16:04:10 +0200 Date: Thu, 21 Sep 2000 16:04:09 +0200 From: Neil Blakey-Milner To: Donn Miller Cc: current@freebsd.org Subject: Re: buildkernel broken? Message-ID: <20000921160409.A14651@mithrandr.moria.org> References: <20000921145439.A13769@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from dmmiller@cvzoom.net on Thu, Sep 21, 2000 at 10:00:59AM -0400 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu 2000-09-21 (10:00), Donn Miller wrote: > On Thu, 21 Sep 2000, Neil Blakey-Milner wrote: > > > On Thu 2000-09-21 (08:48), Donn Miller wrote: > > > An example of what I get when I try to do a make buildkernel. I have set > > > KERNEL=CUSTOM in /etc/make.conf, so I should be alright there. > > > > > > > > {standard input}:2342: Error: Subtraction of two symbols in different sections ".data" {.data section} - "KERNBASE" {*UND* section} at file address 928. > > > > Do you have a populated /usr/obj? (ie, with nm) > > I've been doing "make buildkernel installkernel" in /usr/src without doing > a "make buildworld" first. Is this OK? I guess the buildkernel created a > /usr/obj, but I deleted it and tried buildkernel again with the same > results. No, it's not ok. I have patches awaiting some final decision from Marcel that'll make it possible. It mostly works, but OBJFORMAT_PATH doesn't have access to the same PATH we're exporting during the kernel build, meaning 'nm' won't work. They look something like: cvs diff: cannot find Makefile Index: Makefile.inc1 =================================================================== RCS file: /home/ncvs/src/Makefile.inc1,v retrieving revision 1.167 diff -u -r1.167 Makefile.inc1 --- Makefile.inc1 2000/09/03 02:58:39 1.167 +++ Makefile.inc1 2000/09/06 21:10:53 @@ -193,6 +193,14 @@ PATH=${TMPPATH} WMAKE= ${WMAKEENV} ${MAKE} -f Makefile.inc1 +# kernel stage +.if ${BUILD_ARCH} == ${MACHINE_ARCH} +KMAKEENV= ${WMAKEENV} \ + OBJFORMAT_PATH=${WORLDTMP}/usr/libexec:/usr/libexec +.else +KMAKEENV= ${WMAKEENV} +.endif + # install stage IMAKEENV= ${CROSSENV} \ PATH=${STRICTTMPPATH}:${INSTALLTMP} @@ -383,6 +391,9 @@ .if empty(INSTALLKERNEL) INSTALLKERNEL= ${_kernel} .endif +.else +.BEGIN: + @echo ">>> Kernel configuration ${_kernel} does not exist; not building" .endif .endfor @@ -409,10 +420,10 @@ ${MAKE} -f ${KRNLSRCDIR}/dev/aic7xxx/Makefile .if !defined(NO_KERNELDEPEND) cd ${KRNLOBJDIR}/${_kernel}; \ - ${WMAKEENV} MACHINE=${MACHINE} ${MAKE} KERNEL=${INSTKERNNAME} depend + ${KMAKEENV} MACHINE=${MACHINE} ${MAKE} KERNEL=${INSTKERNNAME} depend .endif cd ${KRNLOBJDIR}/${_kernel}; \ - ${WMAKEENV} MACHINE=${MACHINE} ${MAKE} KERNEL=${INSTKERNNAME} all + ${KMAKEENV} MACHINE=${MACHINE} ${MAKE} KERNEL=${INSTKERNNAME} all .endfor # Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 9:22:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from server02.belenus.com (ns2.belenus.com [131.99.17.130]) by hub.freebsd.org (Postfix) with ESMTP id 5B29F37B422 for ; Thu, 21 Sep 2000 09:22:51 -0700 (PDT) Received: by server02.belenus.com with Internet Mail Service (5.5.2650.21) id ; Thu, 21 Sep 2000 18:22:49 +0200 Message-ID: From: "Schmalzbauer, Harald" To: "'freebsd-current@freebsd.org'" Subject: Intel 815e and SMbus Date: Thu, 21 Sep 2000 18:22:49 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, is the SMBus on the 815e different from the old BX? I'm running 4.1 but it can't find any SMB device. (ASUS CULS2) Is it supported in -current? Thanks, Harry belenus GmbH Harald Schmalzbauer Sys/Net Admin Tel: +49 (89) 21979-120 Fax: +49 (89) 21979-111 www.belenus.com -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.2 iQA/AwUBOconylXEptsBus8cEQIJRACffYkwORv8IfuNt/fUfxitTKVygc0AnRsL hbqPjHnS9PrxqJcrg7XQdRiE =ubXC -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 9:44:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.ic.netlaputa.ne.jp (smtp.ic.netlaputa.ne.jp [202.208.214.17]) by hub.freebsd.org (Postfix) with ESMTP id CBBEE37B422; Thu, 21 Sep 2000 09:44:37 -0700 (PDT) Received: from aragorn.t-ogawa.trans-nt.co.jp (im3-ppp30.ic.netlaputa.ne.jp [202.208.214.222]) by smtp.ic.netlaputa.ne.jp (8.9.1/8.9-smtp) with ESMTP id BAA29316; Fri, 22 Sep 2000 01:44:34 +0900 (JST) Date: Fri, 22 Sep 2000 01:44:20 +0900 Message-ID: <867l85y9sr.wl@triaez.kaisei.org> From: Takaya Ogawa To: current@freebsd.org Cc: jasone@freebsd.org Subject: new idle_proc() makes my laptop very hot User-Agent: Wanderlust/2.3.0 (Roam) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 (generated by EMIKO 1.14.0 - "Zoomastigophora") Content-Type: multipart/mixed; boundary="Multipart_Fri_Sep_22_01:44:20_2000-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Multipart_Fri_Sep_22_01:44:20_2000-1 Content-Type: text/plain; charset=US-ASCII Hi. After new idle_proc() committed to the tree, my laptop become very hot as if under heavy cpu load even when cpu is actually 95%~ idle. If I understand collectly, idle_proc() doesn't contain any HLT instruction in i386 UP case which former idle() had. Attached patch adds back the HLT in i386 UP case and seems to fix my problem, although I'm totally unfamiliar with SMP nor alpha. Other than that, current runs quite fine in normal operation here. Thanks. ---------- Takaya Ogawa t-ogawa@triaez.kaisei.org --Multipart_Fri_Sep_22_01:44:20_2000-1 Content-Type: application/octet-stream; type=patch Content-Disposition: attachment; filename="hlt.patch" Content-Transfer-Encoding: 7bit --- sys/sys/proc.h.orig Wed Sep 20 06:48:38 2000 +++ sys/sys/proc.h Wed Sep 20 06:49:04 2000 @@ -515,6 +515,7 @@ void remrunqueue __P((struct proc *)); void cpu_switch __P((void)); void cpu_throw __P((void)) __dead2; +void cpu_idle __P((void)); void unsleep __P((struct proc *)); void cpu_exit __P((struct proc *)) __dead2; --- sys/i386/i386/swtch.s.orig Wed Sep 20 06:49:54 2000 +++ sys/i386/i386/swtch.s Wed Sep 20 06:51:33 2000 @@ -81,6 +81,12 @@ ret /* + * cpu_idle() + */ +ENTRY(cpu_idle) + jmp *_hlt_vector + +/* * cpu_throw() */ ENTRY(cpu_throw) --- sys/kern/kern_idle.c.orig Wed Sep 20 06:41:47 2000 +++ sys/kern/kern_idle.c Wed Sep 20 06:49:44 2000 @@ -88,6 +88,7 @@ * This is a good place to put things to be done in * the background, including sanity checks. */ + cpu_idle(); if (count++ < 0) CTR0(KTR_PROC, "idle_proc: timed out waiting" " for a process"); --Multipart_Fri_Sep_22_01:44:20_2000-1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 10:10:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (roaming.cacheboy.net [203.56.168.69]) by hub.freebsd.org (Postfix) with ESMTP id 8179F37B422; Thu, 21 Sep 2000 10:10:16 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id eBMIDHi07548; Fri, 22 Dec 2000 19:13:17 +0100 (CET) (envelope-from adrian) Date: Fri, 22 Dec 2000 19:13:17 +0100 From: Adrian Chadd To: freebsd-fs@freebsd.org Cc: freebsd-current@freebsd.org Subject: Fsck wrappers, revisited Message-ID: <20001222191317.A7529@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've updated my fsck wrappers patchset to the latest netbsd and freebsd fsck patches. I'd appreciate some feedback on them before I run off and commit them (with my mentor, of course.) For those who aren't in the know, the general idea is that a single wrapper program spawns a FS-specific fsck process a la mount and mount_*, making multiple-FS support a lot easier. (Think about having fsck_ext2fs, fsck_msdos and fsck_ffs doing your FSes on bootup..) They can be found at http://www.freebsd.org/~adrian/fsck/ . PLEASE read the README before you use them, as there are a few gotchas. Thanks! Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 12:16: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.mail.yahoo.com (smtp1.mail.yahoo.com [128.11.69.60]) by hub.freebsd.org (Postfix) with SMTP id 0E3A537B42C for ; Thu, 21 Sep 2000 12:15:53 -0700 (PDT) Received: from 151ppp.infohighway.proline.at (HELO wsjk02) (212.236.19.5) by smtp.mail.vip.suc.yahoo.com with SMTP; 21 Sep 2000 19:15:49 -0000 X-Apparently-From: Message-ID: <02b601c02400$5d0e44b0$4800a8c0@wsjk02.kmjeuro.com> From: "Karl M. Joch" To: Subject: Notebook & current rebooting problems Date: Thu, 21 Sep 2000 21:15:48 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I am new to -current but running FreeBSD since 2.2.?. current was a result of haveing problems with my notebook after running a long time with 3.x and 4.x. till the last cvsup mid of august and now there must have been changes which cases my notebook to hang when rebooting. it is a Kapok 8700 (233MhZ/128MB/4GB/ESS1879) which is sold under different brands. now i successfully updated to current running in the same problem. if power on is done it boots fine. also shutdown -h now and power off / power on works. but reboot or shutdown -r now makes the box shutting down and it looks like it trys to start (cleaning the screen) and then hangs forever. only power off is possible. i want to stay with this box on current because i always was interested in it so any idea that rebooting works again would be great. there are 2 more questions: 1. i run vmware and after the update the rtc.ko und vm..ko modules cant get loaded. trying to reinstall from the ports works for rtc (but results in exec format error again) and fails for vmware. there was a note about people complaining about the linux emulation after upgrading to current and not moving the old moules away. i moved /modules and /modules.old away and let only an empty /modules. the onld kernel is still in / but when booting it is noted /boot/kernel... kde2 and other software atarts fine. 2. the notebook has an ESS1879 sound card which was the second reason to upgrade. pcm/sbc finds the card without problems at boot time. but artsd from kde2/b5 locks the pc when it is startet. many thanks for any hints. Best rgards, / Mit freundlichen Grüßen, Karl M. Joch _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 14:53:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5BAEC37B424 for ; Thu, 21 Sep 2000 14:53:41 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA06996; Thu, 21 Sep 2000 15:53:39 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA62167; Thu, 21 Sep 2000 15:53:39 -0600 (MDT) Message-Id: <200009212153.PAA62167@harmony.village.org> To: Donn Miller Subject: Re: buildkernel broken? Cc: Neil Blakey-Milner , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 21 Sep 2000 10:00:59 EDT." References: Date: Thu, 21 Sep 2000 15:53:39 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Donn Miller writes: : I've been doing "make buildkernel installkernel" in /usr/src without doing : a "make buildworld" first. Is this OK? NO. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 15:18:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 038ED37B443; Thu, 21 Sep 2000 15:18:34 -0700 (PDT) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA27194; Thu, 21 Sep 2000 18:18:24 -0400 (EDT) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id SAA09510; Thu, 21 Sep 2000 18:18:23 -0400 (EDT) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA09506; Thu, 21 Sep 2000 18:18:23 -0400 (EDT) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Thu, 21 Sep 2000 18:18:23 -0400 (EDT) From: Kenneth Wayne Culver To: Takaya Ogawa Cc: current@FreeBSD.ORG, jasone@FreeBSD.ORG Subject: Re: new idle_proc() makes my laptop very hot In-Reply-To: <867l85y9sr.wl@triaez.kaisei.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can second this... on my PC the cpu used to run around about 84 degrees F with the case at 80 degrees F, now the cpu runs at about 91-93 degrees F while the case runs at 80 degrees F. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Fri, 22 Sep 2000, Takaya Ogawa wrote: > Hi. > > After new idle_proc() committed to the tree, my laptop > become very hot as if under heavy cpu load even when > cpu is actually 95%~ idle. > > If I understand collectly, idle_proc() doesn't contain > any HLT instruction in i386 UP case which former > idle() had. > > Attached patch adds back the HLT in i386 UP case and > seems to fix my problem, although I'm totally > unfamiliar with SMP nor alpha. > > Other than that, current runs quite fine in normal > operation here. > > Thanks. > > ---------- > Takaya Ogawa > t-ogawa@triaez.kaisei.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 15:23: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 7255937B440 for ; Thu, 21 Sep 2000 15:23:01 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA02142; Thu, 21 Sep 2000 15:23:53 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009212223.PAA02142@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kenneth Wayne Culver Cc: current@FreeBSD.ORG Subject: Re: new idle_proc() makes my laptop very hot In-reply-to: Your message of "Thu, 21 Sep 2000 18:18:23 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 15:23:53 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I can second this... on my PC the cpu used to run around about 84 degrees > F with the case at 80 degrees F, now the cpu runs at about 91-93 degrees F > while the case runs at 80 degrees F. While you're tinkering with SMPng, be VERY SURE that you do not have acpi enabled (ie. make sure it's not in your kernel config). We're not yet handling thermal management, and this *will* hurt you. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 15:50:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4B66037B43C for ; Thu, 21 Sep 2000 15:50:11 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA07259; Thu, 21 Sep 2000 16:50:10 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA62765; Thu, 21 Sep 2000 16:50:09 -0600 (MDT) Message-Id: <200009212250.QAA62765@harmony.village.org> To: Kenneth Wayne Culver Subject: Re: new idle_proc() makes my laptop very hot Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 21 Sep 2000 18:18:23 EDT." References: Date: Thu, 21 Sep 2000 16:50:09 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Kenneth Wayne Culver writes: : I can second this... on my PC the cpu used to run around about 84 degrees : F with the case at 80 degrees F, now the cpu runs at about 91-93 degrees F : while the case runs at 80 degrees F. My laptop does seem to run *MUCH* warmer than before as well. It runs hot to begin with, but with the latest kernels it runs really hot. It used to get this hot only when I compiled -j 4. I don't have ACPI enabled and am using UP kernel. There really needs to be a HLT in the idle loop to keep idle machines cools. The thermal management code, iirc, works in conjunction with this by lower the clock rate when things aren't too loaded, but that is a fairly complex thign to wait for. It also seems to help mostly on lightly loaded machines. HLT helps more than you'd otherwise think...c Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 16: 2:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 6F74F37B423 for ; Thu, 21 Sep 2000 16:02:13 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA62850; Thu, 21 Sep 2000 16:03:02 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009212303.QAA62850@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: new idle_proc() makes my laptop very hot In-reply-to: Your message of "Thu, 21 Sep 2000 16:50:09 MDT." <200009212250.QAA62765@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 16:03:02 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My laptop does seem to run *MUCH* warmer than before as well. It runs > hot to begin with, but with the latest kernels it runs really hot. It > used to get this hot only when I compiled -j 4. I don't have ACPI > enabled and am using UP kernel. There really needs to be a HLT in the > idle loop to keep idle machines cools. If I remember from a discussion with John Baldwin, the reason we don't do this (yet) is that HLT only wakes up when you take an interrupt, and there are cases where we can't guarantee that we'll take an interrupt in order to get us out of the HLT. > The thermal management code, iirc, works in conjunction with this by > lower the clock rate when things aren't too loaded, but that is a > fairly complex thign to wait for. It also seems to help mostly on > lightly loaded machines. HLT helps more than you'd otherwise > think...c HLT helps a lot, yes, but the thermal management code is responsible for running the system fan(s) in ACPI mode as well as throttling the CPU. In some cases, that's a real issue (eg. I'm building the world now and extremely worried about how hot this system is because I forgot to turn ACPI off first. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 16:10:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2F5C437B423; Thu, 21 Sep 2000 16:10:53 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA07309; Thu, 21 Sep 2000 17:10:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA62949; Thu, 21 Sep 2000 17:10:51 -0600 (MDT) Message-Id: <200009212310.RAA62949@harmony.village.org> To: Mike Smith Subject: Re: new idle_proc() makes my laptop very hot Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 21 Sep 2000 16:03:02 PDT." <200009212303.QAA62850@mass.osd.bsdi.com> References: <200009212303.QAA62850@mass.osd.bsdi.com> Date: Thu, 21 Sep 2000 17:10:51 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009212303.QAA62850@mass.osd.bsdi.com> Mike Smith writes: : If I remember from a discussion with John Baldwin, the reason we don't do : this (yet) is that HLT only wakes up when you take an interrupt, and : there are cases where we can't guarantee that we'll take an interrupt in : order to get us out of the HLT. I thought that's what the timer interrupts were for... We can't guarantee that we'll get one? That seems very serious to me. : > The thermal management code, iirc, works in conjunction with this by : > lower the clock rate when things aren't too loaded, but that is a : > fairly complex thign to wait for. It also seems to help mostly on : > lightly loaded machines. HLT helps more than you'd otherwise : > think...c : : HLT helps a lot, yes, but the thermal management code is responsible for : running the system fan(s) in ACPI mode as well as throttling the CPU. In : some cases, that's a real issue (eg. I'm building the world now and : extremely worried about how hot this system is because I forgot to turn : ACPI off first. 8) Ah. I don't have a system fan :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 16:17:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 55EAB37B43E for ; Thu, 21 Sep 2000 16:17:30 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA92785; Thu, 21 Sep 2000 16:18:23 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009212318.QAA92785@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: new idle_proc() makes my laptop very hot In-reply-to: Your message of "Thu, 21 Sep 2000 17:10:51 MDT." <200009212310.RAA62949@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 16:18:23 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200009212303.QAA62850@mass.osd.bsdi.com> Mike Smith writes: > : If I remember from a discussion with John Baldwin, the reason we don't do > : this (yet) is that HLT only wakes up when you take an interrupt, and > : there are cases where we can't guarantee that we'll take an interrupt in > : order to get us out of the HLT. > > I thought that's what the timer interrupts were for... We can't > guarantee that we'll get one? That seems very serious to me. Think about the MP environment. There's one timer interrupt, and more than one CPU. In the UP case, you could probably rely on HLT to DTRT though; this is an optimisation that will probably come back shortly. > : HLT helps a lot, yes, but the thermal management code is responsible for > : running the system fan(s) in ACPI mode as well as throttling the CPU. In > : some cases, that's a real issue (eg. I'm building the world now and > : extremely worried about how hot this system is because I forgot to turn > : ACPI off first. 8) > > Ah. I don't have a system fan :-) Some of us need them. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 16:50: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from hand.dotat.at (sfo-gw.covalent.net [207.44.198.62]) by hub.freebsd.org (Postfix) with ESMTP id 2D7FA37B424; Thu, 21 Sep 2000 16:50:03 -0700 (PDT) Received: from fanf by hand.dotat.at with local (Exim 3.15 #3) id 13cG65-000NVl-00; Thu, 21 Sep 2000 23:49:45 +0000 Date: Thu, 21 Sep 2000 23:49:45 +0000 From: Tony Finch To: Warner Losh Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: new idle_proc() makes my laptop very hot Message-ID: <20000921234945.F5948@hand.dotat.at> References: <200009212303.QAA62850@mass.osd.bsdi.com> <200009212310.RAA62949@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200009212310.RAA62949@harmony.village.org> Organization: Covalent Technologies, Inc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: >Mike Smith writes: >> >> If I remember from a discussion with John Baldwin, the reason we >> don't do this (yet) is that HLT only wakes up when you take an >> interrupt, and there are cases where we can't guarantee that we'll >> take an interrupt in order to get us out of the HLT. > >I thought that's what the timer interrupts were for... We can't >guarantee that we'll get one? That seems very serious to me. The problem is that one cpu may wich to schedule a process to run on the idle cpu, but it can't because the idle cpu is halted and won't wake up until the next irq. Tony. -- en oeccget g mtcaa f.a.n.finch v spdlkishrhtewe y dot@dotat.at eatp o v eiti i d. fanf@covalent.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 16:59:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id C0F6537B440; Thu, 21 Sep 2000 16:59:28 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA07515; Thu, 21 Sep 2000 17:59:25 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA63352; Thu, 21 Sep 2000 17:59:25 -0600 (MDT) Message-Id: <200009212359.RAA63352@harmony.village.org> To: Tony Finch Subject: Re: new idle_proc() makes my laptop very hot Cc: Mike Smith , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 21 Sep 2000 23:49:45 -0000." <20000921234945.F5948@hand.dotat.at> References: <20000921234945.F5948@hand.dotat.at> <200009212303.QAA62850@mass.osd.bsdi.com> <200009212310.RAA62949@harmony.village.org> Date: Thu, 21 Sep 2000 17:59:25 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000921234945.F5948@hand.dotat.at> Tony Finch writes: : Warner Losh wrote: : >Mike Smith writes: : >> : >> If I remember from a discussion with John Baldwin, the reason we : >> don't do this (yet) is that HLT only wakes up when you take an : >> interrupt, and there are cases where we can't guarantee that we'll : >> take an interrupt in order to get us out of the HLT. : > : >I thought that's what the timer interrupts were for... We can't : >guarantee that we'll get one? That seems very serious to me. : : The problem is that one cpu may wich to schedule a process to run on : the idle cpu, but it can't because the idle cpu is halted and won't : wake up until the next irq. Since I'm running a UP kernel, that can't happen. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 17:10:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 863E037B424 for ; Thu, 21 Sep 2000 17:10:21 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA52850; Thu, 21 Sep 2000 17:11:14 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200009220011.RAA52850@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: new idle_proc() makes my laptop very hot In-reply-to: Your message of "Thu, 21 Sep 2000 17:59:25 MDT." <200009212359.RAA63352@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Sep 2000 17:11:13 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : >> If I remember from a discussion with John Baldwin, the reason we > : >> don't do this (yet) is that HLT only wakes up when you take an > : >> interrupt, and there are cases where we can't guarantee that we'll > : >> take an interrupt in order to get us out of the HLT. > : > > : >I thought that's what the timer interrupts were for... We can't > : >guarantee that we'll get one? That seems very serious to me. > : > : The problem is that one cpu may wich to schedule a process to run on > : the idle cpu, but it can't because the idle cpu is halted and won't > : wake up until the next irq. > > Since I'm running a UP kernel, that can't happen. Actually, there are pathalogical cases where it could, but they are, well, pathalogical. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 17:39:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from static.unixfreak.org (static.unixfreak.org [63.198.170.139]) by hub.freebsd.org (Postfix) with ESMTP id 29BF837B440; Thu, 21 Sep 2000 17:39:46 -0700 (PDT) Received: by static.unixfreak.org (Postfix, from userid 1000) id 5BC6E1F27; Thu, 21 Sep 2000 17:14:56 -0700 (PDT) Subject: Re: 'host' command with CNAMEs In-Reply-To: from Tim Zingelman at "Sep 21, 2000 10:32:59 am" To: Tim Zingelman Date: Thu, 21 Sep 2000 17:14:56 -0700 (PDT) Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG From: Dima Dorfman Reply-To: dima@unixfreak.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM969581696-60857-0_ Content-Transfer-Encoding: 7bit Message-Id: <20000922001456.5BC6E1F27@static.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM969581696-60857-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > As I recall, Sean Kelly wrote: > > > I've got two machines here, one running 4.1-STABLE (from Aug 3) and a > > > 5.0-CURRENT (from Aug 10) and both of them show the same issue. When > > > you use the 'host' command to resolve a CNAME, it will show all the A > > > records twice: > > > > > > (7) smkelly@edgemaster:~$ host www.microsoft.com > > > www.microsoft.com is a nickname for microsoft.com > > > microsoft.com has address 207.46.130.45 > > > microsoft.com has address 207.46.230.218 > > > microsoft.com has address 207.46.230.219 > > > microsoft.com has address 207.46.230.218 > > > microsoft.com has address 207.46.230.219 > > > microsoft.com has address 207.46.130.45 > > It is more complicated than that... the bug only shows up if you specify > an alias name... You are both correct. In fact, it looks like you're stating the exact same thing. The obvious problem is that if 'host' is resolving a CNAME, there are two independant places which display the real address. My guess is that at some point, two independant developers decided to change the way 'host' deals with CNAMEs, but they put their code in different places. When they commited their code to the CVS repository, there were no conflicts, and the second one to commit failed to notice that a part of his code was already implemented. This bug was actually fixed in rev. 8.28 of host.c (BIND v8.2.1), but was resurrected in rev. 8.31 (BIND v8.2.2-REL). Since ISC doesn't release their CVS logs to the public, I can't find out why this was done (perhaps a developer commited something based on an earlier rev., and didn't merge this change). If anybody wants it, I've made a patch to correct the problem (see attached). It applies against src/contrib/bind/bin/host/host.c of 5-CURRENT (although host.c is the same in RELENG_4, and it applies cleanly there). I heard somewhere that the contrib/ tree shouldn't contain local changes, but I'm unclear as to where local changes to contribited software go, so I made it against that. Once you've applied it, all you should have to do is `( cd /usr/src/usr.bin/host && make)`, although I haven't tested that approach. This should also apply cleanly to host.c of BIND 8.2.3-T5B, as that's what is in FreeBSD. Hope this helps -- Dima Dorfman Finger dima@unixfreak.org for my public PGP key. "When in doubt, use brute force." -- Ken Thompson --ELM969581696-60857-0_ Content-Type: text/plain; charset=US-ASCII Content-Disposition: attachment; filename=host-cname.diff Content-Description: /usr/home/dima/host-cname.diff Content-Transfer-Encoding: 7bit Index: host.c =================================================================== RCS file: /usr/cvs/FreeBSD/src/contrib/bind/bin/host/host.c,v retrieving revision 1.1.1.3 diff -u -r1.1.1.3 host.c --- host.c 2000/05/26 07:17:07 1.1.1.3 +++ host.c 2000/09/21 23:46:26 @@ -696,8 +696,18 @@ if (!hp->ad) if (verbose && isls == 0) printf("The following answer is not verified as authentic by the server:\n"); - while (--ancount >= 0 && cp && cp < eom) + while (--ancount >= 0 && cp && cp < eom) { cp = pr_rr(cp, answer->qb2, stdout, filter); + /* + * When we ask for address and there is a CNAME, it + * seems to return both the CNAME and the address. + * Since we trace down the CNAME chain ourselves, we + * don't really want to print the address at this + * point. + */ + if (cname && ! verbose) + return (1); + } } if (!verbose) return (1); --ELM969581696-60857-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 18: 1:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from drugs.dv.isc.org (drugs.dv.isc.org [130.155.191.236]) by hub.freebsd.org (Postfix) with ESMTP id 83E0237B43F; Thu, 21 Sep 2000 18:01:14 -0700 (PDT) Received: from nominum.com (localhost.dv.isc.org [127.0.0.1]) by drugs.dv.isc.org (8.11.0/8.11.0) with ESMTP id e8M12Pi51386; Fri, 22 Sep 2000 12:02:27 +1100 (EST) (envelope-from marka@nominum.com) Message-Id: <200009220102.e8M12Pi51386@drugs.dv.isc.org> To: dima@unixfreak.org Cc: Tim Zingelman , stable@FreeBSD.ORG, current@FreeBSD.ORG From: Mark.Andrews@nominum.com Subject: Re: 'host' command with CNAMEs In-reply-to: Your message of "Thu, 21 Sep 2000 17:14:56 PDT." <20000922001456.5BC6E1F27@static.unixfreak.org> Date: Fri, 22 Sep 2000 12:02:25 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG BIND 4 and BIND 8 bugs can be reported to bind-bugs@isc.org. BIND 9 bugs can be reported to bind9-bugs@isc.org. Mark P.S. don't bother submitting this as it will just land in my mailbox. > > --ELM969581696-60857-0_ > Content-Type: text/plain; charset=US-ASCII > Content-Transfer-Encoding: 7bit > > > > As I recall, Sean Kelly wrote: > > > > I've got two machines here, one running 4.1-STABLE (from Aug 3) and a > > > > 5.0-CURRENT (from Aug 10) and both of them show the same issue. When > > > > you use the 'host' command to resolve a CNAME, it will show all the A > > > > records twice: > > > > > > > > (7) smkelly@edgemaster:~$ host www.microsoft.com > > > > www.microsoft.com is a nickname for microsoft.com > > > > microsoft.com has address 207.46.130.45 > > > > microsoft.com has address 207.46.230.218 > > > > microsoft.com has address 207.46.230.219 > > > > microsoft.com has address 207.46.230.218 > > > > microsoft.com has address 207.46.230.219 > > > > microsoft.com has address 207.46.130.45 > > > > It is more complicated than that... the bug only shows up if you specify > > an alias name... > > You are both correct. In fact, it looks like you're stating the exact > same thing. > > The obvious problem is that if 'host' is resolving a CNAME, there are > two independant places which display the real address. My guess is > that at some point, two independant developers decided to change the > way 'host' deals with CNAMEs, but they put their code in different > places. When they commited their code to the CVS repository, there > were no conflicts, and the second one to commit failed to notice that > a part of his code was already implemented. > > This bug was actually fixed in rev. 8.28 of host.c (BIND v8.2.1), but > was resurrected in rev. 8.31 (BIND v8.2.2-REL). Since ISC doesn't > release their CVS logs to the public, I can't find out why this was > done (perhaps a developer commited something based on an earlier rev., > and didn't merge this change). > > If anybody wants it, I've made a patch to correct the problem (see > attached). It applies against src/contrib/bind/bin/host/host.c of > 5-CURRENT (although host.c is the same in RELENG_4, and it applies > cleanly there). I heard somewhere that the contrib/ tree shouldn't > contain local changes, but I'm unclear as to where local changes to > contribited software go, so I made it against that. Once you've > applied it, all you should have to do is `( cd /usr/src/usr.bin/host > && make)`, although I haven't tested that approach. This should also > apply cleanly to host.c of BIND 8.2.3-T5B, as that's what is in > FreeBSD. > > Hope this helps > > -- > Dima Dorfman > Finger dima@unixfreak.org for my public PGP key. > > "When in doubt, use brute force." > -- Ken Thompson > > --ELM969581696-60857-0_ > Content-Type: text/plain; charset=US-ASCII > Content-Disposition: attachment; filename=host-cname.diff > Content-Description: /usr/home/dima/host-cname.diff > Content-Transfer-Encoding: 7bit > > Index: host.c > =================================================================== > RCS file: /usr/cvs/FreeBSD/src/contrib/bind/bin/host/host.c,v > retrieving revision 1.1.1.3 > diff -u -r1.1.1.3 host.c > --- host.c 2000/05/26 07:17:07 1.1.1.3 > +++ host.c 2000/09/21 23:46:26 > @@ -696,8 +696,18 @@ > if (!hp->ad) > if (verbose && isls == 0) > printf("The following answer is not verified as authent > ic by the server:\n"); > - while (--ancount >= 0 && cp && cp < eom) > + while (--ancount >= 0 && cp && cp < eom) { > cp = pr_rr(cp, answer->qb2, stdout, filter); > + /* > + * When we ask for address and there is a CNAME, it > + * seems to return both the CNAME and the address. > + * Since we trace down the CNAME chain ourselves, we > + * don't really want to print the address at this > + * point. > + */ > + if (cname && ! verbose) > + return (1); > + } > } > if (!verbose) > return (1); > > --ELM969581696-60857-0_-- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews@nominum.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 18: 7:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 26CE637B423; Thu, 21 Sep 2000 18:07:27 -0700 (PDT) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id VAA07164; Thu, 21 Sep 2000 21:07:26 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id VAA09279; Thu, 21 Sep 2000 21:07:26 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id VAA09275; Thu, 21 Sep 2000 21:07:25 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Thu, 21 Sep 2000 21:07:25 -0400 (EDT) From: Kenneth Wayne Culver To: Mike Smith Cc: current@freebsd.org Subject: Re: new idle_proc() makes my laptop very hot In-Reply-To: <200009212223.PAA02142@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't have it enabled... I am not even on my laptop with -CURRENT... this is on my regular PC... and I'm taking my thermal readings by banging around on some memory addys through /dev/io with a little hack of a program I wrote as a windowmaker dockapp for this purpose... ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Thu, 21 Sep 2000, Mike Smith wrote: > > I can second this... on my PC the cpu used to run around about 84 degrees > > F with the case at 80 degrees F, now the cpu runs at about 91-93 degrees F > > while the case runs at 80 degrees F. > > While you're tinkering with SMPng, be VERY SURE that you do not have acpi > enabled (ie. make sure it's not in your kernel config). We're not yet > handling thermal management, and this *will* hurt you. > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 18: 8:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 17B8537B423; Thu, 21 Sep 2000 18:08:50 -0700 (PDT) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id VAA07220; Thu, 21 Sep 2000 21:08:49 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id VAA09994; Thu, 21 Sep 2000 21:08:48 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id VAA09988; Thu, 21 Sep 2000 21:08:48 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Thu, 21 Sep 2000 21:08:48 -0400 (EDT) From: Kenneth Wayne Culver To: Mike Smith Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: new idle_proc() makes my laptop very hot In-Reply-To: <200009212303.QAA62850@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My system fans always stay on... but again this is not in a laptop .. it is on my regular pc... ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Thu, 21 Sep 2000, Mike Smith wrote: > > My laptop does seem to run *MUCH* warmer than before as well. It runs > > hot to begin with, but with the latest kernels it runs really hot. It > > used to get this hot only when I compiled -j 4. I don't have ACPI > > enabled and am using UP kernel. There really needs to be a HLT in the > > idle loop to keep idle machines cools. > > If I remember from a discussion with John Baldwin, the reason we don't do > this (yet) is that HLT only wakes up when you take an interrupt, and > there are cases where we can't guarantee that we'll take an interrupt in > order to get us out of the HLT. > > > The thermal management code, iirc, works in conjunction with this by > > lower the clock rate when things aren't too loaded, but that is a > > fairly complex thign to wait for. It also seems to help mostly on > > lightly loaded machines. HLT helps more than you'd otherwise > > think...c > > HLT helps a lot, yes, but the thermal management code is responsible for > running the system fan(s) in ACPI mode as well as throttling the CPU. In > some cases, that's a real issue (eg. I'm building the world now and > extremely worried about how hot this system is because I forgot to turn > ACPI off first. 8) > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > > > > > 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 Thu Sep 21 19:33:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 0780B37B42C for ; Thu, 21 Sep 2000 19:33:18 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8M2X7i36645; Thu, 21 Sep 2000 19:33:07 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8M2VYG13520; Thu, 21 Sep 2000 19:31:34 -0700 (PDT) (envelope-from jhb) 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: <39CA2B9C.DB675E0D@we.lc.ehu.es> Date: Thu, 21 Sep 2000 19:31:33 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: "Jose M. Alcaide" Subject: RE: processes only consume system time ???? Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Sep-00 Jose M. Alcaide wrote: > This happens with freshly built -CURRENT, on an uniprocessor machine: > > $ cat loop.c > main() { while (1); } > $ time ./loop > [ wait for ten seconds... ] > ^C > real 0m9.982s > user 0m0.000s > sys 0m5.689s > > Uh? Other utilities, such as top(1) and systat(1) show that 100% of time > is accounted to the system. I imagine that this is related to SMPng... Yes. This is a FAQ. The accounting is screwed up, and some of the statistics are wrong. Your system is scheduling processes close enough to normal that you shouldn't have any problems. > Any clues? > > Cheers, > -- JMA -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 21:51: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from rcpt-expgw.biglobe.ne.jp (rcpt-expgw.biglobe.ne.jp [210.147.6.212]) by hub.freebsd.org (Postfix) with ESMTP id 0FA3637B42C for ; Thu, 21 Sep 2000 21:50:58 -0700 (PDT) Received: from smtp-gw.biglobe.ne.jp by rcpt-expgw.biglobe.ne.jp (8.9.3+3.2W/3.7W-00092117) with ESMTP id NAA17436 for ; Fri, 22 Sep 2000 13:50:56 +0900 (JST) Received: from oemcomputer (211.13.36.107 [211.13.36.107]) by smtp-gw.biglobe.ne.jp id NBOLCAE158CF; Fri, 22 Sep 2000 13:50:55 +0900 (JST) To: freebsd-current@freebsd.org From: link Date: Fri, 22 Sep 2000 13:51:00 +0900 Subject: =?ISO-2022-JP?B?GyRCO0s+ZTpHQmc1LExPJE4lJiUnJVY3TzpHPzclUyU4JU0lOT5wSnMkRyQ5ISMbKEI=?= X-Mailer: IM2000 Version 1.01 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=iso-2022-jp Message-Id: <0922100135100.2277@oemcomputer> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG $B!z!y!z!y!z@$3&:GBg5i$N%7%g%C%T%s%0%b!<%k$,F|K\>eN&!*!z!y!z!y!z(B 10$B7n%*!<%W%sA0$ND6%l%">pJs$G$9!#(B $B$9$G$K?tI4K|E@$N%"%$%F%`$re$2$i$l$k%S%8%M%9%Q!<%H%J!<$r(B $BJg=8$$$?$7$^$9!#(B $BEPO?5Z$S>\:Y$O2<5-%[!<%`%Z!<%8$r$4Mw2<$5$$!#(B $B"-!!"-!!"-!!"-!!"-!!"-!!"-!!"-!!(B http://www.starmax-japan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 22:13:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 5F8D737B422; Thu, 21 Sep 2000 22:13:45 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8M5DLJ33589; Fri, 22 Sep 2000 14:43:21 +0930 (CST) (envelope-from grog) Date: Fri, 22 Sep 2000 14:43:21 +0930 From: Greg Lehey To: "Brandon D. Valentine" Cc: Matthew Jacob , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: 1131 unneeded includes in the kernel... Message-ID: <20000922144321.F66887@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bandix@looksharp.net on Wed, Sep 20, 2000 at 03:10:21AM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 20 September 2000 at 3:10:21 -0400, Brandon D. Valentine wrote: > On Tue, 19 Sep 2000, Matthew Jacob wrote: > >> >> Oh- don't get me wrong. Valuable info. Thanks. > > What would be very cool is to feed this into another script which strips > these unnecesary includes out. Then do a test build of LINT in your > local tree and if it succeeds commit a mass removal of them. The same > concept could be applied to the greater source tree. Things aren't that simple. I've checked some of the vinum ones, and I find something like: #ifdef VINUMDEBUG #include #endif sys/reboot.h has been flagged as unnecessary. Obviously the #ifdef's have to do as well--if the script is correct. There are a number of options in Vinum which never get as far as the source tree. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Sep 21 23:10: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 8A85837B424; Thu, 21 Sep 2000 23:09:58 -0700 (PDT) Received: from gorean.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id XAA53535; Thu, 21 Sep 2000 23:09:57 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39CAF7B5.F1786B15@gorean.org> Date: Thu, 21 Sep 2000 23:09:57 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-092 i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: current@FreeBSD.org Subject: Re: A SMPng suggestion.. References: <200009210742.AAA38613@john.baldwin.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > > If you are running -current with the SMPng code, it would probably > be very production to stick the following options in your kernel > config, especially if you are having crashes: > > SMP_DEBUG > DIAGNOSTIC > INVARIANTS > INVARIANT_SUPPORT Rumor not too long ago was that DIAGNOSTIC is evil, and can actually cause more problems than it solves. Has that changed? Doug -- "The dead cannot be seduced." - Kai, "Lexx" 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 Thu Sep 21 23:16:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 619A537B423 for ; Thu, 21 Sep 2000 23:16:54 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8M6Ghi40964; Thu, 21 Sep 2000 23:16:43 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8M6F9e15141; Thu, 21 Sep 2000 23:15:09 -0700 (PDT) (envelope-from jhb) 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: <39CAF7B5.F1786B15@gorean.org> Date: Thu, 21 Sep 2000 23:15:09 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Doug Barton Subject: Re: A SMPng suggestion.. Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Sep-00 Doug Barton wrote: > John Baldwin wrote: >> >> If you are running -current with the SMPng code, it would probably >> be very production to stick the following options in your kernel >> config, especially if you are having crashes: >> >> SMP_DEBUG >> DIAGNOSTIC >> INVARIANTS >> INVARIANT_SUPPORT > > Rumor not too long ago was that DIAGNOSTIC is evil, and can actually > cause more problems than it solves. Has that changed? Uh, well. It has been helping finding bugs so far. I personally have yet to see a problem with it. It probably hurts performance, but all of these options do that. > Doug > -- > "The dead cannot be seduced." > - Kai, "Lexx" > > Do YOU Yahoo!? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 0: 1:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from updraft.jp.freebsd.org (updraft.jp.FreeBSD.ORG [210.157.158.42]) by hub.freebsd.org (Postfix) with ESMTP id BAFE437B424; Fri, 22 Sep 2000 00:01:40 -0700 (PDT) Received: from castle2.jp.FreeBSD.org (castle2.jp.FreeBSD.org [210.226.20.120]) by updraft.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id QAA88032; Fri, 22 Sep 2000 16:01:38 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by castle2.jp.FreeBSD.org (8.11.0+3.3W/8.11.0) with ESMTP/inet id e8M71aX40737; Fri, 22 Sep 2000 16:01:36 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: jkh@freebsd.org X-Face: '*aj"d@ijeQ:/X}]oM5c5Uz{ZZZk90WPt>a^y4$cGQp8:!H\W=hSM;PuNiidkc]/%,;6VGu e+`&APmz|P;F~OL/QK%;P2vU>\j4X.8@i%j6[%DTs_3J,Fff0)*oHg$A.cDm&jc#pD24WK@{,"Ef!0 P\):.2}8jo-BiZ?X&t$V X-User-Agent: Mew/1.94.2 XEmacs/21.2 (Molpe) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 88 From: Makoto MATSUSHITA To: current@freebsd.org, stable@freebsd.org Subject: sysinstall: Avoiding version checking of CD-ROM (patch included) Date: Fri, 22 Sep 2000 16:00:18 +0900 Message-Id: <20000922160018G.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm an administrator of current.jp.FreeBSD.org, yet another snapshots services in Japan. Now I'm going to make a bootable FreeBSD installation CD which contains FreeBSD 3-stable, 4-stable and -current (namely, 'triplex CD-ROM'). Maybe it's useful for installation events at BUGs (BSD Users Groups), or any people who wanna try both bleeding-edge/solid-state version of FreeBSD. If you have interested in triplex CD-ROM, try (approx. 600MB): The directory layout of CD-ROM is quite simple just like this. % ls 3.5-20000913-JPSNAP 5.0-20000913-JPSNAP 4.1-20000919-JPSNAP boot.img Note that 'boot.img' contains all three versions of kernel images. You can choice which sysinstall to kick (thanks you loader(8).) Most procedures works well, except one warnings. When CD-ROM is initialized to use (after all installation option was selected), sysinstall complains as follows: Warning: The CD currently in the drive is either not a FreeBSD CD or it is an older (pre 2.1.5) FreeBSD CD which does not have a version number on it. Do you wish to use this CD anyway? You can say "yes" to proceed, but it's not welcome. Yeah, It's easy to fix; create 'cdrom.inf' file at root directory of CD-ROM. But the contents of cdrom.inf is the problem. cdrom.inf has it's version name included in CD-ROM, and sysinstall checks its string. Maybe it's OK when CD-ROM has *one* version of FreeBSD, but triplex CD-ROM has *three* versions of FreeBSD. So sysinstall should complains as follow: Warning: The version of the FreeBSD CD currently in the drive (XXX) does not match the version of the boot floppy (YYY). If this is intentional, to avoid this message in the future please visit the Options editor to set the boot floppy version string to match that of the CD before selecting it as your installation media. where 'XXX' is version string in cdrom.inf and 'YYY' is version string in sysinstall. You can also say "yes" to next dialog to proceed installation, however, it's also not welcome. I do not want to make a *custom* sysinstall; it's quite hard to do within a shell script (triplex CD-ROM is built by shell script which is kicked by crom). To avoid this situation, make an escape from version checking. Maybe "CD_VERSION = any" in cdrom.inf is reasonable solution. Index: cdrom.c =================================================================== RCS file: /usr/site/FreeBSD/ncvs/src/release/sysinstall/cdrom.c,v retrieving revision 1.47 diff -c -r1.47 cdrom.c *** cdrom.c 1999/08/28 01:34:08 1.47 --- cdrom.c 2000/09/22 06:12:44 *************** *** 122,128 **** "try again.", mountpoint); } else { ! if (variable_cmp(VAR_RELNAME, cp) && variable_cmp(VAR_RELNAME, "none") && variable_cmp(VAR_RELNAME, "any") && !bogusCDOK) { msgConfirm("Warning: The version of the FreeBSD CD currently in the drive\n" --- 122,129 ---- "try again.", mountpoint); } else { ! if (strcmp(cp, "any") ! && variable_cmp(VAR_RELNAME, cp) && variable_cmp(VAR_RELNAME, "none") && variable_cmp(VAR_RELNAME, "any") && !bogusCDOK) { msgConfirm("Warning: The version of the FreeBSD CD currently in the drive\n" Is there any chance to apply this patch to sysinstall of -current, 4-stable, and 3-stable? -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 1:16:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id B4AC937B422 for ; Fri, 22 Sep 2000 01:16:39 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8M8GK618534; Fri, 22 Sep 2000 01:16:20 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: Makoto MATSUSHITA Cc: current@freebsd.org Subject: Re: sysinstall: Avoiding version checking of CD-ROM (patch included) In-Reply-To: Message from Makoto MATSUSHITA of "Fri, 22 Sep 2000 16:00:18 +0900." <20000922160018G.matusita@jp.FreeBSD.org> Date: Fri, 22 Sep 2000 01:16:20 -0700 Message-ID: <18530.969610580@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Most procedures works well, except one warnings. When CD-ROM is > initialized to use (after all installation option was selected), > sysinstall complains as follows: Thanks for reminding me to go look at that code - you're right, the check is incorrectly done and insufficiently general. Fixed in -current and -stable! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 1:21: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id D58C437B424 for ; Fri, 22 Sep 2000 01:20:57 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8M8Kki43407; Fri, 22 Sep 2000 01:20:46 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8M8JBf16014; Fri, 22 Sep 2000 01:19:11 -0700 (PDT) (envelope-from jhb) 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: <200009211601.e8LG17P00409@guppy.dons.net.au> Date: Fri, 22 Sep 2000 01:19:10 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: "Daniel J. O'Connor" Subject: RE: SMPng panic message Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Sep-00 Daniel J. O'Connor wrote: > Hi, > > When I boot an SMP kernel (updated 2 days ago) I get the following panic > message -> > > panic: cpu_switch: chooseproc returned NULL > cpuid = 0; lapic_id = 00000000 > > db> tr > Debugger(..) > panic(..) > sw0_3(2,c03876f8,0,0,0) at sw0_3 > msleep(c038f958,0,30,c03890dc,64) at msleep+0x235 > random_kthread(c038a37c) at random_kthread+0x79 Matthew Dodd and I are looking at this. The problem seems to be that the idleproc variable is getting hosed during mi_startup() and set to NULL after it is initialized. *sigh* I'm not sure yet what is doing the damage. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 1:56:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 4EA2C37B422; Fri, 22 Sep 2000 01:51:43 -0700 (PDT) Received: from v-ger.we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id KAA11402; Fri, 22 Sep 2000 10:51:41 +0200 (MET DST) Received: from we.lc.ehu.es (localhost [127.0.0.1]) by v-ger.we.lc.ehu.es (8.9.3/8.9.3) with ESMTP id KAA00523; Fri, 22 Sep 2000 10:39:23 +0200 (CEST) (envelope-from jose@we.lc.ehu.es) Message-ID: <39CB1ABB.BCDE0873@we.lc.ehu.es> Date: Fri, 22 Sep 2000 10:39:23 +0200 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: processes only consume system time ???? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > > Yes. This is a FAQ. The accounting is screwed up, and some of the > statistics are wrong. Your system is scheduling processes close enough > to normal that you shouldn't have any problems. > Ah, I am sorry. I searched the -current archives but I didn't find anything related. And yes, I supposed that this problem was an accounting issue, since the scheduling works fine indeed. Thanks, -- JMA ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 2:17:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (gate.interxion.com [194.153.74.13]) by hub.freebsd.org (Postfix) with ESMTP id DD6AB37B422; Fri, 22 Sep 2000 02:17:34 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id eBNAKcT37595; Sat, 23 Dec 2000 11:20:38 +0100 (CET) (envelope-from adrian) Date: Sat, 23 Dec 2000 11:20:38 +0100 From: Adrian Chadd To: freebsd-fs@freebsd.org Cc: freebsd-current@freebsd.org Subject: Re: Fsck wrappers, revisited Message-ID: <20001223112038.A37548@roaming.cacheboy.net> References: <20001222191317.A7529@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001222191317.A7529@roaming.cacheboy.net>; from adrian@FreeBSD.ORG on Fri, Dec 22, 2000 at 07:13:17PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 22, 2000, Adrian Chadd wrote: > > > I've updated my fsck wrappers patchset to the latest netbsd and freebsd > fsck patches. I'd appreciate some feedback on them before I run off > and commit them (with my mentor, of course.) > > For those who aren't in the know, the general idea is that a single wrapper > program spawns a FS-specific fsck process a la mount and mount_*, making > multiple-FS support a lot easier. (Think about having fsck_ext2fs, fsck_msdos > and fsck_ffs doing your FSes on bootup..) > > They can be found at http://www.freebsd.org/~adrian/fsck/ . PLEASE read the > README before you use them, as there are a few gotchas. Thanks to some feedback from bp, I found a stupid mistake in my porting. Here's the patch: --- fsck.c.orig Sat Dec 23 11:13:30 2000 +++ fsck.c Sat Dec 23 11:13:34 2000 @@ -501,7 +501,7 @@ errx(1, "partition `%s' is not of a legal vfstype", str); - if ((vfstype = dktypenames[t]) == NULL) + if ((vfstype = fstypenames[t]) == NULL) errx(1, "vfstype `%s' on partition `%s' is not supported", fstypenames[t], str); So now is a problem which I'm sure the NetBSD people came up against. The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed this by creating a new list 'mountnames[]', which maps the fs type to a string. http://cvsweb.netbsd.org/bsdweb.cgi/syssrc/sys/sys/disklabel.h.diff?r1=1.60&r2=1.61 What do people think about doing this as well? It would certainly make things a little tidier, but every time a new fs comes in the magic autodetection code will need to be updated (if appropriate, of course.) Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 2:28:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 070BA37B42C; Fri, 22 Sep 2000 02:28:53 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 2A6E128805; Fri, 22 Sep 2000 16:27:58 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 204CF28803; Fri, 22 Sep 2000 16:27:58 +0700 (ALMST) Date: Fri, 22 Sep 2000 16:27:58 +0700 (ALMST) From: Boris Popov To: Adrian Chadd Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Fsck wrappers, revisited In-Reply-To: <20001223112038.A37548@roaming.cacheboy.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=koi8-r Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Dec 2000, Adrian Chadd wrote: > So now is a problem which I'm sure the NetBSD people came up against. > The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed > this by creating a new list 'mountnames[]', which maps the fs type to > a string. Probably a hard link to fsck_ffs will do the job fine and makes it clear to see which fs'es are supported: # ls -ail fsck* 6338 -r-xr-xr-x 1 root wheel 66032 22 ÓÅÎ 16:24 fsck 6334 -r-xr-xr-x 3 root wheel 290896 22 ÓÅÎ 15:41 fsck_4.2BSD 6334 -r-xr-xr-x 3 root wheel 290896 22 ÓÅÎ 15:41 fsck_ffs 6334 -r-xr-xr-x 3 root wheel 290896 22 ÓÅÎ 15:41 fsck_ufs -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 2:39:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (gate.interxion.com [194.153.74.13]) by hub.freebsd.org (Postfix) with ESMTP id 58A9137B423; Fri, 22 Sep 2000 02:39:04 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id eBNAfo338064; Sat, 23 Dec 2000 11:41:50 +0100 (CET) (envelope-from adrian) Date: Sat, 23 Dec 2000 11:41:50 +0100 From: Adrian Chadd To: Boris Popov Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Fsck wrappers, revisited Message-ID: <20001223114150.A38052@roaming.cacheboy.net> References: <20001223112038.A37548@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from bp@butya.kz on Fri, Sep 22, 2000 at 04:27:58PM +0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 22, 2000, Boris Popov wrote: > On Sat, 23 Dec 2000, Adrian Chadd wrote: > > > So now is a problem which I'm sure the NetBSD people came up against. > > The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed > > this by creating a new list 'mountnames[]', which maps the fs type to > > a string. > > Probably a hard link to fsck_ffs will do the job fine and makes it > clear to see which fs'es are supported: > > # ls -ail fsck* > 6338 -r-xr-xr-x 1 root wheel 66032 22 sen 16:24 fsck > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_4.2BSD > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_ffs > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_ufs The trouble is that some of the FS strings have spaces in their filenames. This might confuse a few people. Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 2:50:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (gate.interxion.com [194.153.74.13]) by hub.freebsd.org (Postfix) with ESMTP id 98F4137B424; Fri, 22 Sep 2000 02:50:09 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id e8M9o7m38193; Fri, 22 Sep 2000 11:50:07 +0200 (CEST) (envelope-from adrian) Date: Fri, 22 Sep 2000 11:50:07 +0200 From: Adrian Chadd To: freebsd-fs@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: Fsck wrappers, revisited Message-ID: <20000922115007.A38174@roaming.cacheboy.net> References: <20001222191317.A7529@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20001222191317.A7529@roaming.cacheboy.net>; from adrian@FreeBSD.ORG on Fri, Dec 22, 2000 at 07:13:17PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 22, 2000, Adrian Chadd wrote: > > > I've updated my fsck wrappers patchset to the latest netbsd and freebsd > fsck patches. I'd appreciate some feedback on them before I run off > and commit them (with my mentor, of course.) > > For those who aren't in the know, the general idea is that a single wrapper > program spawns a FS-specific fsck process a la mount and mount_*, making > multiple-FS support a lot easier. (Think about having fsck_ext2fs, fsck_msdos > and fsck_ffs doing your FSes on bootup..) > > They can be found at http://www.freebsd.org/~adrian/fsck/ . PLEASE read the > README before you use them, as there are a few gotchas. .. and I've just redone them again, with more bp comments. I've killed fsck_ffs/preen.c and moved the only function the fsck_ffs code now uses to a new util.c . This makes fsck_ffs a tiny bit smaller, and pretty much stomps on the shared code problem. Anyone else up for testing ? Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 4: 0:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id DDD4A37B423; Fri, 22 Sep 2000 04:00:08 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 0626E28805; Fri, 22 Sep 2000 18:00:04 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id E740828803; Fri, 22 Sep 2000 18:00:04 +0700 (ALMST) Date: Fri, 22 Sep 2000 18:00:04 +0700 (ALMST) From: Boris Popov To: Adrian Chadd Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Fsck wrappers, revisited In-Reply-To: <20001223114150.A38052@roaming.cacheboy.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Dec 2000, Adrian Chadd wrote: > On Fri, Sep 22, 2000, Boris Popov wrote: > > On Sat, 23 Dec 2000, Adrian Chadd wrote: > > > > > So now is a problem which I'm sure the NetBSD people came up against. > > > The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed > > > this by creating a new list 'mountnames[]', which maps the fs type to > > > a string. > > > > Probably a hard link to fsck_ffs will do the job fine and makes it > > clear to see which fs'es are supported: > > > > # ls -ail fsck* > > 6338 -r-xr-xr-x 1 root wheel 66032 22 sen 16:24 fsck > > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_4.2BSD > > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_ffs > > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_ufs > > The trouble is that some of the FS strings have spaces in their filenames. > This might confuse a few people. These (and probably other confusing) characters can be replaced with underscores without much harm. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 4:37:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (gate.interxion.com [194.153.74.13]) by hub.freebsd.org (Postfix) with ESMTP id B192A37B422; Fri, 22 Sep 2000 04:37:08 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id e8MBar711458; Fri, 22 Sep 2000 13:36:53 +0200 (CEST) (envelope-from adrian) Date: Fri, 22 Sep 2000 13:36:52 +0200 From: Adrian Chadd To: Boris Popov Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Fsck wrappers, revisited Message-ID: <20000922133652.A10844@roaming.cacheboy.net> References: <20001223114150.A38052@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from bp@butya.kz on Fri, Sep 22, 2000 at 06:00:04PM +0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 22, 2000, Boris Popov wrote: > On Sat, 23 Dec 2000, Adrian Chadd wrote: > > > On Fri, Sep 22, 2000, Boris Popov wrote: > > > On Sat, 23 Dec 2000, Adrian Chadd wrote: > > > > > > > So now is a problem which I'm sure the NetBSD people came up against. > > > > The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed > > > > this by creating a new list 'mountnames[]', which maps the fs type to > > > > a string. > > > > > > Probably a hard link to fsck_ffs will do the job fine and makes it > > > clear to see which fs'es are supported: > > > > > > # ls -ail fsck* > > > 6338 -r-xr-xr-x 1 root wheel 66032 22 sen 16:24 fsck > > > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_4.2BSD > > > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_ffs > > > 6334 -r-xr-xr-x 3 root wheel 290896 22 sen 15:41 fsck_ufs > > > > The trouble is that some of the FS strings have spaces in their filenames. > > This might confuse a few people. > > These (and probably other confusing) characters can be replaced > with underscores without much harm. That shouldn't be that hard to do. What do others think? Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 5:12:40 2000 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 98C6637B424; Fri, 22 Sep 2000 05:12:35 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id XAA12088; Fri, 22 Sep 2000 23:12:17 +1100 Date: Fri, 22 Sep 2000 23:12:13 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Takaya Ogawa Cc: current@FreeBSD.ORG, jasone@FreeBSD.ORG Subject: Re: new idle_proc() makes my laptop very hot In-Reply-To: <867l85y9sr.wl@triaez.kaisei.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Sep 2000, Takaya Ogawa wrote: > Attached patch adds back the HLT in i386 UP case and > seems to fix my problem, although I'm totally > unfamiliar with SMP nor alpha. This has the race bug that was fixed in rev.1.88 of swtch.s. I use the folowing fix. It also fixes the loss of page cleaning in the idle routine. It hasn't been committed mainly because idle page cleaning hasn't been tested for the SMP case or implemented for alphas (the alpha's vm_page_zero_idle() has apparently never been used). Most of the #include changes are unrelated. They are wrong fixes for spam in . diff -c2 kern_idle.c~ kern_idle.c *** kern_idle.c~ Sun Sep 17 04:27:14 2000 --- kern_idle.c Sun Sep 17 23:07:41 2000 *************** *** 29,34 **** #include #include - #include #include #include --- 29,41 ---- #include #include + #ifdef __i386__ /* XXX */ + #ifdef SMP + #include + #endif + #include + #include + #include + #endif #include #include *************** *** 40,43 **** --- 47,52 ---- #endif + extern void (*_hlt_vector)(void); + static void idle_setup(void *dummy); SYSINIT(idle_setup, SI_SUB_SCHED_IDLE, SI_ORDER_FIRST, idle_setup, NULL) *************** *** 84,88 **** --- 93,107 ---- count = 0; + #ifdef __i386__ + disable_intr(); + #endif while (count >= 0 && procrunnable() == 0) { + #ifdef __i386__ + if (vm_page_zero_idle() != 0) + continue; + (*_hlt_vector)(); + disable_intr(); + continue; + #endif /* * This is a good place to put things to be done in *************** *** 93,96 **** --- 112,118 ---- " for a process"); } + #ifdef __i386__ + enable_intr(); + #endif mtx_enter(&sched_lock, MTX_SPIN); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 6:13:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id B56BD37B422 for ; Fri, 22 Sep 2000 06:13:19 -0700 (PDT) Received: from rac4.wam.umd.edu (IDENT:root@rac4.wam.umd.edu [128.8.10.144]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA06669 for ; Fri, 22 Sep 2000 09:13:03 -0400 (EDT) Received: from rac4.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac4.wam.umd.edu (8.9.3/8.9.3) with SMTP id JAA26264 for ; Fri, 22 Sep 2000 09:13:03 -0400 (EDT) Received: from localhost (culverk@localhost) by rac4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA26259 for ; Fri, 22 Sep 2000 09:13:03 -0400 (EDT) X-Authentication-Warning: rac4.wam.umd.edu: culverk owned process doing -bs Date: Fri, 22 Sep 2000 09:13:03 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: fdc problem Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-969628383=:25277" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---559023410-851401618-969628383=:25277 Content-Type: TEXT/PLAIN; charset=US-ASCII as of a few days ago, for some reason my floppy drive controller does not probe right with -CURRENT... I've attached a dmesg, a kernel config, and my hints file as kernstuff.tar Please let me know if I've made some dumb mistake or something in my configs... Kenneth Culver ---559023410-851401618-969628383=:25277 Content-Type: APPLICATION/octet-stream; name="kernstuff.tar" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="kernstuff.tar" ZGV2aWNlLmhpbnRzAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAADEwMDY0NCAAICAxNzUxIAAgIDE3NTEgACAgICAgICAgNzYz ICA3MTYyNjU1MTQ0ICAxMzAxNwAgMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB1c3RhciAgAGN1bHZl cmsAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAY3VsdmVyawAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAABoaW50LmZkYy4wLmF0PSJpc2EiCmhpbnQuZmRj LjAucG9ydD0iMHgzRjAiCmhpbnQuZmRjLjAuaXJxPSI2IgpoaW50LmZkYy4w LmRycT0iMiIKaGludC5mZC4wLmF0PSJmZGMwIgpoaW50LmZkLjAuZHJpdmU9 IjAiCmhpbnQuYXRrYmRjLjAuYXQ9ImlzYSIKaGludC5hdGtiZGMuMC5wb3J0 PSIweDA2MCIKaGludC5hdGtiZC4wLmF0PSJhdGtiZGMiCmhpbnQuYXRrYmQu MC5pcnE9IjEiCmhpbnQuYXRrYmQuMC5mbGFncz0iMHgxIgpoaW50LnBzbS4w LmF0PSJhdGtiZGMiCmhpbnQucHNtLjAuaXJxPSIxMiIKaGludC52Z2EuMC5h dD0iaXNhIgpoaW50LnNjLjAuYXQ9ImlzYSIKaGludC5zYy4wLmZsYWdzPSIw eDEwMCIKaGludC5ucHguMC5hdD0ibmV4dXMiCmhpbnQubnB4LjAucG9ydD0i MHgwRjAiCmhpbnQubnB4LjAuaXJxPSIxMyIKaGludC5wcGMuMC5hdD0iaXNh IgpoaW50LnBwYy4wLmlycT0iNyIKaGludC5hcG0uMC5hdD0ibmV4dXMiCmhp bnQuYXBtLjAuZmxhZ3M9IjB4MCIKAAAAAAAAAAAAAAAAAE1ZS0VSTkVMAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAx MDA2NDQgACAgMTc1MSAAICAxNzUxIAAgICAgICAgNDA3MiAgNzE2MjY1NTEz MyAgMTE2NzUAIDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAdXN0YXIgIABjdWx2ZXJrAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAGN1bHZlcmsAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAbWFjaGluZQkJaTM4NgpjcHUJCUk2ODZfQ1BVCmlkZW50CQkiTVlL RVJORUwiCm1heHVzZXJzCTY0CgpvcHRpb25zIAlJTkVUCQkJI0ludGVyTkVU d29ya2luZwpvcHRpb25zIAlGRlMJCQkjQmVya2VsZXkgRmFzdCBGaWxlc3lz dGVtCm9wdGlvbnMgCUZGU19ST09UCQkjRkZTIHVzYWJsZSBhcyByb290IGRl dmljZSBba2VlcCB0aGlzIV0Kb3B0aW9ucyAJU09GVFVQREFURVMJCSNFbmFi bGUgRkZTIHNvZnQgdXBkYXRlcyBzdXBwb3J0Cm9wdGlvbnMgCVBST0NGUwkJ CSNQcm9jZXNzIGZpbGVzeXN0ZW0Kb3B0aW9ucyAJQ09NUEFUXzQzCQkjQ29t cGF0aWJsZSB3aXRoIEJTRCA0LjMgW0tFRVAgVEhJUyFdCm9wdGlvbnMgCVVD T05TT0xFCQkjQWxsb3cgdXNlcnMgdG8gZ3JhYiB0aGUgY29uc29sZQpvcHRp b25zIAlTWVNWU0hNCQkJI1NZU1Ytc3R5bGUgc2hhcmVkIG1lbW9yeQpvcHRp b25zIAlTWVNWTVNHCQkJI1NZU1Ytc3R5bGUgbWVzc2FnZSBxdWV1ZXMKb3B0 aW9ucyAJU1lTVlNFTQkJCSNTWVNWLXN0eWxlIHNlbWFwaG9yZXMKb3B0aW9u cyAJUDEwMDNfMUIJCSNQb3NpeCBQMTAwM18xQiByZWFsLXRpbWUgZXh0ZW5z aW9ucwpvcHRpb25zIAlfS1BPU0lYX1BSSU9SSVRZX1NDSEVEVUxJTkcKb3B0 aW9ucyAJS0JEX0lOU1RBTExfQ0RFVgkjIGluc3RhbGwgYSBDREVWIGVudHJ5 IGluIC9kZXYKCmRldmljZQkJaXNhCmRldmljZQkJcGNpCgojIEZsb3BweSBk cml2ZXMKZGV2aWNlCQlmZGMKCiMgQVRBIGFuZCBBVEFQSSBkZXZpY2VzCmRl dmljZQkJYXRhCmRldmljZQkJYXRhZGlzawkJCSMgQVRBIGRpc2sgZHJpdmVz CmRldmljZQkJYXRhcGljZAkJCSMgQVRBUEkgQ0RST00gZHJpdmVzCm9wdGlv bnMgCUFUQV9TVEFUSUNfSUQJCSNTdGF0aWMgZGV2aWNlIG51bWJlcmluZwpv cHRpb25zIAlBVEFfRU5BQkxFX0FUQVBJX0RNQQkjRW5hYmxlIERNQSBvbiBB VEFQSSBkZXZpY2VzCgojIGF0a2JkYzAgY29udHJvbHMgYm90aCB0aGUga2V5 Ym9hcmQgYW5kIHRoZSBQUy8yIG1vdXNlCmRldmljZQkJYXRrYmRjCTEKZGV2 aWNlCQlhdGtiZAoKZGV2aWNlCQl2Z2EKCiMgc3BsYXNoIHNjcmVlbi9zY3Jl ZW4gc2F2ZXIKZGV2aWNlCQlzcGxhc2gKCiMgc3lzY29ucyBpcyB0aGUgZGVm YXVsdCBjb25zb2xlIGRyaXZlciwgcmVzZW1ibGluZyBhbiBTQ08gY29uc29s ZQpkZXZpY2UJCXNjCTEKCiMgRmxvYXRpbmcgcG9pbnQgc3VwcG9ydCAtIGRv IG5vdCBkaXNhYmxlLgpkZXZpY2UJCW5weAoKIyBQb3dlciBtYW5hZ2VtZW50 IHN1cHBvcnQgKHNlZSBOT1RFUyBmb3IgbW9yZSBvcHRpb25zKQpkZXZpY2UJ CWFwbQoKIyBTZXJpYWwgKENPTSkgcG9ydHMKZGV2aWNlCQlzaW8KCiMgUGFy YWxsZWwgcG9ydApkZXZpY2UJCXBwYwpkZXZpY2UJCXBwYnVzCQkjIFBhcmFs bGVsIHBvcnQgYnVzIChyZXF1aXJlZCkKZGV2aWNlCQlscHQJCSMgUHJpbnRl cgoKCiMgUENJIEV0aGVybmV0IE5JQ3MuCmRldmljZQkJZGUJCSMgREVDL0lu dGVsIERDMjF4NHggKGBgVHVsaXAnJykKCiMgUENJIEV0aGVybmV0IE5JQ3Mg dGhhdCB1c2UgdGhlIGNvbW1vbiBNSUkgYnVzIGNvbnRyb2xsZXIgY29kZS4K ZGV2aWNlCQltaWlidXMJCSMgTUlJIGJ1cyBzdXBwb3J0CmRldmljZQkJeGwJ CSMgM0NvbSAzYzkweCAoYGBCb29tZXJhbmcnJywgYGBDeWNsb25lJycpCgoj IFBzZXVkbyBkZXZpY2VzIC0gdGhlIG51bWJlciBpbmRpY2F0ZXMgaG93IG1h bnkgdW5pdHMgdG8gYWxsb2NhdGVkLgpkZXZpY2UJCXJhbmRvbQkJIyBFbnRy b3B5IGRldmljZQpkZXZpY2UJCWxvb3AJCSMgTmV0d29yayBsb29wYmFjawpk ZXZpY2UJCWV0aGVyCQkjIEV0aGVybmV0IHN1cHBvcnQKZGV2aWNlCQlwdHkJ CSMgUHNldWRvLXR0eXMgKHRlbG5ldCBldGMpCgojIFRoZSBgYnBmJyBkZXZp Y2UgZW5hYmxlcyB0aGUgQmVya2VsZXkgUGFja2V0IEZpbHRlci4KIyBCZSBh d2FyZSBvZiB0aGUgYWRtaW5pc3RyYXRpdmUgY29uc2VxdWVuY2VzIG9mIGVu YWJsaW5nIHRoaXMhCmRldmljZQkJYnBmCQkjIEJlcmtlbGV5IHBhY2tldCBm aWx0ZXIKCm9wdGlvbnMgU0NfRElTQUJMRV9SRUJPT1QKCm9wdGlvbnMgICAg ICAgICBJUEZJUkVXQUxMCm9wdGlvbnMgICAgICAgICBJUERJVkVSVAoKAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AGRtZXNnLm91dAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAxMDA2NDQgACAgMTc1MSAAICAxNzUxIAAgICAgICAgNzY1 NCAgNzE2MjY1NTIyNCAgMTIzNjYAIDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAdXN0YXIgIABjdWx2 ZXJrAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGN1bHZlcmsAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAQ29weXJpZ2h0IChjKSAxOTkyLTIwMDAgVGhl IEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChjKSAxOTc5LCAxOTgwLCAx OTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAxOTk0 CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlh LiBBbGwgcmlnaHRzIHJlc2VydmVkLgpGcmVlQlNEIDUuMC1DVVJSRU5UICMw OiBGcmkgU2VwIDIyIDAyOjA2OjM4IEVEVCAyMDAwCiAgICBjdWx2ZXJrQGN1 bHZlcmsuc3R1ZGVudC51bWQuZWR1Oi91c3Ivc3JjL3N5cy9jb21waWxlL01Z S0VSTkVMClRpbWVjb3VudGVyICJpODI1NCIgIGZyZXF1ZW5jeSAxMTkzMTgy IEh6CkNQVTogUGVudGl1bSBJSS9QZW50aXVtIElJIFhlb24vQ2VsZXJvbiAo NDUxLjAyLU1IeiA2ODYtY2xhc3MgQ1BVKQogIE9yaWdpbiA9ICJHZW51aW5l SW50ZWwiICBJZCA9IDB4NjUyICBTdGVwcGluZyA9IDIKICBGZWF0dXJlcz0w eDE4M2Y5ZmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixQQUUsTUNFLENYOCxT RVAsTVRSUixQR0UsTUNBLENNT1YsUEFULFBTRTM2LE1NWCxGWFNSPgpyZWFs IG1lbW9yeSAgPSAxMzQxNTIxOTIgKDEzMTAwOEsgYnl0ZXMpCmF2YWlsIG1l bW9yeSA9IDEyNzYxOTA3MiAoMTI0NjI4SyBieXRlcykKUHJlbG9hZGVkIGVs ZiBrZXJuZWwgImtlcm5lbCIgYXQgMHhjMDJlNDAwMC4KUHJlbG9hZGVkIGVs ZiBtb2R1bGUgInVzYi5rbyIgYXQgMHhjMDJlNDA5Yy4KUHJlbG9hZGVkIGVs ZiBtb2R1bGUgInVtcy5rbyIgYXQgMHhjMDJlNDEzOC4KUHJlbG9hZGVkIGVs ZiBtb2R1bGUgImJrdHIua28iIGF0IDB4YzAyZTQxZDQuClByZWxvYWRlZCBl bGYgbW9kdWxlICJia3RyX21lbS5rbyIgYXQgMHhjMDJlNDI3MC4KUHJlbG9h ZGVkIGVsZiBtb2R1bGUgInNuZF9lczEzN3gua28iIGF0IDB4YzAyZTQzMTAu ClByZWxvYWRlZCBlbGYgbW9kdWxlICJzbmRfcGNtLmtvIiBhdCAweGMwMmU0 M2I0Lgpia3RyX21lbTogbWVtb3J5IGhvbGRlciBsb2FkZWQKUGVudGl1bSBQ cm8gTVRSUiBzdXBwb3J0IGVuYWJsZWQKYXBtMDogPEFQTSBCSU9TPiBvbiBt b3RoZXJib2FyZAphcG0wOiBmb3VuZCBBUE0gQklPUyB2MS4yLCBjb25uZWN0 ZWQgYXQgdjEuMgpucHgwOiA8bWF0aCBwcm9jZXNzb3I+IG9uIG1vdGhlcmJv YXJkCm5weDA6IElOVCAxNiBpbnRlcmZhY2UKcGNpYjA6IDxJbnRlbCA4MjQ0 M0JYICg0NDAgQlgpIGhvc3QgdG8gUENJIGJyaWRnZT4gb24gbW90aGVyYm9h cmQKcGNpMDogPFBDSSBidXM+IG9uIHBjaWIwCnBjaWIxOiA8SW50ZWwgODI0 NDNCWCAoNDQwIEJYKSBQQ0ktUENJIChBR1ApIGJyaWRnZT4gYXQgZGV2aWNl IDEuMCBvbiBwY2kwCnBjaTE6IDxQQ0kgYnVzPiBvbiBwY2liMQpwY2kxOiA8 SW50ZWwgaTc0MCBBR1AgU1ZHQSBjb250cm9sbGVyPiBhdCAwLjAKaXNhYjA6 IDxJbnRlbCA4MjM3MUFCIFBDSSB0byBJU0EgYnJpZGdlPiBhdCBkZXZpY2Ug Ny4wIG9uIHBjaTAKaXNhMDogPElTQSBidXM+IG9uIGlzYWIwCmF0YXBjaTA6 IDxJbnRlbCBQSUlYNCBBVEEzMyBjb250cm9sbGVyPiBwb3J0IDB4ZjAwMC0w eGYwMGYgYXQgZGV2aWNlIDcuMSBvbiBwY2kwCmF0YTA6IGF0IDB4MWYwIGly cSAxNCBvbiBhdGFwY2kwCmF0YTE6IGF0IDB4MTcwIGlycSAxNSBvbiBhdGFw Y2kwCnVoY2kwOiA8SW50ZWwgODIzNzFBQi9FQiAoUElJWDQpIFVTQiBjb250 cm9sbGVyPiBwb3J0IDB4ZTAwMC0weGUwMWYgaXJxIDExIGF0IGRldmljZSA3 LjIgb24gcGNpMAp1c2IwOiA8SW50ZWwgODIzNzFBQi9FQiAoUElJWDQpIFVT QiBjb250cm9sbGVyPiBvbiB1aGNpMAp1c2IwOiBVU0IgcmV2aXNpb24gMS4w CnVodWIwOiBJbnRlbCBVSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAx LjAwLzEuMDAsIGFkZHIgMQp1aHViMDogMiBwb3J0cyB3aXRoIDIgcmVtb3Zh YmxlLCBzZWxmIHBvd2VyZWQKdW1zMDogTG9naXRlY2ggVVNCIE1vdXNlLCBy ZXYgMS4xMC82LjEwLCBhZGRyIDIsIGljbGFzcyAzLzEKdW1zMDogNCBidXR0 b25zIGFuZCBaIGRpci4KcGNpMDogPEludGVsIDgyMzcxQUIgUG93ZXIgbWFu YWdlbWVudCBjb250cm9sbGVyPiBhdCA3LjMKcGNpMDogPDNEZnggVm9vZG9v IDIgZ3JhcGhpY3MgYWNjZWxlcmF0b3I+IGF0IDkuMApia3RyMDogPEJyb29r VHJlZSA4Nzg+IG1lbSAweGVhMDAxMDAwLTB4ZWEwMDFmZmYgaXJxIDExIGF0 IGRldmljZSAxMy4wIG9uIHBjaTAKYmt0cjA6IEhhdXBwYXVnZSBNb2RlbCA2 MTI5MSBEMTEwCmJrdHIwOiBIYXVwcGF1Z2UgV2luQ2FzdC9UViwgUGhpbGlw cyBOVFNDIHR1bmVyLCByZW1vdGUgY29udHJvbC4KcGNpMDogPHVua25vd24g Y2FyZD4gKHZlbmRvcj0weDEwOWUsIGRldj0weDA4NzgpIGF0IDEzLjEgaXJx IDExCnhsMDogPDNDb20gM2M5MDBCLVRQTyBFdGhlcmxpbmsgWEw+IHBvcnQg MHhlNDAwLTB4ZTQ3ZiBtZW0gMHhlYTAwMDAwMC0weGVhMDAwMDdmIGlycSA1 IGF0IGRldmljZSAxNS4wIG9uIHBjaTAKeGwwOiBFdGhlcm5ldCBhZGRyZXNz OiAwMDowMTowMjo3MjpkNTpiYwp4bDA6IHNlbGVjdGluZyAxMGJhc2VUIHRy YW5zY2VpdmVyLCBoYWxmIGR1cGxleApkZTA6IDxEaWdpdGFsIDIxMTQwQSBG YXN0IEV0aGVybmV0PiBwb3J0IDB4ZTgwMC0weGU4N2YgbWVtIDB4ZWEwMDIw MDAtMHhlYTAwMjA3ZiBpcnEgMTIgYXQgZGV2aWNlIDE3LjAgb24gcGNpMApk ZTA6IDIxMTQwQSBbMTAtMTAwTWIvc10gcGFzcyAyLjIKZGUwOiBhZGRyZXNz IDAwOmMwOmYwOjFmOjIxOjAyCnBjbTA6IDxBdWRpb1BDSSBFUzEzNzE+IHBv cnQgMHhlYzAwLTB4ZWMzZiBpcnEgMTAgYXQgZGV2aWNlIDE5LjAgb24gcGNp MAppc2EwOiB0b28gbWFueSBkZXBlbmRhbnQgY29uZmlncyAoOCkKc2MwOiA8 U3lzdGVtIGNvbnNvbGU+IG9uIGlzYTAKc2MwOiBWR0EgPDE2IHZpcnR1YWwg Y29uc29sZXMsIGZsYWdzPTB4MjAwPgp2Z2EwOiA8R2VuZXJpYyBJU0EgVkdB PiBhdCBwb3J0IDB4M2MwLTB4M2RmIGlvbWVtIDB4YTAwMDAtMHhiZmZmZiBv biBpc2EwCmF0a2JkYzA6IDxLZXlib2FyZCBjb250cm9sbGVyIChpODA0Mik+ IGF0IHBvcnQgMHg2MCwweDY0IG9uIGlzYTAKYXRrYmQwOiA8QVQgS2V5Ym9h cmQ+IGZsYWdzIDB4MSBpcnEgMSBvbiBhdGtiZGMwCmtiZDAgYXQgYXRrYmQw CmZkYzA6IGNhbm5vdCByZXNlcnZlIEkvTyBwb3J0IHJhbmdlCnBwYzA6IDxQ YXJhbGxlbCBwb3J0PiBhdCBwb3J0IDB4Mzc4LTB4MzdmIGlycSA3IG9uIGlz YTAKcHBjMDogR2VuZXJpYyBjaGlwc2V0IChFUFAvTklCQkxFKSBpbiBDT01Q QVRJQkxFIG1vZGUKbHB0MDogPFByaW50ZXI+IG9uIHBwYnVzMApscHQwOiBJ bnRlcnJ1cHQtZHJpdmVuIHBvcnQKdW5rbm93bjogPFBOUDAzMDM+IGNhbid0 IGFzc2lnbiByZXNvdXJjZXMKdW5rbm93bjogPFBOUDA3MDA+IGNhbid0IGFz c2lnbiByZXNvdXJjZXMKdW5rbm93bjogPFBOUDA0MDA+IGNhbid0IGFzc2ln biByZXNvdXJjZXMKc2lvMDogPFN1cHJhRXhwcmVzcyA1Nmk+IGF0IHBvcnQg MHgzZjgtMHgzZmYgaXJxIDQgb24gaXNhMApzaW8wOiB0eXBlIDE2NTUwQQpJ UCBwYWNrZXQgZmlsdGVyaW5nIGluaXRpYWxpemVkLCBkaXZlcnQgZW5hYmxl ZCwgcnVsZS1iYXNlZCBmb3J3YXJkaW5nIGRpc2FibGVkLCBkZWZhdWx0IHRv IGRlbnksIGxvZ2dpbmcgZGlzYWJsZWQKYWQwOiA4MDYzTUIgPE1heHRvciA5 MDg0NUQ0PiBbMTYzODMvMTYvNjNdIGF0IGF0YTAtbWFzdGVyIFVETUEzMwph ZDE6IDEzMDI5TUIgPE1heHRvciA5MTM2NlU0PiBbMjY0NzMvMTYvNjNdIGF0 IGF0YTAtc2xhdmUgVURNQTMzCmF0YTEtbWFzdGVyOiBETUEgbGltaXRlZCB0 byBVRE1BMzMsIG5vbi1BVEE2NiBjb21wbGlhbnQgY2FibGUKYWQyOiAxNDY1 NU1CIDxNYXh0b3IgNTE1MzZIMz4gWzI5Nzc3LzE2LzYzXSBhdCBhdGExLW1h c3RlciBVRE1BMzMKYWNkMDogRFZELVJPTSA8VE9TSElCQSBEVkQtUk9NIFNE LU0xMjEyPiBhdCBhdGExLXNsYXZlIHVzaW5nIFVETUEzMwpNb3VudGluZyBy b290IGZyb20gdWZzOi9kZXYvYWQxczFhCgAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA== ---559023410-851401618-969628383=:25277-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 7:18:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from wsjk03.kmjeuro.com (151ppp.infohighway.proline.at [212.236.19.5]) by hub.freebsd.org (Postfix) with ESMTP id BC3EF37B423 for ; Fri, 22 Sep 2000 07:18:36 -0700 (PDT) Received: from notebook (localhost [127.0.0.1]) by localhost.kmjeuro.com (8.11.0/8.11.0) with SMTP id e8MDIXb00468; Fri, 22 Sep 2000 15:18:35 +0200 (CEST) From: "Karl M. Joch" To: freebsd-current@freebsd.org Subject: Notebook Status after CVSup again Date: Fri, 22 Sep 2000 15:18:33 +0200 X-Mailer: KMail [version 1.1.94] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00092215183300.00423@notebook> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG after doing a CVSup this morning and make buildworld, kernel, installkernel, installworld again i have the following status: fdc0 doesnt get recogniced (conflict with pccard at 3f0). need to find how to change the I/O of the pccard controller. sometimes fdc0 writes cannot reserve I/O range. reboot still hangs the pc after a complete shutdown forever. zzz runs in the same problem. disabling apm doesnt help also with removing apm from the kernel. after changing: rc, rc.i386, rc.nework adding /boot/kernel for kldload, kldstat shows linux emulation is loaded. but the rtc and vmware ko's still prints Exec format error (+undefined lines see later) and doesnt load. except that it runs fine. KDE/X, Samba and everything else looks like running smoothly. best regards, Karl enclosed some lines of messages: Sep 22 14:53:35 notebook /boot/kernel/kernel: fdc0: direction bit not set Sep 22 14:53:35 notebook /boot/kernel/kernel: fdc0: cmd 3 failed at out byte 1 of 3 Sep 22 14:53:35 notebook /boot/kernel/kernel: pmtimer0 on isa0 Sep 22 14:53:35 notebook /boot/kernel/kernel: sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 Sep 22 14:53:36 notebook /boot/kernel/kernel: pcm0: on sbc0 Sep 22 14:53:36 notebook /boot/kernel/kernel: midi0: on sbc0 Sep 22 14:53:36 notebook /boot/kernel/kernel: midi1: on sbc0 Sep 22 14:53:36 notebook /boot/kernel/kernel: sio4: at port 0x2f8-0x2ff irq 3 on isa0 Sep 22 14:53:36 notebook /boot/kernel/kernel: sio4: type 16550A Sep 22 14:53:36 notebook /boot/kernel/kernel: fdc1: direction bit not set Sep 22 14:53:36 notebook /boot/kernel/kernel: fdc1: cmd 3 failed at out byte 1 of 3 ********* LOAD OF RTC Sep 22 14:53:48 notebook /boot/kernel/kernel: link_elf: symbol lminor undefined ******** LOAD OF VMWARE Sep 22 14:53:55 notebook /boot/kernel/kernel: link_elf: symbol linux_ioctl_register_handler undefined Sep 22 14:54:03 notebook login: ROOT LOGIN (root) ON ttyv0 -- ------------------------------------------------------------ Karl M. Joch k_joch@yahoo.com ------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 7:48:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with ESMTP id C63B737B424 for ; Fri, 22 Sep 2000 07:48:34 -0700 (PDT) Received: (from bugs@localhost) by freebsd.netcom.com (8.8.8+Sun/8.8.8) id JAA20935 for freebsd-current@FreeBSD.ORG; Fri, 22 Sep 2000 09:48:42 -0500 (CDT) From: Mark Hittinger Message-Id: <200009221448.JAA20935@freebsd.netcom.com> Subject: fdc0 and ata1 issues To: freebsd-current@FreeBSD.ORG Date: Fri, 22 Sep 2000 09:48:42 -0500 (CDT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range". The same kernel that I began to see the fdc0 problems I also lost the ability to use devices on ata1. Ata1 seems to probe OK but I get I/O errors on the ata1 drives all of a sudden. A kernel from a week ago is OK. Later Mark Hittinger Earthlink bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 8: 1: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from lavender.sanpei.org (ppp155.dialup.st.keio.ac.jp [131.113.27.155]) by hub.freebsd.org (Postfix) with ESMTP id 3FC6C37B424 for ; Fri, 22 Sep 2000 08:00:58 -0700 (PDT) Received: (from sanpei@localhost) by lavender.sanpei.org (8.11.0/3.7W) id e8MF0Me01325; Sat, 23 Sep 2000 00:00:22 +0900 (JST) Message-Id: <200009221500.e8MF0Me01325@lavender.sanpei.org> To: bde@zeta.org.au Cc: imp@village.org, current@FreeBSD.ORG From: sanpei@FreeBSD.ORG Subject: Re: Please review: small change in sys/i386/isa/clock.c andsys/alpha/alpha/clock.c for PC-Card melody beep code. In-Reply-To: Your message of "Mon, 18 Sep 2000 23:47:49 +1100 (EST)" References: X-Mailer: Mew version 1.70 on Emacs 19.34.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 23 Sep 2000 00:00:21 +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: >On Sun, 17 Sep 2000, Warner Losh wrote: > >> I've seen these patches many times and think that it is a good idea. >> This interface needs to be exported so that the pccard system sounds >> don't interfere with normal systme sounds. > >It needs locking changes to be exportable: > >1) splhigh()/splx(), at least in RELENG_4 where there is no giant lock > and spl*() has a non-null effect, so that callers don't need to know > that it must be called at splsoftclock() or higher. >2) Honor the current locking protocol acquire_timer2()/release_timer2() > -- don't do anything if (!beeping). Hum, is below code which was from PAO3 good for FreeBSD tree? # But I think it has still has 1) problem....... Do you have any # idea about this melody patch... Cheers. --- MIHIRA, Sanpei Yoshiro Yokohama, Japan. --- sys/i386/isa/clock.c.org Mon Jan 3 10:46:36 2000 +++ sys/i386/isa/clock.c Mon Jan 3 10:47:52 2000 @@ -188,6 +188,9 @@ SYSCTL_OPAQUE(_debug, OID_AUTO, tsc_timecounter, CTLFLAG_RD, &tsc_timecounter, sizeof(tsc_timecounter), "S,timecounter", ""); +static struct callout_handle sysbeep_ch + = CALLOUT_HANDLE_INITIALIZER(&sysbeep_ch); + static struct timecounter i8254_timecounter = { i8254_get_timecount, /* get_timecount */ 0, /* no poll_pps */ @@ -536,10 +539,21 @@ /* enable counter2 output to speaker */ outb(IO_PPI, inb(IO_PPI) | 3); beeping = period; - timeout(sysbeepstop, (void *)NULL, period); + sysbeep_ch = timeout(sysbeepstop, (void *)NULL, period); } splx(x); return (0); +} + +int +sysbeep_cancel(void) +{ + if (beeping) { + untimeout(sysbeepstop, (void *)NULL, sysbeep_ch); + sysbeepstop((void *)NULL); + return 0; + } + return -1; } /* --- sys/i386/include/clock.h.org Mon Jan 3 10:58:30 2000 +++ sys/i386/include/clock.h Mon Jan 3 10:59:13 2000 @@ -44,6 +44,7 @@ int release_timer1 __P((void)); #endif int sysbeep __P((int pitch, int period)); +int sysbeep_cancel __P((void)); void i8254_restore __P((void)); #endif /* _KERNEL */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 9: 0:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 0825837B43F for ; Fri, 22 Sep 2000 09:00:21 -0700 (PDT) Received: (qmail 16136 invoked from network); 22 Sep 2000 16:00:16 -0000 Received: from unknown (HELO bde.zeta.org.au) (203.2.228.102) by gidora.zeta.org.au with SMTP; 22 Sep 2000 16:00:16 -0000 Date: Sat, 23 Sep 2000 03:00:11 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Adrian Chadd Cc: freebsd-fs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Fsck wrappers, revisited In-Reply-To: <20001223112038.A37548@roaming.cacheboy.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Dec 2000, Adrian Chadd wrote: > Here's the patch: > > --- fsck.c.orig Sat Dec 23 11:13:30 2000 > +++ fsck.c Sat Dec 23 11:13:34 2000 > @@ -501,7 +501,7 @@ > errx(1, "partition `%s' is not of a legal vfstype", > str); > - if ((vfstype = dktypenames[t]) == NULL) > + if ((vfstype = fstypenames[t]) == NULL) > errx(1, "vfstype `%s' on partition `%s' is not supported", > fstypenames[t], str); > > > So now is a problem which I'm sure the NetBSD people came up against. > The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed > this by creating a new list 'mountnames[]', which maps the fs type to > a string. fs typenames are already strings in FreeBSD (the kernel's vfc_index is an implementation detail which should not be visible in applications). > http://cvsweb.netbsd.org/bsdweb.cgi/syssrc/sys/sys/disklabel.h.diff?r1=1.60&r2=1.61 > > What do people think about doing this as well? It would certainly make things > a little tidier, but every time a new fs comes in the magic autodetection code > will need to be updated (if appropriate, of course.) This would be a bug. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 9:40:13 2000 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 289C937B43E; Fri, 22 Sep 2000 09:40:05 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id DAA22714; Sat, 23 Sep 2000 03:39:55 +1100 Date: Sat, 23 Sep 2000 03:39:51 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: sanpei@FreeBSD.ORG Cc: imp@village.org, current@FreeBSD.ORG Subject: Re: Please review: small change in sys/i386/isa/clock.c andsys/alpha/alpha/clock.c for PC-Card melody beep code. In-Reply-To: <200009221500.e8MF0Me01325@lavender.sanpei.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Sep 2000 sanpei@FreeBSD.ORG wrote: > Bruce Evans wrote: > >It needs locking changes to be exportable: > > > >1) splhigh()/splx(), at least in RELENG_4 where there is no giant lock > > and spl*() has a non-null effect, so that callers don't need to know > > that it must be called at splsoftclock() or higher. > >2) Honor the current locking protocol acquire_timer2()/release_timer2() > > -- don't do anything if (!beeping). > > Hum, is below code which was from PAO3 good for FreeBSD tree? > > # But I think it has still has 1) problem....... Do you have any > # idea about this melody patch... Yes, it has (1) (sysbeep_cancel() must be called at splsoftlock() or maybe at splclock(), while sysbeep() can be called at any ipl). sysbeep_cancel() is a little cleaner -- sysbeepstop() is the timeout routine and calling it directly is a hack. sysbeep_ch could probably be avoided by letting the timeout expire and doing nothing if !beeping. Bruce > --- sys/i386/isa/clock.c.org Mon Jan 3 10:46:36 2000 > +++ sys/i386/isa/clock.c Mon Jan 3 10:47:52 2000 > @@ -188,6 +188,9 @@ > SYSCTL_OPAQUE(_debug, OID_AUTO, tsc_timecounter, CTLFLAG_RD, > &tsc_timecounter, sizeof(tsc_timecounter), "S,timecounter", ""); > > +static struct callout_handle sysbeep_ch > + = CALLOUT_HANDLE_INITIALIZER(&sysbeep_ch); > + > static struct timecounter i8254_timecounter = { > i8254_get_timecount, /* get_timecount */ > 0, /* no poll_pps */ > @@ -536,10 +539,21 @@ > /* enable counter2 output to speaker */ > outb(IO_PPI, inb(IO_PPI) | 3); > beeping = period; > - timeout(sysbeepstop, (void *)NULL, period); > + sysbeep_ch = timeout(sysbeepstop, (void *)NULL, period); > } > splx(x); > return (0); > +} > + > +int > +sysbeep_cancel(void) > +{ > + if (beeping) { > + untimeout(sysbeepstop, (void *)NULL, sysbeep_ch); > + sysbeepstop((void *)NULL); > + return 0; > + } > + return -1; > } > > /* > --- sys/i386/include/clock.h.org Mon Jan 3 10:58:30 2000 > +++ sys/i386/include/clock.h Mon Jan 3 10:59:13 2000 > @@ -44,6 +44,7 @@ > int release_timer1 __P((void)); > #endif > int sysbeep __P((int pitch, int period)); > +int sysbeep_cancel __P((void)); > void i8254_restore __P((void)); > > #endif /* _KERNEL */ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 12:37:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 4BC4537B422 for ; Fri, 22 Sep 2000 12:37:34 -0700 (PDT) Received: from rac3.wam.umd.edu (IDENT:root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA16076 for ; Fri, 22 Sep 2000 15:37:32 -0400 (EDT) Received: from rac3.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id PAA28473 for ; Fri, 22 Sep 2000 15:37:32 -0400 (EDT) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id PAA28469 for ; Fri, 22 Sep 2000 15:37:32 -0400 (EDT) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Fri, 22 Sep 2000 15:37:32 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: -CURRENT crashes under heavy disk activity Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I will try to build a debug kernel, and get a backtrace of what's happening to send to the list, but basically what happened is that I was running a cvsup of the cvs source repository and the ports repository and it just crashed and rebooted (I'm doing this remotely, so I can't really catch any messeges that get sent to the screen right now, not until I go home from work). The second time it happened was doing the cvs update of my source tree and ports tree, and it just crashed and rebooted.. I will make a debug kernel and do a backtrace and send it as soon as I possibly can. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 12:56:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (roaming.cacheboy.net [203.56.168.69]) by hub.freebsd.org (Postfix) with ESMTP id 02F5C37B424; Fri, 22 Sep 2000 12:56:17 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id e8MJtu600558; Fri, 22 Sep 2000 21:55:56 +0200 (CEST) (envelope-from adrian) Date: Fri, 22 Sep 2000 21:55:55 +0200 From: Adrian Chadd To: Bruce Evans Cc: freebsd-fs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Fsck wrappers, revisited Message-ID: <20000922215555.A449@roaming.cacheboy.net> References: <20001223112038.A37548@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from bde@zeta.org.au on Sat, Sep 23, 2000 at 03:00:11AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 23, 2000, Bruce Evans wrote: > On Sat, 23 Dec 2000, Adrian Chadd wrote: > > > Here's the patch: > > > > --- fsck.c.orig Sat Dec 23 11:13:30 2000 > > +++ fsck.c Sat Dec 23 11:13:34 2000 > > @@ -501,7 +501,7 @@ > > errx(1, "partition `%s' is not of a legal vfstype", > > str); > > - if ((vfstype = dktypenames[t]) == NULL) > > + if ((vfstype = fstypenames[t]) == NULL) > > errx(1, "vfstype `%s' on partition `%s' is not supported", > > fstypenames[t], str); > > > > > > So now is a problem which I'm sure the NetBSD people came up against. > > The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed > > this by creating a new list 'mountnames[]', which maps the fs type to > > a string. > > fs typenames are already strings in FreeBSD (the kernel's vfc_index is an > implementation detail which should not be visible in applications). > > > http://cvsweb.netbsd.org/bsdweb.cgi/syssrc/sys/sys/disklabel.h.diff?r1=1.60&r2=1.61 > > > > What do people think about doing this as well? It would certainly make things > > a little tidier, but every time a new fs comes in the magic autodetection code > > will need to be updated (if appropriate, of course.) > > This would be a bug. So what would your suggestion here be? This is only used if a -t isn't given or you don't have an entry in /etc/fstab, so I personally don't think its a big issue. Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 13:31:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id CB0D137B423 for ; Fri, 22 Sep 2000 13:31:17 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA18511; Fri, 22 Sep 2000 22:35:39 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009222035.WAA18511@freebsd.dk> Subject: Re: -CURRENT crashes under heavy disk activity In-Reply-To: from Kenneth Wayne Culver at "Sep 22, 2000 03:37:32 pm" To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Fri, 22 Sep 2000 22:35:39 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kenneth Wayne Culver wrote: > I will try to build a debug kernel, and get a backtrace of what's > happening to send to the list, but basically what happened is that I was > running a cvsup of the cvs source repository and the ports repository and > it just crashed and rebooted (I'm doing this remotely, so I can't really > catch any messeges that get sent to the screen right now, not until I go > home from work). The second time it happened was doing the cvs update of > my source tree and ports tree, and it just crashed and rebooted.. I will > make a debug kernel and do a backtrace and send it as soon as I possibly > can. I see that too, and more frequently just total hangs, remember -current is not close to being stable due to the SMPng work, so if you need decent stability go back to the PRE_SMPNG tag (I have, and I'm happy)... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 13:34:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id 47BDE37B423 for ; Fri, 22 Sep 2000 13:34:24 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id WAA49982; Fri, 22 Sep 2000 22:33:50 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.0/8.8.8) with ESMTP id e8MLXel01959; Fri, 22 Sep 2000 23:33:40 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Fri, 22 Sep 2000 23:33:39 +0200 (CEST) From: Michael Reifenberger To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: -CURRENT crashes under heavy disk activity In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Sep 2000, Kenneth Wayne Culver wrote: ... > To: freebsd-current@FreeBSD.ORG > Subject: -CURRENT crashes under heavy disk activity This is a well known issue. See the -current archive for more information. Search for "vmstat" and "FFS". Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 13:58: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id AF3F037B443 for ; Fri, 22 Sep 2000 13:57:55 -0700 (PDT) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA21635; Fri, 22 Sep 2000 16:57:37 -0400 (EDT) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id QAA15979; Fri, 22 Sep 2000 16:57:37 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id QAA15974; Fri, 22 Sep 2000 16:57:36 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Fri, 22 Sep 2000 16:57:36 -0400 (EDT) From: Kenneth Wayne Culver To: Michael Reifenberger Cc: freebsd-current@FreeBSD.ORG Subject: Re: -CURRENT crashes under heavy disk activity In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alright, I think I may just do that too... I was going to try to tough it out... but it looks like that just won't work.... I wish there was some way to get the other changes without getting the SMP stuff though. ================================================================= | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Fri, 22 Sep 2000, Michael Reifenberger wrote: > On Fri, 22 Sep 2000, Kenneth Wayne Culver wrote: > ... > > To: freebsd-current@FreeBSD.ORG > > Subject: -CURRENT crashes under heavy disk activity > This is a well known issue. > See the -current archive for more information. > Search for "vmstat" and "FFS". > > Bye! > ---- > Michael Reifenberger > ^.*Plaut.*$, IT, R/3 Basis, GPS > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 14: 4: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C215E37B422 for ; Fri, 22 Sep 2000 14:04:01 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id XAA26726; Fri, 22 Sep 2000 23:08:22 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009222108.XAA26726@freebsd.dk> Subject: Re: -CURRENT crashes under heavy disk activity In-Reply-To: from Kenneth Wayne Culver at "Sep 22, 2000 04:57:36 pm" To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Fri, 22 Sep 2000 23:08:22 +0200 (CEST) Cc: root@nihil.plaut.de (Michael Reifenberger), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kenneth Wayne Culver wrote: > Alright, I think I may just do that too... I was going to try to tough it > out... but it looks like that just won't work.... I wish there was some > way to get the other changes without getting the SMP stuff though. You update the ata driver to the lastest no probs that I know :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 14:34:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 3000F37B424 for ; Fri, 22 Sep 2000 14:34:39 -0700 (PDT) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id XAA13213; Fri, 22 Sep 2000 23:35:05 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 13caSl-0007dA-00 for ; Fri, 22 Sep 2000 23:34:31 +0200 Date: Fri, 22 Sep 2000 23:34:31 +0200 From: Szilveszter Adam To: freebsd-current@FreeBSD.ORG Subject: Re: fdc0 and ata1 issues Message-ID: <20000922233431.A29258@petra.hos.u-szeged.hu> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <200009221448.JAA20935@freebsd.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: <200009221448.JAA20935@freebsd.netcom.com>; from bugs@freebsd.netcom.com on Fri, Sep 22, 2000 at 09:48:42AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 22, 2000 at 09:48:42AM -0500, Mark Hittinger wrote: > > I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range". I am also seeing this with a kernel and world from today... also, are there any issues with mount_cd9660? When I issue the following command: # mount -t cd9660 -r /dev/acd0c /cdrom I get: cd9660: Invalid argument Is this already known? -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 15:11:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 81B8D37B422 for ; Fri, 22 Sep 2000 15:11:38 -0700 (PDT) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id AAA05580; Sat, 23 Sep 2000 00:11:29 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.0/8.11.0) with ESMTP id e8MLhnN95431; Fri, 22 Sep 2000 23:43:51 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Fri, 22 Sep 2000 23:43:49 +0200 (CEST) From: Leif Neland To: Brian Somers Cc: freebsd-current@FreeBSD.ORG Subject: Re: ppp.linkdown In-Reply-To: <200008122034.VAA02385@hak.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 12 Aug 2000, Brian Somers wrote: > > Is ppp.linkdown executed before or after the link is down? > > > > I'd like to change a dyndns, but will link activity done in linkdown defeat > > the timeout, or start a new call? > > It'll start a new call in auto mode. > So any ideas how to use dyndns? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 15:46:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 25ADE37B505 for ; Fri, 22 Sep 2000 15:44:18 -0700 (PDT) Received: (from uucp@localhost) by ns.internet.dk (8.9.3/8.9.3) with UUCP id AAA56579 for freebsd-current@freebsd.org; Sat, 23 Sep 2000 00:44:15 +0200 (CEST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.0/8.11.0) with ESMTP id e8MMFVN01606 for ; Sat, 23 Sep 2000 00:15:32 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sat, 23 Sep 2000 00:15:31 +0200 (CEST) From: Leif Neland To: freebsd-current@freebsd.org Subject: Permissions for /var/mail Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pine 4.21 complains that /var/mail is vulnerable, that the perms should be 1777 Would this be less vulnerable than 775 which make world restores it to? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 15:50:53 2000 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 5DFBF37B423 for ; Fri, 22 Sep 2000 15:50:51 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id SAA19621; Fri, 22 Sep 2000 18:50:31 -0400 (EDT) (envelope-from wollman) Date: Fri, 22 Sep 2000 18:50:31 -0400 (EDT) From: Garrett Wollman Message-Id: <200009222250.SAA19621@khavrinen.lcs.mit.edu> To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Permissions for /var/mail In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Pine 4.21 complains that /var/mail is vulnerable, that the perms should be > 1777 Pine is a steaming, festering pile of Let's try that again. The developers of Pine have certain erroneous ideas about how mail systems work; this is one of them. Ignore Pine's plaints and things should actually work correctly. The correct permissions for the /var/mail directory are determined by the local mail delivery agent (mail.local), not by Pine. (I certainly wouldn't accept security advice from the Pine developers....) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 15:57:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from home.se (smtphost2.home.se [195.66.35.198]) by hub.freebsd.org (Postfix) with ESMTP id 6BC0337B423 for ; Fri, 22 Sep 2000 15:57:41 -0700 (PDT) Received: from alastyr@home.se [212.242.96.171] by home.se with Novell Internet Messaging System Web Client; Sat, 23 Sep 2000 00:57:17 Subject: Errors in src/sys/sys/buf.h From: Joel Lindau To: freebsd-current@freebsd.org Date: Fri, 22 Sep 2000 22:57:17 GMT X-Sender: Novell Internet Messaging System Web Client MIME-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Message-Id: <20000922225741.6BC0337B423@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, While compiling the aha module ( buildkernel ) on current i get the following errors from the include src/sys/sys/buf.h: -- ===> aha cc -O2 -pipe -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/aha/../../dev/aha/aha.c In file included from /usr/src/sys/modules/aha/../../dev/aha/aha.c:64: @/sys/buf.h:89: field `b_io' has incomplete type In file included from /usr/src/sys/modules/aha/../../dev/aha/aha.c:64: @/sys/buf.h: In function `bufq_insert_tail': @/sys/buf.h:375: `BIO_ORDERED' undeclared (first use in this function) @/sys/buf.h:375: (Each undeclared identifier is reported only once @/sys/buf.h:375: for each function it appears in.) -- It has been like this for uhm, like a month or so, since i first cvsup:ed to -current, like one week before the smpng patches were comitted. / Joel.L a.k.a Nevyn -- #FreeBSD.se, #unix.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 16:17:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id F15E437B423 for ; Fri, 22 Sep 2000 16:17:25 -0700 (PDT) Received: from slave (Studded@slave [10.0.0.1]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id QAA62826 for ; Fri, 22 Sep 2000 16:17:25 -0700 (PDT) (envelope-from DougB@gorean.org) Date: Fri, 22 Sep 2000 16:17:25 -0700 (PDT) From: Doug Barton X-Sender: doug@dt051n37.san.rr.com To: freebsd-current@freebsd.org Subject: -Current + X 4.0.1 = mouse problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy gang, I recently upgraded my home and work workstation machines to X Free 4.0.1 so that I could test the possibility of using the i810 video card. Surprisingly enough for me, everything works as expected, with the exception of mouse stuff. Previously I had X + moused working just fine, so I had the best of both worlds. With X 4.0.1 if I use moused I get no response from the mouse in X at all. There is no error message, but there is no mouse movement either. If I abandon moused then I get all mouse stuff behaving normally, until I switch consoles. If I go back to the text console, then back to X the mouse is dead. The only way out of it is Ctl-Alt-Bs. The same is true if I exit my wm and go back to xdm. This isn't a huge issue for me, since the mouse is working fine in X itself, but I thought someone would want to know. Doug -- "The dead cannot be seduced." - Kai, "Lexx" 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 Fri Sep 22 17:35:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B3CE437B423 for ; Fri, 22 Sep 2000 17:35:42 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA12401; Fri, 22 Sep 2000 18:35:40 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA72593; Fri, 22 Sep 2000 18:35:40 -0600 (MDT) Message-Id: <200009230035.SAA72593@harmony.village.org> To: Garrett Wollman Subject: Re: Permissions for /var/mail Cc: Leif Neland , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 22 Sep 2000 18:50:31 EDT." <200009222250.SAA19621@khavrinen.lcs.mit.edu> References: <200009222250.SAA19621@khavrinen.lcs.mit.edu> Date: Fri, 22 Sep 2000 18:35:39 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200009222250.SAA19621@khavrinen.lcs.mit.edu> Garrett Wollman writes: : (I certainly wouldn't accept security advice from the Pine : developers....) Maybe we should fix the pine port to not whine like that. Oh wait, we do... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 17:46: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id 3A48937B422 for ; Fri, 22 Sep 2000 17:46:04 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8N0fFC05702; Sat, 23 Sep 2000 01:41:15 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e8N0erx46544; Sat, 23 Sep 2000 01:40:53 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009230040.e8N0erx46544@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Leif Neland Cc: Brian Somers , freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: ppp.linkdown In-Reply-To: Message from Leif Neland of "Fri, 22 Sep 2000 23:43:49 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 23 Sep 2000 01:40:52 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 12 Aug 2000, Brian Somers wrote: > > > > Is ppp.linkdown executed before or after the link is down? > > > > > > I'd like to change a dyndns, but will link activity done in linkdown defeat > > > the timeout, or start a new call? > > > > It'll start a new call in auto mode. > > > So any ideas how to use dyndns? By implementing the time-remaining option in ppp I guess.... If the peer was also capable of this, you could (say) wait 'till the link had 10 seconds left and then reduce your filter timeouts and nuke your dns entry. A bit grotty though. > Leif -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 18:19:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id 9ED5637B42C for ; Fri, 22 Sep 2000 18:19:07 -0700 (PDT) Received: (qmail 8622 invoked by uid 1000); 23 Sep 2000 01:19:01 -0000 Date: Sat, 23 Sep 2000 03:19:01 +0200 From: "Karsten W. Rohrbach" To: Kris Kennaway Cc: Warner Losh , Jordan Hubbard , "Jordan K. Hubbard" , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, current@FreeBSD.org Subject: Re: HEADS UP: sshd (Re: cvs commit: src/release/sysinstall config.c) Message-ID: <20000923031901.A6957@rohrbach.de> Reply-To: karsten@rohrbach.de References: <200009050259.UAA39943@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@FreeBSD.org on Mon, Sep 04, 2000 at 08:09:59PM -0700 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: karsten@rohrbach.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway(kris@FreeBSD.org)@Mon, Sep 04, 2000 at 08:09:59PM -0700: > On Mon, 4 Sep 2000, Warner Losh wrote: > > > In message <17806.968122706@winston.osd.bsdi.com> Jordan Hubbard writes: > > : Well, it's at least one step closer - all they have to do now (the US > > : people) is install the rsaref port to have the already-running sshd > > : work correctly post-install, correct? > > > > Unless they want to use idea for anything... > > I'm pretty sure OpenSSH doesnt support IDEA > damn right (excerpt from the faq): --- In SSH1 mode, only 3DES and Blowfish can be selected. In SSH2 mode, only 3DES, Blowfish, CAST128 or Arcfour can be selected at the current time. The patented and dated IDEA algorithm is not supported. --- /k -- > "I think pop music has done more for oral intercourse than anything else > that has ever happened, and vice versa." -- Frank Zappa KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 18:41:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id 78AC937B424 for ; Fri, 22 Sep 2000 18:41:24 -0700 (PDT) Received: (qmail 12501 invoked by uid 1000); 23 Sep 2000 01:41:23 -0000 Date: Sat, 23 Sep 2000 03:41:23 +0200 From: "Karsten W. Rohrbach" To: Vivek Khera Cc: freebsd-current@FreeBSD.ORG Subject: Re: call for testers: init securelevel patch Message-ID: <20000923034123.C6957@rohrbach.de> Reply-To: karsten@rohrbach.de References: <20000907152923.A57609@murkwood.znh.org> <14776.61431.463710.288320@onceler.kciLink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14776.61431.463710.288320@onceler.kciLink.com>; from khera@kciLink.com on Fri, Sep 08, 2000 at 09:56:07AM -0400 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: karsten@rohrbach.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Vivek Khera(khera@kciLink.com)@Fri, Sep 08, 2000 at 09:56:07AM -0400: [...] > That last sentence makes me think that the person who decided this > does not use a network to update that machine, ie NFS mounting > /usr/src. It is a royal PITA to get networking up and going after a > single-user reboot to get out of secure level. [...] read my lips: con sole ser ver ;-) on a dedicated internal administration network is this the stuff that saves you time. ah, ... and, yes, we use a network also to update the machines ;> but not with nfs mounting /usr/src. best choice is you write a little setup-automagic script for single user mode and place it under /root decrementing securelevel is evil. doing things in userland which can turn off security features is evil. securelevel is your friend. /k -- > Booze is the answer. I don't remember the question. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 18:51:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id 5B1BE37B422 for ; Fri, 22 Sep 2000 18:51:39 -0700 (PDT) Received: (qmail 12872 invoked by uid 1000); 23 Sep 2000 01:51:37 -0000 Date: Sat, 23 Sep 2000 03:51:37 +0200 From: "Karsten W. Rohrbach" To: Leif Neland Cc: freebsd-current@freebsd.org Subject: Re: Permissions for /var/mail Message-ID: <20000923035137.D6957@rohrbach.de> Reply-To: karsten@rohrbach.de References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from leifn@neland.dk on Sat, Sep 23, 2000 at 12:15:31AM +0200 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: karsten@rohrbach.de Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland(leifn@neland.dk)@Sat, Sep 23, 2000 at 12:15:31AM +0200: > Pine 4.21 complains that /var/mail is vulnerable, that the perms should be > 1777 > > Would this be less vulnerable than 775 which make world restores it to? > > Leif since when does qmail write to /var/mail??? *evilgrin* /k -- > Floppy now, hard later. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 19:50:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from urban.iinet.net.au (urban.iinet.net.au [203.59.24.231]) by hub.freebsd.org (Postfix) with ESMTP id B073B37B423 for ; Fri, 22 Sep 2000 19:50:35 -0700 (PDT) Received: from muzak.iinet.net.au (muzak.iinet.net.au [203.59.24.237]) by urban.iinet.net.au (8.8.7/8.8.7) with ESMTP id KAA23175 for ; Sat, 23 Sep 2000 10:50:30 +0800 Received: from jules.elischer.org (reggae-20-108.nv.iinet.net.au [203.59.85.108]) by muzak.iinet.net.au (8.8.5/8.8.5) with SMTP id KAA23851 for ; Sat, 23 Sep 2000 10:50:27 +0800 Message-ID: <39CC1A63.41C67EA6@elischer.org> Date: Fri, 22 Sep 2000 19:50:11 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: Locking doc.? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do we have a document that descibes in great detail the locking policy that the SMPng code should follow? I've seen several descriptionms as to how it might be done, but I haven't seen a "Ok we've decided that this is the strategy we are using" document. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 20: 2:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 2A08D37B422; Fri, 22 Sep 2000 20:02:16 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e8N322p58015; Sat, 23 Sep 2000 12:32:02 +0930 (CST) (envelope-from grog) Date: Sat, 23 Sep 2000 12:32:02 +0930 From: Greg Lehey To: Julian Elischer Cc: current@FreeBSD.ORG, FreeBSD SMP list Subject: Re: Locking doc.? Message-ID: <20000923123202.C3999@wantadilla.lemis.com> References: <39CC1A63.41C67EA6@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <39CC1A63.41C67EA6@elischer.org>; from julian@elischer.org on Fri, Sep 22, 2000 at 07:50:11PM -0700 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 22 September 2000 at 19:50:11 -0700, Julian Elischer wrote: > Do we have a document that descibes in great detail the > locking policy that the SMPng code should follow? > > I've seen several descriptionms as to how it might be done, > but I haven't seen a "Ok we've decided that this is the strategy > we are using" document. I haven't seen one either. On the one hand it might be a little early to come up with a (restrictive) policy document, but I do think we should be discussing more actively how we go about subdividing the locking. There's been plenty of experience in the past to show that it's madness to just go about subdividing locks. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 20: 5: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id D37E337B422 for ; Fri, 22 Sep 2000 20:04:59 -0700 (PDT) Received: from modemcable136.203-201-24.mtl.mc.videotron.ca ([24.201.203.136]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G1B00K23KK9NH@falla.videotron.net> for current@FreeBSD.ORG; Fri, 22 Sep 2000 23:04:58 -0400 (EDT) Date: Fri, 22 Sep 2000 23:08:37 -0400 (EDT) From: Bosko Milekic Subject: Re: Locking doc.? In-reply-to: <39CC1A63.41C67EA6@elischer.org> To: Julian Elischer Cc: current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't believe so. There are several external resources, such as on-line papers, and so on. There is also a man page (which I've found from jasone's web space) which has been prepared by Sheldon Hearn and which should be at ~jake/mutex.9 As far "standard way to do it" documents - I haven't seen any and I'm not sure how worthwile it would be to do this at this point in time, as the code is still quite dynamic. (Of course, I'm not implying "don't do it," just "be careful when you do it") On Fri, 22 Sep 2000, Julian Elischer wrote: > Do we have a document that descibes in great detail the > locking policy that the SMPng code should follow? > > I've seen several descriptionms as to how it might be done, > but I haven't seen a "Ok we've decided that this is the strategy > we are using" document. > > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > ---> X_.---._/ presently in: Perth > v Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 21: 4:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 9FE4A37B424 for ; Fri, 22 Sep 2000 21:04:40 -0700 (PDT) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA13231; Sat, 23 Sep 2000 00:04:26 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id AAA28221; Sat, 23 Sep 2000 00:04:25 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id AAA28217; Sat, 23 Sep 2000 00:04:25 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Sat, 23 Sep 2000 00:04:25 -0400 (EDT) From: Kenneth Wayne Culver To: Soren Schmidt Cc: Michael Reifenberger , freebsd-current@FreeBSD.ORG Subject: Re: -CURRENT crashes under heavy disk activity In-Reply-To: <200009222108.XAA26726@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see.. just cvs update src/sys/dev/ata or something like that I guess.. :-) I'll probably do that then. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D | Kenneth Culver | FreeBSD: The best NT upgrade | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park.=09 | http://www.wam.umd.edu/~culverk/| =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On Fri, 22 Sep 2000, Soren Schmidt wrote: > It seems Kenneth Wayne Culver wrote: > > Alright, I think I may just do that too... I was going to try to tough = it > > out... but it looks like that just won't work.... I wish there was some > > way to get the other changes without getting the SMP stuff though. > =20 > You update the ata driver to the lastest no probs that I know :) >=20 > -S=F8ren >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 21:56:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.m.iinet.net.au (opera3.iinet.net.au [203.59.24.51]) by hub.freebsd.org (Postfix) with SMTP id A800237B422 for ; Fri, 22 Sep 2000 21:56:09 -0700 (PDT) Received: (qmail 11494 invoked by uid 666); 23 Sep 2000 04:56:05 -0000 Received: from unknown (HELO jules.elischer.org) (203.59.169.104) by mail.m.iinet.net.au with SMTP; 23 Sep 2000 04:56:05 -0000 Message-ID: <39CC37D4.167EB0E7@elischer.org> Date: Fri, 22 Sep 2000 21:55:48 -0700 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 5.0-CURRENT i386) MIME-Version: 1.0 To: Bosko Milekic Cc: current@FreeBSD.ORG Subject: Re: Locking doc.? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bosko Milekic wrote: > > I don't believe so. There are several external resources, such as > on-line papers, and so on. There is also a man page (which I've found > from jasone's web space) which has been prepared by Sheldon Hearn and > which should be at ~jake/mutex.9 > As far "standard way to do it" documents - I haven't seen any and I'm > not sure how worthwile it would be to do this at this point in time, as > the code is still quite dynamic. > (Of course, I'm not implying "don't do it," just "be careful when you > do it" What I'm looking for is something that says for example, what stategy should be used for deadlock avoidance. For example. "Order of locking should be proc then vnode then socket then mbuf", or "Use asleep() await() to back out when encountering a locked item that stays locked for more than xx uSecs." At the moment there is no guide as to how one should combine locks in various different subsystems. Throwing a lock in every structure is one thing but then to tie the whole bundle up together is a completely different ballgame. -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Sep 22 22:28:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id E217037B423 for ; Fri, 22 Sep 2000 22:28:07 -0700 (PDT) Received: from modemcable136.203-201-24.mtl.mc.videotron.ca ([24.201.203.136]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G1B00197R6T21@falla.videotron.net> for current@FreeBSD.ORG; Sat, 23 Sep 2000 01:28:05 -0400 (EDT) Date: Sat, 23 Sep 2000 01:31:45 -0400 (EDT) From: Bosko Milekic Subject: Re: Locking doc.? In-reply-to: <39CC37D4.167EB0E7@elischer.org> To: Julian Elischer Cc: current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Sep 2000, Julian Elischer wrote: > Throwing a lock in every structure is > one > thing but then to tie the whole bundle up together is a completely > different ballgame. Yes, that's the hard part. It can be potentially dangerous to, for example, call the mbuf resource allocation code, while holding a mutex, and with M_WAIT. If the call goes in with M_DONTWAIT, then, theoretically, we shouldn't be blocking, so it's not so much of a big deal. However, for now, if you call with M_WAIT, you better make sure that you're not holding any mutexes going in. According to what I've been able to deduce thus far (and I really haven't looked much yet), BSD/OS seems to do this sort of thing as well (drop a lock on the socket before going in to fetch mbufs with M_WAIT). Their locking in the mbuf system seems less fine-grained than what I have so far (they lock the entire subsystem, effectively, when they're allocating mbufs and mclusters (same lock)). Archie Cobbs recently brought up the idea of writing a mbuf(9) man page which should eventually document, amongst numerous other things, when it's safe to be holding a mutex and when it isn't. As each subsystem will most likely have its own locks, it may be difficult to generalize it all. Bottom line: I do agree that we need such documentation, I just think that's it's difficult to do in a definitive set-in-stone way right now... > -- > __--_|\ Julian Elischer > / \ julian@elischer.org > ( OZ ) World tour 2000 > ---> X_.---._/ presently in: Perth > v Later, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 2: 7:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 09FBD37B422 for ; Sat, 23 Sep 2000 02:07:44 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id QAA06349; Sat, 23 Sep 2000 16:07:06 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Sat, 23 Sep 2000 16:07:06 +0700 (NSS) From: Max Khon To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: Permissions for /var/mail In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Sat, 23 Sep 2000, Leif Neland wrote: > Pine 4.21 complains that /var/mail is vulnerable, that the perms should be > 1777 > > Would this be less vulnerable than 775 which make world restores it to? this happens because ports/mail/pine4/patches/patch-aw was not merged when libc-client was moved to separate port /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 2:45: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (roaming.cacheboy.net [203.56.168.69]) by hub.freebsd.org (Postfix) with ESMTP id 8976937B424; Sat, 23 Sep 2000 02:44:55 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id e8N9iYW04433; Sat, 23 Sep 2000 11:44:34 +0200 (CEST) (envelope-from adrian) Date: Sat, 23 Sep 2000 11:44:34 +0200 From: Adrian Chadd To: Bruce Evans Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: Fsck wrappers, revisited Message-ID: <20000923114434.A4419@roaming.cacheboy.net> References: <20001223112038.A37548@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from bde@zeta.org.au on Sat, Sep 23, 2000 at 03:00:11AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 23, 2000, Bruce Evans wrote: > On Sat, 23 Dec 2000, Adrian Chadd wrote: > > > Here's the patch: > > > > --- fsck.c.orig Sat Dec 23 11:13:30 2000 > > +++ fsck.c Sat Dec 23 11:13:34 2000 > > @@ -501,7 +501,7 @@ > > errx(1, "partition `%s' is not of a legal vfstype", > > str); > > - if ((vfstype = dktypenames[t]) == NULL) > > + if ((vfstype = fstypenames[t]) == NULL) > > errx(1, "vfstype `%s' on partition `%s' is not supported", > > fstypenames[t], str); > > > > > > So now is a problem which I'm sure the NetBSD people came up against. > > The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed > > this by creating a new list 'mountnames[]', which maps the fs type to > > a string. > > fs typenames are already strings in FreeBSD (the kernel's vfc_index is an > implementation detail which should not be visible in applications). Oh, wait. I understand what you're talking about now. There isn't any mapping to partition type (p_fstype) to fs typename string. > > http://cvsweb.netbsd.org/bsdweb.cgi/syssrc/sys/sys/disklabel.h.diff?r1=1.60&r2=1.61 > > > > What do people think about doing this as well? It would certainly make things > > a little tidier, but every time a new fs comes in the magic autodetection code > > will need to be updated (if appropriate, of course.) > > This would be a bug. Well, if you have any suggestions, I'm all for it. :-) Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 3:13:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id E007337B42C for ; Sat, 23 Sep 2000 03:13:16 -0700 (PDT) Received: from daniel.sobral (p10-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.139]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id TAA21609 for ; Sat, 23 Sep 2000 19:13:13 +0900 (JST) Received: (from root@localhost) by daniel.sobral (8.9.3/8.9.3) id TAA80548 for current@freebsd.org; Sat, 23 Sep 2000 19:12:19 +0900 (JST) (envelope-from root) From: "Daniel C. Sobral" Message-Id: <200009231012.TAA80548@daniel.sobral> Subject: smp and gdt To: current@freebsd.org Date: Sat, 23 Sep 2000 19:12:18 +0900 (JST) Disclaimer: Klaatu Barada Nikto! X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Compiling a kernel with gdt: /home/src/sys/i386/i386/machdep.c:1183: `MAXCPU' undeclared here (not in a funct ion) /home/src/sys/i386/i386/machdep.c:1183: size of array `gdt' has non-integer type BK said MAXCPU is defined on machine/smp.h. Well, machdep.c includes smp.h only if SMP is defined. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@root.bsdconspiracy.net PAIN: Sliding down a 50-foot razor blade into a bucket of alcohol. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 4: 8:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id 6AFCA37B422 for ; Sat, 23 Sep 2000 04:08:10 -0700 (PDT) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id NAA54308; Sat, 23 Sep 2000 13:07:36 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.0/8.8.8) with ESMTP id e8NB7KM00965; Sat, 23 Sep 2000 13:07:20 +0200 (CEST) (envelope-from root@nihil.plaut.de) Date: Sat, 23 Sep 2000 13:07:20 +0200 (CEST) From: Michael Reifenberger To: Kenneth Wayne Culver Cc: Michael Reifenberger , freebsd-current@FreeBSD.ORG Subject: Re: -CURRENT crashes under heavy disk activity In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 22 Sep 2000, Kenneth Wayne Culver wrote: ... > Alright, I think I may just do that too... I was going to try to tough it > out... but it looks like that just won't work.... I wish there was some Thats not correct. You have to upper kern.vm.kmem.size as a workaround. Please read the thread for more information. BTW: The increased memoryconsumption (and leak?) looks like a bug to me. Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 4:31:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from acs-24-154-25-35.zoominternet.net (acs-24-154-25-35.zoominternet.net [24.154.25.35]) by hub.freebsd.org (Postfix) with ESMTP id 946B737B42C for ; Sat, 23 Sep 2000 04:31:22 -0700 (PDT) Received: (from dmmiller@localhost) by acs-24-154-25-35.zoominternet.net (8.11.0/8.11.0) id e8NBVGI01531; Sat, 23 Sep 2000 07:31:16 -0400 (EDT) (envelope-from dmmiller) Date: Sat, 23 Sep 2000 07:31:16 -0400 (EDT) Message-Id: <200009231131.e8NBVGI01531@acs-24-154-25-35.zoominternet.net> From: Donn Miller To: current@freebsd.org Subject: Re: fdc0 and ata1 issues In-Reply-To: <200009221448.JAA20935@freebsd.netcom.com> User-Agent: tin/1.5.6-20000803 ("Dust") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200009221448.JAA20935@freebsd.netcom.com> you wrote: > I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range". What's up with the fdc driver? I'm seeing the exact same thing. There was never any heads-up about this. Surely, the person who broke it knows about it. :-( It's nice to have a warning before I go and recompile my kernel. But then again, I wouldn't be running -current if I didn't expect problems. Copyright (c) 1992-2000 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 #0: Thu Sep 21 18:23:45 EDT 2000 dmmiller@acs-24-154-25-35.zoominternet.net:/usr/src/sys/compile/CUSTOM Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (166.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 62914560 (61440K bytes) avail memory = 57683968 (56332K bytes) Preloaded elf kernel "kernel" at 0xc038c000. Intel Pentium detected, installing workaround for F00F bug apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f,0xd400-0xd403,0xd800-0xd807,0xe000-0xe003,0xe400-0xe407 irq 11 at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ed0: port 0xb800-0xb81f irq 12 at device 10.0 on pci0 ed0: address 00:c0:df:ed:0b:17, type NE2000 (16 bit) pci0: at 19.0 irq 11 fdc0: cannot reserve I/O port range atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x2e8-0x2ef irq 10 flags 0x10 on isa0 sio0: type 16550A sio2 at port 0x3e8-0x3ef irq 4 on isa0 sio2: type 16550A mse0: at port 0x23c-0x23f irq 3 on isa0 sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 pcm0: on sbc0 ppc0: at port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: 3093MB [6704/15/63] at ata0-master UDMA33 ad1: 1040MB [2114/16/63] at ata0-slave WDMA2 acd0: CDROM at ata1-master using WDMA2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 4:57:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1293C37B424 for ; Sat, 23 Sep 2000 04:57:24 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA40391; Sat, 23 Sep 2000 14:01:49 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200009231201.OAA40391@freebsd.dk> Subject: Re: fdc0 and ata1 issues In-Reply-To: <200009231131.e8NBVGI01531@acs-24-154-25-35.zoominternet.net> from Donn Miller at "Sep 23, 2000 07:31:16 am" To: dmmiller@zoominternet.net (Donn Miller) Date: Sat, 23 Sep 2000 14:01:49 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Donn Miller wrote: > In article <200009221448.JAA20935@freebsd.netcom.com> you wrote: > > > > I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range". > > What's up with the fdc driver? I'm seeing the exact same thing. There was > never any heads-up about this. Surely, the person who broke it knows about > it. :-( It's nice to have a warning before I go and recompile my kernel. > But then again, I wouldn't be running -current if I didn't expect problems. Its not the fdc driver, its the ata driver. The reason is I usr the altport address no in a different manner, that causes the conflict. I'm working on a solution.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 5: 1:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from eeyore.local.dohd.org (d0030.dtk.chello.nl [213.46.0.30]) by hub.freebsd.org (Postfix) with ESMTP id 2B85037B424 for ; Sat, 23 Sep 2000 05:01:34 -0700 (PDT) Received: from tiggr.local.dohd.org (tiggr.local.dohd.org [::ffff:10.0.0.10]) by eeyore.local.dohd.org (Postfix) with ESMTP id 37FF9BAA4 for ; Sat, 23 Sep 2000 14:01:26 +0200 (MET DST) Received: by tiggr.local.dohd.org (Postfix, from userid 1008) id EE3195DF4; Sat, 23 Sep 2000 14:01:21 +0200 (CEST) Date: Sat, 23 Sep 2000 14:01:21 +0200 From: Mark Huizer To: current@freebsd.org Subject: Getting ssh back to work? Message-ID: <20000923140121.A81958@dohd.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm... I thought I had read the interesting stuff on ssh recently in -current, but I can't get ssh to work again on the machine I switched to yesterday's current :-( tiggr 1:31pm [~/.ssh] ssh eeyore ssh: no RSA support in libssl and libcrypto. See ssl(8). Disabling protocol version 1 DH_generate_key That's with USA_RESIDENT=NO, and with rsaref port installed. doing a ssh-keygen -d will just give me: tiggr 1:32pm [~/.ssh] ssh-keygen -d Generating DSA parameter and key. DSA_generate_keys failed That helps :-( Is there anything I've forgotten to do to make it work? mark -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 5:12:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id BC2D637B42C for ; Sat, 23 Sep 2000 05:12:28 -0700 (PDT) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id OAA13799; Sat, 23 Sep 2000 14:12:56 +0200 (MEST) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 13coAH-0001Gr-00 for ; Sat, 23 Sep 2000 14:12:21 +0200 Date: Sat, 23 Sep 2000 14:12:21 +0200 From: Szilveszter Adam To: current@freebsd.org Subject: Re: Getting ssh back to work? Message-ID: <20000923141221.A4424@petra.hos.u-szeged.hu> Mail-Followup-To: current@freebsd.org References: <20000923140121.A81958@dohd.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0.1i In-Reply-To: <20000923140121.A81958@dohd.cx>; from freebsd@dohd.org on Sat, Sep 23, 2000 at 02:01:21PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! On Sat, Sep 23, 2000 at 02:01:21PM +0200, Mark Huizer wrote: > tiggr 1:31pm [~/.ssh] ssh eeyore > ssh: no RSA support in libssl and libcrypto. See ssl(8). > Disabling protocol version 1 > DH_generate_key > > That's with USA_RESIDENT=NO, and with rsaref port installed. ?? Can you give me a reason for doing this?:-) Rsaref (was) only for USA_RESIDENT=yes. If you are using a recent -CURRENT, crypto stuff is no longer separate, but comes with the base system. So you can basically just install the CRYPTO collection (and sources if you like) in sysinstall, or do a 'make world' with full sources. (a cvsup beforehand will take care of this.) Hope this helps... -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 5:15:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 41E0B37B422; Sat, 23 Sep 2000 05:15:33 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id FAA00343; Sat, 23 Sep 2000 05:15:33 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 23 Sep 2000 05:15:32 -0700 (PDT) From: Kris Kennaway To: Mark Huizer Cc: current@freebsd.org Subject: Re: Getting ssh back to work? In-Reply-To: <20000923140121.A81958@dohd.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 23 Sep 2000, Mark Huizer wrote: > I thought I had read the interesting stuff on ssh recently in -current, > but I can't get ssh to work again on the machine I switched to > yesterday's current :-( device random in your kernel. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 5:32:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 80BF537B422 for ; Sat, 23 Sep 2000 05:32:36 -0700 (PDT) Received: from ganerc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 13coTq-0002Aa-00; Sat, 23 Sep 2000 14:32:34 +0200 Received: (from daemon@localhost) by ganerc.mips.inka.de (8.11.0/8.11.0) id e8NBWpp78147 for freebsd-current@freebsd.org; Sat, 23 Sep 2000 13:32:51 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: -Current + X 4.0.1 = mouse problems Date: 23 Sep 2000 13:32:50 +0200 Message-ID: <8qi4d2$2c9q$1@ganerc.mips.inka.de> References: To: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton wrote: > Previously I had X + moused working just fine, so I had the best > of both worlds. With X 4.0.1 if I use moused I get no response from the > mouse in X at all. Make sure you use Option "Protocol" "MouseSystems" Protocol "Auto" is not reliable. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 6:15:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by hub.freebsd.org (Postfix) with SMTP id 5D99037B43F for ; Sat, 23 Sep 2000 06:15:48 -0700 (PDT) Received: (qmail 20048 invoked by uid 0); 23 Sep 2000 13:15:47 -0000 Received: from p3ee20a92.dip.t-dialin.net (HELO speedy.gsinet) (62.226.10.146) by mail.gmx.net with SMTP; 23 Sep 2000 13:15:47 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id JAA13837 for freebsd-current@FreeBSD.ORG; Sat, 23 Sep 2000 09:41:57 +0200 Date: Sat, 23 Sep 2000 09:41:57 +0200 From: Gerhard Sittig To: freebsd-current@FreeBSD.ORG Subject: Re: ppp.linkdown Message-ID: <20000923094156.E5065@speedy.gsinet> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <200008122034.VAA02385@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from leifn@neland.dk on Fri, Sep 22, 2000 at 11:43:49PM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 22, 2000 at 23:43 +0200, Leif Neland wrote: > > On Sat, 12 Aug 2000, Brian Somers wrote: > > > > Is ppp.linkdown executed before or after the link is down? > > > > > > I'd like to change a dyndns, but will link activity done in > > > linkdown defeat the timeout, or start a new call? > > > > It'll start a new call in auto mode. > > > So any ideas how to use dyndns? Simply the way it was designed -- with short TTLs (in a few minutes' order). Have your entry expire instead of "logging off". Your dyndns provider should support such a feature. This means to refresh the entry periodically when you're online -- with a refresh cycle longer than your idle timeout. Doing network actions and damaging your idle timeout by "waving good bye" is just as bad as turning timeouts off close to idlehup time and unconditionally hanging up -- this will collide with "regular" traffic which might have occured by chance (or due to the service's nature? Think of how long it takes to read a webpage and follow the next link). Even hacking a "pre hup hook" into ppp will have the latter problem. The only way out I could see it to have a clear way of recognizing what's data and what's logon/logoff traffic. Then you could teach your ppp not to take into account the dyndns traffic when calculating idlehup times. This could be done by looking at the ports or ipnumbers or whatever ppp(8)'s filter allows for. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 11:50:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 02D2F37B422 for ; Sat, 23 Sep 2000 11:50:48 -0700 (PDT) Received: (qmail 70077 invoked by uid 1040); 23 Sep 2000 18:50:43 -0000 Date: Sat, 23 Sep 2000 20:50:43 +0200 From: =?iso-8859-1?Q?David_Sieb=F6rger?= To: freebsd-current@freebsd.org Subject: Re: -Current + X 4.0.1 = mouse problems Message-ID: <20000923205043.A63108@rucus.ru.ac.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8qi4d2$2c9q$1@ganerc.mips.inka.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG naddy@mips.inka.de (Christian Weisgerber) wrote: > > Doug Barton wrote: > >> Previously I had X + moused working just fine, so I had the best >> of both worlds. With X 4.0.1 if I use moused I get no response from the >> mouse in X at all. > > Make sure you use > > Option "Protocol" "MouseSystems" > > Protocol "Auto" is not reliable. Switching from "Auto" to "MouseSystems" is no panacea, however. I've experienced the (apparently common) problem of switching from X to console and back to X and getting an unresponsive mouse pointer in X. This occurs when I use protocol "Auto", or don't specify a protocol. Switching to "MouseSystems" protocol fixes the above problem, but it introduces a problem: the wheels on my mice no longer work in X. While there may be a way to get the wheel working under MouseSystems protocol, I've not found it. I experience this problem with both my FreeBSD workstations: one running 5.0-CURRENT (circa end-of-August) with a Microsoft IntelliMouse 1.1A for PS/2, and a second running 4.1-STABLE (of 19th September) with a Mitsumi PS/2 Scroll Mouse. Both run XFree86 4.0.1. -drs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 15: 2:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id 60F2A37B422 for ; Sat, 23 Sep 2000 15:02:08 -0700 (PDT) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@FreeBSD.org; Sun, 24 Sep 2000 00:02:05 +0200 (MET DST) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.11.0/8.9.3) id e8NM4cn00977 for freebsd-current@FreeBSD.org; Sun, 24 Sep 2000 00:04:38 +0200 (CEST) (envelope-from tanis) Date: Sun, 24 Sep 2000 00:04:38 +0200 From: German Tischler To: freebsd-current@FreeBSD.org Subject: ahc and SMP Message-ID: <20000924000438.A460@gaspode.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. On my machine the ahc (aic) driver times out while probing for devices on SMP, while it is working on UP. dmesg says ahc0: port 0xd000-0xd0ff mem 0xe1000000 -0xe1000fff irq 15 at device 6.0 on pci0 aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs while booting the SMP kernel it says (probe0:ahc0:0:0:0) Timedout SCB 9 handled by another timeout (probe1:ahc0:0:1:0) SCB 0x8 - timed out while idle, SEQADDR == 0x167 sg[0] - Addr 0x7f2f684 : Length -2147483612 (probe1:ahc0:0:1:0) Queuing a BDR SCB (probe1:ahc0:0:1:0) no longer in timeout, status = 34a and after some more time will print more timeout messages and will not (at least not for a few minutes) finish probing or announce any SCSI devices. devices connected are da0 at ahc0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15) da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) da1 at ahc0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15) da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at ahc0 bus 0 target 8 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 40.000MB/s transfers (20.000MHz, offset 63, 16bit) da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) Is anyone else seeing this ? Another strange thing is that cdrecord -scanbus tells me scsibus0: 0,0,0 0) * 0,1,0 1) * 0,2,0 2) 'IBM ' 'DORS-32160 ' 'S82C' Disk 0,3,0 3) 'IBM ' 'DCAS-34330 ' 'S65A' Disk 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * 0,8,0 8) 'IBM ' 'DDYS-T18350N ' 'S80D' Disk scsibus1: 1,0,0 100) 'YAMAHA ' 'CRW4260 ' '1.0h' Removable CD-ROM 1,1,0 101) * 1,2,0 102) * 1,3,0 103) * 1,4,0 104) * 1,5,0 105) * 1,6,0 106) * 1,7,0 107) * While camcontrol devlist says at scbus0 target 2 lun 0 (pass0,da0) at scbus0 target 3 lun 0 (pass1,da1) at scbus0 target 8 lun 0 (pass2,da2) at scbus1 target 0 lun 0 (pass3,cd0) at scbus1 target 1 lun 0 (pass4,cd1) Maybe just a bug in cdrecord. --gt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 15:49:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 6337537B424 for ; Sat, 23 Sep 2000 15:49:24 -0700 (PDT) Received: from gorean.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id PAA74267; Sat, 23 Sep 2000 15:45:37 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <39CD3291.2A00C204@gorean.org> Date: Sat, 23 Sep 2000 15:45:37 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 5.0-CURRENT-092 i386) X-Accept-Language: en MIME-Version: 1.0 To: David =?iso-8859-1?Q?Sieb=F6rger?= Cc: freebsd-current@freebsd.org Subject: Re: -Current + X 4.0.1 = mouse problems References: <20000923205043.A63108@rucus.ru.ac.za> Content-Type: multipart/mixed; boundary="------------D447E81FA2BBBF8244AD8D9C" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------D447E81FA2BBBF8244AD8D9C Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit David Siebörger wrote: > I've experienced the (apparently common) problem of switching from X > to console and back to X and getting an unresponsive mouse pointer in > X. This occurs when I use protocol "Auto", or don't specify a > protocol. Someone was kind enough to send me the attached patch. With Option "Protocol" "Auto" Option "Device" "/dev/sysmouse" it works with moused. I tried protocol sysmouse, but it didn't work. Neither did Christian's advice about the mousesystems protocol. I also have a wheeled mouse, logitech specifically. It would be nice to include this patch in our X4 port. Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? --------------D447E81FA2BBBF8244AD8D9C Content-Type: text/plain; charset=us-ascii; name="XFree86-4-mouse-fix.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="XFree86-4-mouse-fix.patch" --- programs/Xserver/hw/xfree86/input/mouse/mouse.c.orig Sun Jul 23 17:50:10 2000 +++ programs/Xserver/hw/xfree86/input/mouse/mouse.c Sun Jul 23 17:54:22 2000 @@ -692,10 +692,15 @@ pMse->protocolID = protocolID; } } +#ifndef __FreeBSD__ memcpy(pMse->protoPara, proto[pMse->protocolID], sizeof(pMse->protoPara)); +#endif if (automatic) { if (name) { +#ifdef __FreeBSD__ + memcpy(pMse->protoPara, proto[pMse->protocolID], sizeof(pMse->protoPara)); +#endif /* Possible protoPara overrides from SetupAuto. */ for (i = 0; i < sizeof(pMse->protoPara); i++) if (protoPara[i] != -1) --- programs/Xserver/hw/xfree86/os-support/bsd/bsd_mouse.c.orig Sat Feb 12 22:45:41 2000 +++ programs/Xserver/hw/xfree86/os-support/bsd/bsd_mouse.c Sun Jul 23 17:50:10 2000 @@ -165,7 +165,11 @@ mode.rate = rate > 0 ? rate : -1; mode.resolution = res > 0 ? res : -1; mode.accelfactor = -1; +#ifdef __FreeBSD__ + mode.level = 1; +#else mode.level = -1; +#endif ioctl(pInfo->fd, MOUSE_SETMODE, &mode); } #endif --------------D447E81FA2BBBF8244AD8D9C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 16: 2:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 2FE0B37B422; Sat, 23 Sep 2000 16:02:54 -0700 (PDT) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 9D853BE4; Sat, 23 Sep 2000 16:02:53 -0700 (PDT) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id QAA06726; Sat, 23 Sep 2000 16:02:48 -0700 (PDT) Message-ID: <39CD3698.D2EF0663@cup.hp.com> Date: Sat, 23 Sep 2000 16:02:48 -0700 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Andrey A. Chernov" Cc: Warner Losh , current@freebsd.org, marcel@freebsd.org Subject: Re: mtree again References: <20000915033837.A564@nagual.pp.ru> <200009142341.RAA00700@harmony.village.org> <20000915043925.A83698@nagual.pp.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andrey A. Chernov" wrote: > > --- usr.sbin/mtree/mtree.c.orig Thu Jul 27 07:36:02 2000 > +++ usr.sbin/mtree/mtree.c Fri Sep 15 04:00:46 2000 [snip] > @@ -115,10 +119,6 @@ > case 'q': > qflag = 1; > break; > - case 'P': > - ftsoptions ^= FTS_LOGICAL; > - ftsoptions |= FTS_PHYSICAL; > - break; > case 'r': > rflag = 1; > break; Is their any harm in just keeping the -P flag as a no-op and optionally remove it at some later time (for backward compatibility)? -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 17:26:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id AE94F37B422; Sat, 23 Sep 2000 17:26:16 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA17907; Sat, 23 Sep 2000 18:26:10 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA08490; Sat, 23 Sep 2000 18:26:10 -0600 (MDT) Message-Id: <200009240026.SAA08490@harmony.village.org> To: Marcel Moolenaar Subject: Re: mtree again Cc: "Andrey A. Chernov" , current@freebsd.org, marcel@freebsd.org In-reply-to: Your message of "Sat, 23 Sep 2000 16:02:48 PDT." <39CD3698.D2EF0663@cup.hp.com> References: <39CD3698.D2EF0663@cup.hp.com> <20000915033837.A564@nagual.pp.ru> <200009142341.RAA00700@harmony.village.org> <20000915043925.A83698@nagual.pp.ru> Date: Sat, 23 Sep 2000 18:26:09 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39CD3698.D2EF0663@cup.hp.com> Marcel Moolenaar writes: : Is their any harm in just keeping the -P flag as a no-op and optionally : remove it at some later time (for backward compatibility)? -P is non-standard, was introduced only in July and therefore we don't need to keep it around for any reason at all. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 17:32:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from unix.jdthomas.net (c755117-a.eugene1.or.home.com [24.16.233.151]) by hub.freebsd.org (Postfix) with ESMTP id C6F5D37B422 for ; Sat, 23 Sep 2000 17:32:25 -0700 (PDT) Received: from jdthomas.net (c755117-a.eugene1.or.home.com [24.16.233.151]) by unix.jdthomas.net (8.9.3/8.9.3) with ESMTP id RAA45098 for ; Sat, 23 Sep 2000 17:47:52 -0700 (PDT) (envelope-from justin@jdthomas.net) Message-ID: <39CD4F38.4E25298C@jdthomas.net> Date: Sat, 23 Sep 2000 17:47:52 -0700 From: Justin Thomas X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Subject: Compilation Errors Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to compile (make buildworld) the latest CURRENT version of FreeBSD (5). I keep getting an error when it trys to build "libdisk" about something being redefined or something. This is quite a ways into the build process. Is anyone familiar with this error? Thanks, Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 17:40:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from unix.jdthomas.net (c755117-a.eugene1.or.home.com [24.16.233.151]) by hub.freebsd.org (Postfix) with ESMTP id D07C237B424 for ; Sat, 23 Sep 2000 17:40:18 -0700 (PDT) Received: from jdthomas.net (c755117-a.eugene1.or.home.com [24.16.233.151]) by unix.jdthomas.net (8.9.3/8.9.3) with ESMTP id RAA45124 for ; Sat, 23 Sep 2000 17:55:45 -0700 (PDT) (envelope-from justin@jdthomas.net) Message-ID: <39CD5111.FABE437D@jdthomas.net> Date: Sat, 23 Sep 2000 17:55:45 -0700 From: Justin Thomas X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 4.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Subject: Compilation Errors (libdisk) Content-Type: multipart/mixed; boundary="------------310E77BB14237FB7E739D5AD" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------310E77BB14237FB7E739D5AD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Attached is the end of the .out file where my error occurs. Thanks for any help. ~Justin --------------310E77BB14237FB7E739D5AD Content-Type: text/plain; charset=us-ascii; name="wm.out" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="wm.out" ===> libdevstat cc -O -pipe -I/usr/src/lib/libdevstat -I/usr/src/lib/libdevstat/../../sys -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libdevstat/devstat.c -o devstat.o building standard devstat library ranlib libdevstat.a cc -fpic -DPIC -O -pipe -I/usr/src/lib/libdevstat -I/usr/src/lib/libdevstat/../../sys -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libdevstat/devstat.c -o devstat.So building shared library libdevstat.so.2 ===> libdisk cc -O -pipe -Wall -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libdisk/blocks.c -o blocks.o cc -O -pipe -Wall -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libdisk/disklabel.c -o disklabel.o cc -O -pipe -Wall -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libdisk/../../sbin/disklabel/dkcksum.c -o dkcksum.o /usr/src/lib/libdisk/../../sbin/disklabel/dkcksum.c:47: redefinition of `dkcksum' /usr/obj/usr/src/i386/usr/include/sys/disklabel.h:183: `dkcksum' previously defined here *** Error code 1 Stop in /usr/src/lib/libdisk. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. unix# --------------310E77BB14237FB7E739D5AD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 17:57: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 7155437B424 for ; Sat, 23 Sep 2000 17:56:55 -0700 (PDT) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8O0uYi99929; Sat, 23 Sep 2000 17:56:34 -0700 (PDT) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.0/8.11.0) id e8O0t4U19496; Sat, 23 Sep 2000 17:55:04 -0700 (PDT) (envelope-from jhb) 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: <39CD4F38.4E25298C@jdthomas.net> Date: Sat, 23 Sep 2000 17:55:04 -0700 (PDT) Organization: BSD, Inc. From: John Baldwin To: Justin Thomas Subject: RE: Compilation Errors Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Sep-00 Justin Thomas wrote: > I am trying to compile (make buildworld) the latest CURRENT version of > FreeBSD (5). I keep getting an error when it trys to build "libdisk" > about something being redefined or something. This is quite a ways into > the build process. Is anyone familiar with this error? Your sources are a bit old. update and try again. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 18:46:55 2000 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 B3D1E37B424 for ; Sat, 23 Sep 2000 18:46:53 -0700 (PDT) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA34295; Sat, 23 Sep 2000 21:44:21 -0400 (EDT) (envelope-from wollman) Date: Sat, 23 Sep 2000 21:44:21 -0400 (EDT) From: Garrett Wollman Message-Id: <200009240144.VAA34295@khavrinen.lcs.mit.edu> To: Marcel Moolenaar Cc: current@FreeBSD.ORG Subject: Re: mtree again In-Reply-To: <39CD3698.D2EF0663@cup.hp.com> References: <20000915033837.A564@nagual.pp.ru> <200009142341.RAA00700@harmony.village.org> <20000915043925.A83698@nagual.pp.ru> <39CD3698.D2EF0663@cup.hp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Is their any harm in just keeping the -P flag as a no-op and optionally > remove it at some later time (for backward compatibility)? We should try to be consistent with POSIX.1-200x as much as possible. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 20:36:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 209B837B42C for ; Sat, 23 Sep 2000 20:36:25 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id VAA44704; Sat, 23 Sep 2000 21:36:12 -0600 (MDT) (envelope-from ken) Date: Sat, 23 Sep 2000 21:36:12 -0600 From: "Kenneth D. Merry" To: German Tischler Cc: freebsd-current@FreeBSD.ORG Subject: Re: ahc and SMP Message-ID: <20000923213612.A44671@panzer.kdm.org> References: <20000924000438.A460@gaspode.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000924000438.A460@gaspode.franken.de>; from tanis@gaspode.franken.de on Sun, Sep 24, 2000 at 12:04:38AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Sep 24, 2000 at 00:04:38 +0200, German Tischler wrote: [ problems with SMP, but not UP kernels, I don't know anything about that ] > Is anyone else seeing this ? > > Another strange thing is that cdrecord -scanbus tells me > > scsibus0: > 0,0,0 0) * > 0,1,0 1) * > 0,2,0 2) 'IBM ' 'DORS-32160 ' 'S82C' Disk > 0,3,0 3) 'IBM ' 'DCAS-34330 ' 'S65A' Disk > 0,4,0 4) * > 0,5,0 5) * > 0,6,0 6) * > 0,7,0 7) * > 0,8,0 8) 'IBM ' 'DDYS-T18350N ' 'S80D' Disk > scsibus1: > 1,0,0 100) 'YAMAHA ' 'CRW4260 ' '1.0h' Removable CD-ROM > 1,1,0 101) * > 1,2,0 102) * > 1,3,0 103) * > 1,4,0 104) * > 1,5,0 105) * > 1,6,0 106) * > 1,7,0 107) * > > While camcontrol devlist says > > at scbus0 target 2 lun 0 (pass0,da0) > at scbus0 target 3 lun 0 (pass1,da1) > at scbus0 target 8 lun 0 (pass2,da2) > at scbus1 target 0 lun 0 (pass3,cd0) > at scbus1 target 1 lun 0 (pass4,cd1) > > Maybe just a bug in cdrecord. IIRC, cdrecord opens up each device to do an inquiry on it. So if you don't have enough pass(4) devices in /dev, you may not see some of the devices that are there. So make sure you have /dev/pass{0-4}. Another way to make sure you have a pass device for cd1 is to do: camcontrol tur cd1 -v Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 21:39:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 1C4D937B424 for ; Sat, 23 Sep 2000 21:39:15 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.0/8.11.0) id e8O4YfU50039; Sun, 24 Sep 2000 08:34:41 +0400 (MSD) (envelope-from ache) Date: Sun, 24 Sep 2000 08:34:40 +0400 From: "Andrey A. Chernov" To: Garrett Wollman Cc: Marcel Moolenaar , current@FreeBSD.ORG Subject: Re: mtree again Message-ID: <20000924083440.A49999@nagual.pp.ru> References: <20000915033837.A564@nagual.pp.ru> <200009142341.RAA00700@harmony.village.org> <20000915043925.A83698@nagual.pp.ru> <39CD3698.D2EF0663@cup.hp.com> <200009240144.VAA34295@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009240144.VAA34295@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Sat, Sep 23, 2000 at 09:44:21PM -0400 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Sep 23, 2000 at 09:44:21PM -0400, Garrett Wollman wrote: > < said: > > > Is their any harm in just keeping the -P flag as a no-op and optionally > > remove it at some later time (for backward compatibility)? > > We should try to be consistent with POSIX.1-200x as much as possible. What POSIX.1-200x says about this thing? I don't have this book in hand. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Sep 23 23:22: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 2E4F237B422 for ; Sat, 23 Sep 2000 23:22:05 -0700 (PDT) Received: from work.mzaki.nom (244.pool5.ipctokyo.att.ne.jp [165.76.43.244]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(09/21/00)) id PAA22057; Sun, 24 Sep 2000 15:21:59 +0900 (JST) Date: Sun, 24 Sep 2000 15:21:58 +0900 Message-ID: <8666nml37d.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: "Matthew N. Dodd" Cc: current@FreeBSD.org Subject: NS DP83932 SONIC driver for pc98 X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I updated 'snc' driver for -current. This driver is only for NEC pc98 machines. http://triaez.kaisei.org/~mzaki/sonic/ This is very stable for usual operation. I hope this will be merged into the tree. -- Motomichi Matsuzaki Dept. of Biological Sciences, Grad. School of Science, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message