From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 00:25:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3CB716A4CE for ; Sun, 28 Nov 2004 00:25:26 +0000 (GMT) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id F035D43D3F for ; Sun, 28 Nov 2004 00:25:25 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru (8.13.0/vak/3.0) id iAS0T2EC020877 for freebsd-current@freebsd.org.checked; Sun, 28 Nov 2004 03:29:02 +0300 (MSK) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by hanoi.cronyx.ru (8.13.0/vak/3.0) with ESMTP id iAS0Smex020861; Sun, 28 Nov 2004 03:28:48 +0300 (MSK) (envelope-from rik@cronyx.ru) Message-ID: <41A91816.30807@cronyx.ru> Date: Sun, 28 Nov 2004 03:13:10 +0300 From: Roman Kurakin User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru-RU; rv:1.2.1) Gecko/20030426 X-Accept-Language: ru-ru, en MIME-Version: 1.0 To: freebsd-net@freebsd.org, freebsd-hackers@FreeBSD.org, FreeBSD Current Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: MPSAFE sppp(+fr support) cp cx ctau X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 00:25:26 -0000 Hi, I am glad to announce stable version of patches for sppp, cp, ctau and cx drivers with support of mpsafe. SPPP: Sppp will work in mpsafe mode only for adapters that do not have IFF_NEEDSGIANT flag. Also this patch contains if_spppfr.c with fr support for sppp (4). CP/CX/CTAU: Adapters will work in mpsafe mode only if both debug.mpsafenet and debug.{cp|cx|ctau}.mpsafenet set to 1. Patches (relative current) can be downloaded from: http://people.freebsd.org/~rik/rik_netperf_20041128-1.pch Please test them and let me know if you have any problems. Patches were tested on Tau-PCI - Cisco 2500 at speed 4M on Dual CPU system with ping-f and uptime ~one week. rik From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 00:30:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D20916A510 for ; Sun, 28 Nov 2004 00:30:47 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BA1343D66 for ; Sun, 28 Nov 2004 00:30:39 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (sccrmhc13) with ESMTP id <20041128003038016001jqhce>; Sun, 28 Nov 2004 00:30:38 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) iAS0Ubts000895; Sat, 27 Nov 2004 19:30:37 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)iAS0Uap2000894; Sat, 27 Nov 2004 19:30:36 -0500 (EST) (envelope-from rodrigc) Date: Sat, 27 Nov 2004 19:30:36 -0500 From: Craig Rodrigues To: Vladimir Grebenschikov Message-ID: <20041128003036.GA883@crodrigues.org> References: <1101492325.996.54.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1101492325.996.54.camel@localhost> User-Agent: Mutt/1.4.1i cc: "current@freebsd.org" Subject: Re: ptrace broken on latest CURRENT ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 00:30:48 -0000 On Fri, Nov 26, 2004 at 09:05:25PM +0300, Vladimir Grebenschikov wrote: > Hi > > % truss ls > truss: PIOCBIS: Inappropriate ioctl for device I'm seeing this too. This patch seems to work for me, but I don't know if it is correct or not. --- sys_generic.c.orig Sat Nov 27 19:14:39 2004 +++ sys_generic.c Sat Nov 27 19:17:09 2004 @@ -503,7 +503,7 @@ if ((size > IOCPARM_MAX) || ((com & (IOC_VOID | IOC_IN | IOC_OUT)) == 0) || ((com & IOC_VOID) && size > 0) || - ((com & (IOC_IN | IOC_OUT)) && size == 0)) { + ((com & IOC_OUT) && size == 0)) { fdrop(fp, td); return (ENOTTY); } -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 02:04:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CF6616A4CE for ; Sun, 28 Nov 2004 02:04:21 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 419C543D46 for ; Sun, 28 Nov 2004 02:04:21 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (rwcrmhc11) with ESMTP id <2004112802042001300l316re>; Sun, 28 Nov 2004 02:04:20 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) iAS24Hqg001465; Sat, 27 Nov 2004 21:04:17 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)iAS24BOd001464; Sat, 27 Nov 2004 21:04:11 -0500 (EST) (envelope-from rodrigc) Date: Sat, 27 Nov 2004 21:04:11 -0500 From: Craig Rodrigues To: Vladimir Grebenschikov Message-ID: <20041128020411.GA1436@crodrigues.org> References: <1101492325.996.54.camel@localhost> <20041128003036.GA883@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041128003036.GA883@crodrigues.org> User-Agent: Mutt/1.4.1i cc: "current@freebsd.org" Subject: Re: ptrace broken on latest CURRENT ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 02:04:21 -0000 On Sat, Nov 27, 2004 at 07:30:36PM -0500, Craig Rodrigues wrote: > --- sys_generic.c.orig Sat Nov 27 19:14:39 2004 > +++ sys_generic.c Sat Nov 27 19:17:09 2004 > @@ -503,7 +503,7 @@ > if ((size > IOCPARM_MAX) || > ((com & (IOC_VOID | IOC_IN | IOC_OUT)) == 0) || > ((com & IOC_VOID) && size > 0) || > - ((com & (IOC_IN | IOC_OUT)) && size == 0)) { > + ((com & IOC_OUT) && size == 0)) { > fdrop(fp, td); > return (ENOTTY); > } Hi, If we leave the define of PIOCBIS as: # define PIOCBIS _IOC(IOC_IN, 'p', 1, 0) then the length of this ioctl is going to be 0 (from IOCPARM_LEN). I'm not sure if that is a good thing. This is what tripped up the original ioctl() code in sys_generic.c. If we don't change sys_generic.c, then the other approach to this problem is to fix the ioctl() calls in the procfs. Any comments on this? Index: sys/fs/procfs/procfs_ioctl.c =================================================================== RCS file: /home/ncvs/src/sys/fs/procfs/procfs_ioctl.c,v retrieving revision 1.10 diff -u -r1.10 procfs_ioctl.c --- sys/fs/procfs/procfs_ioctl.c 7 Dec 2003 17:40:00 -0000 1.10 +++ sys/fs/procfs/procfs_ioctl.c 28 Nov 2004 01:58:38 -0000 @@ -46,8 +46,8 @@ procfs_ioctl(PFS_IOCTL_ARGS) { struct procfs_status *ps; - int error, flags, sig; - + int error; + unsigned int flags, sig; PROC_LOCK(p); error = 0; switch (cmd) { Index: sys/sys/pioctl.h =================================================================== RCS file: /home/ncvs/src/sys/sys/pioctl.h,v retrieving revision 1.12 diff -u -r1.12 pioctl.h --- sys/sys/pioctl.h 4 Aug 2002 01:06:58 -0000 1.12 +++ sys/sys/pioctl.h 28 Nov 2004 01:58:40 -0000 @@ -49,12 +49,12 @@ unsigned long val; /* Any extra data */ }; -# define PIOCBIS _IOC(IOC_IN, 'p', 1, 0) /* Set event flag */ -# define PIOCBIC _IOC(IOC_IN, 'p', 2, 0) /* Clear event flag */ -# define PIOCSFL _IOC(IOC_IN, 'p', 3, 0) /* Set flags */ +# define PIOCBIS _IOW('p', 1, unsigned int) /* Set event flag */ +# define PIOCBIC _IOW('p', 2, unsigned int) /* Clear event flag */ +# define PIOCSFL _IOW('p', 3, unsigned int) /* Set flags */ /* wait for proc to stop */ # define PIOCWAIT _IOR('p', 4, struct procfs_status) -# define PIOCCONT _IOC(IOC_IN, 'p', 5, 0) /* Continue a process */ +# define PIOCCONT _IOW('p', 5, unsigned int) /* Continue a process */ /* Get proc status */ # define PIOCSTATUS _IOR('p', 6, struct procfs_status) # define PIOCGFL _IOR('p', 7, unsigned int) /* Get flags */ Index: usr.bin/truss/extern.h =================================================================== RCS file: /home/ncvs/src/usr.bin/truss/extern.h,v retrieving revision 1.9 diff -u -r1.9 extern.h --- usr.bin/truss/extern.h 17 Jul 2004 19:19:36 -0000 1.9 +++ usr.bin/truss/extern.h 28 Nov 2004 01:58:40 -0000 @@ -32,7 +32,7 @@ */ extern int setup_and_wait(char **); -extern int start_tracing(int, int, int); +extern int start_tracing(int, unsigned int, int); extern void restore_proc(int); extern const char *ioctlname(register_t val); extern char *strsig(int sig); Index: usr.bin/truss/main.c =================================================================== RCS file: /home/ncvs/src/usr.bin/truss/main.c,v retrieving revision 1.38 diff -u -r1.38 main.c --- usr.bin/truss/main.c 17 Jul 2004 19:19:36 -0000 1.38 +++ usr.bin/truss/main.c 28 Nov 2004 01:58:42 -0000 @@ -322,7 +322,7 @@ break; } } - if (ioctl(Procfd, PIOCCONT, val) == -1) { + if (ioctl(Procfd, PIOCCONT, &val) == -1) { if (kill(trussinfo->pid, 0) == -1 && errno == ESRCH) break; else Index: usr.bin/truss/setup.c =================================================================== RCS file: /home/ncvs/src/usr.bin/truss/setup.c,v retrieving revision 1.19 diff -u -r1.19 setup.c --- usr.bin/truss/setup.c 7 Jan 2004 14:29:45 -0000 1.19 +++ usr.bin/truss/setup.c 28 Nov 2004 01:58:42 -0000 @@ -54,7 +54,7 @@ #include "truss.h" #include "extern.h" -static int evflags = 0; +static unsigned int evflags = 0; /* * setup_and_wait() is called to start a process. All it really does @@ -69,19 +69,19 @@ char buf[32]; int fd; int pid; - int flags; + unsigned int flags; pid = fork(); if (pid == -1) { err(1, "fork failed"); } if (pid == 0) { /* Child */ - int mask = S_EXEC | S_EXIT; + unsigned int mask = S_EXEC | S_EXIT; fd = open("/proc/curproc/mem", O_WRONLY); if (fd == -1) err(2, "cannot open /proc/curproc/mem"); fcntl(fd, F_SETFD, 1); - if (ioctl(fd, PIOCBIS, mask) == -1) + if (ioctl(fd, PIOCBIS, &mask) == -1) err(3, "PIOCBIS"); flags = PF_LINGER; /* @@ -89,11 +89,11 @@ * process on last close; normally, this is the behaviour * we want. */ - if (ioctl(fd, PIOCSFL, flags) == -1) + if (ioctl(fd, PIOCSFL, &flags) == -1) warn("cannot set PF_LINGER"); execvp(command[0], command); mask = ~0; - ioctl(fd, PIOCBIC, ~0); + ioctl(fd, PIOCBIC, &mask); err(4, "execvp %s", command[0]); } /* Only in the parent here */ @@ -128,7 +128,7 @@ */ int -start_tracing(int pid, int eventflags, int flags) { +start_tracing(int pid, unsigned int eventflags, int flags) { int fd; char buf[32]; struct procfs_status tmp; @@ -151,7 +151,7 @@ } evflags = tmp.events; - if (ioctl(fd, PIOCBIS, eventflags) == -1) + if (ioctl(fd, PIOCBIS, &eventflags) == -1) err(9, "cannot set procfs event bit mask"); /* @@ -160,7 +160,7 @@ * needs to be woken up via procctl. */ - if (ioctl(fd, PIOCSFL, flags) == -1) + if (ioctl(fd, PIOCSFL, &flags) == -1) warn("cannot clear PF_LINGER"); return fd; @@ -174,9 +174,9 @@ */ void restore_proc(int signo __unused) { - - ioctl(Procfd, PIOCBIC, ~0); + unsigned int flags = ~0; + ioctl(Procfd, PIOCBIC, &flags); if (evflags) - ioctl(Procfd, PIOCBIS, evflags); + ioctl(Procfd, PIOCBIS, &evflags); exit(0); } -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 03:21:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE0A016A4CE for ; Sun, 28 Nov 2004 03:21:24 +0000 (GMT) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 997B643D5D for ; Sun, 28 Nov 2004 03:21:24 +0000 (GMT) (envelope-from pbowen25@juno.com) Received: from frontend3.messagingengine.com (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id C283BC3C899 for ; Sat, 27 Nov 2004 22:21:22 -0500 (EST) X-Sasl-enc: Cw+UBJ7jz+ONBCHBcIt1NA 1101612081 Received: from juno.com (unknown [204.110.228.254]) by frontend3.messagingengine.com (Postfix) with ESMTP id 14B322553F for ; Sat, 27 Nov 2004 22:21:20 -0500 (EST) Message-ID: <41A943F9.40106@juno.com> Date: Sat, 27 Nov 2004 21:20:25 -0600 From: Patrick Bowen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD Current References: <41A8C9C3.1020504@juno.com> <20041127192257.GA10638@il.fontys.nl> In-Reply-To: <20041127192257.GA10638@il.fontys.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Getting devfs to recognize a hotplugged fd0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 03:21:25 -0000 Ed Schouten wrote: >Hello Patrick, > >Patrick Bowen wrote: > > >>I'm trying to learn how to get devfs to create an fd0 enty in /dev >>automatically when I plug a floppy drive into the serial port of a >>running Dell D600 laptop running 6.0 current. >> >> > >Are you sure that's possible at all? You know the serial port isn't >plug-and-play? How can the operating system tell that there is something on >the serial port at all? :) > > > Ed; No, I'm not sure. But, in 4.10, with /dev already populated with an entry for fd0, I could plug the floppy into a running machine and then mount it, no problem. So I'm thinking that if can either create an entry for /dev/fd0 during or shortly after boot time, or get devfs to rescan for devices, then it should work on -current also. I occurs to me that rescanning might wreak havoc with operations already using other devices, like a disk write or something, so the first option may be preferable. This is not a critical issue, but falls more in the category of "Gee, I wonder if i can (fill-in-the-blank)" sort of thing. BTW, thanks for your reply... Patrick From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 04:26:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C7C816A4CF for ; Sun, 28 Nov 2004 04:26:54 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 895D043D49 for ; Sun, 28 Nov 2004 04:26:53 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen ([141.153.162.122]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041128042652.GBHU1390.out001.verizon.net@RabbitsDen>; Sat, 27 Nov 2004 22:26:52 -0600 From: "Alexandre \"Sunny\" Kovalenko" To: Divacky Roman In-Reply-To: <20041127092059.GA93818@stud.fit.vutbr.cz> References: <20041127092059.GA93818@stud.fit.vutbr.cz> Content-Type: text/plain; charset=iso-8859-5 Date: Sat, 27 Nov 2004 23:26:44 -0500 Message-Id: <1101616004.1087.9.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [141.153.162.122] at Sat, 27 Nov 2004 22:26:47 -0600 cc: current@freebsd.org Subject: Re: ACPI related panic on early boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 04:26:54 -0000 On Sat, 2004-11-27 at 10:20 +0100, Divacky Roman wrote: > Hi, > > after jhb@-s commits to acpi I am getting this panic early on boot, its > handwritten so there might be mistakes. > I have acpi as a module, and the panic seems to occur after probing fdc wihle I > have no fdc attached. I can provide any info you ask for... > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x5 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc049fb86 > stack pointer = 0x10:0xc0820c88 > frame pointer = 0x10:0xc0820c8c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > [thread pid 0 tid 0] > Stopped at device_get_children+0x10: movl 0x4(%eax),%eax > db>trace > Tracing pid 0 tid 0 td 0xc05f7de0 > device_get_children(c1646100,c0820ca4,c0820ca8,c05d5bc0,101) at device_get_children+0x10 > acpi_wake_sysctl_walk(c157bb00,c1670a00,31,c157bb00,c157bb00) at acpi_wake_sysctl_walk+0x17 > acpi_wake_sysctl_walk(fee00fff,fee00000,c163a028,3,c07072a0) at acpi_wake_sysctl_walk+0x44 > acpi_attach(c157bb00,c157bb00,c1573dc0,c157bc00,c0820d34) at acpi_attach+0x684 > device_attach(c157bb00,c157bc00,c0820d48,c058feb3,c157bc00) at device_attach+0x226 > bus_generic_attach(c157bc00,c157bc00,c157bc4c,c0820d60,c04a039c) at bus_generic_attach+0x14 > nexus_attach(c157bc00,c157bc00,0,825000,c0820d70) at nexus_attach+0x13 > device_attach(c157bc00) at device_attach+0x226 > root_bus_configure(c15ca300,c05c5eec,0,c0820d98,c0468fab) at root_bus_configure+0x16 > configure(0,81ec00,81e000,0,c0429e05) at configure+0x1b > mi_startup() at mi_startup+0x86 > begin() at begin+0x2c > > roman > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Rolling back files below while keeping the rest of the tree current as of 21:40 EST eliminated crash for me: acpi_pci_link.c: 1.33 2004/09/25 06:15:56 acpi_pcib.c: 1.51 2004/11/11 22:33:08 acpi_pcib_acpi.c: 1.45 2004/11/09 07:02:33 acpi_pcib_pci.c: 1.10 2004/08/11 14:52:50 acpi_pcibvar.h: 1.3 2004/08/11 14:52:50 I can try patches or provide any additional details. Unfortunately, panic kicks in way before my remote console (PCMCIA Firewire), so backtraces would have to be hand-trascribed. Current one looks sufficiently like one above that I do not think it will add any value. -- Alexandre "Sunny" Kovalenko (¾ÛÕÚáÐÝÔà ºÞÒÐÛÕÝÚÞ). From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 06:52:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47F2D16A4CE for ; Sun, 28 Nov 2004 06:52:43 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id C368143D5A for ; Sun, 28 Nov 2004 06:52:42 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (sccrmhc13) with ESMTP id <20041128065241016001poske>; Sun, 28 Nov 2004 06:52:41 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) iAS6qdRt015418; Sun, 28 Nov 2004 01:52:40 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)iAS6qca8015417; Sun, 28 Nov 2004 01:52:38 -0500 (EST) (envelope-from rodrigc) Date: Sun, 28 Nov 2004 01:52:38 -0500 From: Craig Rodrigues To: Vladimir Grebenschikov Message-ID: <20041128065238.GA11360@crodrigues.org> References: <1101492325.996.54.camel@localhost> <20041128003036.GA883@crodrigues.org> <20041128020411.GA1436@crodrigues.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline In-Reply-To: <20041128020411.GA1436@crodrigues.org> User-Agent: Mutt/1.4.1i cc: "current@freebsd.org" Subject: Re: ptrace broken on latest CURRENT ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 06:52:43 -0000 --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Nov 27, 2004 at 09:04:11PM -0500, Craig Rodrigues wrote: > On Sat, Nov 27, 2004 at 07:30:36PM -0500, Craig Rodrigues wrote: > > --- sys_generic.c.orig Sat Nov 27 19:14:39 2004 > > +++ sys_generic.c Sat Nov 27 19:17:09 2004 > > @@ -503,7 +503,7 @@ > > if ((size > IOCPARM_MAX) || > > ((com & (IOC_VOID | IOC_IN | IOC_OUT)) == 0) || > > ((com & IOC_VOID) && size > 0) || > > - ((com & (IOC_IN | IOC_OUT)) && size == 0)) { > > + ((com & IOC_OUT) && size == 0)) { > > fdrop(fp, td); > > return (ENOTTY); > > } > > > Hi, > > If we leave the define of PIOCBIS as: > # define PIOCBIS _IOC(IOC_IN, 'p', 1, 0) > > then the length of this ioctl is going to be 0 (from IOCPARM_LEN). > I'm not sure if that is a good thing. This is what tripped > up the original ioctl() code in sys_generic.c. > > If we don't change sys_generic.c, then the other approach > to this problem is to fix the ioctl() calls in the procfs. > Any comments on this? Hi, If PIOCBIS is redefined according to the patch which I submitted, then strace needs to be patched as well. I'm not sure of the best way to do this other than bumping __FreeBSD_version__ and checking it. Here are my patches to procfs and strace. Comments? -- Craig Rodrigues http://crodrigues.org rodrigc@crodrigues.org --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="procfs_patch.txt" Index: sys/fs/procfs/procfs_ioctl.c =================================================================== RCS file: /home/ncvs/src/sys/fs/procfs/procfs_ioctl.c,v retrieving revision 1.10 diff -u -r1.10 procfs_ioctl.c --- sys/fs/procfs/procfs_ioctl.c 7 Dec 2003 17:40:00 -0000 1.10 +++ sys/fs/procfs/procfs_ioctl.c 28 Nov 2004 06:48:03 -0000 @@ -46,8 +46,8 @@ procfs_ioctl(PFS_IOCTL_ARGS) { struct procfs_status *ps; - int error, flags, sig; - + int error; + unsigned int flags, sig; PROC_LOCK(p); error = 0; switch (cmd) { Index: sys/sys/param.h =================================================================== RCS file: /home/ncvs/src/sys/sys/param.h,v retrieving revision 1.218 diff -u -r1.218 param.h --- sys/sys/param.h 4 Nov 2004 08:38:34 -0000 1.218 +++ sys/sys/param.h 28 Nov 2004 06:48:05 -0000 @@ -57,7 +57,7 @@ * is created, otherwise 1. */ #undef __FreeBSD_version -#define __FreeBSD_version 600006 /* Master, propagated to newvers */ +#define __FreeBSD_version 600007 /* Master, propagated to newvers */ #ifndef LOCORE #include Index: sys/sys/pioctl.h =================================================================== RCS file: /home/ncvs/src/sys/sys/pioctl.h,v retrieving revision 1.12 diff -u -r1.12 pioctl.h --- sys/sys/pioctl.h 4 Aug 2002 01:06:58 -0000 1.12 +++ sys/sys/pioctl.h 28 Nov 2004 06:48:05 -0000 @@ -49,12 +49,12 @@ unsigned long val; /* Any extra data */ }; -# define PIOCBIS _IOC(IOC_IN, 'p', 1, 0) /* Set event flag */ -# define PIOCBIC _IOC(IOC_IN, 'p', 2, 0) /* Clear event flag */ -# define PIOCSFL _IOC(IOC_IN, 'p', 3, 0) /* Set flags */ +# define PIOCBIS _IOW('p', 1, unsigned int) /* Set event flag */ +# define PIOCBIC _IOW('p', 2, unsigned int) /* Clear event flag */ +# define PIOCSFL _IOW('p', 3, unsigned int) /* Set flags */ /* wait for proc to stop */ # define PIOCWAIT _IOR('p', 4, struct procfs_status) -# define PIOCCONT _IOC(IOC_IN, 'p', 5, 0) /* Continue a process */ +# define PIOCCONT _IOW('p', 5, unsigned int) /* Continue a process */ /* Get proc status */ # define PIOCSTATUS _IOR('p', 6, struct procfs_status) # define PIOCGFL _IOR('p', 7, unsigned int) /* Get flags */ Index: usr.bin/truss/extern.h =================================================================== RCS file: /home/ncvs/src/usr.bin/truss/extern.h,v retrieving revision 1.9 diff -u -r1.9 extern.h --- usr.bin/truss/extern.h 17 Jul 2004 19:19:36 -0000 1.9 +++ usr.bin/truss/extern.h 28 Nov 2004 06:48:06 -0000 @@ -32,7 +32,7 @@ */ extern int setup_and_wait(char **); -extern int start_tracing(int, int, int); +extern int start_tracing(int, unsigned int, int); extern void restore_proc(int); extern const char *ioctlname(register_t val); extern char *strsig(int sig); Index: usr.bin/truss/main.c =================================================================== RCS file: /home/ncvs/src/usr.bin/truss/main.c,v retrieving revision 1.38 diff -u -r1.38 main.c --- usr.bin/truss/main.c 17 Jul 2004 19:19:36 -0000 1.38 +++ usr.bin/truss/main.c 28 Nov 2004 06:48:07 -0000 @@ -322,7 +322,7 @@ break; } } - if (ioctl(Procfd, PIOCCONT, val) == -1) { + if (ioctl(Procfd, PIOCCONT, &val) == -1) { if (kill(trussinfo->pid, 0) == -1 && errno == ESRCH) break; else Index: usr.bin/truss/setup.c =================================================================== RCS file: /home/ncvs/src/usr.bin/truss/setup.c,v retrieving revision 1.19 diff -u -r1.19 setup.c --- usr.bin/truss/setup.c 7 Jan 2004 14:29:45 -0000 1.19 +++ usr.bin/truss/setup.c 28 Nov 2004 06:48:08 -0000 @@ -54,7 +54,7 @@ #include "truss.h" #include "extern.h" -static int evflags = 0; +static unsigned int evflags = 0; /* * setup_and_wait() is called to start a process. All it really does @@ -69,19 +69,19 @@ char buf[32]; int fd; int pid; - int flags; + unsigned int flags; pid = fork(); if (pid == -1) { err(1, "fork failed"); } if (pid == 0) { /* Child */ - int mask = S_EXEC | S_EXIT; + unsigned int mask = S_EXEC | S_EXIT; fd = open("/proc/curproc/mem", O_WRONLY); if (fd == -1) err(2, "cannot open /proc/curproc/mem"); fcntl(fd, F_SETFD, 1); - if (ioctl(fd, PIOCBIS, mask) == -1) + if (ioctl(fd, PIOCBIS, &mask) == -1) err(3, "PIOCBIS"); flags = PF_LINGER; /* @@ -89,11 +89,11 @@ * process on last close; normally, this is the behaviour * we want. */ - if (ioctl(fd, PIOCSFL, flags) == -1) + if (ioctl(fd, PIOCSFL, &flags) == -1) warn("cannot set PF_LINGER"); execvp(command[0], command); mask = ~0; - ioctl(fd, PIOCBIC, ~0); + ioctl(fd, PIOCBIC, &mask); err(4, "execvp %s", command[0]); } /* Only in the parent here */ @@ -128,7 +128,7 @@ */ int -start_tracing(int pid, int eventflags, int flags) { +start_tracing(int pid, unsigned int eventflags, int flags) { int fd; char buf[32]; struct procfs_status tmp; @@ -151,7 +151,7 @@ } evflags = tmp.events; - if (ioctl(fd, PIOCBIS, eventflags) == -1) + if (ioctl(fd, PIOCBIS, &eventflags) == -1) err(9, "cannot set procfs event bit mask"); /* @@ -160,7 +160,7 @@ * needs to be woken up via procctl. */ - if (ioctl(fd, PIOCSFL, flags) == -1) + if (ioctl(fd, PIOCSFL, &flags) == -1) warn("cannot clear PF_LINGER"); return fd; @@ -174,9 +174,9 @@ */ void restore_proc(int signo __unused) { - - ioctl(Procfd, PIOCBIC, ~0); + unsigned int flags = ~0; + ioctl(Procfd, PIOCBIC, &flags); if (evflags) - ioctl(Procfd, PIOCBIS, evflags); + ioctl(Procfd, PIOCBIS, &evflags); exit(0); } --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-strace.c" --- strace.c.orig Tue Nov 11 16:24:23 2003 +++ strace.c Sun Nov 28 01:33:18 2004 @@ -798,7 +798,11 @@ return -1; } arg &= ~PF_LINGER; +#if __FreeBSD_version >= 600007 + if (ioctl(tcp->pfd, PIOCSFL, &arg) < 0) { +#else if (ioctl(tcp->pfd, PIOCSFL, arg) < 0) { +#endif /* __FreeBSD_version */ perror("PIOCSFL"); return -1; } @@ -859,7 +863,11 @@ #else /* FREEBSD */ /* set events flags. */ arg = S_SIG | S_SCE | S_SCX ; +#if __FreeBSD_version >= 600007 + if(ioctl(tcp->pfd, PIOCBIS, &arg) < 0) { +#else if(ioctl(tcp->pfd, PIOCBIS, arg) < 0) { +#endif perror("PIOCBIS"); return -1; } @@ -898,7 +906,7 @@ break; } /* Set it running: maybe execve will be next. */ -#ifndef FREEBSD +#if !defined(FREEBSD) || ((defined FREEBSD) && (__FreeBSD_version >= 600007)) arg = 0; if (IOCTL(tcp->pfd, PIOCRUN, &arg) < 0) { #else /* FREEBSD */ @@ -1796,7 +1804,7 @@ break; } arg = 0; -#ifndef FREEBSD +#if !defined(FREEBSD) || ((defined FREEBSD) && (__FreeBSD_version >= 600007)) if (IOCTL (tcp->pfd, PIOCRUN, &arg) < 0) { #else if (IOCTL (tcp->pfd, PIOCRUN, 0) < 0) { --UlVJffcvxoiEqYs2-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 09:02:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EA1916A4CE for ; Sun, 28 Nov 2004 09:02:43 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id E64BB43D39 for ; Sun, 28 Nov 2004 09:02:41 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received-SPF: pass (eva.fit.vutbr.cz: domain of xdivac02@eva.fit.vutbr.cz designates 127.0.0.1 as permitted sender) receiver=eva.fit.vutbr.cz; client_ip=127.0.0.1; envelope-from=xdivac02@eva.fit.vutbr.cz; Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id iAS92be9058157 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 28 Nov 2004 10:02:37 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id iAS92bkB058156; Sun, 28 Nov 2004 10:02:37 +0100 (CET) Date: Sun, 28 Nov 2004 10:02:37 +0100 From: Divacky Roman To: Alexandre Sunny Kovalenko Message-ID: <20041128090237.GA58114@stud.fit.vutbr.cz> References: <20041127092059.GA93818@stud.fit.vutbr.cz> <1101616004.1087.9.camel@RabbitsDen> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1101616004.1087.9.camel@RabbitsDen> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: current@freebsd.org Subject: Re: ACPI related panic on early boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 09:02:43 -0000 with the recent commit from njl@ which disabled "something" I am getting another trace... it is very lengty so I'd like to avoid to have to rewrite it. On Sat, Nov 27, 2004 at 11:26:44PM -0500, Alexandre Sunny Kovalenko wrote: > On Sat, 2004-11-27 at 10:20 +0100, Divacky Roman wrote: > > Hi, > > > > after jhb@-s commits to acpi I am getting this panic early on boot, its > > handwritten so there might be mistakes. > > I have acpi as a module, and the panic seems to occur after probing fdc wihle I > > have no fdc attached. I can provide any info you ask for... > > > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0x5 > > fault code = supervisor read, page not present > > instruction pointer = 0x8:0xc049fb86 > > stack pointer = 0x10:0xc0820c88 > > frame pointer = 0x10:0xc0820c8c > > code segment = base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, def32 1, gran 1 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > current process = 0 (swapper) > > [thread pid 0 tid 0] > > Stopped at device_get_children+0x10: movl 0x4(%eax),%eax > > db>trace > > Tracing pid 0 tid 0 td 0xc05f7de0 > > device_get_children(c1646100,c0820ca4,c0820ca8,c05d5bc0,101) at device_get_children+0x10 > > acpi_wake_sysctl_walk(c157bb00,c1670a00,31,c157bb00,c157bb00) at acpi_wake_sysctl_walk+0x17 > > acpi_wake_sysctl_walk(fee00fff,fee00000,c163a028,3,c07072a0) at acpi_wake_sysctl_walk+0x44 > > acpi_attach(c157bb00,c157bb00,c1573dc0,c157bc00,c0820d34) at acpi_attach+0x684 > > device_attach(c157bb00,c157bc00,c0820d48,c058feb3,c157bc00) at device_attach+0x226 > > bus_generic_attach(c157bc00,c157bc00,c157bc4c,c0820d60,c04a039c) at bus_generic_attach+0x14 > > nexus_attach(c157bc00,c157bc00,0,825000,c0820d70) at nexus_attach+0x13 > > device_attach(c157bc00) at device_attach+0x226 > > root_bus_configure(c15ca300,c05c5eec,0,c0820d98,c0468fab) at root_bus_configure+0x16 > > configure(0,81ec00,81e000,0,c0429e05) at configure+0x1b > > mi_startup() at mi_startup+0x86 > > begin() at begin+0x2c > > > > roman > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > Rolling back files below while keeping the rest of the tree current as > of 21:40 EST eliminated crash for me: > > acpi_pci_link.c: 1.33 2004/09/25 06:15:56 > acpi_pcib.c: 1.51 2004/11/11 22:33:08 > acpi_pcib_acpi.c: 1.45 2004/11/09 07:02:33 > acpi_pcib_pci.c: 1.10 2004/08/11 14:52:50 > acpi_pcibvar.h: 1.3 2004/08/11 14:52:50 > > I can try patches or provide any additional details. Unfortunately, > panic kicks in way before my remote console (PCMCIA Firewire), so > backtraces would have to be hand-trascribed. Current one looks > sufficiently like one above that I do not think it will add any value. > > -- > Alexandre "Sunny" Kovalenko (????????? ?????????). From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 10:25:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 118A316A4CE for ; Sun, 28 Nov 2004 10:25:20 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1394843D66 for ; Sun, 28 Nov 2004 10:25:17 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iASAP8fQ006238; Sun, 28 Nov 2004 20:55:09 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Sun, 28 Nov 2004 20:55:00 +1030 User-Agent: KMail/1.7 References: <41A8C9C3.1020504@juno.com> <20041127192257.GA10638@il.fontys.nl> In-Reply-To: <20041127192257.GA10638@il.fontys.nl> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1561447.tqgpDCc7X8"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411282055.07190.doconnor@gsoft.com.au> X-Spam-Score: -2.8 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Patrick Bowen cc: Ed Schouten Subject: Re: Getting devfs to recognize a hotplugged fd0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 10:25:20 -0000 --nextPart1561447.tqgpDCc7X8 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sun, 28 Nov 2004 05:52, Ed Schouten wrote: > Hello Patrick, > > Patrick Bowen wrote: > > I'm trying to learn how to get devfs to create an fd0 enty in /dev > > automatically when I plug a floppy drive into the serial port of a > > running Dell D600 laptop running 6.0 current. > > Are you sure that's possible at all? You know the serial port isn't > plug-and-play? How can the operating system tell that there is something = on > the serial port at all? :) I would guess he means USB when he says serial. I imagine the floppy drive appears as da0 in -current. Perhaps it worked as= =20 fd0 in 4.x with heavy (HEAVY) BIOS magic.. Also he could be parallel when he says serial... Patrik - how many pins does the port in question have? What model laptop is= =20 it? =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1561447.tqgpDCc7X8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBqaeD5ZPcIHs/zowRAmN6AKCIBoXFdsANsW42nLeouC24WweyygCggZi6 GgJTRnrzXkd1PZBb5RvxQpk= =LZMe -----END PGP SIGNATURE----- --nextPart1561447.tqgpDCc7X8-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 10:44:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C624016A4CE for ; Sun, 28 Nov 2004 10:44:54 +0000 (GMT) Received: from av1-2-sn3.vrr.skanova.net (av1-2-sn3.vrr.skanova.net [81.228.9.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E9EE43D4C for ; Sun, 28 Nov 2004 10:44:54 +0000 (GMT) (envelope-from diizzy@telia.com) Received: by av1-2-sn3.vrr.skanova.net (Postfix, from userid 502) id 58C7C37E53; Sun, 28 Nov 2004 11:44:53 +0100 (CET) Received: from smtp1-2-sn3.vrr.skanova.net (smtp1-2-sn3.vrr.skanova.net [81.228.9.178]) by av1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 42A2C37E42 for ; Sun, 28 Nov 2004 11:44:53 +0100 (CET) Received: from d1o401.telia.com (d1o401.telia.com [195.67.227.91]) by smtp1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 317DF3800E for ; Sun, 28 Nov 2004 11:44:53 +0100 (CET) Received: by d1o401.telia.com (8.11.1/8.10.1) id iASAir823626; Sun, 28 Nov 2004 11:44:53 +0100 (CET) Date: Sun, 28 Nov 2004 11:44:53 +0100 (CET) Message-Id: <200411281044.iASAir823626@d1o401.telia.com> X-Authentication-Warning: d1o401.telia.com: www set sender to diizzy@telia.com using -f From: "Daniel Engberg" To: freebsd-current@freebsd.org X-Mailer: SF Webmail X-SF-webmail-clientstamp: [217.210.253.102] 2004-11-28 11:44:53 Subject: Re: if_pcn & netfinity 5500 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Engberg List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 10:44:54 -0000 I had the same issue and it got solved by this patch. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/72966 //Danne From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 11:27:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E26316A4CE for ; Sun, 28 Nov 2004 11:27:30 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id D452A43D1F for ; Sun, 28 Nov 2004 11:27:29 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iASBRRNB007707; Sun, 28 Nov 2004 12:27:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kris Kennaway From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 27 Nov 2004 14:56:38 PST." <20041127225638.GA99683@xor.obsecurity.org> Date: Sun, 28 Nov 2004 12:27:27 +0100 Message-ID: <7706.1101641247@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freeBSD.org Subject: Re: panic: sleeping thread (pid 57200) owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 11:27:30 -0000 >db> tr 57200 >Tracing pid 57200 tid 100163 td 0xc578f480 >sched_switch(c578f480,0,1,11e,c35984d3) at sched_switch+0xef >mi_switch(1,0,c06e70b7,1ab,1) at mi_switch+0x1c2 >sleepq_switch(c06e3a2c,18e,1,1,eecbdc50) at sleepq_switch+0x10a >sleepq_wait(c5d3b24c,0,c06e4d0f,da,0) at sleepq_wait+0x1a >msleep(c5d3b24c,c5d3b228,64,c06e0dc6,0) at msleep+0x4e4 >checkdirs(c5853000,eecbdca4,c578f480,c578f480,0) at checkdirs+0xe0 Ok, got it. Fixed I hope. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 12:55:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB54F16A4CF for ; Sun, 28 Nov 2004 12:55:33 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B01343D58 for ; Sun, 28 Nov 2004 12:55:33 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iASCrYVQ096313; Sun, 28 Nov 2004 07:53:34 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iASCrXmF096310; Sun, 28 Nov 2004 12:53:33 GMT (envelope-from robert@fledge.watson.org) Date: Sun, 28 Nov 2004 12:53:33 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Patrick Bowen In-Reply-To: <41A943F9.40106@juno.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD Current Subject: Re: Getting devfs to recognize a hotplugged fd0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 12:55:33 -0000 On Sat, 27 Nov 2004, Patrick Bowen wrote: > No, I'm not sure. But, in 4.10, with /dev already populated with an > entry for fd0, I could plug the floppy into a running machine and then > mount it, no problem. So I'm thinking that if can either create an entry > for /dev/fd0 during or shortly after boot time, or get devfs to rescan > for devices, then it should work on -current also. I occurs to me that > rescanning might wreak havoc with operations already using other > devices, like a disk write or something, so the first option may be > preferable. > > This is not a critical issue, but falls more in the category of "Gee, I > wonder if i can (fill-in-the-blank)" sort of thing. > > BTW, thanks for your reply... I think some of the confusion here is from the use of terminology: devfs doesn't operate quite like MAKEDEV did -- the creation of devfs nodes is driven by the device drivers and device driver frameworks directly. If a device node is missing in /dev, it's because no device driver has registered it, not because devfs needs to realize the set of devices has changed and update its list. Right now, storage drivers register with GEOM to announce that a new disk is available, using the disk(9) API. GEOM will perform the necessary probing and transforms to find disk labels, etc, and then announce the resulting device nodes to devfs using make_dev(9). If /dev/fd0 isn't in /dev, it's most likely because the floppy disk device driver hasn't notified GEOM that one is available. It's worth noting that there are actually two approaches to removable media in FreeBSD: first, one where the drive itself is considered a fairly "fixed" device, with removable media that come and go, and second, where the device itself coes and goes. The floppy disk subsystem has generally taken the former approach, which results in the floppy disk device node being present even if a floppy disk itself is not present in the drive. My understanding is that, unlike with SCSI or USB, the floppy disk controller interface doesn't have the capability to announce device arrival or departure. It could be that in 4.x, we had the device node hooked up to the driver regardless of a successful probe, and an open of the node would result in a hardware probe, whereas in 5.x, the device node is only presented if the driver says "it's here". The device driver has also changed quite a bit since 4.x -- could you compare what is probed in the dmesg output of 4.x and 5.x, in terms of probing the controller (fdc) vs. drives (fd*)? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sat Nov 27 14:08:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F3D416A4CE; Sat, 27 Nov 2004 14:08:16 +0000 (GMT) Received: from therion.astral-on.net (therion.astral-on.net [193.41.4.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ACF543D49; Sat, 27 Nov 2004 14:08:14 +0000 (GMT) (envelope-from ad@astral-on.net) Received: from odin.astral-on.net (odin.astral-on.net [193.41.4.6]) iARE7AFs093427; Sat, 27 Nov 2004 16:07:12 +0200 (EET) (envelope-from ad@astral-on.net) Received: from odin.astral-on.net (localhost [127.0.0.1]) by odin.astral-on.net (8.12.8p2/8.12.8) with ESMTP id iARE7Awk027914; Sat, 27 Nov 2004 16:07:10 +0200 (EET) (envelope-from ad@odin.astral-on.net) Received: (from ad@localhost) by odin.astral-on.net (8.12.8p2/8.12.8/Submit) id iARE77BV027913; Sat, 27 Nov 2004 16:07:07 +0200 (EET) Date: Sat, 27 Nov 2004 16:07:07 +0200 From: Andrew Degtiariov To: Daniel Hartmeier Message-ID: <20041127140707.GA20356@astral-on.net> Mail-Followup-To: Daniel Hartmeier , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <20041126203354.GB81834@astral-on.net> <20041127120149.GE23786@insomnia.benzedrine.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041127120149.GE23786@insomnia.benzedrine.cx> User-Agent: Mutt/1.5.6i X-Mailman-Approved-At: Sun, 28 Nov 2004 13:01:34 +0000 cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: rsh is malfunctioning due to pf X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ad@astral-on.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Nov 2004 14:08:16 -0000 On Sat, Nov 27, 2004 at 01:01:49PM +0100, Daniel Hartmeier wrote: > On Fri, Nov 26, 2004 at 10:33:54PM +0200, Andrew Degtiariov wrote: > > > I have ipcad installed on 2 PC's running 5.3-RELEASE and 5-STABLE from > > Nov 21. ipcad (ports/net-mgmt/ipcad) provides ability to control them > > by rsh (ipcad implement rsh server by yourself). While using pf with > > primitive rulesets rsh stops its working. It seems like pf drop short > > packets. > > The 'short' reason is a little overloaded, it can have two meanings. > The less likely case is where the mbuf didn't contain a complete IP > header. More likely, the packet contains IP options, which pf blocks by > default. You can isolate the problem by > > a) enabling debug logging with pfctl -xm and watching the console > or /var/log/messages for messages from 'pf: ' > b) dumping an entire packet that is being blocked, with > tcpdump -s 1600 -nvvvetttSXi pflog0 > c) adding 'allow-opts' to all your pass rules and see if the problem > goes away Yes, allow-opts restored ipcad functionality. Probality need to add warning to pf documentation about this behavior, b/c enabling pf broke multicast (ospf for me) with out rules with allow-opts. I was see note about it exists only in pf.conf (in allow-opts description) and leave out it unnoticed while read this manual page. -- Andrew Degtiariov DA-RIPE From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 10:01:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB65216A4CE for ; Sun, 28 Nov 2004 10:01:54 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 757F243D67 for ; Sun, 28 Nov 2004 10:01:54 +0000 (GMT) (envelope-from dr.clau@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so332134rnf for ; Sun, 28 Nov 2004 02:01:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:disposition-notification-to:date:from:user-agent:x-accept-language:mime-version:to:subject:x-enigmail-version:x-enigmail-supports:content-type; b=rmJxLNl4J+rBvezN2d5017k+mz4CpgR/txMKADGmX8Vo7g/UmDthMJscRxoR7XlDcZkVBipBGPOzJhrQpfDRGkwpYXZc+GDVXEyiEkwWu8OgFBfkAeGOg3JiGmOiubSOkFOxTIoQnTk1YVwt4LsHCR9HCLtBI3TBBnw74hoLacc= Received: by 10.38.208.78 with SMTP id f78mr339915rng; Sun, 28 Nov 2004 02:01:53 -0800 (PST) Received: from ?82.79.29.15? ([82.79.29.15]) by smtp.gmail.com with ESMTP id 64sm182rna; Sun, 28 Nov 2004 02:01:53 -0800 (PST) Message-ID: <41A9A24F.7050403@gmail.com> Date: Sun, 28 Nov 2004 12:02:55 +0200 From: Claudiu Dragalia-Paraipan User-Agent: Mozilla Thunderbird 0.9 (X11/20041125) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig3558850BDFD5B0E9816A932C" X-Mailman-Approved-At: Sun, 28 Nov 2004 13:01:34 +0000 Subject: ssh & select() problem on 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 10:01:55 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3558850BDFD5B0E9816A932C Content-Type: multipart/mixed; boundary="------------080405090304050100040708" This is a multi-part message in MIME format. --------------080405090304050100040708 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello, I've posted this on hackers list too, but it might be more 'at home' here. Since I have upgraded to FreeBSD 5.3 I have the following problem with SSH client: I log on several FreeBSD 5.2.1 machines, and when I start a command that gives a 'large' result (like dmesg, cat a file), ssh client locks. I ran ssh in gdb, and found out that it locks in select() in libc.so.5. I do it like this: run ssh in gdb, connect to the host, run a dmesg. After this it locks, and I have to send a SIGKILL or SIGTERM before I can see this in gdb: Program received signal SIGTERM, Terminated. 0x282b5dd7 in select () from /lib/libc.so.5 (gdb) The result of a bt is (if relevant): #0 0x282b5dd7 in select () from /lib/libc.so.5 #1 0x08050aae in ?? () #2 0x0000000a in ?? () #3 0x0806e3a0 in ?? () #4 0x0806e3c0 in ?? () #5 0x00000000 in ?? () #6 0x00000000 in ?? () #7 0x0806e3a0 in ?? () #8 0xbfbfe878 in ?? () #9 0x08050a47 in ?? () #10 0x280c1134 in datafellows () from /usr/lib/libssh.so.2 #11 0x280c11e0 in datafellows () from /usr/lib/libssh.so.2 #12 0xbfbfe818 in ?? () #13 0x280ab99f in packet_read_expect () from /usr/lib/libssh.so.2 #14 0x08051efd in ?? () #15 0xbfbfe8b0 in ?? () #16 0xbfbfe8b4 in ?? () #17 0xbfbfe8b8 in ?? () #18 0xbfbfe8bc in ?? () #19 0x00000000 in ?? () #20 0x00000000 in ?? () #21 0xbfbfe948 in ?? () #22 0x08051ec5 in ?? () #23 0x080644dc in ?? () #24 0x080644c0 in ?? () #25 0xc856fd7a in ?? () #26 0x41d06a17 in ?? () #27 0x0806e3a0 in ?? () #28 0x0806e3c0 in ?? () #29 0x00000009 in ?? () #30 0x00000004 in ?? () #31 0x0805e87c in ?? () #32 0xbfbfe904 in ?? () #33 0x28066b02 in rlock_release () from /libexec/ld-elf.so.1 #34 0x0804e8e7 in ?? () #35 0x00000001 in ?? () #36 0x0000007e in ?? () #37 0x00000000 in ?? () #38 0x0804e880 in ?? () #39 0x08060180 in ?? () #40 0x0805ef2c in environ () #41 0xbfbfeb80 in ?? () #42 0x0804da63 in ?? () #43 0x28085150 in ?? () #44 0xbfbfeb48 in ?? () #45 0xbfbfe998 in ?? () #46 0x28064262 in find_symdef () from /libexec/ld-elf.so.1 Previous frame inner to this frame (corrupt stack?) This happens both in SMP on UP kernels. Attached is dmesg for UP kernel. Also, ocasionally it hangs at shutdown or reboot, at random places (?), and it seems to be happening after I have a locked ssh client in the system. If you need more informations about this, and you think this are related, let me know and I will run a kernel with debugging enabled, to get more informations. Best regards, -- Claudiu Dragalina-Paraipan dr.clau@gmail.com --------------080405090304050100040708 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.txt" Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE-p1 #0: Sat Nov 27 12:37:28 EET 2004 root@oxygen:/usr/obj/usr/src/sys/O2 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.20-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 250802176 (239 MB) avail memory = 239951872 (228 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: port 0xec00-0xec07 mem 0xffa80000-0xffafffff,0xf0000000-0xf7ffffff irq 16 at device 2.0 on pci0 agp0: detected 16252k stolen memory agp0: aperture size is 128M pcib1: at device 30.0 on pci0 pci1: on pcib1 rl0: port 0xd800-0xd8ff mem 0xff8ffc00-0xff8ffcff irq 17 at device 5.0 on pci1 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:10:b5:87:62:d3 fxp0: port 0xdc00-0xdc3f mem 0xff8fe000-0xff8fefff irq 20 at device 8.0 on pci1 miibus1: on fxp0 inphy0: on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:0c:f1:e2:33:e5 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) pci0: at device 31.5 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled Timecounter "TSC" frequency 2793198416 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ad0: 76319MB [155061/16/63] at ata0-master UDMA100 ad2: 39266MB [79780/16/63] at ata1-master UDMA100 acd0: CDRW at ata1-slave UDMA33 Mounting root from ufs:/dev/ad0s3a pflog0: promiscuous mode enabled --------------080405090304050100040708-- --------------enig3558850BDFD5B0E9816A932C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBqaJUm0FWxb+swkQRAtsaAJ405MaaAiVO10lL/ztt3U3kVUpnqgCeNxFl puHh7MsgW9Gduquhb9LPh1Y= =9jJ0 -----END PGP SIGNATURE----- --------------enig3558850BDFD5B0E9816A932C-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 14:26:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B468616A4CE for ; Sun, 28 Nov 2004 14:26:02 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A32143D4C for ; Sun, 28 Nov 2004 14:26:02 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iASEO2dQ097725; Sun, 28 Nov 2004 09:24:02 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iASEO2KQ097722; Sun, 28 Nov 2004 14:24:02 GMT (envelope-from robert@fledge.watson.org) Date: Sun, 28 Nov 2004 14:24:02 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Claudiu Dragalia-Paraipan In-Reply-To: <41A9A24F.7050403@gmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: ssh & select() problem on 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 14:26:02 -0000 On Sun, 28 Nov 2004, Claudiu Dragalia-Paraipan wrote: > Since I have upgraded to FreeBSD 5.3 I have the following problem with > SSH client: I log on several FreeBSD 5.2.1 machines, and when I start a > command that gives a 'large' result (like dmesg, cat a file), ssh client > locks. I ran ssh in gdb, and found out that it locks in select() in > libc.so.5. I do it like this: run ssh in gdb, connect to the host, run > a dmesg. After this it locks, and I have to send a SIGKILL or SIGTERM > before I can see this in gdb: > > Program received signal SIGTERM, Terminated. > 0x282b5dd7 in select () from /lib/libc.so.5 > (gdb) > > The result of a bt is (if relevant): > #0 0x282b5dd7 in select () from /lib/libc.so.5 > This happens both in SMP on UP kernels. Attached is dmesg for UP kernel. > Also, ocasionally it hangs at shutdown or reboot, at random places (?), > and it seems to be happening after I have a locked ssh client in the > system. If you need more informations about this, and you think this are > related, let me know and I will run a kernel with debugging enabled, to > get more informations. Sounds like a bug, but the interesting question is really whether it's a kernel bug or an SSH bug. I'm not up on SSH internals, but there are a few other knobs you might try and things to look at that might help address whether it's a kernel bug or not: (1) Try debug.mpsafenet=0 in loader.conf on the 5.3 box -- if we're looking at a kernel race condition due to a locking bug, that might close the race. However, it might also just changing the timing... That this happens on SMP and UP suggests that it's not so much a timing issue. (2) select() is almost always used to wait for space in a buffer to write, or wait for data in a buffer to read. Using a combination of netstat(1) and sockstat(1), it would be useful to know whether there is in fact data in either the send or receive buffer. Combined with inspecting the state of the select arguments and socket buffers in kernel, this might reveal whether perhaps there was a missed wakeup. It's worth noting that we believe we corrected a bug with exactly thes symptoms shortly before 5.3 release. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 16:43:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 762DB16A4CE for ; Sun, 28 Nov 2004 16:43:03 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8685743D54 for ; Sun, 28 Nov 2004 16:42:49 +0000 (GMT) (envelope-from dr.clau@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so343652rnf for ; Sun, 28 Nov 2004 08:42:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:disposition-notification-to:date:from:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:x-enigmail-supports:content-type; b=RNJjgaoONGG2tqzR+i7WVvFwJecIUyq2d3Cgu8JPSJzUG5GwN3ZBfbfZNf4gRWDs87jbM4ep79RExupwzCFuJ74MLGvSt+LI46liMTDdoiq6R8n6Bcwv4rwgHb7MnPAhRriyj6gpcc7P3FEEi1PGaa3U4PuDzC0oDnCh32l9qyM= Received: by 10.38.83.75 with SMTP id g75mr1195743rnb; Sun, 28 Nov 2004 08:42:45 -0800 (PST) Received: from ?82.79.29.15? ([82.79.29.15]) by smtp.gmail.com with ESMTP id 71sm6114rnb; Sun, 28 Nov 2004 08:42:45 -0800 (PST) Message-ID: <41AA0043.5070109@gmail.com> Date: Sun, 28 Nov 2004 18:43:47 +0200 From: Claudiu Dragalia-Paraipan User-Agent: Mozilla Thunderbird 0.9 (X11/20041125) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC03C16C868CA298C8D5432BB" cc: hackers@freebsd.org cc: current@freebsd.org Subject: Re: ssh & select() problem on 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 16:43:03 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC03C16C868CA298C8D5432BB Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, Robert Watson wrote: > Sounds like a bug, but the interesting question is really whether it's a > kernel bug or an SSH bug. I'm not up on SSH internals, but there are a > few other knobs you might try and things to look at that might help > address whether it's a kernel bug or not: > > (1) Try debug.mpsafenet=0 in loader.conf on the 5.3 box -- if we're > looking at a kernel race condition due to a locking bug, that might > close the race. However, it might also just changing the timing... > That this happens on SMP and UP suggests that it's not so much a > timing issue. I tried debug.mpsafenet=0. No change. > > (2) select() is almost always used to wait for space in a buffer to write, > or wait for data in a buffer to read. Using a combination of > netstat(1) and sockstat(1), it would be useful to know whether there > is in fact data in either the send or receive buffer. Combined with > inspecting the state of the select arguments and socket buffers in > kernel, this might reveal whether perhaps there was a missed wakeup. > It's worth noting that we believe we corrected a bug with exactly thes > symptoms shortly before 5.3 release. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee Research I knew about the poll()/select() issue, that's why I thought this is the case. I have tried to same connection from a Windows with Putty client, on one machine everything is ok, but on another dmesg triggers again the lock. A friend tried both FreeBSD 5.3 and Windows, and it seems that it locks more often in 5.3, but not only in 5.3. More, I connected to another machine with ssh, and from there I ssh'ed to the server which seems to trigger the lock. It still locks. Even more, a tcpdump on the other end (I have access to the router/firewall, which is right before the machine I am testing with), after the lock-up, still shows packets being send from the server to me, but a tcpdump at my end shows nothing: packets never get here. In the light of the new events, I guess I can say that FreeBSD 5.3 acts exactly as it should act, select() waits for packets that never get here. Unless packets get here but are never processed by kernel (?). Since the problem occurs only when I connect to the firewall or to a server behind it, I started to suspect a hardware failure. Could a network card cause such problems ? The firewall is running on FreeBSD 5.2.1 with PF+ALTQ, and I can observe the same behaviour: dmesg locks ssh connection. I have test this with PF disabled, and the problem still occurs, so I can eliminate PF as a problem. I've crossposted to hackers list too, since this can be of interest there too. If anyone has any ideea of what might be going on, it would be helpful. With respect, -- Claudiu Dragalina-Paraipan dr.clau@gmail.com --------------enigC03C16C868CA298C8D5432BB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBqgBIm0FWxb+swkQRAkL/AJ9Ae9XtPWVogfjjiGmaBBx6BOhccwCgnnGV vcbFYH0Aq06Lif4pkVIjLIc= =3hLL -----END PGP SIGNATURE----- --------------enigC03C16C868CA298C8D5432BB-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 18:08:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35FE516A4CE; Sun, 28 Nov 2004 18:08:45 +0000 (GMT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE8A343D45; Sun, 28 Nov 2004 18:08:44 +0000 (GMT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.13.1/8.13.1) with ESMTP id iASI8hwH060436; Sun, 28 Nov 2004 13:08:43 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.13.1/8.13.1/Submit) id iASI8hCE060435; Sun, 28 Nov 2004 13:08:43 -0500 (EST) (envelope-from barney) Date: Sun, 28 Nov 2004 13:08:43 -0500 From: Barney Wolff To: Claudiu Dragalia-Paraipan Message-ID: <20041128180843.GA58546@pit.databus.com> References: <41AA0043.5070109@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AA0043.5070109@gmail.com> User-Agent: Mutt/1.5.6i X-Scanned-By: MIMEDefang 2.48 on 127.0.0.1 cc: hackers@freebsd.org cc: Robert Watson cc: current@freebsd.org Subject: Re: ssh & select() problem on 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 18:08:45 -0000 On Sun, Nov 28, 2004 at 06:43:47PM +0200, Claudiu Dragalia-Paraipan wrote: > > Since the problem occurs only when I connect to the firewall or to a > server behind it, I started to suspect a hardware failure. Could a > network card cause such problems ? > The firewall is running on FreeBSD 5.2.1 with PF+ALTQ, and I can observe > the same behaviour: dmesg locks ssh connection. I have test this with PF > disabled, and the problem still occurs, so I can eliminate PF as a problem. Perhaps an MTU problem, with the ICMP "fragmentation needed but DF set" being blocked by the firewall? It would only show up when the server has enough to send to fill a packet. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 18:29:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D6AC16A4CE; Sun, 28 Nov 2004 18:29:52 +0000 (GMT) Received: from mail.rdstm.ro (mail.rdstm.ro [193.231.233.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB6AA43D46; Sun, 28 Nov 2004 18:29:51 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from [10.0.0.2] (casa_auto [81.196.32.25]) by mail.rdstm.ro (8.12.10/8.12.1) with ESMTP id iASIQUOp026010; Sun, 28 Nov 2004 20:26:30 +0200 Message-ID: <41AA192B.10802@spintech.ro> Date: Sun, 28 Nov 2004 20:30:03 +0200 From: Alin-Adrian Anton User-Agent: Mozilla Thunderbird 0.8 (X11/20041016) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Barney Wolff , freebsd-current@freebsd.org, freebsd-hackers@freebsd.org References: <41AA0043.5070109@gmail.com> <20041128180843.GA58546@pit.databus.com> In-Reply-To: <20041128180843.GA58546@pit.databus.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ssh & select() problem on 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 18:29:52 -0000 Hi, Barney Wolff wrote: > > Perhaps an MTU problem, with the ICMP "fragmentation needed but DF set" > being blocked by the firewall? It would only show up when the server > has enough to send to fill a packet. > I'm the friend he was talking about. The very same thing happens when the firewall is disabled. I tried from 5.2.1 console and same thing happens. However, we were unable to reproduce the problem on any other servers. It only happens there. No, it's not an ssh bug. I wrote a connect-back snippet and the same thing happens when running commands with relatively big output (like dmesg). I tried logging from 5.2.1 and 5.3 to different servers behind his firewall, running also 5.3 and 5.2.1. The results are similar for all the possible combinations. A tcpdump shows that what actually happens is that packets won't reach me in spite of the fact that his firewall(router)'s tcpdump shows that he keeps sending them to me. Packets never reach me, but I am still able to send them, by pressing ENTER on the ssh console. Interesting fact is that I also get ACK packets for each of the packet I send by pressing ENTER. However this is useless, as the connection is already desynced and I receive no output. The connection times out in 5 minutes. I hope I didn't use a way too obfuscated English. PS: I personally suspect a hardware failure, probably an ethernet card, and he is going to check this out tomorrow. Regards, -- Alin-Adrian Anton Spintech Systems GPG keyID 0x1E2FFF2E (2963 0C11 1AF1 96F6 0030 6EE9 D323 639D 1E2F FF2E) gpg --keyserver pgp.mit.edu --recv-keys 1E2FFF2E From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 19:50:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8F6F16A4CE for ; Sun, 28 Nov 2004 19:50:13 +0000 (GMT) Received: from smtp202.mail.sc5.yahoo.com (smtp202.mail.sc5.yahoo.com [216.136.129.92]) by mx1.FreeBSD.org (Postfix) with SMTP id 8871343D2D for ; Sun, 28 Nov 2004 19:50:13 +0000 (GMT) (envelope-from ricardo_bsd@yahoo.com.br) Received: from unknown (HELO ?201.1.87.198?) (ricardo?bsd@201.1.87.198 with plain) by smtp202.mail.sc5.yahoo.com with SMTP; 28 Nov 2004 19:50:10 -0000 Message-ID: <41AA2BE9.4010309@yahoo.com.br> Date: Sun, 28 Nov 2004 17:50:01 -0200 From: Ricardo Alves dos Reis User-Agent: Mozilla Thunderbird 0.9 (X11/20041115) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/mixed; boundary="------------060809030508020201050000" Subject: [Fwd: Netgrafh ng_mppc, disabling node!!] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 19:50:14 -0000 This is a multi-part message in MIME format. --------------060809030508020201050000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit --------------060809030508020201050000 Content-Type: message/rfc822; name="Netgrafh ng_mppc, disabling node!!" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Netgrafh ng_mppc, disabling node!!" X-Account-Key: account1 X-Apparently-To: ricardo_bsd@yahoo.com.br via 66.163.169.177; Fri, 26 Nov 2004 14:24:53 -0800 Authentication-Results: mta102.mail.sc5.yahoo.com from=freebsd.org; domainkeys=neutral (no sig) X-Originating-IP: [216.136.204.119] Return-Path: Received: from 216.136.204.119 (EHLO mx2.freebsd.org) (216.136.204.119) by mta102.mail.sc5.yahoo.com with SMTP; Fri, 26 Nov 2004 14:21:07 -0800 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 4F3D858252; Fri, 26 Nov 2004 22:19:54 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5253016A515; Fri, 26 Nov 2004 22:19:47 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D58916A4CE for ; Fri, 26 Nov 2004 22:19:38 +0000 (GMT) Received: from smtp206.mail.sc5.yahoo.com (smtp206.mail.sc5.yahoo.com [216.136.129.96]) by mx1.FreeBSD.org (Postfix) with SMTP id DC98C43D58 for ; Fri, 26 Nov 2004 22:19:37 +0000 (GMT) (envelope-from ricardo_bsd@yahoo.com.br) Received: from unknown (HELO ?201.13.11.228?) (ricardo?bsd@201.13.11.228 with plain) by smtp206.mail.sc5.yahoo.com with SMTP; 26 Nov 2004 22:19:36 -0000 Message-ID: <41A7ABF2.5000909@yahoo.com.br> Date: Fri, 26 Nov 2004 20:19:30 -0200 From: Ricardo Alves dos Reis User-Agent: Mozilla Thunderbird 0.9 (X11/20041115) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Netgrafh ng_mppc, disabling node!! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: owner-freebsd-stable@freebsd.org Errors-To: owner-freebsd-stable@freebsd.org Hello All, I have in my work one vpn server (point to multi-point ) using MPD, AAA with FreeRadius and 5.3-STABLE, sometimes a look in dmesg this messages. "ng_mppc_decompress: too many (4095) packets dropped, disabling node 0xc34d4800!ng_mppc_decompress: too many (4004) packets dropped, disabling node 0xc33be700! " What is the problem? i using a generic kernel with a "HZ=2000 e POLLING" dmesg output ......................... Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #0: Wed Nov 24 00:50:30 BRDT 2004 root@monitor.epm.br:/usr/src/sys/i386/compile/GENERIC MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.66GHz (2658.10-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1073676288 (1023 MB) avail memory = 1041108992 (992 MB) ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 24 ioapic2: Assuming intbase of 48 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 0.1 (no driver attached) pcib1: at device 3.0 on pci0 pci2: on pcib1 pci2: at device 28.0 (no driver attached) pcib2: at device 29.0 on pci2 pci4: on pcib2 ahd0: port 0x4000-0x40ff,0x3800-0x38ff mem 0xfe8f0000-0xfe8f1fff irq 50 at device 7.0 on pci4 ahd0: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ahd1: port 0x3400-0x34ff,0x3000-0x30ff mem 0xfe9f0000-0xfe9f1fff irq 49 at device 7.1 on pci4 ahd1: [GIANT-LOCKED] aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs pci2: at device 30.0 (no driver attached) pcib3: at device 31.0 on pci2 pci3: on pcib3 em0: port 0x2040-0x207f mem 0xfe6c0000-0xfe6dffff irq 30 at device 7 .0 on pci3 em0: Ethernet address: 00:07:e9:06:4c:22 em0: Speed:N/A Duplex:N/A em1: port 0x2000-0x203f mem 0xfe6e0000-0xfe6fffff irq 31 at device 7 .1 on pci3 em1: Ethernet address: 00:07:e9:06:4c:23 em1: Speed:N/A Duplex:N/A pci0: at device 3.1 (no driver attached) pcib4: at device 30.0 on pci0 pci1: on pcib4 pci1: at device 12.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x3a0-0x3af,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) cpu0 on motherboard orm0: at iomem 0xc9800-0xcafff,0xc8000-0xc97ff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (irq) Timecounter "TSC" frequency 2658100184 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDROM at ata1-master UDMA33 Waiting 15 seconds for SCSI devices to settle ses0 at ahd1 bus 0 target 6 lun 0 ses0: Fixed Processor SCSI-2 device ses0: 3.300MB/s transfers ses0: SAF-TE Compliant Device da0 at ahd1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 35046MB (71775284 512 byte sectors: 255H 63S/T 4467C) Mounting root from ufs:/dev/da0s1a ---------------------- MPD.conf default: load p2p0 ... load p2p254 global: set bundle disable multilink set bundle yes bw-manage set bundle yes compression set iface enable proxy-arp set iface idle 3600 set iface session 28800 set iface enable tcpmssfix set ipcp dns xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx set ipcp nbns xxx.xxx.xxx.xxx set ipcp yes vjcomp set ipcp yes req-pri-dns set ipcp yes req-pri-nbns set link yes chap-msv2 chap-msv1 chap-md5 set link yes acfcomp protocomp set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e56 set ccp yes mpp-stateless set ecp yes des radius: set radius server xxx.xxx.xxx.xxx XXXXXX 1812 1813 set radius me xxx.xxx.xxx.xxx set bundle enable radius-auth set bundle enable radius-acct set bundle enable radius-fallback set ipcp enable radius-ip set radius retries 2 set radius timeout 2 p2p0: new -i ng0 p2p0 p2p0 set ipcp ranges 172.22.11.1/32 172.22.11.2/32 load global load radius .... p2p254: new -i ng254 p2p254 p2p254 set ipcp ranges 172.22.11.1/32 172.22.11.254/32 load global load radius Atenciosamente Ricardo A. Reis UNIFESP - DIS _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" --------------060809030508020201050000-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 21:21:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B939016A4CE for ; Sun, 28 Nov 2004 21:21:31 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87FA243D2D for ; Sun, 28 Nov 2004 21:21:31 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CYWU7-00019Q-3C for freebsd-current@freebsd.org; Sun, 28 Nov 2004 13:21:31 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16810.16730.688799.574061@ran.psg.com> Date: Sun, 28 Nov 2004 13:21:30 -0800 To: FreeBSD Current Subject: strangeness on new cvsup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 21:21:31 -0000 smp i386 cv supped Nov 28 19:26 gmt boot single abuser to do the installworld :/> mount -a WARNING: R/W mount of /usr/home denied. Filesystem is not clean - run fsck mount: /dev/twed0s1gW: AOperation not peRrmitted NING: /root was not properly dismounted as the system was taken down cleanly, i was not amused. so i went to boot the kernel.old, and it was not there! OK ls boot boot d defaults d kernel d modules mbr boot0 boot0sio boot boot1 boot2 cdboot loader loader.help loader.4th support.4th screen.4th frames.4th beastie.4th loader.rc pxeboot device.hints loader.conf loader.old d kernel.bad loader.conf.local loader.conf.local~ randy From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 21:27:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D66D16A4CE for ; Sun, 28 Nov 2004 21:27:56 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7DFF43D1F for ; Sun, 28 Nov 2004 21:27:55 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CYWaJ-00033V-Go; Sun, 28 Nov 2004 13:27:55 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16810.17115.9902.941797@ran.psg.com> Date: Sun, 28 Nov 2004 13:27:55 -0800 To: FreeBSD Current References: <16810.16744.991061.531924@ran.psg.com> Subject: Re: strangeness on new cvsup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 21:27:56 -0000 then, after install, this same one again as last week kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x104 fault code = supervisor read, page not present instruction pointer = 0x8:0xc04b408c stack pointer = 0x10:0xe6e2795c frame pointer = 0x10:0xe6e27970 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 485 (asterisk) [thread pid 485 tid 100178 ] Stopped at _mtx_lock_sleep+0x9c: cmpl $0x4,0x104(%ebx) db> trace Tracing pid 485 tid 100178 td 0xc2492c00 _mtx_lock_sleep(c21a206c,c2492c00,0,c2592edb,6ac) at _mtx_lock_sleep+0x9c _mtx_lock_flags(c21a206c,0,c2592edb,6ac,2) at _mtx_lock_flags+0x45 zt_clone(0,c23c1900,3,c2cdd100,c2492c00) at zt_clone+0x71 zt_timing_open(c23c1900,3,c2492c00,6,c2d17564) at zt_timing_open+0xbd ztopen(c23c1900,3,2000,c2492c00,e6e27a48) at ztopen+0x6c devfs_open(e6e27a6c,e6e27a64,c05f6199,180,c2492c00) at devfs_open+0x1d1 vn_open_cred(e6e27bd8,e6e27cd8,0,c1e91780,12) at vn_open_cred+0x3f1 vn_open(e6e27bd8,e6e27cd8,0,12,0) at vn_open+0x33 kern_open(c2492c00,284488b6,0,3,0) at kern_open+0x113 open(c2492c00,e6e27d14,c,c2492c00,6) at open+0x30 syscall(80d002f,80d002f,bf6e002f,80db000,0) at syscall+0x330 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, FreeBSD ELF32, open), eip = 0x2830b10f, esp = 0xbfbfe9ec, ebp = 0xbfbfea08 --- From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 21:45:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 578A816A4CE for ; Sun, 28 Nov 2004 21:45:34 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D93843D2F for ; Sun, 28 Nov 2004 21:45:34 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CYWrN-0008Ao-Oj for freebsd-current@freebsd.org; Sun, 28 Nov 2004 13:45:33 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16810.18173.356498.560172@ran.psg.com> Date: Sun, 28 Nov 2004 13:45:33 -0800 To: FreeBSD Current References: <16810.16744.991061.531924@ran.psg.com> <16810.17115.9902.941797@ran.psg.com> Subject: Re: strangeness on new cvsup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 21:45:34 -0000 and again, with a non-smp kernel kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x6c fault code = supervisor read, page not present instruction pointer = 0x8:0xc04e4cad stack pointer = 0x10:0xe6d9c924 frame pointer = 0x10:0xe6d9c928 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 482 (asterisk) [thread pid 482 tid 100144 ] Stopped at turnstile_setowner+0xd: movl 0x6c(%ecx),%eax db> trace Tracing pid 482 tid 100144 td 0xc2639600 turnstile_setowner(c215ab00,0,c04e4d6d,0,c2639600) at turnstile_setowner+0xd turnstile_wait(c2135c3c,0,c2135c3c,c2135bd0,e6d9c98c) at turnstile_wait+0x102 _mtx_lock_sleep(c2135c3c,c2639600,0,c2518edb,6ac) at _mtx_lock_sleep+0xb4 _mtx_lock_flags(c2135c3c,0,c2518edb,6ac,2) at _mtx_lock_flags+0x44 zt_clone(0,c242a800,3,c263c440,c2639600) at zt_clone+0x71 zt_timing_open(c242a800,3,c2639600,6,c2c15000) at zt_timing_open+0xbd ztopen(c242a800,3,2000,c2639600,e6d9ca48) at ztopen+0x6c devfs_open(e6d9ca6c,2f,280,180,c2639600) at devfs_open+0x1d1 vn_open_cred(e6d9cbd8,e6d9ccd8,0,c1e74d80,14) at vn_open_cred+0x3f1 vn_open(e6d9cbd8,e6d9ccd8,0,14,0) at vn_open+0x33 kern_open(c2639600,284488b6,0,3,0) at kern_open+0x113 open(c2639600,e6d9cd14,c,c2639600,6) at open+0x30 syscall(2f,2f,2f,80db000,0) at syscall+0x330 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, FreeBSD ELF32, open), eip = 0x2830b10f, esp = 0xbfbfe9ec, ebp = 0xbfbfea08 --- From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 22:28:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 392D616A4CE; Sun, 28 Nov 2004 22:28:08 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 1541543D31; Sun, 28 Nov 2004 22:28:07 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 28 Nov 2004 22:28:06 +0000 (GMT) Date: Sun, 28 Nov 2004 22:28:05 +0000 From: David Malone To: Alin-Adrian Anton Message-ID: <20041128222805.GA7142@walton.maths.tcd.ie> References: <41AA0043.5070109@gmail.com> <20041128180843.GA58546@pit.databus.com> <41AA192B.10802@spintech.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AA192B.10802@spintech.ro> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie cc: Barney Wolff cc: freebsd-hackers@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: ssh & select() problem on 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 22:28:08 -0000 On Sun, Nov 28, 2004 at 08:30:03PM +0200, Alin-Adrian Anton wrote: > A tcpdump shows that what actually happens is that packets won't reach > me in spite of the fact that his firewall(router)'s tcpdump shows that > he keeps sending them to me. Packets never reach me, but I am still able > to send them, by pressing ENTER on the ssh console. It sounds very like a path MTU discovery problem then. I guess what is happening is that large packets are being lost when sent along this particular network path. Whatever is dropping them should send a message saying "packet too big" and this will cause the machine to send smaller packets in future. However either this message is being dropped or not generated. You can probably test this idea by using "ping -s " or by setting the MTU on the interface on your machine "ifconfig interface mtu ". The real fix is to find out what's happened to the "packet too big" ICMP message. David. From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 01:20:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79E3916A4CE for ; Mon, 29 Nov 2004 01:20:37 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 208B343D2F for ; Mon, 29 Nov 2004 01:20:22 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAT1JIZg011608 for ; Mon, 29 Nov 2004 11:49:18 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Mon, 29 Nov 2004 11:50:13 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAT11HQ06409 for ; Mon, 29 Nov 2004 11:31:17 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id X5H5LKK1; Mon, 29 Nov 2004 11:30:59 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAT11UwF009223 for ; Mon, 29 Nov 2004 11:31:30 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAT11UxD009222 for freebsd-current@freebsd.org; Mon, 29 Nov 2004 11:31:30 +1030 (CST) (envelope-from wilkinsa) Date: Mon, 29 Nov 2004 11:31:30 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041129010130.GB8939@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: ata vs atapicam ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 01:20:37 -0000 Hi all, Question: Now that we can manage ATA devs via the CAM layer [atapicam(4)], I would like to ask: what is the point and benefit of doing so ? - aW From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 01:36:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED20F16A4CE for ; Mon, 29 Nov 2004 01:36:04 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85FC843D39 for ; Mon, 29 Nov 2004 01:36:04 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAT1dNLI098571; Sun, 28 Nov 2004 18:39:23 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AA7D1E.2090806@freebsd.org> Date: Sun, 28 Nov 2004 18:36:30 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wilkinson, Alex" References: <20041129010130.GB8939@squash.dsto.defence.gov.au> In-Reply-To: <20041129010130.GB8939@squash.dsto.defence.gov.au> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: ata vs atapicam ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 01:36:05 -0000 Wilkinson, Alex wrote: > Hi all, > > Question: Now that we can manage ATA devs via the CAM layer > [atapicam(4)], I would like to ask: what is the point > and benefit of doing so ? > > - aW > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" ATA devices cannot be managed via CAM, only ATAPI devices. However, this is useful for the plethora of applications that want to talk to CDROMs via SCSI commands (and the MMC part of the ATAPI spec is just striped-down SCSI anyways). Scott From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 02:48:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 836CD16A4CE for ; Mon, 29 Nov 2004 02:48:46 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 843AA43D54 for ; Mon, 29 Nov 2004 02:48:45 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 21129 invoked by uid 65534); 29 Nov 2004 02:48:43 -0000 Received: from pD95D8F14.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.93.143.20) by mail.gmx.net (mp002) with SMTP; 29 Nov 2004 03:48:43 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iAT2mXMo010663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 29 Nov 2004 03:48:36 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) Message-ID: <41AA8E00.2050401@gmx.net> Date: Mon, 29 Nov 2004 03:48:32 +0100 From: Michael Nottebrock User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en, de-de MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Subject: fsck shortcomings X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 02:48:46 -0000 I recently had a filesystem go bad on me in such a way that it was recognized way bigger than it actually was, causing fsck to fail while trying to allocate and equally astronomic amount of memory (and my machine already had 1 Gig of mem + 2 Gig swap available). I just newfs'd and I'm now in the process of restoring data, however, I googled a bit on this and it seems that this kind of fs corruption is occurring quite often, in particular due to power failures. Is there really no way that fsck could be made smarter about dealing with seemingly huge filesystems? Also, what kind of memory would be required to fsck a _real_ 11TB filesystem? -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 03:14:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F13A16A4CE for ; Mon, 29 Nov 2004 03:14:57 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F2AB43D45 for ; Mon, 29 Nov 2004 03:14:56 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAT3IJ4M098933; Sun, 28 Nov 2004 20:18:19 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AA944A.5090109@freebsd.org> Date: Sun, 28 Nov 2004 20:15:22 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Nottebrock References: <41AA8E00.2050401@gmx.net> In-Reply-To: <41AA8E00.2050401@gmx.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: fsck shortcomings X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 03:14:57 -0000 Michael Nottebrock wrote: > I recently had a filesystem go bad on me in such a way that it was > recognized way bigger than it actually was, causing fsck to fail while > trying to allocate and equally astronomic amount of memory (and my > machine already had 1 Gig of mem + 2 Gig swap available). > I just newfs'd and I'm now in the process of restoring data, however, I > googled a bit on this and it seems that this kind of fs corruption is > occurring quite often, in particular due to power failures. Yes, very troubling. You said that the alternate superblocks didn't help? > > Is there really no way that fsck could be made smarter about dealing > with seemingly huge filesystems? Also, what kind of memory would be > required to fsck a _real_ 11TB filesystem? > More than you can address in 32 bits. Reducing the RAM footprint of fsck_ufs is something that desperately needs to be done, especially since it's now easy to trash crashdumps that are saved in swap because fsck is consuming so much memory. Scott From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 03:31:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35A3916A4CF for ; Mon, 29 Nov 2004 03:31:29 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 3C1C443D48 for ; Mon, 29 Nov 2004 03:31:28 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 14491 invoked by uid 65534); 29 Nov 2004 03:31:27 -0000 Received: from pD95D8F14.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.93.143.20) by mail.gmx.net (mp012) with SMTP; 29 Nov 2004 04:31:27 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iAT3VMMo011439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Nov 2004 04:31:24 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) Message-ID: <41AA9808.4050903@gmx.net> Date: Mon, 29 Nov 2004 04:31:20 +0100 From: Michael Nottebrock User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en, de-de MIME-Version: 1.0 To: Scott Long References: <41AA8E00.2050401@gmx.net> <41AA944A.5090109@freebsd.org> In-Reply-To: <41AA944A.5090109@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new cc: freebsd-current@freebsd.org Subject: Re: fsck shortcomings X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 03:31:29 -0000 Scott Long wrote: > Michael Nottebrock wrote: > >> I recently had a filesystem go bad on me in such a way that it was >> recognized way bigger than it actually was, causing fsck to fail while >> trying to allocate and equally astronomic amount of memory (and my >> machine already had 1 Gig of mem + 2 Gig swap available). >> I just newfs'd and I'm now in the process of restoring data, however, >> I googled a bit on this and it seems that this kind of fs corruption >> is occurring quite often, in particular due to power failures. > > > Yes, very troubling. You said that the alternate superblocks didn't > help? Yes, although that might have been bad luck - I didn't realise something was wrong with the fs right away. Since I had background fsck enabled, the filesystem got mounted anyway, but the system hung at executing dhclient, so I fiddled around with disabling acpi/apic & other stuff, assuming that something was wrong with the NIC or the NIC driver... I guess the alternate superblock might have worked if I had recognized the problem at once and tried fsck_ffs -b right away instead of mounting the bad fs over and over while trying to fix the NIC. -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 05:43:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D899316A4CE; Mon, 29 Nov 2004 05:43:45 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4531343D67; Mon, 29 Nov 2004 05:43:45 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAT5hiPE001403; Mon, 29 Nov 2004 00:43:44 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iAT5hiNV071585; Mon, 29 Nov 2004 00:43:44 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 901EA7306E; Mon, 29 Nov 2004 00:43:43 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041129054343.901EA7306E@freebsd-current.sentex.ca> Date: Mon, 29 Nov 2004 00:43:43 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 05:43:46 -0000 TB --- 2004-11-29 04:15:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-29 04:15:01 - starting CURRENT tinderbox run for alpha/alpha TB --- 2004-11-29 04:15:01 - checking out the source tree TB --- 2004-11-29 04:15:01 - cd /home/tinderbox/CURRENT/alpha/alpha TB --- 2004-11-29 04:15:01 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-29 04:21:47 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-29 04:21:47 - cd /home/tinderbox/CURRENT/alpha/alpha/src TB --- 2004-11-29 04:21:47 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-29 05:36:49 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-29 05:36:49 - cd /home/tinderbox/CURRENT/alpha/alpha/src TB --- 2004-11-29 05:36:49 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Nov 29 05:36:50 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/alpha/alpha/src/sys -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/altq -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/pf -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /tinderbox/CURRENT/alpha/alpha/src/sys/kern/vfs_cache.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/alpha/alpha/src/sys -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/altq -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/pf -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /tinderbox/CURRENT/alpha/alpha/src/sys/kern/vfs_cluster.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/alpha/alpha/src/sys -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/altq -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/pf -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /tinderbox/CURRENT/alpha/alpha/src/sys/kern/vfs_default.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/alpha/alpha/src/sys -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/altq -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/pf -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /tinderbox/CURRENT/alpha/alpha/src/sys/kern/vfs_export.c /tinderbox/CURRENT/alpha/alpha/src/sys/kern/vfs_export.c: In function `vfs_hang_addrlist': /tinderbox/CURRENT/alpha/alpha/src/sys/kern/vfs_export.c:132: error: `SA_MAX' undeclared (first use in this function) /tinderbox/CURRENT/alpha/alpha/src/sys/kern/vfs_export.c:132: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/alpha/alpha/src/sys/kern/vfs_export.c:132: error: for each function it appears in.) *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/obj/alpha/tinderbox/CURRENT/alpha/alpha/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. TB --- 2004-11-29 05:43:43 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-29 05:43:43 - ERROR: failed to build generic kernel TB --- 2004-11-29 05:43:43 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 06:06:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3D9016A4CE for ; Mon, 29 Nov 2004 06:06:00 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E0F443D39 for ; Mon, 29 Nov 2004 06:06:00 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 7FF0D72DF8; Sun, 28 Nov 2004 22:06:00 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 7B2DE72DCB; Sun, 28 Nov 2004 22:06:00 -0800 (PST) Date: Sun, 28 Nov 2004 22:06:00 -0800 (PST) From: Doug White To: Randy Bush In-Reply-To: <16805.38319.825546.497936@ran.psg.com> Message-ID: <20041128220455.F40277@carver.gumbysoft.com> References: <20041123182254.GB10721@ninthgate.net> <20041124232820.J2006@carver.gumbysoft.com> <16805.38319.825546.497936@ran.psg.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 06:06:00 -0000 On Thu, 25 Nov 2004, Randy Bush wrote: > > A backtrace would be interesting to look at. > > indeed. but i was lucky to get the screen scrape before the > beastie wiped the screen as it auto-rebooted. > > > Looks like you just need to set 'dumpdev' in rc.conf. What is your boot > > device and swap partition(s)? > > # grep dump /etc/rc.conf > dumpdev="/dev/twed0s1b" # Device name to crashdump to (or NO). > dumpdir="/var/crash" # Directory where crash dumps are to be stored Hm, this should be getting set; the twe driver supports crashdumps. What happens if you run 'dumpon /dev/twed0s1b' manually? > > if you turn on session logging in your comm program > > comm program? it's a cisco 2511 term serv being used as a > craft port octopus for 16 devices What program are you using to connect to the 2511 to view the console on the target? Telnet? Real terminal? :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 06:20:08 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 980A116A4CE for ; Mon, 29 Nov 2004 06:20:08 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8258243D60 for ; Mon, 29 Nov 2004 06:20:08 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 7536672DF8; Sun, 28 Nov 2004 22:20:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 6F70172DCB; Sun, 28 Nov 2004 22:20:08 -0800 (PST) Date: Sun, 28 Nov 2004 22:20:08 -0800 (PST) From: Doug White To: Aaron Wallace In-Reply-To: <41A60006.3060708@uiuc.edu> Message-ID: <20041128220740.O40277@carver.gumbysoft.com> References: <41A60006.3060708@uiuc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: bug report: AMD64, 5.3, sym driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 06:20:08 -0000 On Thu, 25 Nov 2004, Aaron Wallace wrote: > I believe that I've found a bug with the sym driver in AMD64. I don't > have this problem with 5.3 under i386. I wasn't able to submit this > report via web because the anti-spam code wasn't being recognized. > > The problem occurs during boot up / driver detect. I get the following > messages in bootup which I've manually copied: > > sym0: <810a> port 0x9000-0x90ff mem 0xea094000-0xea0940ff irq 12 at > device 7.0 on pci1 > __sym_calloc2: failed to allocate HCB[4288] > device_attach: sym0 attach returned 6 Oh yuck. The sym driver has its own memory allocator that caps allocations at 1 page. Since PAGE_SIZE on amd64 is 4k, and the 64 bit resizing of the structs puts the size over 4k, the struct will need some pruning. (PAGE_SIZE is 8k on sparc64 (and alpha?) which is why this hasn't been caught previously.) You will have to use a different controller until the driver can be fixed. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 06:24:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FB0816A4CE for ; Mon, 29 Nov 2004 06:24:40 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59B1B43D45 for ; Mon, 29 Nov 2004 06:24:38 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 4CAF872DF8; Sun, 28 Nov 2004 22:24:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 4A65572DD4; Sun, 28 Nov 2004 22:24:38 -0800 (PST) Date: Sun, 28 Nov 2004 22:24:38 -0800 (PST) From: Doug White To: Randy Bush In-Reply-To: <16807.10942.710868.490640@ran.psg.com> Message-ID: <20041128222418.R40277@carver.gumbysoft.com> References: <16807.10942.710868.490640@ran.psg.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD Current Subject: Re: crash on just cvsupped build X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 06:24:40 -0000 On Fri, 26 Nov 2004, Randy Bush wrote: > 6-current just cvsupped crashes within five mins > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x104 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc04b417c > stack pointer = 0x10:0xe6d9c95c > frame pointer = 0x10:0xe6d9c970 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 486 (asterisk) > [thread pid 486 tid 100145 ] > Stopped at _mtx_lock_sleep+0x9c: cmpl $0x4,0x104(%ebx) > db> trace > Tracing pid 486 tid 100145 td 0xc2427780 > _mtx_lock_sleep(c237e45c,c2427780,0,c25aaedb,6ac) at _mtx_lock_sleep+0x9c > _mtx_lock_flags(c237e45c,0,c25aaedb,6ac,2) at _mtx_lock_flags+0x45 > zt_clone(0,c23cce00,3,c1f92ac0,c2427780) at zt_clone+0x71 > zt_timing_open(c23cce00,3,c2427780,c04e72b5,e6d9ca04) at zt_timing_open+0xbd > ztopen(c23cce00,3,2000,c2427780,e6d9ca48) at ztopen+0x6c Whats the 'zt' device? Its not a shipping FreeBSD driver. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 07:24:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0097C16A4CE; Mon, 29 Nov 2004 07:24:32 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8345F43D5C; Mon, 29 Nov 2004 07:24:31 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAT7OUIj014633; Mon, 29 Nov 2004 02:24:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iAT7OUao015182; Mon, 29 Nov 2004 02:24:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A666E7306E; Mon, 29 Nov 2004 02:24:30 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041129072430.A666E7306E@freebsd-current.sentex.ca> Date: Mon, 29 Nov 2004 02:24:30 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 07:24:32 -0000 TB --- 2004-11-29 05:43:43 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-29 05:43:43 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-11-29 05:43:43 - checking out the source tree TB --- 2004-11-29 05:43:43 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-11-29 05:43:43 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-29 06:01:31 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-29 06:01:31 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-29 06:01:31 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cp loader.sym loader.bin strip -R .comment -R .note loader.bin btxld -v -f aout -e 0x200000 -o loader -l /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/../btx/btxldr/btxldr -b /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/../btx/btx/btx loader.bin kernel: ver=1.01 size=780 load=9000 entry=9010 map=16M pgctl=0:33 client: fmt=elf size=39530 text=32cbc data=53cc bss=6114 entry=0 output: fmt=aout size=3c000 text=1000 data=3a000 org=200000 entry=200000 cat /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/../../common/help.common /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/help.i386 | awk -f /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/../../common/merge_help.awk > loader.help make: don't know how to make /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/loader.rc. Stop *** Error code 2 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/boot. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-11-29 07:24:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-29 07:24:30 - ERROR: failed to build world TB --- 2004-11-29 07:24:30 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 07:41:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78A9016A4CE for ; Mon, 29 Nov 2004 07:41:50 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2663043D4C for ; Mon, 29 Nov 2004 07:41:50 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by rproxy.gmail.com with SMTP id a41so369913rng for ; Sun, 28 Nov 2004 23:41:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=DPKuTde7Q3uQZYaKpvrMgJ1OCkkuxlNWcEvh6cdQ1fD0/Gx+QppjAn/mk9ACUc4Auyc8gzLXsQh9a6mzOoKHyB1YiEtjyfFJzq3DnnyuMAsKVgmbxEdFpEuHZ5bKcTZ4AkeGNUPjBBKYFiBu2ghaYTaeD1imQ26B/M7HL5zZzwQ= Received: by 10.38.149.29 with SMTP id w29mr1446368rnd; Sun, 28 Nov 2004 23:41:47 -0800 (PST) Received: by 10.38.13.6 with HTTP; Sun, 28 Nov 2004 23:41:47 -0800 (PST) Message-ID: <84dead72041128234147af1478@mail.gmail.com> Date: Mon, 29 Nov 2004 13:11:47 +0530 From: Joseph Koshy To: freebsd-current Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: -current broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 07:41:50 -0000 .../src/sys/kern/vfs_export.c: In function `vfs_hang_addrlist': .../src/sys/kern/vfs_export.c:132: error: `SA_MAX' undeclared (first use in this function) .../src/sys/kern/vfs_export.c:132: error: (Each undeclared identifier is reported only once .../src/sys/kern/vfs_export.c:132: error: for each function it appears in.) From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 08:22:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6607E16A4CE for ; Mon, 29 Nov 2004 08:22:05 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33AA243D5C for ; Mon, 29 Nov 2004 08:22:05 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E96A4512B1; Mon, 29 Nov 2004 00:27:02 -0800 (PST) Date: Mon, 29 Nov 2004 00:27:02 -0800 From: Kris Kennaway To: Joseph Koshy Message-ID: <20041129082702.GA35251@xor.obsecurity.org> References: <84dead72041128234147af1478@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <84dead72041128234147af1478@mail.gmail.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-current Subject: Re: -current broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 08:22:05 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Nov 29, 2004 at 01:11:47PM +0530, Joseph Koshy wrote: > .../src/sys/kern/vfs_export.c: In function `vfs_hang_addrlist': > .../src/sys/kern/vfs_export.c:132: error: `SA_MAX' undeclared (first > use in this function) > .../src/sys/kern/vfs_export.c:132: error: (Each undeclared identifier > is reported only once > .../src/sys/kern/vfs_export.c:132: error: for each function it appears in.) Yeah; see the tinderbox emails on this list. Kris --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBqt1WWry0BWjoQKURApJbAJoDHOPqYhE1vv+Q8bKtqIhwWd/NugCcCCLo VPk8MFpT0HKbDDv/NkOlRv8= =D1q1 -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 08:37:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DAC616A4CE; Mon, 29 Nov 2004 08:37:39 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A5C743D4C; Mon, 29 Nov 2004 08:37:39 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAT8bcX5025968; Mon, 29 Nov 2004 03:37:38 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iAT8bchr029616; Mon, 29 Nov 2004 03:37:38 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id DB7FB7306E; Mon, 29 Nov 2004 03:37:37 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041129083737.DB7FB7306E@freebsd-current.sentex.ca> Date: Mon, 29 Nov 2004 03:37:37 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 08:37:39 -0000 TB --- 2004-11-29 07:24:30 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-29 07:24:30 - starting CURRENT tinderbox run for i386/i386 TB --- 2004-11-29 07:24:30 - checking out the source tree TB --- 2004-11-29 07:24:30 - cd /home/tinderbox/CURRENT/i386/i386 TB --- 2004-11-29 07:24:30 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-29 07:30:55 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-29 07:30:55 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-11-29 07:30:55 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cp loader.sym loader.bin strip -R .comment -R .note loader.bin btxld -v -f aout -e 0x200000 -o loader -l /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/boot/i386/loader/../btx/btxldr/btxldr -b /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/boot/i386/loader/../btx/btx/btx loader.bin kernel: ver=1.01 size=780 load=9000 entry=9010 map=16M pgctl=0:2b client: fmt=elf size=31530 text=2ab3c data=53cc bss=6114 entry=0 output: fmt=aout size=34000 text=1000 data=32000 org=200000 entry=200000 cat /tinderbox/CURRENT/i386/i386/src/sys/boot/i386/loader/../../common/help.common /tinderbox/CURRENT/i386/i386/src/sys/boot/i386/loader/help.i386 | awk -f /tinderbox/CURRENT/i386/i386/src/sys/boot/i386/loader/../../common/merge_help.awk > loader.help make: don't know how to make /tinderbox/CURRENT/i386/i386/src/sys/boot/i386/loader/loader.rc. Stop *** Error code 2 Stop in /tinderbox/CURRENT/i386/i386/src/sys/boot/i386. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/boot. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. TB --- 2004-11-29 08:37:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-29 08:37:37 - ERROR: failed to build world TB --- 2004-11-29 08:37:37 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 09:25:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D17816A4CE; Mon, 29 Nov 2004 09:25:13 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55E5D43D48; Mon, 29 Nov 2004 09:25:12 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAT9PAFO064889; Mon, 29 Nov 2004 11:25:10 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 38682-17; Mon, 29 Nov 2004 11:25:09 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAT9P9G1064882 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Nov 2004 11:25:09 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAT9PB4i080848; Mon, 29 Nov 2004 11:25:11 +0200 (EET) (envelope-from ru) Date: Mon, 29 Nov 2004 11:25:11 +0200 From: Ruslan Ermilov To: Poul-Henning Kamp Message-ID: <20041129092510.GA80748@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="f2QGlHpHGjS2mn6Y" Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: current@FreeBSD.org Subject: [PATCH] mount(8) broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 09:25:13 -0000 --f2QGlHpHGjS2mn6Y Content-Type: multipart/mixed; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Poul-Henning, Your recent change to sys/sys/mount.h that made MNT_NODEV zero broke mount(8) -- the "mount" command doesn't display mount status anymore. The attached patch should fix it. Other instances of MNT_NODEV that need addressing: contrib/smbfs/mount_smbfs/mntopts.h lib/libc/sys/statfs.2 lib/libc/sys/mount.2 share/man/man9/vfs_mount.9 sys/compat/linprocfs/linprocfs.c sys/sys/mount.h Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: mount/mntopts.h =================================================================== RCS file: /home/ncvs/src/sbin/mount/mntopts.h,v retrieving revision 1.22 diff -u -p -r1.22 mntopts.h --- mount/mntopts.h 25 Nov 2004 13:31:46 -0000 1.22 +++ mount/mntopts.h 28 Nov 2004 21:21:16 -0000 @@ -40,7 +40,6 @@ struct mntopt { /* User-visible MNT_ flags. */ #define MOPT_ASYNC { "async", 0, MNT_ASYNC, 0 } #define MOPT_NOATIME { "atime", 1, MNT_NOATIME, 0 } -#define MOPT_NODEV { "dev", 1, MNT_NODEV, 0 } #define MOPT_NOEXEC { "exec", 1, MNT_NOEXEC, 0 } #define MOPT_NOSUID { "suid", 1, MNT_NOSUID, 0 } #define MOPT_NOSYMFOLLOW { "symfollow", 1, MNT_NOSYMFOLLOW, 0 } @@ -76,7 +75,6 @@ struct mntopt { MOPT_GROUPQUOTA, \ MOPT_FSTAB_COMPAT, \ MOPT_NOATIME, \ - MOPT_NODEV, \ MOPT_NOEXEC, \ MOPT_SUIDDIR, /* must be before MOPT_NOSUID */ \ MOPT_NOSUID, \ Index: mount/mount.8 =================================================================== RCS file: /home/ncvs/src/sbin/mount/mount.8,v retrieving revision 1.68 diff -u -p -r1.68 mount.8 --- mount/mount.8 17 May 2004 08:35:42 -0000 1.68 +++ mount/mount.8 28 Nov 2004 21:21:54 -0000 @@ -28,7 +28,7 @@ .\" @(#)mount.8 8.8 (Berkeley) 6/16/94 .\" $FreeBSD: src/sbin/mount/mount.8,v 1.68 2004/05/17 08:35:42 ru Exp $ .\" -.Dd April 7, 2003 +.Dd November 26, 2004 .Dt MOUNT 8 .Os .Sh NAME @@ -177,12 +177,6 @@ flag. Disable read clustering. .It Cm noclusterw Disable write clustering. -.It Cm nodev -Do not interpret character or block special devices on the file system. -This option is useful for a server that has file systems containing -special devices for architectures other than its own. -This option is set automatically when the user does not have super-user -privileges. .It Cm noexec Do not allow execution of any binaries on the mounted file system. This option is useful for a server that has file systems containing Index: mount/mount.c =================================================================== RCS file: /home/ncvs/src/sbin/mount/mount.c,v retrieving revision 1.66 diff -u -p -r1.66 mount.c --- mount/mount.c 26 Apr 2004 15:13:45 -0000 1.66 +++ mount/mount.c 28 Nov 2004 21:18:54 -0000 @@ -93,7 +93,6 @@ static struct opt { { MNT_EXPORTED, "NFS exported" }, { MNT_LOCAL, "local" }, { MNT_NOATIME, "noatime" }, - { MNT_NODEV, "nodev" }, { MNT_NOEXEC, "noexec" }, { MNT_NOSUID, "nosuid" }, { MNT_NOSYMFOLLOW, "nosymfollow" }, @@ -750,7 +749,6 @@ flags2opts(flags) if (flags & MNT_SYNCHRONOUS) res = catopt(res, "sync"); if (flags & MNT_NOEXEC) res = catopt(res, "noexec"); if (flags & MNT_NOSUID) res = catopt(res, "nosuid"); - if (flags & MNT_NODEV) res = catopt(res, "nodev"); if (flags & MNT_UNION) res = catopt(res, "union"); if (flags & MNT_ASYNC) res = catopt(res, "async"); if (flags & MNT_NOATIME) res = catopt(res, "noatime"); Index: mount_std/mount_std.8 =================================================================== RCS file: /home/ncvs/src/sbin/mount_std/mount_std.8,v retrieving revision 1.22 diff -u -p -r1.22 mount_std.8 --- mount_std/mount_std.8 2 Jul 2004 21:45:04 -0000 1.22 +++ mount_std/mount_std.8 29 Nov 2004 09:12:04 -0000 @@ -32,7 +32,7 @@ .\" .\" $FreeBSD: src/sbin/mount_std/mount_std.8,v 1.22 2004/07/02 21:45:04 ru Exp $ .\" -.Dd May 13, 1996 +.Dd November 26, 2004 .Dt MOUNT_STD 8 .Os .Sh NAME @@ -70,7 +70,6 @@ accepts only the standard options .Dq ro , .Dq rw , -.Dq nodev , .Dq noexec , .Dq nosuid , and --pWyiEgJYm5f9v55/-- --f2QGlHpHGjS2mn6Y Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBqur2qRfpzJluFF4RAif4AJ444FY0g+wCKYwPcOo77E8begZG/QCfURc/ R2dY8qcpORy8q2BeXP23XWU= =01lk -----END PGP SIGNATURE----- --f2QGlHpHGjS2mn6Y-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 09:26:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAA6A16A4CE; Mon, 29 Nov 2004 09:26:51 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2686943D64; Mon, 29 Nov 2004 09:26:51 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAT9QoZc028132; Mon, 29 Nov 2004 10:26:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Ruslan Ermilov From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 29 Nov 2004 11:25:11 +0200." <20041129092510.GA80748@ip.net.ua> Date: Mon, 29 Nov 2004 10:26:50 +0100 Message-ID: <28131.1101720410@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@FreeBSD.org Subject: Re: [PATCH] mount(8) broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 09:26:52 -0000 By all means commit it! Poul-Henning In message <20041129092510.GA80748@ip.net.ua>, Ruslan Ermilov writes: > >--f2QGlHpHGjS2mn6Y >Content-Type: multipart/mixed; boundary="pWyiEgJYm5f9v55/" >Content-Disposition: inline > > >--pWyiEgJYm5f9v55/ >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >Hi Poul-Henning, > >Your recent change to sys/sys/mount.h that made MNT_NODEV zero >broke mount(8) -- the "mount" command doesn't display mount >status anymore. The attached patch should fix it. > >Other instances of MNT_NODEV that need addressing: > > contrib/smbfs/mount_smbfs/mntopts.h > lib/libc/sys/statfs.2 > lib/libc/sys/mount.2 > share/man/man9/vfs_mount.9 > sys/compat/linprocfs/linprocfs.c > sys/sys/mount.h > > >Cheers, >--=20 >Ruslan Ermilov >ru@FreeBSD.org >FreeBSD committer > >--pWyiEgJYm5f9v55/ >Content-Type: text/plain; charset=us-ascii >Content-Disposition: attachment; filename=p > >Index: mount/mntopts.h >=================================================================== >RCS file: /home/ncvs/src/sbin/mount/mntopts.h,v >retrieving revision 1.22 >diff -u -p -r1.22 mntopts.h >--- mount/mntopts.h 25 Nov 2004 13:31:46 -0000 1.22 >+++ mount/mntopts.h 28 Nov 2004 21:21:16 -0000 >@@ -40,7 +40,6 @@ struct mntopt { > /* User-visible MNT_ flags. */ > #define MOPT_ASYNC { "async", 0, MNT_ASYNC, 0 } > #define MOPT_NOATIME { "atime", 1, MNT_NOATIME, 0 } >-#define MOPT_NODEV { "dev", 1, MNT_NODEV, 0 } > #define MOPT_NOEXEC { "exec", 1, MNT_NOEXEC, 0 } > #define MOPT_NOSUID { "suid", 1, MNT_NOSUID, 0 } > #define MOPT_NOSYMFOLLOW { "symfollow", 1, MNT_NOSYMFOLLOW, 0 } >@@ -76,7 +75,6 @@ struct mntopt { > MOPT_GROUPQUOTA, \ > MOPT_FSTAB_COMPAT, \ > MOPT_NOATIME, \ >- MOPT_NODEV, \ > MOPT_NOEXEC, \ > MOPT_SUIDDIR, /* must be before MOPT_NOSUID */ \ > MOPT_NOSUID, \ >Index: mount/mount.8 >=================================================================== >RCS file: /home/ncvs/src/sbin/mount/mount.8,v >retrieving revision 1.68 >diff -u -p -r1.68 mount.8 >--- mount/mount.8 17 May 2004 08:35:42 -0000 1.68 >+++ mount/mount.8 28 Nov 2004 21:21:54 -0000 >@@ -28,7 +28,7 @@ > .\" @(#)mount.8 8.8 (Berkeley) 6/16/94 > .\" $FreeBSD: src/sbin/mount/mount.8,v 1.68 2004/05/17 08:35:42 ru Exp $ > .\" >-.Dd April 7, 2003 >+.Dd November 26, 2004 > .Dt MOUNT 8 > .Os > .Sh NAME >@@ -177,12 +177,6 @@ flag. > Disable read clustering. > .It Cm noclusterw > Disable write clustering. >-.It Cm nodev >-Do not interpret character or block special devices on the file system. >-This option is useful for a server that has file systems containing >-special devices for architectures other than its own. >-This option is set automatically when the user does not have super-user >-privileges. > .It Cm noexec > Do not allow execution of any binaries on the mounted file system. > This option is useful for a server that has file systems containing >Index: mount/mount.c >=================================================================== >RCS file: /home/ncvs/src/sbin/mount/mount.c,v >retrieving revision 1.66 >diff -u -p -r1.66 mount.c >--- mount/mount.c 26 Apr 2004 15:13:45 -0000 1.66 >+++ mount/mount.c 28 Nov 2004 21:18:54 -0000 >@@ -93,7 +93,6 @@ static struct opt { > { MNT_EXPORTED, "NFS exported" }, > { MNT_LOCAL, "local" }, > { MNT_NOATIME, "noatime" }, >- { MNT_NODEV, "nodev" }, > { MNT_NOEXEC, "noexec" }, > { MNT_NOSUID, "nosuid" }, > { MNT_NOSYMFOLLOW, "nosymfollow" }, >@@ -750,7 +749,6 @@ flags2opts(flags) > if (flags & MNT_SYNCHRONOUS) res = catopt(res, "sync"); > if (flags & MNT_NOEXEC) res = catopt(res, "noexec"); > if (flags & MNT_NOSUID) res = catopt(res, "nosuid"); >- if (flags & MNT_NODEV) res = catopt(res, "nodev"); > if (flags & MNT_UNION) res = catopt(res, "union"); > if (flags & MNT_ASYNC) res = catopt(res, "async"); > if (flags & MNT_NOATIME) res = catopt(res, "noatime"); >Index: mount_std/mount_std.8 >=================================================================== >RCS file: /home/ncvs/src/sbin/mount_std/mount_std.8,v >retrieving revision 1.22 >diff -u -p -r1.22 mount_std.8 >--- mount_std/mount_std.8 2 Jul 2004 21:45:04 -0000 1.22 >+++ mount_std/mount_std.8 29 Nov 2004 09:12:04 -0000 >@@ -32,7 +32,7 @@ > .\" > .\" $FreeBSD: src/sbin/mount_std/mount_std.8,v 1.22 2004/07/02 21:45:04 ru Exp $ > .\" >-.Dd May 13, 1996 >+.Dd November 26, 2004 > .Dt MOUNT_STD 8 > .Os > .Sh NAME >@@ -70,7 +70,6 @@ accepts only the standard > options > .Dq ro , > .Dq rw , >-.Dq nodev , > .Dq noexec , > .Dq nosuid , > and > >--pWyiEgJYm5f9v55/-- > >--f2QGlHpHGjS2mn6Y >Content-Type: application/pgp-signature >Content-Disposition: inline > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.2.6 (FreeBSD) > >iD8DBQFBqur2qRfpzJluFF4RAif4AJ444FY0g+wCKYwPcOo77E8begZG/QCfURc/ >R2dY8qcpORy8q2BeXP23XWU= >=01lk >-----END PGP SIGNATURE----- > >--f2QGlHpHGjS2mn6Y-- > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 09:32:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2663416A4CE; Mon, 29 Nov 2004 09:32:35 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CDFE43D1F; Mon, 29 Nov 2004 09:32:34 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAT9WXRQ065543; Mon, 29 Nov 2004 11:32:33 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 39899-09; Mon, 29 Nov 2004 11:32:32 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iAT9WWPA065540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Nov 2004 11:32:32 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAT9WYXf080971; Mon, 29 Nov 2004 11:32:34 +0200 (EET) (envelope-from ru) Date: Mon, 29 Nov 2004 11:32:34 +0200 From: Ruslan Ermilov To: Scott Long Message-ID: <20041129093233.GB80748@ip.net.ua> References: <20041129072430.A666E7306E@freebsd-current.sentex.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="32u276st3Jlj2kUU" Content-Disposition: inline In-Reply-To: <20041129072430.A666E7306E@freebsd-current.sentex.ca> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: current@FreeBSD.org Subject: Re: [current tinderbox] failure on amd64/amd64 [FIXED] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 09:32:35 -0000 --32u276st3Jlj2kUU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Scott, On Mon, Nov 29, 2004 at 02:24:30AM -0500, FreeBSD Tinderbox wrote: > >>> stage 4.4: building everything > [...] > cp loader.sym loader.bin > strip -R .comment -R .note loader.bin > btxld -v -f aout -e 0x200000 -o loader -l /tinderbox/CURRENT/amd64/amd64/= obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/../btx/btx= ldr/btxldr -b /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/a= md64/amd64/src/sys/boot/i386/loader/../btx/btx/btx loader.bin > kernel: ver=3D1.01 size=3D780 load=3D9000 entry=3D9010 map=3D16M pgctl=3D= 0:33 > client: fmt=3Delf size=3D39530 text=3D32cbc data=3D53cc bss=3D6114 entry= =3D0 > output: fmt=3Daout size=3D3c000 text=3D1000 data=3D3a000 org=3D200000 ent= ry=3D200000 > cat /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/../../common/= help.common /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/help.i3= 86 | awk -f /tinderbox/CURRENT/amd64/amd64/src/sys/boot/i386/loader/../../c= ommon/merge_help.awk > loader.help > make: don't know how to make /tinderbox/CURRENT/amd64/amd64/src/sys/boot/= i386/loader/loader.rc. Stop > *** Error code 2 >=20 I needed it to work now, so I went ahead and committed a fix as sys/boot/i386/loader/Makefile,v 1.78. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --32u276st3Jlj2kUU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBquyxqRfpzJluFF4RAjP2AJ4oBpPZu8uV4DDfP4ed5utkf9ipSwCePlWa hgUN304f1Zx/rvAEker31YA= =Kt9C -----END PGP SIGNATURE----- --32u276st3Jlj2kUU-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 09:37:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7472F16A4CE for ; Mon, 29 Nov 2004 09:37:42 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id E617E43D58 for ; Mon, 29 Nov 2004 09:37:41 +0000 (GMT) (envelope-from se@freebsd.org) Received: from [212.227.126.205] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CYhyW-0004wY-00; Mon, 29 Nov 2004 10:37:40 +0100 Received: from [80.132.243.41] (helo=Gatekeeper.FreeBSD.org) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1CYhyW-00062v-00; Mon, 29 Nov 2004 10:37:40 +0100 Received: from StefanEsser.FreeBSD.org (StefanEsser [192.168.0.10]) by Gatekeeper.FreeBSD.org (Postfix) with ESMTP id 47AC25F57; Mon, 29 Nov 2004 10:37:38 +0100 (CET) Received: by StefanEsser.FreeBSD.org (Postfix, from userid 200) id 550D22305; Mon, 29 Nov 2004 10:37:37 +0100 (CET) Date: Mon, 29 Nov 2004 10:37:35 +0100 From: Stefan =?iso-8859-1?Q?E=DFer?= To: Doug White Message-ID: <20041129093735.GA1734@StefanEsser.FreeBSD.org> Mail-Followup-To: Stefan =?iso-8859-1?Q?E=DFer?= , Doug White , Aaron Wallace , freebsd-current@freebsd.org References: <41A60006.3060708@uiuc.edu> <20041128220740.O40277@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041128220740.O40277@carver.gumbysoft.com> User-Agent: Mutt/1.5.6i X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:fa3fae9b6ca38d745862a668565919f6 cc: Aaron Wallace cc: freebsd-current@freebsd.org Subject: Re: bug report: AMD64, 5.3, sym driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 09:37:42 -0000 On 2004-11-28 22:20 -0800, Doug White wrote: > On Thu, 25 Nov 2004, Aaron Wallace wrote: > > > I believe that I've found a bug with the sym driver in AMD64. I don't > > have this problem with 5.3 under i386. I wasn't able to submit this > > report via web because the anti-spam code wasn't being recognized. > > > > The problem occurs during boot up / driver detect. I get the following > > messages in bootup which I've manually copied: > > > > sym0: <810a> port 0x9000-0x90ff mem 0xea094000-0xea0940ff irq 12 at > > device 7.0 on pci1 > > __sym_calloc2: failed to allocate HCB[4288] > > device_attach: sym0 attach returned 6 > > Oh yuck. The sym driver has its own memory allocator that caps allocations > at 1 page. Since PAGE_SIZE on amd64 is 4k, and the 64 bit resizing of the > structs puts the size over 4k, the struct will need some pruning. > (PAGE_SIZE is 8k on sparc64 (and alpha?) which is why this hasn't been > caught previously.) > > You will have to use a different controller until the driver can be fixed. Hmmm, does the NCR driver work? The sym driver adds full support for NCR/Symbios chips that offer an advanced command set (e.g. including indirect loads and stores) but the 53c810a does not implement those extra commands. If the NCR driver is affected, too, I'm willing to fix it (though I currently don't have access to any AMD64 equipment). The fix may also apply to sym, which was derived from the ncr driver, long ago. Regards, STefan From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 09:43:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F56816A4CE; Mon, 29 Nov 2004 09:43:23 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8ABEF43D48; Mon, 29 Nov 2004 09:43:22 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAT9hMZ7034038; Mon, 29 Nov 2004 04:43:22 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iAT9hM7A013013; Mon, 29 Nov 2004 04:43:22 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A73B37306E; Mon, 29 Nov 2004 04:43:21 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041129094321.A73B37306E@freebsd-current.sentex.ca> Date: Mon, 29 Nov 2004 04:43:21 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 09:43:23 -0000 TB --- 2004-11-29 08:37:38 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-29 08:37:38 - starting CURRENT tinderbox run for i386/pc98 TB --- 2004-11-29 08:37:38 - checking out the source tree TB --- 2004-11-29 08:37:38 - cd /home/tinderbox/CURRENT/i386/pc98 TB --- 2004-11-29 08:37:38 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-29 08:44:12 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-29 08:44:12 - cd /home/tinderbox/CURRENT/i386/pc98/src TB --- 2004-11-29 08:44:12 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cp loader.sym loader.bin strip -R .comment -R .note loader.bin btxld -v -f aout -e 0x100000 -o loader -l /tinderbox/CURRENT/i386/pc98/obj/pc98/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/loader/../btx/btxldr/btxldr -b /tinderbox/CURRENT/i386/pc98/obj/pc98/tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/loader/../btx/btx/btx loader.bin kernel: ver=1.01 size=7c0 load=9000 entry=9010 map=16M pgctl=0:28 client: fmt=elf size=2a450 text=273dc data=1f0c bss=6154 entry=0 output: fmt=aout size=2d000 text=1000 data=2b000 org=100000 entry=100000 cat /tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/loader/../../common/help.common /tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/loader/help.pc98 | awk -f /tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/loader/../../common/merge_help.awk > loader.help make: don't know how to make /tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98/loader/../../i386/loader/loader.rc. Stop *** Error code 2 Stop in /tinderbox/CURRENT/i386/pc98/src/sys/boot/pc98. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src/sys/boot. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src/sys. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src. TB --- 2004-11-29 09:43:21 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-29 09:43:21 - ERROR: failed to build world TB --- 2004-11-29 09:43:21 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 10:04:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B80416A4CE for ; Mon, 29 Nov 2004 10:04:14 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C381343D64 for ; Mon, 29 Nov 2004 10:04:12 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iATA4Bs8067301; Mon, 29 Nov 2004 12:04:11 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 42988-13; Mon, 29 Nov 2004 12:04:10 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iATA49HL067298 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Nov 2004 12:04:10 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iATA4BGd081309; Mon, 29 Nov 2004 12:04:11 +0200 (EET) (envelope-from ru) Date: Mon, 29 Nov 2004 12:04:11 +0200 From: Ruslan Ermilov To: Poul-Henning Kamp Message-ID: <20041129100411.GC80748@ip.net.ua> References: <20041129092510.GA80748@ip.net.ua> <28131.1101720410@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2Z2K0IlrPCVsbNpk" Content-Disposition: inline In-Reply-To: <28131.1101720410@critter.freebsd.dk> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: current@freebsd.org Subject: Re: [PATCH] mount(8) broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 10:04:14 -0000 --2Z2K0IlrPCVsbNpk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Mon, Nov 29, 2004 at 10:26:50AM +0100, Poul-Henning Kamp wrote: >=20 > By all means commit it! >=20 Done. I've also fixed the following four manpages: lib/libc/sys/mount.2 lib/libc/sys/statfs.2 share/man/man7/security.7 share/man/man9/vfs_mount.9 But these still need a careful fixing: sys/compat/linprocfs/linprocfs.c contrib/smbfs/mount_smbfs/mntopts.h usr.sbin/amd/include/config.h etc/amd.map share/doc/papers/devfs/paper.me ("grep -i nodev" in these files.) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --2Z2K0IlrPCVsbNpk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBqvQbqRfpzJluFF4RAmmhAJ9oBQ0d6AzGrMlyA2k0VWNS3yJVfACgmYvy +ZoxrT6GAMesrBGO7a0vOZk= =/6cX -----END PGP SIGNATURE----- --2Z2K0IlrPCVsbNpk-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 10:06:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2500816A4CE; Mon, 29 Nov 2004 10:06:51 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C02843D46; Mon, 29 Nov 2004 10:06:50 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iATA6mHB028881; Mon, 29 Nov 2004 11:06:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Ruslan Ermilov From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 29 Nov 2004 12:04:11 +0200." <20041129100411.GC80748@ip.net.ua> Date: Mon, 29 Nov 2004 11:06:48 +0100 Message-ID: <28880.1101722808@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: [PATCH] mount(8) broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 10:06:51 -0000 In message <20041129100411.GC80748@ip.net.ua>, Ruslan Ermilov writes: >But these still need a careful fixing: > >sys/compat/linprocfs/linprocfs.c >contrib/smbfs/mount_smbfs/mntopts.h >usr.sbin/amd/include/config.h >etc/amd.map >share/doc/papers/devfs/paper.me They should hopefully be able to cope due to the fact that MNT_NODEV is now defined as 0. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 11:27:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47B3316A4CE; Mon, 29 Nov 2004 11:27:21 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EAC843D2F; Mon, 29 Nov 2004 11:27:20 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iATBRJXk049126; Mon, 29 Nov 2004 06:27:19 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iATBRJ1l068850; Mon, 29 Nov 2004 06:27:19 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id B3E347306E; Mon, 29 Nov 2004 06:27:19 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041129112719.B3E347306E@freebsd-current.sentex.ca> Date: Mon, 29 Nov 2004 06:27:19 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 11:27:21 -0000 TB --- 2004-11-29 09:43:21 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-29 09:43:21 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2004-11-29 09:43:21 - checking out the source tree TB --- 2004-11-29 09:43:21 - cd /home/tinderbox/CURRENT/ia64/ia64 TB --- 2004-11-29 09:43:21 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-29 09:49:25 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-29 09:49:25 - cd /home/tinderbox/CURRENT/ia64/ia64/src TB --- 2004-11-29 09:49:25 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-29 11:20:10 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-29 11:20:10 - cd /home/tinderbox/CURRENT/ia64/ia64/src TB --- 2004-11-29 11:20:10 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Nov 29 11:20:10 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/ia64/ia64/src/sys -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/altq -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/pf -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ia64/libuwx/src -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata -ffreestanding -Werror /tinderbox/CURRENT/ia64/ia64/src/sys/kern/vfs_cache.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/ia64/ia64/src/sys -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/altq -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/pf -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ia64/libuwx/src -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata -ffreestanding -Werror /tinderbox/CURRENT/ia64/ia64/src/sys/kern/vfs_cluster.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/ia64/ia64/src/sys -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/altq -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/pf -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ia64/libuwx/src -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata -ffreestanding -Werror /tinderbox/CURRENT/ia64/ia64/src/sys/kern/vfs_default.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/ia64/ia64/src/sys -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/altq -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/pf -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ia64/libuwx/src -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata -ffreestanding -Werror /tinderbox/CURRENT/ia64/ia64/src/sys/kern/vfs_export.c /tinderbox/CURRENT/ia64/ia64/src/sys/kern/vfs_export.c: In function `vfs_hang_addrlist': /tinderbox/CURRENT/ia64/ia64/src/sys/kern/vfs_export.c:132: error: `SA_MAX' undeclared (first use in this function) /tinderbox/CURRENT/ia64/ia64/src/sys/kern/vfs_export.c:132: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/ia64/ia64/src/sys/kern/vfs_export.c:132: error: for each function it appears in.) *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/obj/ia64/tinderbox/CURRENT/ia64/ia64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. TB --- 2004-11-29 11:27:19 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-29 11:27:19 - ERROR: failed to build generic kernel TB --- 2004-11-29 11:27:19 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 12:43:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8272616A4D7; Mon, 29 Nov 2004 12:43:53 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15E4C43D69; Mon, 29 Nov 2004 12:43:53 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iATChqZQ060747; Mon, 29 Nov 2004 07:43:52 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iATChpEl089838; Mon, 29 Nov 2004 07:43:51 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 3F7607306E; Mon, 29 Nov 2004 07:43:52 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041129124352.3F7607306E@freebsd-current.sentex.ca> Date: Mon, 29 Nov 2004 07:43:52 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 12:43:53 -0000 TB --- 2004-11-29 11:27:19 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-29 11:27:19 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2004-11-29 11:27:19 - checking out the source tree TB --- 2004-11-29 11:27:19 - cd /home/tinderbox/CURRENT/sparc64/sparc64 TB --- 2004-11-29 11:27:19 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-29 11:33:42 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-29 11:33:42 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2004-11-29 11:33:42 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-29 12:39:43 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-29 12:39:43 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2004-11-29 12:39:43 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Nov 29 12:39:43 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/vfs_cache.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/vfs_cluster.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/vfs_default.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/vfs_export.c /tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/vfs_export.c: In function `vfs_hang_addrlist': /tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/vfs_export.c:132: error: `SA_MAX' undeclared (first use in this function) /tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/vfs_export.c:132: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/sparc64/sparc64/src/sys/kern/vfs_export.c:132: error: for each function it appears in.) *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2004-11-29 12:43:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-29 12:43:52 - ERROR: failed to build generic kernel TB --- 2004-11-29 12:43:52 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Nov 28 23:37:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2AF316A4CE for ; Sun, 28 Nov 2004 23:37:27 +0000 (GMT) Received: from smtpauth08.mail.atl.earthlink.net (smtpauth08.mail.atl.earthlink.net [209.86.89.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C53A143D31 for ; Sun, 28 Nov 2004 23:37:27 +0000 (GMT) (envelope-from welchsm@earthlink.net) Received: from [66.41.102.215] (helo=NitroPhys.welchsmnet.net) by smtpauth08.mail.atl.earthlink.net with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1CYYbf-0005fT-8a for freebsd-current@freebsd.org; Sun, 28 Nov 2004 18:37:27 -0500 Received: from NitroPhys.welchsmnet.net (localhost [127.0.0.1]) iASNb5rr081692 for ; Sun, 28 Nov 2004 17:37:05 -0600 (CST) (envelope-from welchsm@localhost.welchsmnet.net) Received: (from welchsm@localhost) by NitroPhys.welchsmnet.net (8.13.1/8.13.1/Submit) id iASNb5T4081691 for freebsd-current@freebsd.org; Sun, 28 Nov 2004 17:37:05 -0600 (CST) (envelope-from welchsm) Date: Sun, 28 Nov 2004 17:37:05 -0600 From: Sean Welch To: freebsd-current@freebsd.org Message-ID: <20041128233704.GB62951@NitroPhys.welchsmnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-ELNK-Trace: 15d86f98c8ef8acad780f4a490ca69563f9fea00a6dd62bcbe774f87b8e0c341caf5bd434256563a350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.41.102.215 X-Mailman-Approved-At: Mon, 29 Nov 2004 13:21:44 +0000 Subject: top under 5.3-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Sean_Welch@alum.wofford.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Nov 2004 23:37:28 -0000 I realize this is not strictly pertaining to -CURRENT (though I suspect it may pertain), but I've noticed a change in the output of top that I don't really understand. Through 5.2.1-RELEASE I've been accustomed to seeing the top few processes using a % of cpu that correspondes to the % free cpu value in the header part of the output. Ie, if the machine is 20% idle I expect to see the process %s to add up to roughly 80%. This seems no longer to be the case under 5.3-RELEASE and I'm rather confused by a 0% idle statement with the process %s adding up to only about 15% or so. The amount jumps around a bit and seems to bear the relationship I expect when there is light load, but it looks completely wrong to me when there is heavy load (as in compiling a port). Can anyone explain this seeming inconsistency to me? Sean From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 13:30:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63DD116A4CE for ; Mon, 29 Nov 2004 13:30:30 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DC6343D4C for ; Mon, 29 Nov 2004 13:30:30 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CYlbp-000O0o-Jj; Mon, 29 Nov 2004 05:30:29 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16811.9333.99454.679978@ran.psg.com> Date: Mon, 29 Nov 2004 05:30:29 -0800 To: Doug White References: <20041123182254.GB10721@ninthgate.net> <16804.64917.872924.733444@ran.psg.com> <20041124232820.J2006@carver.gumbysoft.com> <16805.38319.825546.497936@ran.psg.com> <20041128220455.F40277@carver.gumbysoft.com> cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 13:30:30 -0000 >>> Looks like you just need to set 'dumpdev' in rc.conf. What is your boot >>> device and swap partition(s)? >> # grep dump /etc/rc.conf >> dumpdev="/dev/twed0s1b" # Device name to crashdump to (or NO). >> dumpdir="/var/crash" # Directory where crash dumps are to be stored > Hm, this should be getting set; the twe driver supports crashdumps. What > happens if you run 'dumpon /dev/twed0s1b' manually? # dumpon /dev/twed0s1b # >>> if you turn on session logging in your comm program >> comm program? it's a cisco 2511 term serv being used as a >> craft port octopus for 16 devices > What program are you using to connect to the 2511 to view the console on > the target? Telnet? Real terminal? :) telnet?!?!?!?! you're kidding, right? i am using ssh. randy From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 13:31:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7182E16A4E0 for ; Mon, 29 Nov 2004 13:31:19 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E68243D1F for ; Mon, 29 Nov 2004 13:31:19 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CYlcc-000OFw-VG; Mon, 29 Nov 2004 05:31:19 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16811.9382.458712.205175@ran.psg.com> Date: Mon, 29 Nov 2004 05:31:18 -0800 To: Doug White References: <16807.10942.710868.490640@ran.psg.com> <20041128222418.R40277@carver.gumbysoft.com> cc: FreeBSD Current Subject: Re: crash on just cvsupped build X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 13:31:19 -0000 > Whats the 'zt' device? Its not a shipping FreeBSD driver. that was it. asterisk's zaptel driver. removed it last night and the server is at least running. randy From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 13:38:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67F5D16A4CE; Mon, 29 Nov 2004 13:38:28 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF97C43D5D; Mon, 29 Nov 2004 13:38:27 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id C4972ACAFB; Mon, 29 Nov 2004 14:38:25 +0100 (CET) Date: Mon, 29 Nov 2004 14:38:25 +0100 From: Pawel Jakub Dawidek To: Chris Hedley Message-ID: <20041129133825.GL7232@darkness.comp.waw.pl> References: <20041127193532.X15946@teapot.cbhnet> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Gnkm4uF329L9IN0W" Content-Disposition: inline In-Reply-To: <20041127193532.X15946@teapot.cbhnet> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: freebsd-current@freebsd.org cc: marcel@freebsd.org Subject: Re: GEOM: gpt partitions on a gmirror array possible? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 13:38:28 -0000 --Gnkm4uF329L9IN0W Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 27, 2004 at 07:58:35PM +0000, Chris Hedley wrote: +> Hi all, +>=20 +> A hopefully quick question! I have looked for a solution for (or=20 +> discussion about) this, if I've just failed to find it, please point me = in=20 +> the right direction. +>=20 +> This is what I'm trying to do: I've created a RAID-1 array, m1, using=20 +> gmirror on two scsi units, da0 and da1, and I'd like to chop it up into= =20 +> logical partitions using gpt, as I understand (correctly, hopefully) the= re=20 +> are leanings toward gpt rather than bsdlabel as being the correct way to= =20 +> do things. Now when I initialise and create my gpt partition on=20 +> mirror/m1, I get no new entries in /dev/mirror but I _do_ get separate= =20 +> /dev/da0p1 and /dev/da1p1 entries appearing. I've probably completely= =20 +> failed to understand the whole concept of GEOM tasting and unprejudiced= =20 +> hierarchy and so on as I decided I may as well try to create my UFS2=20 +> filesystem on /dev/da0p1 in /dev/mirror/m1p1's absence and see if=20 +> /dev/da1p1 magically follows suit. Needless to say it doesn't, I just e= nd=20 +> up with a dirty RAID-1 disc that needs resynchronising, with da0p1=20 +> (un)mysteriously disappearing after the newfs. +>=20 +> Is there a correct way to do this, or am I once again guilty of trying t= o=20 +> use something that isn't quite ready yet? Perhaps I should do it the=20 +> other way around and use gpt first and create one gmirror per partition;= =20 +> that solution didn't "feel" right for some reason, but I can't really=20 +> quantify that particularly as, if I understand the GEOM documentation=20 +> correctly, multiple gmirrors with their respective paritions on the same= =20 +> set of discs shouldn't compete with each for access. +>=20 +> My system is FreeBSD/amd64, 6.0-current (Oct 25th vintage) using ahc for= =20 +> my test scsi discs and aac for my active discs. It is because GEOM_GPT class only allow to create GPT labels on rank#1 providers (i.e. disks). I'm not sure why we have this hack, maybe marcel@ knows something more (cc'ed). --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --Gnkm4uF329L9IN0W Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBqyZRForvXbEpPzQRAhgSAKCPgwYs4PwT6KcaepgxWoRPQczJxgCcCVnt hLeVVz+ToYjPmCor5zR4b7M= =Eb4i -----END PGP SIGNATURE----- --Gnkm4uF329L9IN0W-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 13:44:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3987E16A4CE for ; Mon, 29 Nov 2004 13:44:57 +0000 (GMT) Received: from jazz.hansabank.lt (jazz.hansabank.lt [193.109.235.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id E76E843D2D for ; Mon, 29 Nov 2004 13:44:55 +0000 (GMT) (envelope-from Putinas.Piliponis@hansa.lt) Received: from localhost (localhost [127.0.0.1]) by jazz.hansabank.lt (Postfix) with ESMTP id ADAA3F941; Mon, 29 Nov 2004 15:44:54 +0200 (EET) content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 29 Nov 2004 15:44:53 +0200 Content-Type: multipart/signed; boundary="----=_NextPart_000_0012_01C4D62A.595BB790"; protocol="application/x-pkcs7-signature"; micalg=SHA1 X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 Message-ID: <217202CB5FF8AE439E263CE3D48ECB50757F13@honda.int.hansa.lt> X-MS-Has-Attach: yes X-MS-TNEF-Correlator: Thread-Topic: if_pcn & netfinity 5500 Thread-Index: AcTVN3DUq0yEI5tMS3qumevUJNXkNgA4hdgw From: "Putinas Piliponis" To: "Daniel Engberg" , Subject: RE: if_pcn & netfinity 5500 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 13:44:57 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0012_01C4D62A.595BB790 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Thank you, I will try that :) -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Daniel Engberg Sent: Sunday, November 28, 2004 12:45 To: freebsd-current@freebsd.org Subject: Re: if_pcn & netfinity 5500 I had the same issue and it got solved by this patch. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/72966 //Danne _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" ------=_NextPart_000_0012_01C4D62A.595BB790 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIV7jCCAiww ggGVoAMCAQICAxAAADANBgkqhkiG9w0BAQQFADA5MQswCQYDVQQGEwJFRTESMBAGA1UEChMJSGFu c2FwYW5rMRYwFAYDVQQDEw1IYW5zYSBSb290IENBMB4XDTk5MDMxMTA3MTk1M1oXDTA5MDMwODA3 MTk1M1owOTELMAkGA1UEBhMCRUUxEjAQBgNVBAoTCUhhbnNhcGFuazEWMBQGA1UEAxMNSGFuc2Eg Um9vdCBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAy09IBycOA2YSkc0ilg27V8srhWbO MHt3z/8e6y9qXxXYEbLJRaI5cQMAtwjEG+TRym0ViGgVYLU4QPrYXoGitgLtFOgG7urnHTRXjptE e7yOIBMUqUUhMLU/bnqvLTj6hU0U3lkQRdTj+DBEDkVC1RFnTT1LNEExIFIQ3b217ZECAwEAAaNC MEAwHQYDVR0OBBYEFArETktiEtIrt02CpZm0nloulC/YMB8GA1UdIwQYMBaAFArETktiEtIrt02C pZm0nloulC/YMA0GCSqGSIb3DQEBBAUAA4GBAJIH/kuITLXf/CzHSvydCCO0dffp/Z94PC37vEG4 obR1H5x+qQiuqigxhT9sfaCcZE9WoGZWcfYP2l9Q2VT4hHRhKbVKhCuZBh0fats1T36CbtdsLxNH yMOPfaNp9VW2RWyi1hYjTG0tNWFaH0Kd2NDWroQbXGCGHkIlOMcGwQFkMIICXTCCAcagAwIBAgID DVLGMA0GCSqGSIb3DQEBBAUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3Vs dGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWlu ZyBDQTAeFw0wNDEwMjgxODIyNDJaFw0wNTEwMjgxODIyNDJaMEwxHzAdBgNVBAMTFlRoYXd0ZSBG cmVlbWFpbCBNZW1iZXIxKTAnBgkqhkiG9w0BCQEWGnB1dGluYXMucGlsaXBvbmlzQGhhbnNhLmx0 MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC73A+48AVvwDxL+RbBL5bXsGF9rABC+znkbRL8 evzGT5P22qyEtAKYxE6drt7eBTS3bnHsnbFfQJog64FTFfsooXuethclBsPgOcfcD6ClxIHp7K5t gL3Hf/JsNdQ8WiCgLn8Td0x5jcmMt2XTvwsLL4fsrpHs8v6R0FtZEqXeLQIDAQABozcwNTAlBgNV HREEHjAcgRpwdXRpbmFzLnBpbGlwb25pc0BoYW5zYS5sdDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3 DQEBBAUAA4GBAELW8v2TeLaGQRjFnmQ6DQ3Y8wPhZ5r6tIhfkBJ2A7spQd7gSOxtTPR8kA69booS yG1UQAJti0vGPrcPdXFEAs1cbAbWj0Q5kAnw9+A8y4/WQGZWgnyi5cFPffJYalem9ULBddLjQ35K D/g6EVjbvbv2gKQROV0JGgQV8xc+jwYCMIIDLTCCApagAwIBAgIBADANBgkqhkiG9w0BAQQFADCB 0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3du MRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2 aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJ KoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTk2MDEwMTAwMDAwMFoX DTIwMTIzMTIzNTk1OVowgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQ BgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0Nl cnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBG cmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTCB nzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA1GnX1LCUZFtx6UfYDFG26nKRsIRefS0Nj3sS34Ul dSh0OkIsYyeflXtL734Zhx2G6qPduc6WZBrCFG5ErHzmj+hND3EfQDimAKOHePb5lIZererAXnbr 2RSjXW56fAylS1V/Bhkpf56aJtVquzgkCGqYx7Hao5iR/Xnb5VrEHLkCAwEAAaMTMBEwDwYDVR0T AQH/BAUwAwEB/zANBgkqhkiG9w0BAQQFAAOBgQDH7JJ+Tvj1lqVnYiqk8E0RYNBvjWBYYawmu1I1 XAjPMPuoSpaKH2JCI4wXD/S6ZJwXrEcp352YXtJsYHFcoqzceePnbgBHH7UNKOgCneSa/RP0ptl8 sfjcXyMmCZGAc9AUG95DqYMl8uacLxXK/qarigd1iwzdUYRr5PjRzneigTCCAz8wggKooAMCAQIC AQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUx EjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsT H0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25h bCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNv bTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065 yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FW y688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5k GXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0 dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQE AwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcN AQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t 4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpb NU1341YheILcIRk13iSx0x1G/11fZU8wggQ3MIIDoKADAgECAgIBBzANBgkqhkiG9w0BAQQFADA5 MQswCQYDVQQGEwJFRTESMBAGA1UEChMJSGFuc2FwYW5rMRYwFAYDVQQDEw1IYW5zYSBSb290IENB MB4XDTAyMDcxNjA4MjY1OFoXDTA5MDIwOTA4MjY1OFowRTELMAkGA1UEBhMCTFQxEjAQBgNVBAoT CUhhbnNhYmFuazEiMCAGA1UEAxMZSGFuc2FiYW5rIExUIGNvcnBvcmF0ZSBDQTCCASIwDQYJKoZI hvcNAQEBBQADggEPADCCAQoCggEBAOywhJxDqmwwPaz2jh36IYl3j8dqyV7CQobdaGarwYINDEBI REvwpJWU+XQMzCjl+f+2Nc6BZVh3TP1L20xnU1h5x9QW54M0h/3MOGnR9+/K0HQytltL9H/shRWL Xn96TKJikjcEHuHBtQXx2bz+8tZxJfuDlINLCrchTHDxXvAzc2vvG8JZKu2v8D4wOnQujQJMvbOz 33FdlI5xZK/Qf1M76wHBKNpo3TznKG41g39Xe7IEJVqMgZ0+51T7jswjiuh50UBIuB29JZeZKlks Yxkw3KlZJuzwFH7eO5MYDjJHRoaExrlT3BqoiYK2nbQN+xqox8kuE6BCchkC8/pscPMCAwEAAaOC AbwwggG4MB0GA1UdDgQWBBSQnWUmeUksJegDA5/wTRWbmR5m/DBjBgNVHSMEXDBagBQKxE5LYhLS K7dNgqWZtJ5aLpQv2KE9pDswOTELMAkGA1UEBhMCRUUxEjAQBgNVBAoTCUhhbnNhcGFuazEWMBQG A1UEAxMNSGFuc2EgUm9vdCBDQYIDEAAAMA8GA1UdEwEB/wQFMAMBAf8wCwYDVR0PBAQDAgFGMIIB EgYDVR0fBIIBCTCCAQUwgc6ggcuggciGgcVsZGFwOi8vL0NOPUhhbnNhJTIwUm9vdCUyY0NOPWFs cGhhJTJjQ049Q0RQJTJjQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMlMmNDTj1TZXJ2aWNlcyUy Y0NOPUNvbmZpZ3VyYXRpb24lMmNEQz1pbnQlMmNEQz1oYW5zYSUyY0RDPWVlP2NlcnRpZmljYXRl UmV2b2NhdGlvbkxpc3Q/YmFzZT9vYmplY3RjbGFzcz1jUkxEaXN0cmlidXRpb25Qb2ludDAyoDCg LoYsaHR0cDovL2F1ZGkuaW50LmhhbnNhLmx0L2NlcnRlbnJvbGwvcm9vdC5jcmwwDQYJKoZIhvcN AQEEBQADgYEAfbgx849ncHuZJ9XLbYT1h3MKazFD3PDu+3w/BAbCY/j1fdODW2qv4OjU/L8w4ffs 5WjofKE6bnZItRBmygvFrfAcJg9MCmBLyMMFWDbix3Nq6fZ/awnC6/YlNsCNIu+TVrVsWJspyC+s iBYR3sXnaU0JErt4vNYhokE37H/ucd4wggaqMIIFkqADAgECAgoguUEuAAEAACHBMA0GCSqGSIb3 DQEBBQUAMEUxCzAJBgNVBAYTAkxUMRIwEAYDVQQKEwlIYW5zYWJhbmsxIjAgBgNVBAMTGUhhbnNh YmFuayBMVCBjb3Jwb3JhdGUgQ0EwHhcNMDQwODExMDYzNDU5WhcNMDYwODExMDYzNDU5WjBHMSkw JwYJKoZIhvcNAQkBFhpQdXRpbmFzLlBpbGlwb25pc0BoYW5zYS5sdDEaMBgGA1UEAxMRUHV0aW5h cyBQaWxpcG9uaXMwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAL9MadCNAF9prlqEM79LnMtU ZUsmjPYVaWxgjYbpNnb1K/YLgt8IKvi1y7orN71HIy6XOLtceuKnJF4UyYu0hnzpX1YCrApj1kmY jttzwUMLmldoMI/+Nw5R5QioXFAJht09OwqEBHxGOwDMt4Gs4f1DdjElUqyEzSFucCedel6vAgMB AAGjggQcMIIEGDALBgNVHQ8EBAMCBaAwKQYDVR0lBCIwIAYIKwYBBQUHAwQGCCsGAQUFBwMCBgor BgEEAYI3FAICMCkGCSsGAQQBgjcUAgQcHhoAUwBtAGEAcgB0AGMAYQByAGQAVQBzAGUAcjAdBgNV HQ4EFgQUtlF3XdHE1kc/hYjvbsBc8Nu4TnMwYgYDVR0jBFswWYAUkJ1lJnlJLCXoAwOf8E0Vm5ke ZvyhPaQ7MDkxCzAJBgNVBAYTAkVFMRIwEAYDVQQKEwlIYW5zYXBhbmsxFjAUBgNVBAMTDUhhbnNh IFJvb3QgQ0GCAgEHMIIBYwYDVR0fBIIBWjCCAVYwgdCggc2ggcqGgcdsZGFwOi8vL0NOPUhhbnNh YmFuayUyMExUJTIwY29ycG9yYXRlJTIwQ0EsQ049YXVkaSxDTj1DRFAsQ049UHVibGljJTIwS2V5 JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1pbnQsREM9aGFuc2Es REM9ZWU/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdGNsYXNzPWNSTERpc3Ry aWJ1dGlvblBvaW50ME2gS6BJhkdodHRwOi8vYXVkaS5pbnQuaGFuc2EubHQvQ2VydEVucm9sbC9I YW5zYWJhbmslMjBMVCUyMGNvcnBvcmF0ZSUyMENBLmNybDAyoDCgLoYsaHR0cDovL2F1ZGkuaW50 LmhhbnNhLmx0L2NlcnRlbnJvbGwvcm9vdC5jcmwwggF7BggrBgEFBQcBAQSCAW0wggFpMIHCBggr BgEFBQcwAoaBtWxkYXA6Ly8vQ049SGFuc2FiYW5rJTIwTFQlMjBjb3Jwb3JhdGUlMjBDQSxDTj1B SUEsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlv bixEQz1pbnQsREM9aGFuc2EsREM9ZWU/Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdGNsYXNzPWNl cnRpZmljYXRpb25BdXRob3JpdHkwaAYIKwYBBQUHMAKGXGh0dHA6Ly9hdWRpLmludC5oYW5zYS5s dC9DZXJ0RW5yb2xsL2F1ZGkuaW50LmhhbnNhLmx0X0hhbnNhYmFuayUyMExUJTIwY29ycG9yYXRl JTIwQ0EoMSkuY3J0MDgGCCsGAQUFBzAChixodHRwOi8vYXVkaS5pbnQuaGFuc2EubHQvY2VydGVu cm9sbC9yb290LmNydDBKBgNVHREEQzBBoCMGCisGAQQBgjcUAgOgFQwTcHV0cGlsQGludC5oYW5z YS5sdIEaUHV0aW5hcy5QaWxpcG9uaXNAaGFuc2EubHQwDQYJKoZIhvcNAQEFBQADggEBAIAG4B0U AGtYXA8Rml8J6bIquNip7aIMMb5tw3Tri00vjY+fo5fRxeqTtyxLp2URhpIzR/2Vfq70nACn1yA9 2rkTIgfdQ11rZ03TrFDW3fOzfZCTdyYLMkm5v3DgaPE8SUcOLbHIQvgJ6l2QqNwIVGgPYT73aYXE D0GT7AwzxpksmyotwroUlLTo7Guw9IJv1WZuYFiQWgrqUrp4eXEwpmbJIfksvVox/Uw4tUwtrn5u Qp1yAkm7FGIo9yrRPd6Pbqwmx+uXtEsBnCKSE2N/9Gmi6MswOoUKx6zsPISj3hdqd6ZcSkUIkBpl ApN1CqiKw5ITKCvppz3LvWPv9SopigMxggKFMIICgQIBATBpMGIxCzAJBgNVBAYTAlpBMSUwIwYD VQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29u YWwgRnJlZW1haWwgSXNzdWluZyBDQQIDDVLGMAkGBSsOAwIaBQCgggFyMBgGCSqGSIb3DQEJAzEL BgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA0MTEyOTEzNDQ0NFowIwYJKoZIhvcNAQkEMRYE FHct4iTiYChC4h4JN4yxItW+PHDAMEkGCSqGSIb3DQEJDzE8MDowCgYIKoZIhvcNAwcwDgYIKoZI hvcNAwICAgCAMAcGBSsOAwIHMAcGBSsOAwIaMAoGCCqGSIb3DQIFMGIGCSsGAQQBgjcQBDFVMFMw RTELMAkGA1UEBhMCTFQxEjAQBgNVBAoTCUhhbnNhYmFuazEiMCAGA1UEAxMZSGFuc2FiYW5rIExU IGNvcnBvcmF0ZSBDQQIKILlBLgABAAAhwTBkBgsqhkiG9w0BCRACCzFVoFMwRTELMAkGA1UEBhMC TFQxEjAQBgNVBAoTCUhhbnNhYmFuazEiMCAGA1UEAxMZSGFuc2FiYW5rIExUIGNvcnBvcmF0ZSBD QQIKILlBLgABAAAhwTANBgkqhkiG9w0BAQEFAASBgJJ4TdY8+WUcbezVTzwlIr1pJUOn8IQheV+K +Wwb+/6f1+IJgcEECX7Vt8qAkNlfZTkKpWEm8RcFeAaOvy80zShR4MNXWR0Oseoii4lhp17TSa+l 4nh+lxWMfp68HgstFhwhABY8YJmX7/kx+A6oHhKkXkhPzCieO1HClIyg4DQbAAAAAAAA ------=_NextPart_000_0012_01C4D62A.595BB790-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 15:15:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7462216A4CF for ; Mon, 29 Nov 2004 15:15:47 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6290643D58 for ; Mon, 29 Nov 2004 15:15:46 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 2223 invoked from network); 29 Nov 2004 15:07:20 -0000 Received: from unknown (HELO freebsd.org) ([62.48.0.53]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 29 Nov 2004 15:07:20 -0000 Message-ID: <41AB3D24.80DEBD08@freebsd.org> Date: Mon, 29 Nov 2004 16:15:48 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "David G. Lawrence" References: <41A628F3.3000309@freebsd.org> <20041125205210.GA673@opteron.dglawrence.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Jeremie Le Hen cc: freebsd-current@freebsd.org cc: Robert Watson cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 15:15:47 -0000 "David G. Lawrence" wrote: > > > >>tests. With the re driver, no change except placing a 100BT setup with > > >>no packet loss to a gigE setup (both linksys switches) will cause > > >>serious packet loss at 20Mbps data rates. I have discovered the only > > >>way to get good performance with no packet loss was to > > >> > > >>1) Remove interrupt moderation > > >>2) defrag each mbuf that comes in to the driver. > > > > > >Sounds like you're bumping into a queue limit that is made worse by > > >interrupting less frequently, resulting in bursts of packets that are > > >relatively large, rather than a trickle of packets at a higher rate. > > >Perhaps a limit on the number of outstanding descriptors in the driver or > > >hardware and/or a limit in the netisr/ifqueue queue depth. You might try > > >changing the default IFQ_MAXLEN from 50 to 128 to increase the size of the > > >ifnet and netisr queues. You could also try setting net.isr.enable=1 to > > >enable direct dispatch, which in the in-bound direction would reduce the > > >number of context switches and queueing. It sounds like the device driver > > >has a limit of 256 receive and transmit descriptors, which one supposes is > > >probably derived from the hardware limit, but I have no documentation on > > >hand so can't confirm that. > > > > > >It would be interesting on the send and receive sides to inspect the > > >counters for drops at various points in the network stack; i.e., are we > > >dropping packets at the ifq handoff because we're overfilling the > > >descriptors in the driver, are packets dropped on the inbound path going > > >into the netisr due to over-filling before the netisr is scheduled, etc. > > >And, it's probably interesting to look at stats on filling the socket > > >buffers for the same reason: if bursts of packets come up the stack, the > > >socket buffers could well be being over-filled before the user thread can > > >run. > > > > I think it's the tcp_output() path that overflows the transmit side of > > the card. I take that from the better numbers when he defrags the packets. > > Once I catch up with my mails I start to put up the code I wrote over the > > last two weeks. :-) You can call me Mr. TCP now. ;-) > > He was doing his test with NFS over TCP, right? ...That would be a single > connection, so how is it possible to 'overflow the transmit side of the > card'? The TCP window size will prevent more than 64KB to be outstanding. > Assuming standard size ethernet frames, that would be a maximum of 45 packets > in-flight at any time (65536/1460=45), well below the 256 available transmit > descriptors. > It is also worth pointing out that 45 full-size packets is 540us at > gig-e speeds. Even when you add up typical switch latencies and interrupt > overhead and coalesing on both sides, it's hard to imagine that the window > size (bandwidth * delay) would be a significant limiting factor across a > gig-e LAN. For some reason he is getting long mbuf chains and that is why a call to m_defrag helps. With long mbuf chains you can easily overflow the transmit descriptors. > I too am seeing low NFS performance (both TCP and UDP) with non-SMP > 5.3, but on the same systems I can measure raw TCP performance (using > ttcp) of >850Mbps. It looks to me like there is something wrong with > NFS, perhaps caused by delays with scheduling nfsd? -- Andre From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 15:48:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64F9E16A4CE for ; Mon, 29 Nov 2004 15:48:18 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F02443D49 for ; Mon, 29 Nov 2004 15:48:18 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iATFm6ME040264; Mon, 29 Nov 2004 09:48:06 -0600 (CST) (envelope-from dan) Date: Mon, 29 Nov 2004 09:48:05 -0600 From: Dan Nelson To: Sean Welch Message-ID: <20041129154805.GD5518@dan.emsphone.com> References: <20041128233704.GB62951@NitroPhys.welchsmnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041128233704.GB62951@NitroPhys.welchsmnet.net> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: top under 5.3-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 15:48:18 -0000 In the last episode (Nov 28), Sean Welch said: > Through 5.2.1-RELEASE I've been accustomed to seeing the top few > processes using a % of cpu that correspondes to the % free cpu value > in the header part of the output. Ie, if the machine is 20% idle I > expect to see the process %s to add up to roughly 80%. This seems no > longer to be the case under 5.3-RELEASE and I'm rather confused by a > 0% idle statement with the process %s adding up to only about 15% or > so. > > The amount jumps around a bit and seems to bear the relationship I > expect when there is light load, but it looks completely wrong to me > when there is heavy load (as in compiling a port). > > Can anyone explain this seeming inconsistency to me? For things like port builds, you end up with a lot of very short-lived processes (sh, sed, cc, etc). Those either don't show up in top at all becuase they have started and exited between the sampling intervals, or else have not accumulated enough CPU time to register any %CPU (which is a weighted average over time). The values should total up better when you have processes that hang around a bit more. There was a regression in 5.3's libpthreads that can make it report 0 CPU, so if you have some CPU-hungry threaded programs, they may not show up in top at all even though they're using 100% cpu. libthr and libc_r report CPU correctly. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 16:47:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4611816A4CE for ; Mon, 29 Nov 2004 16:47:54 +0000 (GMT) Received: from duchess.speedfactory.net (duchess.speedfactory.net [66.23.201.84]) by mx1.FreeBSD.org (Postfix) with SMTP id A131343D31 for ; Mon, 29 Nov 2004 16:47:53 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 26780 invoked by uid 89); 29 Nov 2004 16:47:32 -0000 Received: from duchess.speedfactory.net (66.23.201.84) by duchess.speedfactory.net with SMTP; 29 Nov 2004 16:47:32 -0000 Received: (qmail 20547 invoked by uid 89); 29 Nov 2004 16:45:48 -0000 Received: from unknown (HELO palm.tree.com) (66.23.216.49) by duchess.speedfactory.net with SMTP; 29 Nov 2004 16:45:48 -0000 Received: from [127.0.0.1] (localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id iATGjj9k021973; Mon, 29 Nov 2004 11:45:45 -0500 (EST) (envelope-from ups@tree.com) From: Stephan Uphoff To: "current@freebsd.org" , "i386@freebsd.org" Content-Type: text/plain Message-Id: <1101746745.11465.2838.camel@palm.tree.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 29 Nov 2004 11:45:45 -0500 Content-Transfer-Encoding: 7bit Subject: new patch for "Previous IPI is stuck" - PLEASE TEST X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 16:47:54 -0000 Hi, The last patch for Previous IPI is stuck" seems to have fixed the problem for all testers (Thanks for the feedback!) and this is the promised optimized version. You can download the patch at: http://people.freebsd.org/~ups/ipi5_patch Please make sure that exception.o is rebuild. ( Makefile seems to miss the dependency to apic_vector.s) I would like to check in the changes as soon as possible. However since I can not reproduce the problem locally I will have to wait for feedback from testers. Thanks again to all for the positive feedback for the last patch. Stephan From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 17:08:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C76516A4CE for ; Mon, 29 Nov 2004 17:08:28 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAC2F43D3F for ; Mon, 29 Nov 2004 17:08:27 +0000 (GMT) (envelope-from frank.altpeter@gmail.com) Received: by wproxy.gmail.com with SMTP id 55so527550wri for ; Mon, 29 Nov 2004 09:08:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=IngY0R15gJ4TFSic78s+fuNY21mZcot9mPg5vL41WH2Gk1Pe6/l0YK5H8DO3f4grYNySYXE9wnDCfxOc2gPiHnOMyMKRbZUIEIvPecl8+H2HlMiv3ur94Ub2sU2MX4QfoXweCD6sCG+R0yVTlpzJGwdmutveAbgJd18I8kQYkm4= Received: by 10.54.43.63 with SMTP id q63mr1182446wrq; Mon, 29 Nov 2004 09:07:12 -0800 (PST) Received: by 10.54.14.21 with HTTP; Mon, 29 Nov 2004 09:07:09 -0800 (PST) Message-ID: Date: Mon, 29 Nov 2004 18:07:09 +0100 From: Frank Altpeter To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: serial connection freezes host X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Frank Altpeter List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 17:08:28 -0000 Hi there, Since some time, the attempt to hotsync my PDA via serial connection does result in a complete freeze of my notebook. I don't know exactly since when this happens, because i usually don't hotsync that often, but i'm sure it happens without changing anything on my system but the frequent world and kernel updates. The host is an IBM ThinkPad t40 running a some days old 6.0-CURRENT, which provides serial connection to a Palm m505 handheld running PalmOS version 4.0 Some informational snippets: freddy@pegasus:~ 0% dmesg | grep sio0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 3 flags 0x10 on acpi0 sio0: type 16550A freddy@pegasus:~ 0% pkg_version -v -s pilot-link pilot-link-0.11.8_3 = up-to-date with port After plugging the PDA, starting "pilot-xfer -p /dev/cuad0 -l" and pressing the hotsync button, the notebook stands still - still as in complete freeze. Only a power cycle can reanimate the notebook - but nothing is found in any log providing an idea on what was going on. Any information appreciated :-) Regards, Frank -- "Two of the most famous products of Berkeley are LSD and Unix. I don't think that this is a coincidence." -- Anonymous From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 18:35:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D3C916A4CE; Mon, 29 Nov 2004 18:35:15 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id A864443D6A; Mon, 29 Nov 2004 18:35:14 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iATIZDiO084238; Mon, 29 Nov 2004 10:35:14 -0800 (PST) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.13.1/8.13.1/Submit) id iATIZBnZ084237; Mon, 29 Nov 2004 10:35:11 -0800 (PST) (envelope-from marcel) Date: Mon, 29 Nov 2004 10:35:11 -0800 From: Marcel Moolenaar To: Pawel Jakub Dawidek Message-ID: <20041129183511.GA84117@ns1.xcllnt.net> References: <20041127193532.X15946@teapot.cbhnet> <20041129133825.GL7232@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041129133825.GL7232@darkness.comp.waw.pl> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@FreeBSD.org cc: Chris Hedley Subject: Re: GEOM: gpt partitions on a gmirror array possible? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 18:35:15 -0000 On Mon, Nov 29, 2004 at 02:38:25PM +0100, Pawel Jakub Dawidek wrote: > > It is because GEOM_GPT class only allow to create GPT labels on rank#1 > providers (i.e. disks). I'm not sure why we have this hack, maybe marcel@ > knows something more (cc'ed). It's there, because it was there for the MBR class when I used that class as a blueprint for implementing GPT support. Since GPT is not allowed within an MBR slice, or within a GPT partition (no nesting), not to mention all the non-native partitioning schemes that GEOM supports, that test made sure we only tasted GPT partitions on the one kind of providers that existed besides slicers: disks. I guess a change like geom_mbr.c:1.57 is in order, or a more to-the- point test for rejecting GPT on MBR or GPT on GPT. FYI, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 18:52:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BDC116A4CE; Mon, 29 Nov 2004 18:52:01 +0000 (GMT) Received: from mail25.syd.optusnet.com.au (mail25.syd.optusnet.com.au [211.29.133.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6BB543D69; Mon, 29 Nov 2004 18:52:00 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) iATIpwMv030230 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 30 Nov 2004 05:51:59 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])iATIpwxP061235; Tue, 30 Nov 2004 05:51:58 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)iATIprXg061234; Tue, 30 Nov 2004 05:51:53 +1100 (EST) (envelope-from pjeremy) Date: Tue, 30 Nov 2004 05:51:52 +1100 From: Peter Jeremy To: Claudiu Dragalia-Paraipan Message-ID: <20041129185152.GF804@cirb503493.alcatel.com.au> References: <41AA0043.5070109@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AA0043.5070109@gmail.com> User-Agent: Mutt/1.4.2i cc: hackers@freebsd.org cc: current@freebsd.org Subject: Re: ssh & select() problem on 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 18:52:01 -0000 On Sun, 2004-Nov-28 18:43:47 +0200, Claudiu Dragalia-Paraipan wrote: >Since the problem occurs only when I connect to the firewall or to a >server behind it, I started to suspect a hardware failure. Could a >network card cause such problems ? A couple of people have mentioned path-MTU problems. I've also bumped into this problem when playing with VLANs where one end of the VLAN trunk doesn't support long frames - an oversize packet will get ignored by the receiver without any error being returned. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 19:55:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BABC516A4CE; Mon, 29 Nov 2004 19:55:18 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E86543D48; Mon, 29 Nov 2004 19:55:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2701A512C2; Mon, 29 Nov 2004 12:00:21 -0800 (PST) Date: Mon, 29 Nov 2004 12:00:21 -0800 From: Kris Kennaway To: phk@freeBSD.org, current@FreeBSD.org Message-ID: <20041129200020.GA8557@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Still fdesc sleep warning/lor X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 19:55:18 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sleeping on "fdesc" with the following non-sleepable locks held: exclusive sleep mutex fdesc r = 0 (0xc0740940) locked @ kern/vfs_mount.c:967 KDB: stack backtrace: witness_warn(2,c59dfe28,c06e4bf7,c06e0cbf,c076cc98) at witness_warn+0x175 msleep(c59dfe4c,c59dfe28,64,c06e0cbf,0) at msleep+0x47 checkdirs(c59e4800,f15b2ca4,c7626180,c7626180,0) at checkdirs+0xe0 dounmount(c59e4800,8080000,c7626180,43a,606ffc8) at dounmount+0x3fa unmount(c7626180,f15b2d14,8,3ff,2) at unmount+0x1f4 syscall(2f,2f,2f,804a618,bfbfe749) at syscall+0x13b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (22, FreeBSD ELF32, unmount), eip = 0x280c5a63, esp = 0xbfbfe4dc, ebp = 0xbfbfe598 --- lock order reversal 1st 0xc0740940 fdesc (fdesc) @ kern/vfs_mount.c:967 2nd 0xc07411e0 Giant (Giant) @ kern/kern_synch.c:238 KDB: stack backtrace: witness_checkorder(c07411e0,9,c06e4c08,ee,c0544222) at witness_checkorder+0x5ed _mtx_lock_flags(c07411e0,0,c06e4c08,ee,0) at _mtx_lock_flags+0x54 msleep(c59dfe4c,c59dfe28,64,c06e0cbf,0) at msleep+0x292 checkdirs(c59e4800,f15b2ca4,c7626180,c7626180,0) at checkdirs+0xe0 dounmount(c59e4800,8080000,c7626180,43a,606ffc8) at dounmount+0x3fa unmount(c7626180,f15b2d14,8,3ff,2) at unmount+0x1f4 syscall(2f,2f,2f,804a618,bfbfe749) at syscall+0x13b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (22, FreeBSD ELF32, unmount), eip = 0x280c5a63, esp = 0xbfbfe4dc, ebp = 0xbfbfe598 --- Kris --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBq3/UWry0BWjoQKURAtHNAKDwgv6uK92cTJpiU5blqwSyjj/aAgCeLzQY t8v9nWd33Ppj5JslhnABiv8= =oDX4 -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 20:07:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD3ED16A4ED for ; Mon, 29 Nov 2004 20:07:16 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A52BA43D62 for ; Mon, 29 Nov 2004 20:07:16 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 3CFB87A403; Mon, 29 Nov 2004 12:07:16 -0800 (PST) Message-ID: <41AB8174.4090205@elischer.org> Date: Mon, 29 Nov 2004 12:07:16 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Dan Nelson References: <20041128233704.GB62951@NitroPhys.welchsmnet.net> <20041129154805.GD5518@dan.emsphone.com> In-Reply-To: <20041129154805.GD5518@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: Sean Welch Subject: Re: top under 5.3-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 20:07:17 -0000 Dan Nelson wrote: >In the last episode (Nov 28), Sean Welch said: > > >>Through 5.2.1-RELEASE I've been accustomed to seeing the top few >>processes using a % of cpu that correspondes to the % free cpu value >>in the header part of the output. Ie, if the machine is 20% idle I >>expect to see the process %s to add up to roughly 80%. This seems no >>longer to be the case under 5.3-RELEASE and I'm rather confused by a >>0% idle statement with the process %s adding up to only about 15% or >>so. >> >>The amount jumps around a bit and seems to bear the relationship I >>expect when there is light load, but it looks completely wrong to me >>when there is heavy load (as in compiling a port). >> >>Can anyone explain this seeming inconsistency to me? >> >> > >For things like port builds, you end up with a lot of very short-lived >processes (sh, sed, cc, etc). Those either don't show up in top at all >becuase they have started and exited between the sampling intervals, or >else have not accumulated enough CPU time to register any %CPU (which >is a weighted average over time). > >The values should total up better when you have processes that hang >around a bit more. There was a regression in 5.3's libpthreads that >can make it report 0 CPU, so if you have some CPU-hungry threaded >programs, they may not show up in top at all even though they're using >100% cpu. libthr and libc_r report CPU correctly. > As background, libpthread assigns user threads to arbitrary kernel threads "as needed". The trouble is that if a user thread comes into the kernel, uses a kernel thread, and then exits the kernel and another user thread does the same, where can we store the info about the first thread? We have no place to store this info in libpthreads.. at least not in a form useful to 'top' and 'ps'. From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 20:18:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9796216A4CE for ; Mon, 29 Nov 2004 20:18:48 +0000 (GMT) Received: from web54605.mail.yahoo.com (web54605.mail.yahoo.com [68.142.225.189]) by mx1.FreeBSD.org (Postfix) with SMTP id 036FB43D48 for ; Mon, 29 Nov 2004 20:18:48 +0000 (GMT) (envelope-from nskyline_r35@yahoo.com) Received: (qmail 44471 invoked by uid 60001); 29 Nov 2004 20:18:47 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=QAlNchTf3FefjNZlcooRKC4Re94m4b+Jkyh7bM0Yhzxorat4+kBp1N9a18xzYRPjPmsbx2aa1u4CZXWNGMrkvujWBDNkBDqn7gT+AZ/f4c6AAAo71k3rHTJ+4Imt3bIvshpv7Hj/nMefZ/UkNXHgGkiqGgZwL6NV7c1GFxJKIlY= ; Message-ID: <20041129201847.44469.qmail@web54605.mail.yahoo.com> Received: from [82.43.51.230] by web54605.mail.yahoo.com via HTTP; Mon, 29 Nov 2004 12:18:47 PST Date: Mon, 29 Nov 2004 12:18:47 -0800 (PST) From: Nik Azim Azam To: Stephan Uphoff , "current@freebsd.org" , "i386@freebsd.org" In-Reply-To: <1101746745.11465.2838.camel@palm.tree.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: new patch for "Previous IPI is stuck" - PLEASE TEST X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 20:18:48 -0000 My computer is still up after 2 hours of intensive use. Usually it will crash after a few minutes, so I think the patch is working good. I'll report ASAP if I there is something wrong. thanks, nik. --- Stephan Uphoff wrote: > Hi, > > The last patch for Previous IPI is stuck" seems to > have fixed the > problem for all testers (Thanks for the feedback!) > and this is the > promised optimized version. > > You can download the patch at: > http://people.freebsd.org/~ups/ipi5_patch > Please make sure that exception.o is rebuild. > ( Makefile seems to miss the dependency to > apic_vector.s) > > I would like to check in the changes as soon as > possible. > However since I can not reproduce the problem > locally I will have to > wait for feedback from testers. > Thanks again to all for the positive feedback for > the last patch. > > Stephan > > __________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 20:20:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8075416A4CE for ; Mon, 29 Nov 2004 20:20:57 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8DAF43D45 for ; Mon, 29 Nov 2004 20:20:56 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 4129 invoked from network); 29 Nov 2004 20:12:28 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 29 Nov 2004 20:12:28 -0000 Message-ID: <41AB84A6.50309@freebsd.org> Date: Mon, 29 Nov 2004 21:20:54 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Jeremy References: <41AA0043.5070109@gmail.com> <20041129185152.GF804@cirb503493.alcatel.com.au> In-Reply-To: <20041129185152.GF804@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: Claudiu Dragalia-Paraipan cc: current@freebsd.org Subject: Re: ssh & select() problem on 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 20:20:57 -0000 Peter Jeremy wrote: > On Sun, 2004-Nov-28 18:43:47 +0200, Claudiu Dragalia-Paraipan wrote: > >>Since the problem occurs only when I connect to the firewall or to a >>server behind it, I started to suspect a hardware failure. Could a >>network card cause such problems ? > > A couple of people have mentioned path-MTU problems. I've also bumped > into this problem when playing with VLANs where one end of the VLAN > trunk doesn't support long frames - an oversize packet will get ignored > by the receiver without any error being returned. If the oversized ethernet frame makes it to the FreeBSD box it will drop the frame in the ethernet hardware or in ether_input() with a message. If you don't get a message on the console you have to look at the driver statistics if it got any oversized frames. If the switches along the patch can't handle the oversized frame they will simply drop it. No way to work around that. -- Andre From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 20:54:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A774716A4CE for ; Mon, 29 Nov 2004 20:54:13 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A0A143D2F for ; Mon, 29 Nov 2004 20:54:13 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iATKs8Fv090867; Mon, 29 Nov 2004 14:54:08 -0600 (CST) (envelope-from dan) Date: Mon, 29 Nov 2004 14:54:08 -0600 From: Dan Nelson To: Julian Elischer Message-ID: <20041129205408.GH5518@dan.emsphone.com> References: <20041128233704.GB62951@NitroPhys.welchsmnet.net> <20041129154805.GD5518@dan.emsphone.com> <41AB8174.4090205@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AB8174.4090205@elischer.org> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Sean Welch Subject: Re: top under 5.3-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 20:54:13 -0000 In the last episode (Nov 29), Julian Elischer said: > Dan Nelson wrote: > >The values should total up better when you have processes that hang > >around a bit more. There was a regression in 5.3's libpthreads that > >can make it report 0 CPU, so if you have some CPU-hungry threaded > >programs, they may not show up in top at all even though they're > >using 100% cpu. libthr and libc_r report CPU correctly. > > As background, libpthread assigns user threads to arbitrary kernel > threads "as needed". The trouble is that if a user thread comes into > the kernel, uses a kernel thread, and then exits the kernel and > another user thread does the same, where can we store the info about > the first thread? We have no place to store this info in > libpthreads.. at least not in a form useful to 'top' and 'ps'. Can you just add the stats to the primary kse (the one with id==pid)? That's always around as long as the process exists afaik. Any thread would do, since you can't guarantee that a thread will use the same kse twice anyway. What's annoying is seeing a CPU-bound threaded app (mysql or java, for example) showing 0 %CPU in top/ps but the TIME column incrementing 1 per second... -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 20:57:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 267A216A4D1 for ; Mon, 29 Nov 2004 20:57:10 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 328D543D49 for ; Mon, 29 Nov 2004 20:57:09 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [192.168.1.35] (ti211110a080-5666.bb.online.no [80.213.182.36]) by smtp1.powertech.no (Postfix) with ESMTP id BED2D82FD for ; Mon, 29 Nov 2004 21:57:07 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <3BE1BF5E-4249-11D9-9F7A-000A95A9A574@nordahl.net> Content-Type: text/plain; charset=US-ASCII; format=flowed To: freebsd-current@freebsd.org From: Frode Nordahl Date: Mon, 29 Nov 2004 21:57:08 +0100 X-Mailer: Apple Mail (2.619) Subject: Got rid of my SiI3112A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 20:57:11 -0000 Hello, I have at last given up on the hope that the above mentioned hardware will work any time soon, so I'm waiting for my Promise TX2200 cards to arrive tomorrow! :-) But as things are today, I think it would be best to remove support for SiI3112A. Especially since the general attitude towards it is "it's too broke, we don't want to waste any more time on it". Attempting to use it in a 5.3-RELEASE or 6-CURRENT system will most likelly make your system crash and burn, and make your data unrecoverable beyond repair. I think FreeBSD ATA subsystem rocks and beats any ATA subsystem in existance, but when we know something doesn't work with it, we should not pretend it does. Mvh, Frode Nordahl From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 21:08:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CEF816A4CF for ; Mon, 29 Nov 2004 21:08:55 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EAF643D5C for ; Mon, 29 Nov 2004 21:08:54 +0000 (GMT) (envelope-from dr.clau@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so444073rnf for ; Mon, 29 Nov 2004 13:08:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:disposition-notification-to:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:x-enigmail-version:x-enigmail-supports:content-type; b=cJQXuob9IkRZEFQnTMv/MK8zxvtdYyFTC97ukaPnfpeUlMo+bJTATknLgYvQ33d9Nxh7sRLYpm30AFwqfKmV3ucpNHEmI2RpHq6Njpwhvnt41r4o3MxylPaKWdDoJooQcSYbsmGlKkZSPPFtzRBn46T6ozuw+pZ6Vpf6qHxJyjQ= Received: by 10.38.77.63 with SMTP id z63mr114867rna; Mon, 29 Nov 2004 13:08:53 -0800 (PST) Received: from ?82.79.29.15? ([82.79.29.15]) by smtp.gmail.com with ESMTP id 70sm10953rnc; Mon, 29 Nov 2004 13:08:53 -0800 (PST) Message-ID: <41AB9022.5030901@gmail.com> Date: Mon, 29 Nov 2004 23:09:54 +0200 From: Claudiu Dragalia-Paraipan User-Agent: Mozilla Thunderbird 0.9 (X11/20041125) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <41AA0043.5070109@gmail.com> <20041129185152.GF804@cirb503493.alcatel.com.au> In-Reply-To: <20041129185152.GF804@cirb503493.alcatel.com.au> X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFAD6BFDC713378300120853E" Subject: Re: ssh & select() problem on 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 21:08:55 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFAD6BFDC713378300120853E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Peter Jeremy wrote: > On Sun, 2004-Nov-28 18:43:47 +0200, Claudiu Dragalia-Paraipan wrote: > >>Since the problem occurs only when I connect to the firewall or to a >>server behind it, I started to suspect a hardware failure. Could a >>network card cause such problems ? > > > A couple of people have mentioned path-MTU problems. I've also bumped > into this problem when playing with VLANs where one end of the VLAN > trunk doesn't support long frames - an oversize packet will get ignored > by the receiver without any error being returned. > It seems that packets of size more then 1478 are dropped somewhere, but not on the FreeBSD Firewall. The problem seems to be that it never receives a ICMP "fragmentation needed but DF set". Unfortunately I have control only over the firewall and what's behind it. Next after the firewall (towards internet) there are a switch and a Cisco router. I asked about the settings of this two, and it seems that the switch is used for VLANs, and the Cisco for making a tunnel over fiber channel with the next hop. I have too few information about this at the moment, but I am almost certain that the problems are occuring because of the Cisco router. I did a traceroute from the firewall to outside, and big packets always stop on Cisco router. A traceroute from outside to the firewall always stops at the hop exactly before the cisco router I am talking about, which I suppose is the other end of this tunnel. -- Claudiu Dragalina-Paraipan dr.clau@gmail.com --------------enigFAD6BFDC713378300120853E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBq5Aqm0FWxb+swkQRAoi9AKCIL8aYR5UcEIVvjRk+nBDAnjf7tgCdEUdr GC2k26dN32dHKhG+igINyWg= =E0Qm -----END PGP SIGNATURE----- --------------enigFAD6BFDC713378300120853E-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 21:14:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02ABC16A4CE for ; Mon, 29 Nov 2004 21:14:58 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D31DC43D60 for ; Mon, 29 Nov 2004 21:14:57 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id AD4897A41E; Mon, 29 Nov 2004 13:14:57 -0800 (PST) Message-ID: <41AB9151.8070601@elischer.org> Date: Mon, 29 Nov 2004 13:14:57 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Dan Nelson References: <20041128233704.GB62951@NitroPhys.welchsmnet.net> <20041129154805.GD5518@dan.emsphone.com> <41AB8174.4090205@elischer.org> <20041129205408.GH5518@dan.emsphone.com> In-Reply-To: <20041129205408.GH5518@dan.emsphone.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: Sean Welch Subject: Re: top under 5.3-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 21:14:58 -0000 Dan Nelson wrote: >In the last episode (Nov 29), Julian Elischer said: > > >>Dan Nelson wrote: >> >> >>>The values should total up better when you have processes that hang >>>around a bit more. There was a regression in 5.3's libpthreads that >>>can make it report 0 CPU, so if you have some CPU-hungry threaded >>>programs, they may not show up in top at all even though they're >>>using 100% cpu. libthr and libc_r report CPU correctly. >>> >>> >>As background, libpthread assigns user threads to arbitrary kernel >>threads "as needed". The trouble is that if a user thread comes into >>the kernel, uses a kernel thread, and then exits the kernel and >>another user thread does the same, where can we store the info about >>the first thread? We have no place to store this info in >>libpthreads.. at least not in a form useful to 'top' and 'ps'. >> >> > >Can you just add the stats to the primary kse (the one with id==pid)? > there is no "primary KSE" There is a ksegrp associated with every group of threads that could aggregate this information for all threads under its umbrella, but ps and top don't know about it. >That's always around as long as the process exists afaik. > nope.. once you have switched to threading mode, all threads are the same and the original thread is just as likely as any other thread, to be declared "surplus" and discarded when teh process requires less kernel threads. > Any thread >would do, since you can't guarantee that a thread will use the same kse >twice anyway. What's annoying is seeing a CPU-bound threaded app >(mysql or java, for example) showing 0 %CPU in top/ps but the TIME >column incrementing 1 per second... > understood.. but when 'ps' gets the information, it gets each thread.. where does the info get stored? the threads may have just flashed into existence a fraction of a second ago, and prior to that thay may have belonged to a compeltely different process. It's not a simple problem. However there may be some relatively "ok" answers if we can define well enough what we want to see. For example all taking the total cputime for the KSEGRP and dividing it by the number of non-sleeping threads might be a possibility. (or some variant of that). > > > From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 21:21:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D86F16A4D6 for ; Mon, 29 Nov 2004 21:21:29 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6619A43D54 for ; Mon, 29 Nov 2004 21:21:27 +0000 (GMT) (envelope-from dr.clau@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so445134rnf for ; Mon, 29 Nov 2004 13:21:25 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:disposition-notification-to:date:from:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:x-enigmail-supports:content-type; b=EeYffCaRgMmQHOAeBJ1SYkbjCypwLKdw6+LfPfMOkXigTlYyaqi32mxA5CAnnW7s9mf7N9CK76tKsEx/yKzZK1VsoOzjF30qBj7KvnNgShtGS3eip6+X5hKngKsiibB4BBcwCXARdd0CAw+YQdpiPR8lFix6Qug3I5XlXR3FYVw= Received: by 10.38.77.63 with SMTP id z63mr117320rna; Mon, 29 Nov 2004 13:21:24 -0800 (PST) Received: from ?82.79.29.15? ([82.79.29.15]) by smtp.gmail.com with ESMTP id 70sm11174rnc; Mon, 29 Nov 2004 13:21:24 -0800 (PST) Message-ID: <41AB926F.30003@gmail.com> Date: Mon, 29 Nov 2004 23:19:43 +0200 From: Claudiu Dragalia-Paraipan User-Agent: Mozilla Thunderbird 0.9 (X11/20041125) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Oppermann References: <41AA0043.5070109@gmail.com> <20041129185152.GF804@cirb503493.alcatel.com.au> <41AB84A6.50309@freebsd.org> In-Reply-To: <41AB84A6.50309@freebsd.org> X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig07BB196C97858DA16AF839F1" cc: Peter Jeremy cc: hackers@freebsd.org cc: current@freebsd.org Subject: Re: ssh & select() problem on 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 21:21:29 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig07BB196C97858DA16AF839F1 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Andre Oppermann wrote: > Peter Jeremy wrote: > >> On Sun, 2004-Nov-28 18:43:47 +0200, Claudiu Dragalia-Paraipan wrote: >> >>> Since the problem occurs only when I connect to the firewall or to a >>> server behind it, I started to suspect a hardware failure. Could a >>> network card cause such problems ? >> >> >> A couple of people have mentioned path-MTU problems. I've also bumped >> into this problem when playing with VLANs where one end of the VLAN >> trunk doesn't support long frames - an oversize packet will get ignored >> by the receiver without any error being returned. > > > If the oversized ethernet frame makes it to the FreeBSD box it will drop > the frame in the ethernet hardware or in ether_input() with a message. If > you don't get a message on the console you have to look at the driver > statistics if it got any oversized frames. > > If the switches along the patch can't handle the oversized frame they will > simply drop it. No way to work around that. > When the MTU is set to a value below 1500, for example 1450, I get this messages: Nov 29 23:02:34 firewall kernel: rl0: discard oversize frame (ether type 800 flags 3 len 1466 > max 1464) Nov 29 23:03:00 firewall kernel: rl0: discard oversize frame (ether type 800 flags 3 len 1514 > max 1464) ... and much many of them. With MTU 1500 I didn't notice any such message in logs. So, can I safely assume that the problem occurs because somewhere packets are simply dropped, without any warning ? -- Claudiu Dragalina-Paraipan dr.clau@gmail.com --------------enig07BB196C97858DA16AF839F1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBq5Jvm0FWxb+swkQRAuCdAJ9rm+kLUMtczXxU6u9BJ560p13YQgCfcmyO M7Vj5ns5mS/Njs5t5uZuYx8= =WLTQ -----END PGP SIGNATURE----- --------------enig07BB196C97858DA16AF839F1-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 21:40:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0ECC316A4CE for ; Mon, 29 Nov 2004 21:40:50 +0000 (GMT) Received: from av1-1-sn4.m-sp.skanova.net (av1-1-sn4.m-sp.skanova.net [81.228.10.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5C6243D55 for ; Mon, 29 Nov 2004 21:40:49 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av1-1-sn4.m-sp.skanova.net (Postfix, from userid 502) id EACAF37F07; Mon, 29 Nov 2004 22:40:48 +0100 (CET) Received: from smtp2-2-sn4.m-sp.skanova.net (smtp2-2-sn4.m-sp.skanova.net [81.228.10.182]) by av1-1-sn4.m-sp.skanova.net (Postfix) with ESMTP id DCA6C37EBF; Mon, 29 Nov 2004 22:40:48 +0100 (CET) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp2-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id BCD5A37E5A; Mon, 29 Nov 2004 22:40:48 +0100 (CET) From: "Daniel Eriksson" To: "'Frode Nordahl'" , Date: Mon, 29 Nov 2004 22:40:41 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <3BE1BF5E-4249-11D9-9F7A-000A95A9A574@nordahl.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTWViKlTvRrCGu7T4O7kOYpCkRJdAABJ/Og Subject: RE: Got rid of my SiI3112A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 21:40:50 -0000 Frode Nordahl wrote: > But as things are today, I think it would be best to remove > support for > SiI3112A. Especially since the general attitude towards it is > "it's too > broke, we don't want to waste any more time on it". > > Attempting to use it in a 5.3-RELEASE or 6-CURRENT system will most > likelly make your system crash and burn, and make your data > unrecoverable beyond repair. I will have to agree with Frode on this one. I recently put -CURRENT on a machine with an ASUS mobo that had a SiL 3112 controller. Hooking up two 250GB WD discs to it quickly resulted in timeouts, followed by some strange messages from geom_stripe (used it to stripe the two discs), followed by filesystem corruption and panics. I tried all the "normal" things, such as running with/without ACPI & APIC, moving other PCI cards around to ensure it wasn't a ithread sharing problem, removing PREEMPTION from the kernel, ... To me it looks like SiL 3112 support is bad enough that it could hurt FreeBSD's reputation. At the very least there should be some warnings in places you cannot miss that it might fry your data. (I was expecting problems, so I really didn't loose anything important.) /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 23:32:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B515A16A4CE; Mon, 29 Nov 2004 23:32:11 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C6C443D5C; Mon, 29 Nov 2004 23:32:11 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iATNWBZ8027472; Mon, 29 Nov 2004 15:32:11 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iATNWBKo027471; Mon, 29 Nov 2004 15:32:11 -0800 (PST) (envelope-from sgk) Date: Mon, 29 Nov 2004 15:32:11 -0800 From: Steve Kargl To: freebsd-amd64@freebsd.org Message-ID: <20041129233211.GA27426@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041129211341.GA26548@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 23:32:11 -0000 On Mon, Nov 29, 2004 at 01:13:41PM -0800, Steve Kargl wrote: > kmem_suballoc: bad status return of 3 > panic: kmem_suballoc > cpuid = 0 > KDB: stack backtrace: > kdb_backtrace() at kdb_backtrace+0x37 > panic() at painc+0x1d1 > kmem_suballoc() at kmem_suballoc+0x93 > kmeminit() at kmeminit+0x16d > mi_startuup() at mi_startup+0xb6 > btext90 at btext+0x2c > KDB: enter: panic > [thread pid 0 tid 0] > > This is a Tyan K8S Pro motherboard with 16 GB of PC2700 > Cosair ECC memory. The BIOS was flashed to the latest > available from Tyan. The scheduler is 4BSD. There are > no ATA devices in the system and no ATA subsystem in > the kernel. This a SCSI only box. World and kernel > were rebuilt today with CFLAGS=-O -pipe and > COPTFLAGS=-O -pipe. > > If I set hw.physmem="#G" n /boot/loader.conf where # is > less than or equal to 8 the box boots up (see dmesg below). > If # > 8, then we have the above panic. > > Any ideas where to look for the a fix? > (dmesg snipped) (CC'd to -current because the may impact any system with >8 GB of ram) As a data point, I've downloaded, burned, and booted the netbsd/amd64 ISO image. Netbsd's dmesg shows that netbsd correctly finds 16 GB of memory on the system. -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 02:14:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2131C16A4CE; Tue, 30 Nov 2004 02:14:59 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 892E843D2F; Tue, 30 Nov 2004 02:14:58 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAU2Esc9016136; Mon, 29 Nov 2004 21:14:54 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iAU2ErhZ081790; Mon, 29 Nov 2004 21:14:53 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 906EF7306E; Mon, 29 Nov 2004 21:14:54 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041130021454.906EF7306E@freebsd-current.sentex.ca> Date: Mon, 29 Nov 2004 21:14:54 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 02:14:59 -0000 TB --- 2004-11-30 01:00:31 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-30 01:00:31 - starting CURRENT tinderbox run for i386/i386 TB --- 2004-11-30 01:00:31 - checking out the source tree TB --- 2004-11-30 01:00:31 - cd /home/tinderbox/CURRENT/i386/i386 TB --- 2004-11-30 01:00:31 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-30 01:06:56 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-30 01:06:56 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-11-30 01:06:56 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-30 02:13:35 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-30 02:13:35 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-11-30 02:13:35 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Nov 30 02:13:35 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] awk -f /tinderbox/CURRENT/i386/i386/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/i386/i386/src/sys/isa/isa_if.m -h awk -f /tinderbox/CURRENT/i386/i386/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/i386/i386/src/sys/pci/agp_if.m -h awk -f /tinderbox/CURRENT/i386/i386/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/i386/i386/src/sys/dev/acpica/acpi_if.m -h if [ -f .olddep ]; then mv .olddep .depend; fi rm -f .newdep /home/tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/make.i386/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/i386/i386/src/sys -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/altq -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/pf -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-bounda ry=2 -ffreestanding /tinderbox/CURRENT/i386/i386/src/sys/kern/subr_param.c:59:2: #endif without #if mkdep: compile failed *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. TB --- 2004-11-30 02:14:54 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-30 02:14:54 - ERROR: failed to build generic kernel TB --- 2004-11-30 02:14:54 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 02:58:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1602116A4CE; Tue, 30 Nov 2004 02:58:03 +0000 (GMT) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.150.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B61843D5D; Tue, 30 Nov 2004 02:57:59 +0000 (GMT) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id 049E24EFCDD; Tue, 30 Nov 2004 10:57:50 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id 0031E4EFCDC; Tue, 30 Nov 2004 10:57:50 +0800 (CST) Date: Tue, 30 Nov 2004 10:57:50 +0800 (CST) From: Tai-hwa Liang To: peter@freebsd.org In-Reply-To: <20041130021454.906EF7306E@freebsd-current.sentex.ca> Message-ID: <0411301053530.66150@www.mmlab.cse.yzu.edu.tw> References: <20041130021454.906EF7306E@freebsd-current.sentex.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: current@freebsd.org cc: i386@freebsd.org Subject: Re: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 02:58:03 -0000 Looks like src/sys/kern/subr_param.c:1.68 breaks the build. Would someone please commit following patch? --- sys/kern/subr_param.c Tue Nov 30 10:37:15 2004 +++ sys/kern/subr_param.c.orig Tue Nov 30 10:49:34 2004 @@ -51,11 +51,11 @@ */ #ifndef HZ -# elif defined(__amd64__) || defined(__i386__) || defined(__ia64__) +# if defined(__amd64__) || defined(__i386__) || defined(__ia64__) # define HZ 1000 # else # define HZ 100 -#endif +# endif #endif #define NPROC (20 + 16 * maxusers) #ifndef NBUF On Mon, 29 Nov 2004, FreeBSD Tinderbox wrote: [...] > awk -f /tinderbox/CURRENT/i386/i386/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/i386/i386/src/sys/pci/agp_if.m -h > awk -f /tinderbox/CURRENT/i386/i386/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/i386/i386/src/sys/dev/acpica/acpi_if.m -h > if [ -f .olddep ]; then mv .olddep .depend; fi > rm -f .newdep > /home/tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/make.i386/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/i386/i386/src/sys -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/altq -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/pf -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boun da > ry=2 -ffreestanding > /tinderbox/CURRENT/i386/i386/src/sys/kern/subr_param.c:59:2: #endif without #if > mkdep: compile failed > *** Error code 1 > > Stop in /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/GENERIC. > *** Error code 1 > > Stop in /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/GENERIC. > *** Error code 1 > > Stop in /tinderbox/CURRENT/i386/i386/src. > *** Error code 1 > > Stop in /tinderbox/CURRENT/i386/i386/src. > TB --- 2004-11-30 02:14:54 - WARNING: /usr/bin/make returned exit code 1 > TB --- 2004-11-30 02:14:54 - ERROR: failed to build generic kernel > TB --- 2004-11-30 02:14:54 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 03:25:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 697AF16A4CE; Tue, 30 Nov 2004 03:25:10 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1D5843D1F; Tue, 30 Nov 2004 03:25:09 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id BC71F651F4; Tue, 30 Nov 2004 03:25:07 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 61582-05-4; Tue, 30 Nov 2004 03:25:07 +0000 (GMT) Received: from empiric.dek.spc.org (dhcp120.icir.org [192.150.187.120]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id E5ED0651EE; Tue, 30 Nov 2004 03:24:59 +0000 (GMT) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id 393F46710; Mon, 29 Nov 2004 19:24:54 -0800 (PST) Date: Mon, 29 Nov 2004 19:24:53 -0800 From: Bruce M Simpson To: Tai-hwa Liang Message-ID: <20041130032453.GC61236@empiric.icir.org> References: <20041130021454.906EF7306E@freebsd-current.sentex.ca> <0411301053530.66150@www.mmlab.cse.yzu.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0411301053530.66150@www.mmlab.cse.yzu.edu.tw> cc: current@freebsd.org cc: peter@freebsd.org cc: i386@freebsd.org Subject: Re: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 03:25:10 -0000 On Tue, Nov 30, 2004 at 10:57:50AM +0800, Tai-hwa Liang wrote: > Looks like src/sys/kern/subr_param.c:1.68 breaks the build. Would someone > please commit following patch? Bandaid committed, thanks. BMS From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 03:29:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E048716A4CE; Tue, 30 Nov 2004 03:29:34 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36F7143D49; Tue, 30 Nov 2004 03:29:33 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAU3TWI6026961; Mon, 29 Nov 2004 22:29:32 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iAU3TVZn012338; Mon, 29 Nov 2004 22:29:31 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 1ED4A7306E; Mon, 29 Nov 2004 22:29:32 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041130032932.1ED4A7306E@freebsd-current.sentex.ca> Date: Mon, 29 Nov 2004 22:29:32 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 03:29:35 -0000 TB --- 2004-11-30 02:14:54 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-30 02:14:54 - starting CURRENT tinderbox run for i386/pc98 TB --- 2004-11-30 02:14:54 - checking out the source tree TB --- 2004-11-30 02:14:54 - cd /home/tinderbox/CURRENT/i386/pc98 TB --- 2004-11-30 02:14:54 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-30 02:21:32 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-30 02:21:32 - cd /home/tinderbox/CURRENT/i386/pc98/src TB --- 2004-11-30 02:21:32 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-30 03:28:24 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-30 03:28:24 - cd /home/tinderbox/CURRENT/i386/pc98/src TB --- 2004-11-30 03:28:24 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Nov 30 03:28:24 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] awk -f /tinderbox/CURRENT/i386/pc98/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/i386/pc98/src/sys/dev/pci/pcib_if.m -h awk -f /tinderbox/CURRENT/i386/pc98/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/i386/pc98/src/sys/dev/ppbus/ppbus_if.m -h awk -f /tinderbox/CURRENT/i386/pc98/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/i386/pc98/src/sys/isa/isa_if.m -h if [ -f .olddep ]; then mv .olddep .depend; fi rm -f .newdep /home/tinderbox/CURRENT/i386/pc98/obj/tinderbox/CURRENT/i386/pc98/src/make.i386/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/i386/pc98/src/sys -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/altq -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/pf -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-bounda ry=2 -ffreestanding /tinderbox/CURRENT/i386/pc98/src/sys/kern/subr_param.c:59:2: #endif without #if mkdep: compile failed *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/obj/pc98/tinderbox/CURRENT/i386/pc98/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/obj/pc98/tinderbox/CURRENT/i386/pc98/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src. TB --- 2004-11-30 03:29:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-30 03:29:31 - ERROR: failed to build generic kernel TB --- 2004-11-30 03:29:31 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 03:56:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99BEA16A4CE; Tue, 30 Nov 2004 03:56:01 +0000 (GMT) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDBA843D1D; Tue, 30 Nov 2004 03:56:00 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.12.11/8.12.11) with ESMTP id iAU3tsQR033034; Mon, 29 Nov 2004 20:55:54 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.12.11/8.12.5/Submit) id iAU3tqjI033033; Mon, 29 Nov 2004 20:55:52 -0700 (MST) (envelope-from ken) Date: Mon, 29 Nov 2004 20:55:52 -0700 From: "Kenneth D. Merry" To: current@FreeBSD.org Message-ID: <20041130035552.GA32924@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="J2SCkAp4GZ/dPZZf" Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on nargothrond.kdm.org X-Virus-Status: Clean cc: rwatson@FreeBSD.org cc: alc@cs.rice.edu cc: gallatin@cs.duke.edu Subject: -current hang during boot on SMP machine X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 03:56:01 -0000 --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I'm trying to get -current (from Friday, November 26th 2004) online on a dual 1GHz Pentium III box. It hangs during boot, normal dmesg, bootverbose dmesg and the kernel config file are attached. (bootverbose dmesg is right after the normal dmesg.) The last line printed prior to the hang is: pci_link0: irq 10 on acpi0 It currently runs 4.x fine on a separate disk. (I built -current on the 4.x disk, and installed it on top of a 2 year old -current on the other disk.) It's a Supermicro 370DE6 motherboard (Serverworks chipset) with 2 1GHz Pentium IIIs. It has 2.5GB RAM, and is booting from an onboard Adaptec 7899. Thanks for any help, Ken -- Kenneth Merry ken@FreeBSD.ORG --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="session.log.boot_hang.gondolin.20041129.txt" /boot/kernel/kernel text=0x412e54 data=0x6a524+0x39dfc syms=[0x4+0x527b0+0x4+0x664ff] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 9 seconds... Booting [/boot/kernel/kernel] in 8 seconds... Booting [/boot/kernel/kernel] in 7 seconds... Booting [/boot/kernel/kernel] in 6 seconds... Booting [/boot/kernel/kernel] in 5 seconds... Booting [/boot/kernel/kernel]... /boot/kernel/acpi.ko text=0x3fc3c data=0x1d24+0x110c syms=[0x4+0x73f0+0x4+0x9986] Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-CURRENT #2: Fri Nov 26 23:49:42 MST 2004 ken@gondolin.kdm.org:/usr/obj/usr/home/ken/perforce3/FreeBSD-ken/src/sys/gondolin ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (999.53-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383fbff real memory = 2684289024 (2559 MB) avail memory = 2624294912 (2502 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ACPI-0697: *** Warning: Type override - [DEB_] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [MLIB] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [IO__] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [DATA] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [SIO_] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [SB__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [PM__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [ICNT] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [ACPI] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [OSB4] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [PM__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [BIOS] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [CMOS] had invalid type (Integer) for Scope operator, changed to (Scope) MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard netsmb_dev: loaded npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu1: Failed to attach throttling P_CNT acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci_link0: irq 10 on acpi0 /boot/kernel/kernel text=0x412e54 data=0x6a524+0x39dfc syms=[0x4+0x527b0+0x4+0x664ff] Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 9 seconds... Type '?' for a list of commands, 'help' for more detailed help. OK boot -v /boot/kernel/acpi.ko text=0x3fc3c data=0x1d24+0x110c syms=[0x4+0x73f0+0x4+0x9986] SMAP type=01 base=0000000000000000 len=000000000009fc00 SMAP type=02 base=000000000009fc00 len=0000000000000400 SMAP type=02 base=00000000000e0000 len=0000000000020000 SMAP type=01 base=0000000000100000 len=000000009fef0000 SMAP type=03 base=000000009fff0000 len=000000000000f000 SMAP type=04 base=000000009ffff000 len=0000000000001000 SMAP type=02 base=00000000fec00000 len=0000000000001000 SMAP type=02 base=00000000fec01000 len=0000000000001000 SMAP type=02 base=00000000fee00000 len=0000000000001000 SMAP type=02 base=00000000fff80000 len=0000000000080000 Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-CURRENT #2: Fri Nov 26 23:49:42 MST 2004 ken@gondolin.kdm.org:/usr/obj/usr/home/ken/perforce3/FreeBSD-ken/src/sys/gondolin Preloaded elf kernel "/boot/kernel/kernel" at 0xc09c6000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc09c61a8. Table 'FACP' at 0x9fff0030 Table 'APIC' at 0x9fff00b0 MADT: Found table at 0x9fff00b0 MP Configuration Table version 1.4 found at 0xc00f0c40 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 1 ACPI ID 1: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 0 ACPI ID 2: disabled MADT: Found CPU APIC ID 0 ACPI ID 3: disabled ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193255 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 999531190 Hz CPU: Intel Pentium III (999.53-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383fbff real memory = 2684289024 (2559 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c28000 - 0x000000009d2bffff, 2624159744 bytes (640664 pages) avail memory = 2624294912 (2502 MB) APIC ID: physical 0, logical 0:0 APIC ID: physical 1, logical 0:1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): AP0 cpu1 (AP): APIC ID: 1 bios32: Found BIOS32 Service Directory header at 0xc00fdb80 bios32: Entry = 0xfdb90 (c00fdb90) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xdbb1 pnpbios: Found PnP BIOS data at 0xc00f4d70 pnpbios: Entry = f0000:3cf4 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 ACPI-0697: *** Warning: Type override - [DEB_] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [MLIB] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [IO__] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [DATA] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [SIO_] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [SB__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [PM__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [ICNT] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [ACPI] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [OSB4] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [PM__] had invalid type (String) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [BIOS] had invalid type (Integer) for Scope operator, changed to (Scope) ACPI-0697: *** Warning: Type override - [CMOS] had invalid type (Integer) for Scope operator, changed to (Scope) MADT: Found IO APIC ID 4, Interrupt 0 at 0xfec00000 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: intpin 0 -> ExtINT (edge, high) ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) MADT: Found IO APIC ID 5, Interrupt 16 at 0xfec01000 ioapic1: intpin 0 -> PCI IRQ 16 (level, low) ioapic1: intpin 1 -> PCI IRQ 17 (level, low) ioapic1: intpin 2 -> PCI IRQ 18 (level, low) ioapic1: intpin 3 -> PCI IRQ 19 (level, low) ioapic1: intpin 4 -> PCI IRQ 20 (level, low) ioapic1: intpin 5 -> PCI IRQ 21 (level, low) ioapic1: intpin 6 -> PCI IRQ 22 (level, low) ioapic1: intpin 7 -> PCI IRQ 23 (level, low) ioapic1: intpin 8 -> PCI IRQ 24 (level, low) ioapic1: intpin 9 -> PCI IRQ 25 (level, low) ioapic1: intpin 10 -> PCI IRQ 26 (level, low) ioapic1: intpin 11 -> PCI IRQ 27 (level, low) ioapic1: intpin 12 -> PCI IRQ 28 (level, low) ioapic1: intpin 13 -> PCI IRQ 29 (level, low) ioapic1: intpin 14 -> PCI IRQ 30 (level, low) ioapic1: intpin 15 -> PCI IRQ 31 (level, low) MADT: intr override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high MADT: Forcing active-low polarity and level trigger for SCI ioapic0: intpin 9 polarity: low ioapic0: intpin 9 trigger: level ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00040011 LDR: 0x01000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff crypto: mem: Pentium Pro MTRR support enabled null: netsmb_dev: loaded random: io: npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] acpi0: Power Button (fixed) pci_open(1): mode 1 addr port (0x0cf8) is 0x80000070 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00081166) pcibios: BIOS version 2.10 Found $PIR table, 10 entries at 0xc00f52e0 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded 0 0 A 0x1e 3 4 5 7 9 10 11 12 14 15 embedded 0 0 B 0x1e 3 4 5 7 9 10 11 12 14 15 embedded 0 15 A 0x01 10 slot 1 0 1 A 0x10 3 4 5 7 9 10 11 12 14 15 slot 1 0 1 B 0x11 3 4 5 7 9 10 11 12 14 15 slot 1 0 1 C 0x10 3 4 5 7 9 10 11 12 14 15 slot 1 0 1 D 0x11 3 4 5 7 9 10 11 12 14 15 slot 2 0 2 A 0x12 3 4 5 7 9 10 11 12 14 15 slot 2 0 2 B 0x13 3 4 5 7 9 10 11 12 14 15 slot 2 0 2 C 0x12 3 4 5 7 9 10 11 12 14 15 slot 2 0 2 D 0x13 3 4 5 7 9 10 11 12 14 15 slot 3 0 3 A 0x14 3 4 5 7 9 10 11 12 14 15 slot 3 0 3 B 0x15 3 4 5 7 9 10 11 12 14 15 slot 3 0 3 C 0x14 3 4 5 7 9 10 11 12 14 15 slot 3 0 3 D 0x15 3 4 5 7 9 10 11 12 14 15 slot 4 0 4 A 0x1c 3 4 5 7 9 10 11 12 14 15 slot 4 0 4 B 0x1d 3 4 5 7 9 10 11 12 14 15 slot 4 0 4 C 0x1c 3 4 5 7 9 10 11 12 14 15 slot 4 0 4 D 0x1d 3 4 5 7 9 10 11 12 14 15 embedded 0 5 A 0x1a 3 4 5 7 9 10 11 12 14 15 embedded 0 5 B 0x1b 3 4 5 7 9 10 11 12 14 15 embedded 0 5 C 0xff 3 4 5 7 9 10 11 12 14 15 embedded 0 5 D 0xff 3 4 5 7 9 10 11 12 14 15 embedded 0 6 A 0x1f 3 4 5 7 9 10 11 12 14 15 embedded 0 6 B 0xff 3 4 5 7 9 10 11 12 14 15 embedded 0 6 C 0xff 3 4 5 7 9 10 11 12 14 15 embedded 0 6 D 0xff 3 4 5 7 9 10 11 12 14 15 slot 5 2 1 A 0x16 3 4 5 7 9 10 11 12 14 15 slot 5 2 1 B 0x17 3 4 5 7 9 10 11 12 14 15 slot 5 2 1 C 0x16 3 4 5 7 9 10 11 12 14 15 slot 5 2 1 D 0x17 3 4 5 7 9 10 11 12 14 15 slot 6 2 2 A 0x18 3 4 5 7 9 10 11 12 14 15 slot 6 2 2 B 0x19 3 4 5 7 9 10 11 12 14 15 slot 6 2 2 C 0x18 3 4 5 7 9 10 11 12 14 15 slot 6 2 2 D 0x19 3 4 5 7 9 10 11 12 14 15 AcpiOsDerivePciId: bus 0 dev 0 func 0 AcpiOsDerivePciId: bus 0 dev 0 func 2 AcpiOsDerivePciId: bus 0 dev 0 func 3 ACPI timer: 0/59 0/4 0/11 0/4 0/63 0/27 0/11 0/4 0/4 0/3 -> 0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu1: Failed to attach throttling P_CNT acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci_link0: irq 10 on acpi0 --J2SCkAp4GZ/dPZZf Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=gondolin # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the NOTES configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.332 2001/12/14 16:27:08 iedowse Exp $ machine i386 cpu I586_CPU cpu I686_CPU ident gondolin maxusers 0 #To statically compile in device wiring instead of /boot/device.hints #hints "gondolin.hints" #Default places to look for devices. makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options SCHED_4BSD #4BSD scheduler options INET #InterNETworking options INET6 #IPv6 communications protocols options FAST_IPSEC #new IPsec (cannot define w/ IPSEC) options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options DUMMYNET options IPV6FIREWALL #firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPDIVERT #divert sockets options NETSMB #SMB/CIFS requester options NETSMBCRYPTO #encrypted password support for SMB options LIBMCHAIN options LIBICONV options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options MD_ROOT #MD is a potential root device options NFSCLIENT #Network Filesystem Client options NFSSERVER #Network Filesystem Server options NFS_ROOT #NFS usable as root device, requires NFSCLIENT options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS #Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 #options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI #options USERCONFIG #boot -c editor #options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV # install a CDEV entry in /dev options AHC_ALLOW_MEMIO options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options CONSPEED=115200 options CAMDEBUG options COMPAT_LINUX options COMPAT_AOUT # Zero copy options options ZERO_COPY_SOCKETS options MCLSHIFT=12 # 4k (page size) mbuf clusters #options MSIZE=256 # 256byte mbufs options TI_JUMBO_HDRSPLIT #options NMBCLUSTERS=(512+512*32) device crypto # core crypto support device cryptodev # /dev/crypto for access to h/w # Debugging for use in -current # options DDB #Enable the kernel debugger # options DDB_UNATTENDED #options INVARIANTS #Enable calls of extra sanity checking #options INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS #options WITNESS #Enable mutex checks to detects deadlocks and cycles #options WITNESS_SKIPSPIN #Don't run witness on spinlocks for speed #options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to #DDB, if available. options CONSPEED=115200 # speed for serial console # (default 9600) # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel device apic # I/O APIC device isa #device eisa device pci #options PCI_ENABLE_IO_MODES # Enable pci resources left off by a "lazy BIOS" # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering device atapicam # emulate ATAPI devices as SCSI ditto via CAM # needs CAM to be present (scbus & pass) # SCSI Controllers #device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device ahd # AHA39320/29320 and onboard AIC79xx devices device isp # Qlogic family device ispfw # Qlogic family # RAID controllers interfaced to the SCSI subsystem device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID device dpt # DPT Smartcache III, IV - See NOTES for options! # SCSI peripherals device scbus # SCSI bus (required) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers device aac # Adaptec FSA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # At keyboard controller device atkbd # at keyboard device psm # psm mouse device vga # VGA screen device smbus # Bus support, required for smb below. device intpm device ichsmb device smb device bktr device iicbus # Bus support, required for ic/iic/iicsmb below. device iicbb device ic device iic device iicsmb # smb over i2c bridge device sound device snd_emu10k1 # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) device apm # Add suspend/resume support for the i8254. device pmtimer # PCCARD (PCMCIA) support # device card # pccard bus # device pcic # PCMCIA bridge # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device em # Intel PRO/1000 adapter Gigabit Ethernet Card device ti # Alteon Networks Tigon I/II gigabit ethernet # Pseudo devices - the number indicates how many units to allocate. device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device ccd #Concatenated disk driver #device gif # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device urio # Diamond Rio 500 MP3 player device uscanner # Scanners # USB Ethernet, requires mii device aue # ADMtek USB ethernet device axe # ASIX Electronics USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet # FireWire support device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) --J2SCkAp4GZ/dPZZf-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 04:20:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B428516A4CE for ; Tue, 30 Nov 2004 04:20:57 +0000 (GMT) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E36043D31 for ; Tue, 30 Nov 2004 04:20:57 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 65EF8651EE for ; Tue, 30 Nov 2004 04:20:56 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 62607-02 for ; Tue, 30 Nov 2004 04:20:55 +0000 (GMT) Received: from empiric.dek.spc.org (dhcp120.icir.org [192.150.187.120]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id 86A16651EB for ; Tue, 30 Nov 2004 04:20:55 +0000 (GMT) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id 396D06710; Mon, 29 Nov 2004 20:20:53 -0800 (PST) Date: Mon, 29 Nov 2004 20:20:52 -0800 From: Bruce M Simpson To: freebsd-current@freebsd.org Message-ID: <20041130042052.GD61236@empiric.icir.org> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EDJsL2R9iCFAt7IV" Content-Disposition: inline Subject: fsck/mount breakage in -current since 25th (/usr affected) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 04:20:57 -0000 --EDJsL2R9iCFAt7IV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, This issue has already been reported by mkm@ so apologies if this is a duplicate, thought I should chime in too. The mount code reports that /usr is not clean, yet fsck claims to have marked /usr clean after its usual post-boot background preen (even if I am dropped into single-user mode, unmount, and force a foreground fsck). Therefore multi-user mode boot fails. mkm@ reports this issue since the 25th Nov. I only noticed it today. The workaround which mkm@ and I are currently using is to add the -f flag to /etc/rc.d/mountcritlocal - this is not desirable for many reasons! Can anyone advise on resolution of the problem? Many thanks, BMS --EDJsL2R9iCFAt7IV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: '' iD8DBQFBq/UkueUpAYYNtTsRAlIyAJwN+xuj78oSfH61R2KRMj9V+bjakQCfTjxm F2sBvImX3RTLd8QPv/2cPmw= =TDA/ -----END PGP SIGNATURE----- --EDJsL2R9iCFAt7IV-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 04:32:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00D7816A4CE for ; Tue, 30 Nov 2004 04:32:57 +0000 (GMT) Received: from omoikane.mb.skyweb.ca (omoikane.mb.skyweb.ca [64.42.246.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6671243D55 for ; Tue, 30 Nov 2004 04:32:57 +0000 (GMT) (envelope-from mark@skyweb.ca) Received: by omoikane.mb.skyweb.ca (Postfix, from userid 1001) id 07CC061E9B; Mon, 29 Nov 2004 22:32:56 -0600 (CST) From: Mark Johnston To: current@freebsd.org, freebsd-cvs-summary@lists.enderunix.org Date: Mon, 29 Nov 2004 22:32:56 -0600 User-Agent: KMail/1.6.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200411292232.56344.mjohnston@skyweb.ca> Subject: cvs-src summary for November 22-29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 04:32:58 -0000 FreeBSD cvs-src summary for 22/11/04 to 29/11/04 ++++++++++++++++++++++++++++++++++++++++++++++++ This is a regular weekly summary of FreeBSD's cutting-edge development. It is intended to help the FreeBSD community keep up with the fast-paced work going on in FreeBSD-CURRENT by distilling the deluge of data from the CVS mailing list into a (hopefully) easy-to-read newsletter. This newsletter is marked up in reStructuredText_, so any odd punctuation that you see is likely intended for the reST parser. .. _reStructuredText: http://docutils.sourceforge.net/rst.html You can get old summaries, and an HTML version of this one, at http://www.xl0.org/FreeBSD/. Please send any comments to Mark Johnston (mark at xl0.org). For Lukasz Dudek and Szymon Roczniak's Polish translations of these summaries, which may lag the English ones slightly, please see http://mocart.pinco.pl/FreeBSD/. .. contents:: ============ New features ============ New ACPI PCI linking code ------------------------- John Baldwin (jhb) committed a major rewrite of the ACPI PCI linking code, which assigns IRQs to and does other handling of PCI devices. This new code supports multiple IRQs and other resources per link device and improves on the IRQ assignment algorithm. If you are using tunables to override default IRQ settings, note that the new code routes entire PCI link devices, rather than individual devices using that link. John writes, "For example, to adjust the IRQ that \_SB_.LNKA uses, one would set 'hw.pci.link.LNKA.irq=10' from the loader." http://www.freebsd.org/cgi/mid.cgi?200411232226.iANMQioc077290 Low-level TCP information available from sockets ------------------------------------------------ Robert Watson (rwatson) added support for some parts of the TCP_INFO socket option, as found in Linux 2.6. This allows processes to query sockets for some low-level TCP information, like the send, bandwidth, and congestion windows. http://www.freebsd.org/cgi/mid.cgi?200411261858.iAQIwlXV032915 periodic security output now includes packets blocked by PF ----------------------------------------------------------- Max Laier (mlaier) committed code to the daily security run to display packets blocked by PF, in the way that packets blocked by ipfw are. A new variable, named daily_status_security_pfdenied_enable, is now supported in /etc/periodic.conf; it defaults to YES. This code was submitted by Clive Lin (clive). http://www.freebsd.org/cgi/mid.cgi?200411241841.iAOIfsY5054400 New -m (month) flag added to ncal --------------------------------- Garrett Wollman (wollman) added support to ncal, which displays calendars on the console, for a new month flag. If -m is passed to ncal, it will display the given month of the current year. http://www.freebsd.org/cgi/mid.cgi?200411232257.iANMvHaD078657 New failure-detection algorithm for Netgraph -------------------------------------------- Gleb Smirnoff (glebius) committed a new failure detection algorithm for Netgraph, a modular system to hook together networking functions, called NG_ONE2MANY_FAIL_NOTIFY. The new algorithm detects downstream components that are offline and removes them from or adds them to its list of downstreams appropriately. http://www.freebsd.org/cgi/mid.cgi?200411230945.iAN9jmSW027271 Per-jail fstab support ---------------------- Maxime Henrion (mux) changed rc.conf to support an fstab file for each jail. He gave this example:: jail_foo_mount_enable="YES" jail_foo_fstab="/etc/fstab.foo" He also noted that the second line has no effect in this case, since /etc/fstab. is the default when no fstab is specified. The code Maxime committed was submitted by Jeremie Le Hen. http://www.freebsd.org/cgi/mid.cgi?200411232009.iANK9w8G066191 ================= Discussion topics ================= Beastie boot menu removed ------------------------- [ This is something of an inflammatory issue, so as you read the summary, please keep in mind that cvs-src posts represent only some people's reaction to commits, and that usually the people that post are the objectors to any commit. Specifically, the fact that the replies to this commit were generally in opposition should /not/ be construed as a general consensus that it was a bad thing. I have no clue whether more people consider the menu a bad idea than a good one, but that would be a matter for more-formal discussion on another list. ] Scott Long (scottl) removed the Beastie boot menu, saying, "It offends some and annoys everyone else, and I'm frankly tired of the controversy. When people ask me why FreeBSD isn't user-friendly, I'll tell them that I tried. RIP." This post prompted many replies; in general opposition to eliminating the menu were David Xu (davidxu), Jiawei Ye, John Birrell, Johan Karlson (johan), Gleb Smirnoff (glebius), Alexey Dokuchaev (danfe), Stijn Hoop, Frank Mayhar, John Baldwin (jhb), and Danny J. Zerkel. Garance A. Drosihn (gad), Mike Silbersack (silby), Dag-Erling Smorgrav (des), Robert Watson (rwatson), Bjoern A. Zeeb (bz), and Roman Kurakin (rik) generally suggested that the boot menu would be as useful without the ASCII-art Beastie, for reasons ranging from possible offense to slow display, and that a plain text menu might be a suitable way to revive it. Scott noted, in response to this last suggestion, "I had patches in the works to make the image optional. [ . . . ] However, there were a quite a few complaints about the timer, text, options, and keys that had nothing to do with the image." In response to Scott's comments earlier about ease-of-use, M. Warner Losh (imp) suggested, "One could easily have a 'safeboot' command, which would disable all the things that the safe boot menu item used to do." Scott replied, "safeboot isn't the same as 'disable acpi'. It was actually quite useful to disable ACPI but still leave ATA-DMA and SMP enabled." Warner responded, "Agreed. A few wrappers would go a long way is all I'm saying.." Scott asked, "Where would these 'wrappers' be documented?" In another conversation, Poul-Henning Kamp (phk) suspected that it was his removal of the Beastie menu from NanoBSD that prompted Scott's commit; he said, "The reason why I disable the beastie menu in some of my nanobsd builds are that a couple of those systems sit with a 2400bps GSM phone as console connection. [ . . . ] whatever happens in nanobsd should not be taken as indicative of anything related to user-friendlyness [ . . . ]." Scott replied, "It actually had nothing to do with nanobsd. It has everything to do with many months of conversations with many people." In another reply to Scott's initial commit, Eivind Eklund (eivind) suggested, "I've for a long time been thinking of the benefits of creating a 'user friendliness officer' similar to the security officer / tech advisory board we have now. As it is, we end up with bikesheds over UI issues all the time, grumbling, and a user interface that's the result of who shouts loudest." http://www.freebsd.org/cgi/mid.cgi?200411290132.iAT1WAse056942 ================= Committer changes ================= Jean-Sebastien Pedron (dumbbell) has joined as a new src committer. Jean-Sebastien has implemented read-only ReiserFS support for FreeBSD, which he will continue to work on (among other things) as a committer. Maxime Henrion (mux) will be his mentor. http://www.freebsd.org/cgi/mid.cgi?200411292130.iATLUrgT033674 =================== Important bug fixes =================== Crash or load failure with sk driver on Gigabit-Ethernet-only cards fixed ------------------------------------------------------------------------- Bjoern A. Zeeb (bz) fixed a bug in the networking code that was preventing the sk driver, which supports the SysKonnect chip found on many Gigabit Ethernet boards, from loading properly. The bug would show up when the driver was used with boards that supported only Gigabit Ethernet, instead of Gigabit, Fast, and regular Ethernet. This fix closes PRs 63313_, 71733_, and 73725_. .. _63313: http://www.freebsd.org/cgi/query-pr.cgi?pr=63313 .. _71733: http://www.freebsd.org/cgi/query-pr.cgi?pr=71733 .. _73725: http://www.freebsd.org/cgi/query-pr.cgi?pr=73725 http://www.freebsd.org/cgi/mid.cgi?200411261942.iAQJgeXo039249 Long-standing TCP bug with ignored RSTs fixed --------------------------------------------- Mike Silbersack (silby) corrected a bug in the TCP code that would cause the stack to ignore RST (reset) packets if the receive window was 0 bytes in size. This could have caused connections to hang open when they should have been disconnected. The bug description and fix, as well as a test case, were submitted by Michiel Boland. http://www.freebsd.org/cgi/mid.cgi?200411251904.iAPJ4KXf045915 Crash in PF when using bidirectional NAT on dynamic interfaces fixed -------------------------------------------------------------------- Daniel Hartmeier (dhartmei) fixed a bug in PF, the OpenBSD packet filter, that can cause a crash. The crash was caused by bidirectional NAT rules in the form "binat from ... to ... -> (interface)" were used with a dynamic interface. The bug was discovered by kos at bastard dot net, and analyzed by Pyun YongHyeon (yongari). http://www.freebsd.org/cgi/mid.cgi?200411240043.iAO0hYv4082483 From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 05:09:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6343316A4CE; Tue, 30 Nov 2004 05:09:26 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F294A43D68; Tue, 30 Nov 2004 05:09:25 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAU59Pmd042389; Tue, 30 Nov 2004 00:09:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iAU59PND045155; Tue, 30 Nov 2004 00:09:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id E547A7306E; Tue, 30 Nov 2004 00:09:24 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041130050924.E547A7306E@freebsd-current.sentex.ca> Date: Tue, 30 Nov 2004 00:09:24 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 05:09:26 -0000 TB --- 2004-11-30 03:29:32 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-30 03:29:32 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2004-11-30 03:29:32 - checking out the source tree TB --- 2004-11-30 03:29:32 - cd /home/tinderbox/CURRENT/ia64/ia64 TB --- 2004-11-30 03:29:32 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-30 03:35:35 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-30 03:35:35 - cd /home/tinderbox/CURRENT/ia64/ia64/src TB --- 2004-11-30 03:35:35 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-30 05:07:16 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-30 05:07:16 - cd /home/tinderbox/CURRENT/ia64/ia64/src TB --- 2004-11-30 05:07:16 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Nov 30 05:07:18 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] awk -f /tinderbox/CURRENT/ia64/ia64/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/ia64/ia64/src/sys/isa/isa_if.m -h awk -f /tinderbox/CURRENT/ia64/ia64/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/ia64/ia64/src/sys/dev/acpica/acpi_if.m -h awk -f /tinderbox/CURRENT/ia64/ia64/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/clock_if.m -h if [ -f .olddep ]; then mv .olddep .depend; fi rm -f .newdep /home/tinderbox/CURRENT/ia64/ia64/obj/tinderbox/CURRENT/ia64/ia64/src/make.i386/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/ia64/ia64/src/sys -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/altq -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/pf -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ngatm -I/tinderbox/CURRENT/ia64/ia64/src/sys/contrib/ia64/libuwx/src -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-functi on-growth=1000 -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -mno-sdata -ffreestanding /tinderbox/CURRENT/ia64/ia64/src/sys/kern/subr_param.c:59:2: #endif without #if mkdep: compile failed *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/obj/ia64/tinderbox/CURRENT/ia64/ia64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/obj/ia64/tinderbox/CURRENT/ia64/ia64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. TB --- 2004-11-30 05:09:24 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-30 05:09:24 - ERROR: failed to build generic kernel TB --- 2004-11-30 05:09:24 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 05:30:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6259916A4CE for ; Tue, 30 Nov 2004 05:30:46 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E968943D5A for ; Tue, 30 Nov 2004 05:30:45 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iAU5Ufro019907; Mon, 29 Nov 2004 23:30:41 -0600 (CST) (envelope-from dan) Date: Mon, 29 Nov 2004 23:30:41 -0600 From: Dan Nelson To: Julian Elischer Message-ID: <20041130053040.GL5518@dan.emsphone.com> References: <20041128233704.GB62951@NitroPhys.welchsmnet.net> <20041129154805.GD5518@dan.emsphone.com> <41AB8174.4090205@elischer.org> <20041129205408.GH5518@dan.emsphone.com> <41AB9151.8070601@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AB9151.8070601@elischer.org> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Sean Welch Subject: Re: top under 5.3-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 05:30:46 -0000 In the last episode (Nov 29), Julian Elischer said: > understood.. but when 'ps' gets the information, it gets each > thread.. where does the info get stored? the threads may have just > flashed into existence a fraction of a second ago, and prior to that > thay may have belonged to a compeltely different process. It's not a > simple problem. However there may be some relatively "ok" answers if > we can define well enough what we want to see. For example all > taking the total cputime for the KSEGRP and dividing it by the number > of non-sleeping threads might be a possibility. (or some variant of > that). Is the real problem that %CPU and WCPU are no longer used by the schedulers in any meaningful way? I thought at one point they were used to dampen the priority of cpu-intensive proceses. Maybe they should be removed and replaced with some other counters that can record cpu usage better. %CPU can certainly be extracted by subtracting the "struct rusage" values every sampling interval; unixtop does that for quite a few OSes where %CPU isn't available or is useless. WCPU is nice to get a longer-term picture of what processes are consistently using CPU though. I suppose top could maintain its own running average by averaging its calculated %CPU over an interval, but ps couldn't. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 06:24:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA3B216A4CE for ; Tue, 30 Nov 2004 06:24:56 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62AB543D54 for ; Tue, 30 Nov 2004 06:24:56 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iAU6Og0N063257; Tue, 30 Nov 2004 01:24:42 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iAU6Of5I063246; Tue, 30 Nov 2004 01:24:42 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Tue, 30 Nov 2004 01:24:41 -0500 (EST) From: Jeff Roberson To: Jeremie Le Hen In-Reply-To: <20041122223621.GG960@obiwan.tataz.chchile.org> Message-ID: <20041130012408.S85758@mail.chesapeake.net> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr> <20041122223621.GG960@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org cc: Ivan Voras Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 06:24:57 -0000 On Mon, 22 Nov 2004, Jeremie Le Hen wrote: > Hi Jeff, > > > I haven't received any feedback from the list though. I hope people are > > testing it. Perhaps the silence indicates universal success? :-) > > I have just tested your patch. It compiles like a charm. FYI, my > kernel have MUTEX_DEBUG, INVARIANTS and WITNESS enabled, but no > PREEMPTION. > While using my system with debug.mpsavevfs=1, I encountered two different > panics. (Sorry, I do not have a serial cable plugged into my laptop and > manual writing of hexadecimal addresses is very annoying.) Thanks, this was plenty of information. I have these fixed and I will post a new patch in a day or so. Cheers, Jeff > > The first one seems to be related to union mounts as when I use Tobias > Roth's profile.sh (which union mounts a vnode md(4) device over /etc) > `ls /etc' panics the system but when I don't have the mount, everything > seems to work : > panic: mutex Giant not owned at ../../../kern/vfs_vnops.c:962 > db> trace > kdb_enter() > panic() > _mtx_assert() > vn_write_suspend_wait() > ufs_inactive() > ufs_vnoperate() > vput() > getdirentries() > syscall() > > > The second one appeared just when I ask bash(1) to complete a command > name : it has to scan all directories from $HOME and stat(2) every files > in them. Here is the panic() : > Memory modified after free 0xc1ddc300 (252) val=c1df59c4 @ 0xc1ddc374 > panic: Most recently used by UFS mount > kdb_enter() > panic() > mtrash_ctor() > uma_zalloc_arg() > malloc() > fdinit() > fdcopy() > fork1() > fork() > syscall() > > > I hope this will help. > Best regads, > -- > Jeremie Le Hen > jeremie@le-hen.org > From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 06:28:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B9CF16A4CE; Tue, 30 Nov 2004 06:28:04 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1314A43D54; Tue, 30 Nov 2004 06:28:04 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iAU6S30N065637; Tue, 30 Nov 2004 01:28:03 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iAU6S3LE065620; Tue, 30 Nov 2004 01:28:03 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Tue, 30 Nov 2004 01:28:01 -0500 (EST) From: Jeff Roberson To: John Baldwin In-Reply-To: <200411231140.10041.jhb@FreeBSD.org> Message-ID: <20041130012736.A85758@mail.chesapeake.net> References: <20041120000743.G18094@mail.chesapeake.net> <20041123083801.GA40401@peter.osted.lan> <200411231140.10041.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@FreeBSD.org cc: current@FreeBSD.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 06:28:04 -0000 On Tue, 23 Nov 2004, John Baldwin wrote: > On Tuesday 23 November 2004 03:38 am, Peter Holm wrote: > > On Sat, Nov 20, 2004 at 12:24:10AM -0500, Jeff Roberson wrote: > > > I have a patch that I would like people to test and review. It's > > > available here: > > > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > I have a panic at http://www.holm.cc/stress/log/jeff02.html > > with GENERIC HEAD from Nov 22 14:40 UTC + your Giantless VFS patch. > > > > But the fault does not seem to related to your changes? > > Might be an incorrect parameter to mtx_init() that results in a bogus pointer > eventually for the name of a lock? I forgot to call mtx_destroy() before I freed the name. This could have done it eh? > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 06:28:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B9CF16A4CE; Tue, 30 Nov 2004 06:28:04 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1314A43D54; Tue, 30 Nov 2004 06:28:04 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iAU6S30N065637; Tue, 30 Nov 2004 01:28:03 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iAU6S3LE065620; Tue, 30 Nov 2004 01:28:03 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Tue, 30 Nov 2004 01:28:01 -0500 (EST) From: Jeff Roberson To: John Baldwin In-Reply-To: <200411231140.10041.jhb@FreeBSD.org> Message-ID: <20041130012736.A85758@mail.chesapeake.net> References: <20041120000743.G18094@mail.chesapeake.net> <20041123083801.GA40401@peter.osted.lan> <200411231140.10041.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@FreeBSD.org cc: current@FreeBSD.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 06:28:04 -0000 On Tue, 23 Nov 2004, John Baldwin wrote: > On Tuesday 23 November 2004 03:38 am, Peter Holm wrote: > > On Sat, Nov 20, 2004 at 12:24:10AM -0500, Jeff Roberson wrote: > > > I have a patch that I would like people to test and review. It's > > > available here: > > > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > I have a panic at http://www.holm.cc/stress/log/jeff02.html > > with GENERIC HEAD from Nov 22 14:40 UTC + your Giantless VFS patch. > > > > But the fault does not seem to related to your changes? > > Might be an incorrect parameter to mtx_init() that results in a bogus pointer > eventually for the name of a lock? I forgot to call mtx_destroy() before I freed the name. This could have done it eh? > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 06:35:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C35A016A4CE; Tue, 30 Nov 2004 06:35:23 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6309D43D5E; Tue, 30 Nov 2004 06:35:23 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iAU6ZM0N068200; Tue, 30 Nov 2004 01:35:22 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iAU6ZM8f068190; Tue, 30 Nov 2004 01:35:22 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Tue, 30 Nov 2004 01:35:21 -0500 (EST) From: Jeff Roberson To: Robert Watson In-Reply-To: Message-ID: <20041130013406.U85758@mail.chesapeake.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 06:35:23 -0000 On Fri, 26 Nov 2004, Robert Watson wrote: > > On Sat, 20 Nov 2004, Jeff Roberson wrote: > > > I have a patch that I would like people to test and review. It's > > available here: > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > I built a GENERIC kernel from 6.x of yesterday with this patch, installed > it on a box, and hen left it overnight. At some point during the night, > the following was generated: > > login: lock order reversal > 1st 0xc28e8bdc vnode interlock (vnode interlock) @ kern/vfs_subr.c:722 > 2nd 0xc251b044 struct mount mtx (struct mount mtx) @ kern/vfs_vnops.c:997 Thanks, I have a fix for this. I'll post it soon. > KDB: stack backtrace: > witness_checkorder(c251b044,9,c081bc6e,3e5) at witness_checkorder+0x500 > _mtx_lock_flags(c251b044,0,c081bc6e,3e5,c28e8bdc) at _mtx_lock_flags+0x40 > vn_finished_write(c251b000,c2afec00,0,c282618c,c251b000) at > vn_finished_write+0x21 > getnewvnode(c0819ba0,c251b800,c2517500,ef16ea04) at getnewvnode+0x4ff > ffs_vget(c251b800,13fb,2,ef16ea88) at ffs_vget+0x74 > ufs_lookup(ef16eb38) at ufs_lookup+0x81e > vfs_cache_lookup(ef16eba8,8,ef16ec44,c2afec00,0) at vfs_cache_lookup+0x25d > lookup(ef16ec30,c2b40228,c2afec00,ef16ec08,c2b40200) at lookup+0x269 > namei(ef16ec30,8064da8,0,0,c2762228) at namei+0x2a0 > lstat(c2afec00,ef16ed14,2,10e,292) at lstat+0x4a > syscall(805002f,805002f,bfbf002f,8064d00,8064d48) at syscall+0x128 > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (190, FreeBSD ELF32, lstat), eip = 0x280c7707, esp = > 0xbfbfeb9c, ebp = 0xbfbfec38 --- > > If it's a property of load, it presumably happened during the daily > event... > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee Research > > From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 06:42:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 877A016A4CE for ; Tue, 30 Nov 2004 06:42:48 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2693543D48 for ; Tue, 30 Nov 2004 06:42:48 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iAU6d20N069546; Tue, 30 Nov 2004 01:39:02 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iAU6d2sP069543; Tue, 30 Nov 2004 01:39:02 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Tue, 30 Nov 2004 01:39:01 -0500 (EST) From: Jeff Roberson To: Peter Holm In-Reply-To: <20041123013054.GA38804@peter.osted.lan> Message-ID: <20041130013802.J85758@mail.chesapeake.net> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr><20041123013054.GA38804@peter.osted.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org cc: Ivan Voras Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 06:42:48 -0000 On Tue, 23 Nov 2004, Peter Holm wrote: > On Mon, Nov 22, 2004 at 06:46:50AM -0500, Jeff Roberson wrote: > > On Mon, 22 Nov 2004, Ivan Voras wrote: > > > > > Jeff Roberson wrote: > > > > > > > The short description: > > > > This patch removes Giant from the read(), write(), and fstat() syscalls, > > > > as well as page faults, and bufdone (io interrupts) when using FFS. It > > > > > > What is the plan re: RELENG_5? Will things like this (giantless vm, fs) > > > be merged into it? > > > > The giantless vm was already merged back to RELENG_5 and enabled on amd64, > > and i386. I hope to merge the giantless vfs back after a month or so of > > no problems on -current. I hope to commit it to -current this week. > > > > I haven't received any feedback from the list though. I hope people are > > testing it. Perhaps the silence indicates universal success? :-) > > > > Here's a problem I ran into during stress test: > > http://www.holm.cc/stress/log/jeff01.html > > Let me know if you need more gdb output. Thanks, this is the most serious bug of the couple that were reported. It indicates a possible race to flush a buffer. I'm still looking for this. What steps did you take to produce this panic? > > - Peter > > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 07:56:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46D5116A4CE for ; Tue, 30 Nov 2004 07:56:06 +0000 (GMT) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 8C37443D5E for ; Tue, 30 Nov 2004 07:56:05 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 97541 invoked from network); 30 Nov 2004 07:56:04 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 30 Nov 2004 07:56:04 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iAU7u3Qj072967; Tue, 30 Nov 2004 08:56:03 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iAU7u3Se072966; Tue, 30 Nov 2004 08:56:03 +0100 (CET) (envelope-from pho) Date: Tue, 30 Nov 2004 08:56:02 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041130075602.GA72926@peter.osted.lan> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr> <20041122064318.Y18094@mail.chesapeake.net> <20041123013054.GA38804@peter.osted.lan> <20041130013802.J85758@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041130013802.J85758@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org cc: Ivan Voras Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 07:56:06 -0000 On Tue, Nov 30, 2004 at 01:39:01AM -0500, Jeff Roberson wrote: > > On Tue, 23 Nov 2004, Peter Holm wrote: > > > On Mon, Nov 22, 2004 at 06:46:50AM -0500, Jeff Roberson wrote: > > > On Mon, 22 Nov 2004, Ivan Voras wrote: > > > > > > > Jeff Roberson wrote: > > > > > > > > > The short description: > > > > > This patch removes Giant from the read(), write(), and fstat() syscalls, > > > > > as well as page faults, and bufdone (io interrupts) when using FFS. It > > > > > > > > What is the plan re: RELENG_5? Will things like this (giantless vm, fs) > > > > be merged into it? > > > > > > The giantless vm was already merged back to RELENG_5 and enabled on amd64, > > > and i386. I hope to merge the giantless vfs back after a month or so of > > > no problems on -current. I hope to commit it to -current this week. > > > > > > I haven't received any feedback from the list though. I hope people are > > > testing it. Perhaps the silence indicates universal success? :-) > > > > > > > Here's a problem I ran into during stress test: > > > > http://www.holm.cc/stress/log/jeff01.html > > > > Let me know if you need more gdb output. > > Thanks, this is the most serious bug of the couple that were reported. It > indicates a possible race to flush a buffer. I'm still looking for this. > What steps did you take to produce this panic? > I ran my kernel stress test: http://www.holm.cc/stress/src/stress.tgz I stopped using your patch after the two reported problems. Let me know if you would like me to perform more testing with your patch. - Peter > > > > - Peter > > > > > > _______________________________________________ > > > > freebsd-current@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 08:18:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9644116A4CE for ; Tue, 30 Nov 2004 08:18:12 +0000 (GMT) Received: from smtp-vbr14.xs4all.nl (smtp-vbr14.xs4all.nl [194.109.24.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FF6143D55 for ; Tue, 30 Nov 2004 08:18:11 +0000 (GMT) (envelope-from michiel@boland.org) Received: from xs6.xs4all.nl (xs6.xs4all.nl [194.109.21.6]) by smtp-vbr14.xs4all.nl (8.12.11/8.12.11) with ESMTP id iAU8IAYw056966 for ; Tue, 30 Nov 2004 09:18:10 +0100 (CET) (envelope-from michiel@boland.org) Received: from xs6.xs4all.nl (boland37@localhost.xs4all.nl [127.0.0.1]) by xs6.xs4all.nl (8.12.10/8.12.10) with ESMTP id iAU8I9jl029762 for ; Tue, 30 Nov 2004 09:18:09 +0100 (CET) (envelope-from michiel@boland.org) Received: (from boland37@localhost) by xs6.xs4all.nl (8.12.10/8.12.9/Submit) id iAU8I4u3029673 for current@freebsd.org; Tue, 30 Nov 2004 09:18:04 +0100 (CET) (envelope-from michiel@boland.org) X-Authentication-Warning: xs6.xs4all.nl: boland37 set sender to michiel@boland.org using -f Date: Tue, 30 Nov 2004 09:18:04 +0100 From: Michiel Boland To: current@freebsd.org Message-ID: <20041130081804.GA22353@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Virus-Scanned: by XS4ALL Virus Scanner Subject: bash/readline coredumps X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 08:18:12 -0000 Hi. Lately I am getting core dumps from bash (bash-2.05b.007_2 from ports). To reproduce: type a command that spans multiple lines, like echo ' ' Then bring up the last line with cursor-up or ^P and press enter. Some gdb output: (gdb) bt #0 rl_do_undo () at /usr/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/undo.c:124 #1 0x280ee279 in rl_revert_line (count=1, key=0) at /usr/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/undo.c:239 #2 0x28102e4d in readline_internal_teardown (eof=0) at /usr/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/readline.c:372 #3 0x281039fc in readline (prompt=0x80c4180 "mboland@leefnet:~$ ") at /usr/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/readline.c:504 #4 0x08058623 in yy_input_name () #5 0x080c4180 in ?? () #6 0x0807c5e8 in termination_unwind_protect () #7 0x08059fa1 in yyerror () #8 0x0805ae83 in yyerror () #9 0x0805d529 in yyparse () #10 0x08058133 in parse_command () #11 0x080581dd in read_command () #12 0x0805831c in reader_loop () #13 0x08057441 in main () (gdb) print rl_undo_list $2 = (UNDO_LIST *) 0x30313100 This is -CURRENT from last Friday, but the problem has been around longer. Anyone any ideas? Cheers Michiel From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 08:38:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47D2616A4CE for ; Tue, 30 Nov 2004 08:38:25 +0000 (GMT) Received: from protov.plain.co.nz (protov.plain.co.nz [202.36.174.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50EB143D67 for ; Tue, 30 Nov 2004 08:38:24 +0000 (GMT) (envelope-from andrew@fubar.geek.nz) Received: from localhost (localhost [127.0.0.1]) by protov.plain.co.nz (Postfix) with ESMTP id BEE93904CC for ; Tue, 30 Nov 2004 21:38:22 +1300 (NZDT) Received: from protov.plain.co.nz ([127.0.0.1]) by localhost (protov [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 19870-01-62 for ; Tue, 30 Nov 2004 21:38:22 +1300 (NZDT) Received: from serv.int.fubar.geek.nz (ppp65196.cyberxpress.co.nz [202.49.65.196]) by protov.plain.co.nz (Postfix) with ESMTP id B969690F6F for ; Tue, 30 Nov 2004 21:38:17 +1300 (NZDT) Received: from [192.168.1.99] (unknown [192.168.1.99]) by serv.int.fubar.geek.nz (Postfix) with ESMTP id A077C6124 for ; Tue, 30 Nov 2004 21:38:34 +1300 (NZDT) Message-ID: <41AC315D.4040409@fubar.geek.nz> Date: Tue, 30 Nov 2004 21:37:49 +1300 From: Andrew Turner User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD Current Content-Type: multipart/mixed; boundary="------------050000090203090406070004" X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at cyberxpress.co.nz Subject: Live FreeBSD CD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 08:38:25 -0000 This is a multi-part message in MIME format. --------------050000090203090406070004 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Using nanobsd as a starting point I have created a live CD system I've named liveFreeBSD. It requires syutils/cdrtools to create liveFreeBSD.iso. Unlike FreeBSIE it only uses files from the tree with 3 exceptions. To use run the shell archive and set WORLDDIR to an appropriate value ie. /usr/src. It works in a similar way to nanobsd with the exception of the way it is customised. To customise liveFreeBSD create a new directory then have CUSTOMIZE point to it. If there is a make.conf file in it liveFreeBSD will pick it up and use it in the came way as an /etc/make.conf. Any directories will have their contents copied. eg. $ find /home/andrew/FreeBSD -type f /home/andrew/FreeBSD/etc/test1.txt /home/andrew/FreeBSD/make.conf $ make obj $ make CUSTOMIZE=/home/andrew/FreeBSD Will build the bootable CD with the file /etc/test1.txt. It will bring in any Makefile options from /home/andrew/FreeBSD/make.conf I have tested this on HEAD and RELENG_5. KNOWN BUGS: * Customize will only copy files 1 level deep, ie. ${CUSTOMIZE}/etc/ but not ${CUSTOMIZE}/usr/share/ Andrew -- 437742420 --------------050000090203090406070004 Content-Type: text/plain; name="livefreebsd.shar" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="livefreebsd.shar" # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # Makefile # etc # make.conf # echo x - Makefile sed 's/^X//' >Makefile << 'END-of-Makefile' X# Copyright (c) 2003-2004 Poul-Henning Kamp. X# Copyright (c) 2004 Thomas Quinot. X# Copyright (c) 2004 Andrew Turner. X# X# See /usr/share/examples/etc/bsd-style-copyright for license terms. X# X# $FreeBSD: src/tools/tools/nanobsd/Makefile,v 1.8 2004/08/16 22:41:58 thomas Exp $ X X#.include "${.CURDIR}/make.conf" X X# parallism flag for make. XMAKEJ?= X X# You probably do not need to change these. XWORLDDIR?= ${.CURDIR}/../../.. XWD?= ${.OBJDIR}/_.w X X# Keep overides for custom builds in the ${.CURDIR}/${CUSTOMIZE} directory X#CUSTOMIZE?=test X X.if defined(CUSTOMIZE) && !empty(CUSTOMIZE) X.if ${CUSTOMIZE:C/^\/.*$/\//} == "/" XCUSTOMIZE_PATH=${CUSTOMIZE} X.elif exists(${.CURDIR}/${CUSTOMIZE}) XCUSTOMIZE_PATH=${.CURDIR}/${CUSTOMIZE} X.endif X.endif X X.if exists(${CUSTOMIZE_PATH}/make.conf) XMAKE_CONF_INCLUDE=${CUSTOMIZE_PATH}/make.conf X.include "${MAKE_CONF_INCLUDE}" X.endif X X# X# The final resulting image is in ${.OBJDIR}/_.i and the single slice X# image in ${.OBJDIR}/_.i.s1 X# X X# Main target Xall: buildworld installworld buildimage X X# X# This is where you customizations to the image can be performed X# Please make sure to do everything relative to ${WD} here. X# X.if defined(CUSTOMIZE_PATH) XPATHS!= find ${CUSTOMIZE_PATH} -type d -depth 1 X.endif X XCustomize: _.cs X_.cs: _.iw _.di _.ik _.di X.if defined(CUSTOMIZE_PATH) X.for __DIR in ${PATHS} X @echo ${WD}${__DIR:S/${CUSTOMIZE_PATH}//} X mkdir -p ${WD}${__DIR:S/${CUSTOMIZE_PATH}//} X -cp ${__DIR}/* ${WD}/${__DIR:S/${CUSTOMIZE_PATH}//} X.endfor X.endif X touch _.cs X X########################################################################### X# X# The rest is pretty (or ugly if you prefer) magic, and should generally X# not need to be fiddled with. Good luck if you need to venture past this X# point. X# X X# Run a buildworld with our private make.conf Xbuildworld: _.bw X_.bw: X (cd ${WORLDDIR} && \ X make ${MAKEJ} -s buildworld __MAKE_CONF=${.CURDIR}/make.conf \ X MAKE_CONF_INCLUDE=${MAKE_CONF_INCLUDE} ) > _.bw.tmp 2>&1 X mv _.bw.tmp _.bw X X# Run installworld and install into our object directory Xinstallworld: _.iw X_.iw: _.bw X -rm -rf ${WD} > /dev/null 2>&1 X -chflags -R noschg ${WD} > /dev/null 2>&1 X rm -rf ${WD} X mkdir -p ${WD} X (cd ${WORLDDIR} && \ X make ${MAKEJ} -s installworld \ X DESTDIR=${WD} \ X __MAKE_CONF=${.CURDIR}/make.conf \ X MAKE_CONF_INCLUDE=${MAKE_CONF_INCLUDE} \ X ) > _.iw.tmp 2>&1 X mv _.iw.tmp _.iw X X# Run distribution target in /etc. X_.di: _.iw X mkdir -p ${WD} X (cd ${WORLDDIR}/etc && \ X make ${MAKEJ} -s distribution \ X DESTDIR=${WD} \ X __MAKE_CONF=${.CURDIR}/make.conf \ X MAKE_CONF_INCLUDE=${MAKE_CONF_INCLUDE} \ X ) > _.di.tmp 2>&1 X mv _.di.tmp _.di X X# Build kernel X_.bk: X (cd ${WORLDDIR} && \ X make ${MAKEJ} -s buildkernel \ X __MAKE_CONF=${.CURDIR}/make.conf \ X MAKE_CONF_INCLUDE=${MAKE_CONF_INCLUDE} \ X ) > _.bk.tmp 2>&1 X mv _.bk.tmp _.bk X X# Install kernel and hints file X_.ik: _.bk _.di X cp ${WORLDDIR}/sys/i386/conf/GENERIC.hints ${WD}/boot/device.hints X (cd ${WORLDDIR} && \ X make ${MAKEJ} installkernel \ X DESTDIR=${WD} \ X __MAKE_CONF=${.CURDIR}/make.conf \ X MAKE_CONF_INCLUDE=${MAKE_CONF_INCLUDE} \ X ) > _.ik.tmp 2>&1 X mv _.ik.tmp _.ik X X X# Create a disk image from the installed image Xbuildimage: _.md X_.md: _.cs X -umount ${WD}/dev > /dev/null 2>&1 X chflags -R noschg ${WD} > /dev/null 2>&1 X rm -rf ${WD}/var/* ${WD}/dev/* ${WD}/tmp X ln -s var/tmp ${WD}/tmp X cp ${.CURDIR}/etc/* ${WD}/etc X mkisofs -R -U -b boot/cdboot -no-emul-boot \ X -o liveFreeBSD.iso ${WD} X touch _.md X Xclean: X -rm -rf _.* > /dev/null 2>&1 X -chflags -R noschg _.* > /dev/null 2>&1 X rm -rf _.* liveFreeBSD.iso X X.include END-of-Makefile echo c - etc mkdir -p etc > /dev/null 2>&1 echo x - make.conf sed 's/^X//' >make.conf << 'END-of-make.conf' X# X# Copyright (c) 2003-2004 Poul-Henning Kamp. X# Copyright (c) 2004 Thomas Quinot. X# Copyright (c) 2004 Andrew Turner. X# X# See /usr/share/examples/etc/bsd-style-copyright for license terms. X# X# $FreeBSD: src/tools/tools/nanobsd/make.conf,v 1.3 2004/08/16 22:52:40 thomas Exp $ X# XKERNCONF?=GENERIC X X.if defined (MAKE_CONF_INCLUDE) && !empty(MAKE_CONF_INCLUDE) && exists(${MAKE_CONF_INCLUDE}) X.include "${MAKE_CONF_INCLUDE}" X.endif X END-of-make.conf # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # etc/fstab # etc/host.conf # etc/nsswitch.conf # echo x - etc/fstab sed 's/^X//' >etc/fstab << 'END-of-etc/fstab' X/dev/acd0 / cd9660 ro 0 0 X END-of-etc/fstab echo x - etc/host.conf sed 's/^X//' >etc/host.conf << 'END-of-etc/host.conf' X# Auto-generated from nsswitch.conf, do not edit Xhosts Xbind END-of-etc/host.conf echo x - etc/nsswitch.conf sed 's/^X//' >etc/nsswitch.conf << 'END-of-etc/nsswitch.conf' Xgroup: compat Xgroup_compat: nis Xhosts: files dns Xnetworks: files Xpasswd: compat Xpasswd_compat: nis Xshells: files END-of-etc/nsswitch.conf exit --------------050000090203090406070004-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 11:21:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 669E316A4CE for ; Tue, 30 Nov 2004 11:21:44 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [194.213.218.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DA2B43D3F for ; Tue, 30 Nov 2004 11:21:43 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from [127.0.0.1] (localhost [127.0.0.1]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id iAUBLf9T047220 for ; Tue, 30 Nov 2004 12:21:41 +0100 (CET) (envelope-from mime@traveller.cz) Message-ID: <41AC57BF.6060604@traveller.cz> Date: Tue, 30 Nov 2004 12:21:35 +0100 From: Michal Mertl User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; cs-CZ; rv:1.7.3) Gecko/20041117 X-Accept-Language: cs, en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="------------030208060203010101060903" Subject: enhacement to mdmfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 11:21:44 -0000 This is a multi-part message in MIME format. --------------030208060203010101060903 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hello, I've recently shot my foot with mdmfs. Of course it was a pilot error but the funcioanility I was looking for might be usefull. I want to mount vnode-backed md(4) on boot without formatting it (e.g. for a jail). Is it possible with current boot scripts? I wrote a simple patch to mdmfs so such md disk can be put in /etc/fstab. It adds '-K' option do mdmfs(8) to Keep contents. The line to attach such disk in fstab looks like this: md /jail mfs rw,-K,-F=/var/jailfile 0 0 Comments welcome. If people find it usefull I'd like to have it commited. I can fill the PR with enhancement request. Patch attached. -- Michal Mertl --------------030208060203010101060903 Content-Type: text/plain; name="mdmfs.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mdmfs.diff" Index: mdmfs.8 =================================================================== RCS file: /home/fcvs/cvs/src/sbin/mdmfs/mdmfs.8,v retrieving revision 1.20 diff -u -3 -r1.20 mdmfs.8 --- mdmfs.8 17 May 2004 08:35:41 -0000 1.20 +++ mdmfs.8 30 Nov 2004 10:56:22 -0000 @@ -36,7 +36,7 @@ driver .Sh SYNOPSIS .Nm -.Op Fl DLlMNSUX +.Op Fl DKLlMNSUX .Op Fl a Ar maxcontig .Op Fl b Ar block-size .Op Fl c Ar cylinders @@ -57,7 +57,7 @@ .Ar mount-point .Nm .Fl C -.Op Fl lNU +.Op Fl KlNU .Op Fl a Ar maxcontig .Op Fl b Ar block-size .Op Fl c Ar cylinders @@ -162,6 +162,12 @@ The fragment size of the file system in bytes. .It Fl i Ar bytes Number of bytes per inode. +.It Fl K +Preserve contents of vnode-backed +.Pq Dv MD_VNODE +memory disk. +Must be used in conjunction with +.Fl F . .It Fl l Enable multilabel MAC on the new file system. .It Fl L Index: mdmfs.c =================================================================== RCS file: /home/fcvs/cvs/src/sbin/mdmfs/mdmfs.c,v retrieving revision 1.20 diff -u -3 -r1.20 mdmfs.c --- mdmfs.c 17 May 2004 07:07:20 -0000 1.20 +++ mdmfs.c 30 Nov 2004 10:51:56 -0000 @@ -89,7 +89,7 @@ *mount_arg; enum md_types mdtype; /* The type of our memory disk. */ bool have_mdtype; - bool detach, softdep, autounit; + bool detach, softdep, autounit, keepdata; char *mtpoint, *unitstr; char *p; int ch; @@ -119,7 +119,7 @@ compat = true; while ((ch = getopt(argc, argv, - "a:b:Cc:Dd:e:F:f:hi:LlMm:Nn:O:o:p:Ss:t:Uv:w:X")) != -1) + "a:b:Cc:Dd:e:F:f:hi:KLlMm:Nn:O:o:p:Ss:t:Uv:w:X")) != -1) switch (ch) { case 'a': argappend(&newfs_arg, "-a %s", optarg); @@ -167,6 +167,8 @@ usage(); loudsubs = true; break; + case 'K': + keepdata = true; case 'l': argappend(&newfs_arg, "-l"); break; @@ -233,7 +235,6 @@ argv += optind; if (argc < 2) usage(); - /* Make compatibility assumptions. */ if (compat) { mi.mi_mode = 01777; @@ -258,6 +259,11 @@ mtpoint = argv[1]; if (!have_mdtype) mdtype = MD_SWAP; + + /* If we want to use vnode backed file and don't newfs it */ + if (keepdata && mdtype != MD_VNODE) + err(1, "Must specify -F with -K"); + if (softdep) argappend(&newfs_arg, "-U"); @@ -268,7 +274,8 @@ do_mdconfig_attach_au(mdconfig_arg, mdtype); else do_mdconfig_attach(mdconfig_arg, mdtype); - do_newfs(newfs_arg); + if (!keepdata) + do_newfs(newfs_arg); do_mount(mount_arg, mtpoint); do_mtptsetup(mtpoint, &mi); @@ -665,13 +672,13 @@ name = "mdmfs"; if (!compat) fprintf(stderr, -"usage: %s [-DLlMNSUX] [-a maxcontig [-b block-size] [-c cylinders]\n" +"usage: %s [-DKLlMNSUX] [-a maxcontig [-b block-size] [-c cylinders]\n" "\t[-d rotdelay] [-e maxbpg] [-F file] [-f frag-size] [-i bytes]\n" "\t[-m percent-free] [-n rotational-positions] [-O optimization]\n" "\t[-o mount-options] [-p permissions] [-s size] [-w user:group]\n" "\tmd-device mount-point\n", name); fprintf(stderr, -"usage: %s -C [-lNU] [-a maxcontig] [-b block-size] [-c cylinders]\n" +"usage: %s -C [-lKNU] [-a maxcontig] [-b block-size] [-c cylinders]\n" "\t[-d rotdelay] [-e maxbpg] [-F file] [-f frag-size] [-i bytes]\n" "\t[-m percent-free] [-n rotational-positions] [-O optimization]\n" "\t[-o mount-options] [-s size] md-device mount-point\n", name); --------------030208060203010101060903-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 11:29:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6FF116A4CE for ; Tue, 30 Nov 2004 11:29:47 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07F5D43D3F for ; Tue, 30 Nov 2004 11:29:47 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by rproxy.gmail.com with SMTP id b11so485416rne for ; Tue, 30 Nov 2004 03:29:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=W5FfflwdTq4gyGRr3t0eoVzynBuWJXu9gPR+lFjpcBqqgAjb2tdACyuCwMsZxdJN/FBzcHVzAPqXItk1A31IO409MK8+Hu3N7oCwABwbotA0B10w0Ph4g6oyFX+0fQzmoSKBXHXTR9Op+sgqJMkwouX5r8vn/P+kuXCQjs1GOgM= Received: by 10.38.162.18 with SMTP id k18mr425544rne; Tue, 30 Nov 2004 03:29:45 -0800 (PST) Received: by 10.38.13.6 with HTTP; Tue, 30 Nov 2004 03:29:45 -0800 (PST) Message-ID: <84dead720411300329249d4bf3@mail.gmail.com> Date: Tue, 30 Nov 2004 16:59:45 +0530 From: Joseph Koshy To: freebsd-current Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_769_12954910.1101814185802" Subject: Dual CPU detection problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 11:29:47 -0000 ------=_Part_769_12954910.1101814185802 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Strange problem. On an IBM xSeries 335 machine with TWO P4 HTT cpus (mptable, dmesg output enclosed) FreeBSD -CURRENT will sometimes detect both the physical CPUs and will sometimes detect only one. FreeBSD 5.3 reliably detects the 2 physical / 4 logical CPUs that are present. Any suggestions on how to debug this? ------=_Part_769_12954910.1101814185802 Content-Type: text/plain; name=mptable.txt; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="mptable.txt" =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: EBDA physical address: 0x0009e140 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0x97 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x0009f010 signature: 'PCMP' base table length: 260 version: 1.4 checksum: 0x36 OEM ID: 'IBM ENSW' Product ID: 'TURQUIOSESMP' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 24 local APIC address: 0xfee00000 extended table length: 208 extended table checksum: 84 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x14 BSP, usable 15 2 9 0x0301 6 0x14 AP, usable 15 2 9 0x0301 -- Bus: Bus ID Type 0 PCI 1 PCI 2 PCI 3 ISA -- I/O APICs: APIC ID Version State Address 14 0x11 usable 0xfec00000 13 0x11 usable 0xfec01000 12 0x11 usable 0xfec02000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# INT conforms conforms 3 1 14 1 INT conforms conforms 3 0 14 2 INT conforms conforms 3 4 14 4 INT conforms conforms 3 6 14 6 INT conforms conforms 3 8 14 8 INT conforms conforms 3 12 14 12 INT conforms conforms 3 13 14 13 INT conforms conforms 3 14 14 14 INT conforms conforms 3 15 14 15 INT conforms conforms 0 1:A 13 10 INT conforms conforms 0 15:A 14 10 INT conforms conforms 2 1:A 13 8 INT conforms conforms 2 2:A 13 9 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# NMI conforms conforms 3 0 255 1 ExtINT conforms conforms 3 0 255 0 ------------------------------------------------------------------------------- MP Config Extended Table Entries: -- System Address Space bus ID: 0 address type: memory address address base: 0xa0000 address range: 0x20000 -- System Address Space bus ID: 0 address type: memory address address base: 0xc8000 address range: 0x18000 -- System Address Space bus ID: 0 address type: memory address address base: 0xfc000000 address range: 0x4000000 -- System Address Space bus ID: 2 address type: memory address address base: 0xfa000000 address range: 0x2000000 -- System Address Space bus ID: 0 address type: I/O address address base: 0x0 address range: 0x3b0 -- System Address Space bus ID: 0 address type: I/O address address base: 0x3b0 address range: 0xc -- System Address Space bus ID: 0 address type: I/O address address base: 0x3bc address range: 0x4 -- System Address Space bus ID: 0 address type: I/O address address base: 0x3c0 address range: 0x20 -- System Address Space bus ID: 0 address type: I/O address address base: 0x3e0 address range: 0x1f20 -- System Address Space bus ID: 2 address type: I/O address address base: 0x2300 address range: 0xdd00 -- Bus Heirarchy bus ID: 3 bus info: 0x01 parent bus ID: 0 =============================================================================== ------=_Part_769_12954910.1101814185802 Content-Type: text/plain; name=dmesg-current.txt; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg-current.txt" Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-CURRENT #23: Tue Nov 30 16:06:14 IST 2004 root@mismatcher.hq.netapp.com:/usr/obj/home/fcpi/src/sys/MISMATCHER WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3056.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 1610530816 (1535 MB) avail memory = 1573531648 (1500 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 16 ioapic2: Assuming intbase of 32 ioapic2 irqs 32-47 on motherboard ioapic1 irqs 16-31 on motherboard ioapic0 irqs 0-15 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 1.0 (no driver attached) atapci0: port 0x700-0x70f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 15.2 (no driver attached) isab0: at device 15.3 on pci0 isa0: on isab0 pcib3: pcibus 3 on motherboard pci3: on pcib3 pcib1: pcibus 1 on motherboard pci1: on pcib1 pcib2: pcibus 2 on motherboard pci2: on pcib2 bge0: mem 0xfbff0000-0xfbffffff irq 24 at device 1.0 on pci2 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:0d:60:d5:93:ce bge1: mem 0xfbfe0000-0xfbfeffff irq 25 at device 2.0 on pci2 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:0d:60:d5:93:cf cpu0 on motherboard cpu1 on motherboard orm0: at iomem 0xc0000-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) Timecounters tick every 1.000 msec ad0: 38162MB [77536/16/63] at ata0-master UDMA100 acd0: CDROM at ata1-master UDMA33 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad0s1d ohci0: mem 0xfebfe000-0xfebfefff irq 10 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ------=_Part_769_12954910.1101814185802-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 11:55:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80C7D16A4CE for ; Tue, 30 Nov 2004 11:55:00 +0000 (GMT) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2E9043D54 for ; Tue, 30 Nov 2004 11:54:59 +0000 (GMT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id 5B3435312; Tue, 30 Nov 2004 12:54:58 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id 9AF6B5310; Tue, 30 Nov 2004 12:54:51 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id 5C6E3B85E; Tue, 30 Nov 2004 12:54:51 +0100 (CET) To: Patrick Bowen References: <41A8C9C3.1020504@juno.com> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Tue, 30 Nov 2004 12:54:51 +0100 In-Reply-To: <41A8C9C3.1020504@juno.com> (Patrick Bowen's message of "Sat, 27 Nov 2004 12:38:59 -0600") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on flood.des.no X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MAILTO_TO_SPAM_ADDR autolearn=no version=2.64 cc: freebsd-current@freebsd.org Subject: Re: Getting devfs to recognize a hotplugged fd0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 11:55:00 -0000 Patrick Bowen writes: > I'm trying to learn how to get devfs to create an fd0 enty in /dev > automatically when I plug a floppy drive into the serial port of a > running Dell D600 laptop running 6.0 current. The D-series media bay floppy drive is a USB device. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 12:06:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA93F16A4CE for ; Tue, 30 Nov 2004 12:06:46 +0000 (GMT) Received: from ei.bzerk.org (ei.xs4all.nl [213.84.67.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 968C343D2F for ; Tue, 30 Nov 2004 12:06:45 +0000 (GMT) (envelope-from mail25@bzerk.org) Received: from ei.bzerk.org (BOFH@localhost [127.0.0.1]) by ei.bzerk.org (8.13.1/8.13.1) with ESMTP id iAUC8uAp045041; Tue, 30 Nov 2004 13:08:56 +0100 (CET) (envelope-from mail25@bzerk.org) Received: (from bulk@localhost) by ei.bzerk.org (8.13.1/8.13.1/Submit) id iAUC8uer045040; Tue, 30 Nov 2004 13:08:56 +0100 (CET) (envelope-from mail25@bzerk.org) Date: Tue, 30 Nov 2004 13:08:56 +0100 From: Ruben de Groot To: Michal Mertl Message-ID: <20041130120856.GA44543@ei.bzerk.org> Mail-Followup-To: Ruben de Groot , Michal Mertl , freebsd-current@freebsd.org References: <41AC57BF.6060604@traveller.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AC57BF.6060604@traveller.cz> User-Agent: Mutt/1.4.2.1i X-Spam-Status: No, score=-1.7 required=5.0 tests=ALL_TRUSTED, FROM_ENDS_IN_NUMS,J_CHICKENPOX_64 autolearn=failed version=3.0.0 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on ei.bzerk.org cc: freebsd-current@freebsd.org Subject: Re: enhacement to mdmfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 12:06:46 -0000 On Tue, Nov 30, 2004 at 12:21:35PM +0100, Michal Mertl typed: > Hello, > > I've recently shot my foot with mdmfs. Of course it was a pilot error but > the funcioanility I was looking for might be usefull. > > I want to mount vnode-backed md(4) on boot without formatting it (e.g. for > a jail). Is it possible with current boot scripts? > > I wrote a simple patch to mdmfs so such md disk can be put in /etc/fstab. > It adds '-K' option do mdmfs(8) to Keep contents. The line to attach such > disk in fstab looks like this: > > md /jail mfs rw,-K,-F=/var/jailfile 0 0 > > Comments welcome. If people find it usefull I'd like to have it commited. I > can fill the PR with enhancement request. I filed a PR about this allready in October 2003: http://www.freebsd.org/cgi/query-pr.cgi?pr=57641 Ruben > Patch attached. > > -- > Michal Mertl > > > > Index: mdmfs.8 > =================================================================== > RCS file: /home/fcvs/cvs/src/sbin/mdmfs/mdmfs.8,v > retrieving revision 1.20 > diff -u -3 -r1.20 mdmfs.8 > --- mdmfs.8 17 May 2004 08:35:41 -0000 1.20 > +++ mdmfs.8 30 Nov 2004 10:56:22 -0000 > @@ -36,7 +36,7 @@ > driver > .Sh SYNOPSIS > .Nm > -.Op Fl DLlMNSUX > +.Op Fl DKLlMNSUX > .Op Fl a Ar maxcontig > .Op Fl b Ar block-size > .Op Fl c Ar cylinders > @@ -57,7 +57,7 @@ > .Ar mount-point > .Nm > .Fl C > -.Op Fl lNU > +.Op Fl KlNU > .Op Fl a Ar maxcontig > .Op Fl b Ar block-size > .Op Fl c Ar cylinders > @@ -162,6 +162,12 @@ > The fragment size of the file system in bytes. > .It Fl i Ar bytes > Number of bytes per inode. > +.It Fl K > +Preserve contents of vnode-backed > +.Pq Dv MD_VNODE > +memory disk. > +Must be used in conjunction with > +.Fl F . > .It Fl l > Enable multilabel MAC on the new file system. > .It Fl L > Index: mdmfs.c > =================================================================== > RCS file: /home/fcvs/cvs/src/sbin/mdmfs/mdmfs.c,v > retrieving revision 1.20 > diff -u -3 -r1.20 mdmfs.c > --- mdmfs.c 17 May 2004 07:07:20 -0000 1.20 > +++ mdmfs.c 30 Nov 2004 10:51:56 -0000 > @@ -89,7 +89,7 @@ > *mount_arg; > enum md_types mdtype; /* The type of our memory disk. */ > bool have_mdtype; > - bool detach, softdep, autounit; > + bool detach, softdep, autounit, keepdata; > char *mtpoint, *unitstr; > char *p; > int ch; > @@ -119,7 +119,7 @@ > compat = true; > > while ((ch = getopt(argc, argv, > - "a:b:Cc:Dd:e:F:f:hi:LlMm:Nn:O:o:p:Ss:t:Uv:w:X")) != -1) > + "a:b:Cc:Dd:e:F:f:hi:KLlMm:Nn:O:o:p:Ss:t:Uv:w:X")) != -1) > switch (ch) { > case 'a': > argappend(&newfs_arg, "-a %s", optarg); > @@ -167,6 +167,8 @@ > usage(); > loudsubs = true; > break; > + case 'K': > + keepdata = true; > case 'l': > argappend(&newfs_arg, "-l"); > break; > @@ -233,7 +235,6 @@ > argv += optind; > if (argc < 2) > usage(); > - > /* Make compatibility assumptions. */ > if (compat) { > mi.mi_mode = 01777; > @@ -258,6 +259,11 @@ > mtpoint = argv[1]; > if (!have_mdtype) > mdtype = MD_SWAP; > + > + /* If we want to use vnode backed file and don't newfs it */ > + if (keepdata && mdtype != MD_VNODE) > + err(1, "Must specify -F with -K"); > + > if (softdep) > argappend(&newfs_arg, "-U"); > > @@ -268,7 +274,8 @@ > do_mdconfig_attach_au(mdconfig_arg, mdtype); > else > do_mdconfig_attach(mdconfig_arg, mdtype); > - do_newfs(newfs_arg); > + if (!keepdata) > + do_newfs(newfs_arg); > do_mount(mount_arg, mtpoint); > do_mtptsetup(mtpoint, &mi); > > @@ -665,13 +672,13 @@ > name = "mdmfs"; > if (!compat) > fprintf(stderr, > -"usage: %s [-DLlMNSUX] [-a maxcontig [-b block-size] [-c cylinders]\n" > +"usage: %s [-DKLlMNSUX] [-a maxcontig [-b block-size] [-c cylinders]\n" > "\t[-d rotdelay] [-e maxbpg] [-F file] [-f frag-size] [-i bytes]\n" > "\t[-m percent-free] [-n rotational-positions] [-O optimization]\n" > "\t[-o mount-options] [-p permissions] [-s size] [-w user:group]\n" > "\tmd-device mount-point\n", name); > fprintf(stderr, > -"usage: %s -C [-lNU] [-a maxcontig] [-b block-size] [-c cylinders]\n" > +"usage: %s -C [-lKNU] [-a maxcontig] [-b block-size] [-c cylinders]\n" > "\t[-d rotdelay] [-e maxbpg] [-F file] [-f frag-size] [-i bytes]\n" > "\t[-m percent-free] [-n rotational-positions] [-O optimization]\n" > "\t[-o mount-options] [-s size] md-device mount-point\n", name); > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 13:04:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55EF516A4CE; Tue, 30 Nov 2004 13:04:31 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B17D743D1D; Tue, 30 Nov 2004 13:04:30 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAUD81ai006963; Tue, 30 Nov 2004 06:08:01 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AC6FF8.40501@freebsd.org> Date: Tue, 30 Nov 2004 06:04:56 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Kargl References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041129233211.GA27426@troutmask.apl.washington.edu> In-Reply-To: <20041129233211.GA27426@troutmask.apl.washington.edu> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 13:04:31 -0000 Steve Kargl wrote: > On Mon, Nov 29, 2004 at 01:13:41PM -0800, Steve Kargl wrote: > >>kmem_suballoc: bad status return of 3 >>panic: kmem_suballoc >>cpuid = 0 >>KDB: stack backtrace: >>kdb_backtrace() at kdb_backtrace+0x37 >>panic() at painc+0x1d1 >>kmem_suballoc() at kmem_suballoc+0x93 >>kmeminit() at kmeminit+0x16d >>mi_startuup() at mi_startup+0xb6 >>btext90 at btext+0x2c >>KDB: enter: panic >>[thread pid 0 tid 0] >> >>This is a Tyan K8S Pro motherboard with 16 GB of PC2700 >>Cosair ECC memory. The BIOS was flashed to the latest >>available from Tyan. The scheduler is 4BSD. There are >>no ATA devices in the system and no ATA subsystem in >>the kernel. This a SCSI only box. World and kernel >>were rebuilt today with CFLAGS=-O -pipe and >>COPTFLAGS=-O -pipe. >> >>If I set hw.physmem="#G" n /boot/loader.conf where # is >>less than or equal to 8 the box boots up (see dmesg below). >>If # > 8, then we have the above panic. >> >>Any ideas where to look for the a fix? >> > > > (dmesg snipped) > (CC'd to -current because the may impact any system with >8 GB of ram) > > As a data point, I've downloaded, burned, and booted the netbsd/amd64 > ISO image. Netbsd's dmesg shows that netbsd correctly finds 16 GB > of memory on the system. > I fixed this on i386 a few months ago, and I applied a similar fix to amd64 on the advice of Peter Wemm. Go beat him up on this one =-) Scott From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 13:12:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1FF016A4CF; Tue, 30 Nov 2004 13:12:56 +0000 (GMT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EC8243D2D; Tue, 30 Nov 2004 13:12:56 +0000 (GMT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id iAUDCtSG017209 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Nov 2004 08:12:55 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id iAUDCTwR029514; Tue, 30 Nov 2004 08:12:29 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16812.29117.221988.730885@grasshopper.cs.duke.edu> Date: Tue, 30 Nov 2004 08:12:29 -0500 (EST) To: "Kenneth D. Merry" In-Reply-To: <20041130035552.GA32924@nargothrond.kdm.org> References: <20041130035552.GA32924@nargothrond.kdm.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@FreeBSD.org Subject: Re: -current hang during boot on SMP machine X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 13:12:56 -0000 Have you tried disabling ACPI via hint.acpi.0.disabled="1" in /boot/loader.conf The ACPI on these older machines is pretty bad. I have a very similar SuperMicro machine w/o SCSI at work which runs 5.3-R fine w/ACPI disabled. I discovered early in the 5.0 cycle that enabling ACPI would lead to a console message for each fxp0 interrupt.. Drew From owner-freebsd-current@FreeBSD.ORG Mon Nov 29 16:16:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5879E16A4CE for ; Mon, 29 Nov 2004 16:16:40 +0000 (GMT) Received: from smtpauth01.mail.atl.earthlink.net (smtpauth01.mail.atl.earthlink.net [209.86.89.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2768143D31 for ; Mon, 29 Nov 2004 16:16:40 +0000 (GMT) (envelope-from welchsm@earthlink.net) Received: from [66.41.102.215] (helo=NitroPhys.welchsmnet.net) by smtpauth01.mail.atl.earthlink.net with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1CYoCd-0006Mq-PP; Mon, 29 Nov 2004 11:16:39 -0500 Received: from NitroPhys.welchsmnet.net (localhost [127.0.0.1]) iATGGDhL069588; Mon, 29 Nov 2004 10:16:13 -0600 (CST) (envelope-from welchsm@localhost.welchsmnet.net) Received: (from welchsm@localhost) by NitroPhys.welchsmnet.net (8.13.1/8.13.1/Submit) id iATGGDaS069584; Mon, 29 Nov 2004 10:16:13 -0600 (CST) (envelope-from welchsm) Date: Mon, 29 Nov 2004 10:16:13 -0600 From: Sean Welch To: Dan Nelson Message-ID: <20041129161613.GA53189@NitroPhys.welchsmnet.net> References: <20041128233704.GB62951@NitroPhys.welchsmnet.net> <20041129154805.GD5518@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041129154805.GD5518@dan.emsphone.com> User-Agent: Mutt/1.5.6i X-ELNK-Trace: 15d86f98c8ef8acad780f4a490ca69563f9fea00a6dd62bc9559c7fcca35abee6fff7359eb55af82350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.41.102.215 X-Mailman-Approved-At: Tue, 30 Nov 2004 13:14:42 +0000 cc: freebsd-current@FreeBSD.org Subject: Re: top under 5.3-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Sean_Welch@alum.wofford.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 16:16:40 -0000 On Mon, Nov 29, 2004 at 09:48:05AM -0600, Dan Nelson wrote: > For things like port builds, you end up with a lot of very short-lived > processes (sh, sed, cc, etc). Those either don't show up in top at all > becuase they have started and exited between the sampling intervals, or > else have not accumulated enough CPU time to register any %CPU (which > is a weighted average over time). Ah. Thank you for filling me in. > The values should total up better when you have processes that hang > around a bit more. There was a regression in 5.3's libpthreads that > can make it report 0 CPU, so if you have some CPU-hungry threaded > programs, they may not show up in top at all even though they're using > 100% cpu. libthr and libc_r report CPU correctly. Okay. Mostly what I've been seeing so far is the first scenario (as I'm still trying to set up the system the way I like it), but I'll file away the second for when I start hammering it in normal use. Sean From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 15:34:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB6FE16A4CF for ; Tue, 30 Nov 2004 15:34:06 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [194.213.218.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5733243D54 for ; Tue, 30 Nov 2004 15:34:06 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from [127.0.0.1] (localhost [127.0.0.1]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id iAUFXuFp047803; Tue, 30 Nov 2004 16:33:57 +0100 (CET) (envelope-from mime@traveller.cz) Message-ID: <41AC92DE.8080402@traveller.cz> Date: Tue, 30 Nov 2004 16:33:50 +0100 From: Michal Mertl User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; cs-CZ; rv:1.7.3) Gecko/20041117 X-Accept-Language: cs, en-us, en MIME-Version: 1.0 To: Ruben de Groot References: <41AC57BF.6060604@traveller.cz> <20041130120856.GA44543@ei.bzerk.org> In-Reply-To: <20041130120856.GA44543@ei.bzerk.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: enhacement to mdmfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 15:34:07 -0000 Ruben de Groot wrote: > On Tue, Nov 30, 2004 at 12:21:35PM +0100, Michal Mertl typed: > >>Hello, >> >>I've recently shot my foot with mdmfs. Of course it was a pilot error but >>the funcioanility I was looking for might be usefull. >> >>I want to mount vnode-backed md(4) on boot without formatting it (e.g. for >>a jail). Is it possible with current boot scripts? >> >>I wrote a simple patch to mdmfs so such md disk can be put in /etc/fstab. >>It adds '-K' option do mdmfs(8) to Keep contents. The line to attach such >>disk in fstab looks like this: >> >>md /jail mfs rw,-K,-F=/var/jailfile 0 0 >> >>Comments welcome. If people find it usefull I'd like to have it commited. I >>can fill the PR with enhancement request. > > > I filed a PR about this allready in October 2003: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=57641 > > Ruben > Indeed. The patch is almost the same. Last update is from today stating it will be commited. Hurray. -- Michal From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 15:37:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7945616A4CE; Tue, 30 Nov 2004 15:37:57 +0000 (GMT) Received: from lon-mail-2.gradwell.net (lon-mail-2.gradwell.net [193.111.201.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 841D443D2D; Tue, 30 Nov 2004 15:37:56 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from cpc3-oxfd4-4-0-cust42.oxfd.cable.ntl.com ([80.3.247.42] helo=mail.cbhnet) 1.156) id 41ac93d3.13f20.52; Tue, 30 Nov 2004 15:37:55 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.cbhnet (Postfix) with ESMTP id 87CBE31B018; Tue, 30 Nov 2004 15:37:52 +0000 (GMT) Received: from mail.cbhnet ([127.0.0.1]) by localhost (mail.cbhnet [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 24914-07-2; Tue, 30 Nov 2004 15:37:52 +0000 (GMT) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.cbhnet (Postfix) with ESMTP id 3BE2D31AFF6; Tue, 30 Nov 2004 15:37:52 +0000 (GMT) Date: Tue, 30 Nov 2004 15:37:52 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: Marcel Moolenaar In-Reply-To: <20041129183511.GA84117@ns1.xcllnt.net> Message-ID: <20041130153044.E20313@teapot.cbhnet> References: <20041127193532.X15946@teapot.cbhnet> <20041129133825.GL7232@darkness.comp.waw.pl> <20041129183511.GA84117@ns1.xcllnt.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at chrishedley.com cc: freebsd-current@FreeBSD.org cc: Pawel Jakub Dawidek Subject: Re: GEOM: gpt partitions on a gmirror array possible? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 15:37:57 -0000 On Mon, 29 Nov 2004, Marcel Moolenaar wrote: > On Mon, Nov 29, 2004 at 02:38:25PM +0100, Pawel Jakub Dawidek wrote: >> >> It is because GEOM_GPT class only allow to create GPT labels on rank#1 >> providers (i.e. disks). I'm not sure why we have this hack, maybe marcel@ >> knows something more (cc'ed). > > It's there, because it was there for the MBR class when I used that > class as a blueprint for implementing GPT support. Since GPT is not > allowed within an MBR slice, or within a GPT partition (no nesting), > not to mention all the non-native partitioning schemes that GEOM > supports, that test made sure we only tasted GPT partitions on the > one kind of providers that existed besides slicers: disks. > > I guess a change like geom_mbr.c:1.57 is in order, or a more to-the- > point test for rejecting GPT on MBR or GPT on GPT. Thanks for the quick responses, guys. While the great and good are considering it, I may in the meantime throw caution to the wind and see if I can make some appropriately ad hoc changes to my own system. Any suggestions before I start butchering the file in question? Maybe since I no longer need more than 7 partitions per logical volume I should go back to using bsdlabel for the time being, although that feels too much like taking the easy way out. :) Chris. From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 17:16:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F2E716A4CE for ; Tue, 30 Nov 2004 17:16:36 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC14043D1D for ; Tue, 30 Nov 2004 17:16:35 +0000 (GMT) (envelope-from dr.clau@gmail.com) Received: by rproxy.gmail.com with SMTP id b11so517620rne for ; Tue, 30 Nov 2004 09:16:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:disposition-notification-to:date:from:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:x-enigmail-supports:content-type; b=Q6RvaFbYuWpguwwT6kwKX6zDUpxmWuBVRSSC5uguAj76ZRVNrkz3je2r7a2VRnUyhk2gGa+WoN/4GXKrnO6wVPHwgiFC0ygn3dtpWF/7uVBzmuOey9VtIrujIUvADsyRxiczoZAkTHlfgfHVnJt5i2OX3v/CAp7PQeusVTIFWDk= Received: by 10.38.161.9 with SMTP id j9mr567021rne; Tue, 30 Nov 2004 09:16:34 -0800 (PST) Received: from ?82.79.29.15? ([82.79.29.15]) by smtp.gmail.com with ESMTP id 79sm16306rna; Tue, 30 Nov 2004 09:16:34 -0800 (PST) Message-ID: <41ACAB34.4080504@gmail.com> Date: Tue, 30 Nov 2004 19:17:40 +0200 From: Claudiu Dragalia-Paraipan User-Agent: Mozilla Thunderbird 0.9 (X11/20041125) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org References: <41AA0043.5070109@gmail.com> <20041129185152.GF804@cirb503493.alcatel.com.au> <41AB84A6.50309@freebsd.org> In-Reply-To: <41AB84A6.50309@freebsd.org> X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8BCC1E1365E1E9112FCFF675" cc: current@freebsd.org Subject: Re: ssh & select() problem on 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 17:16:36 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8BCC1E1365E1E9112FCFF675 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Just for the record, the problem is solved. It was indeed a misconfiguration at the next hop, at the provider. Thank you. With respect, -- Claudiu Dragalina-Paraipan dr.clau@gmail.com --------------enig8BCC1E1365E1E9112FCFF675 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBrKs4m0FWxb+swkQRAuYyAKCJ6Nw031TRyKATpexVbAHmpVY6OgCfbUQz nwJHfuGQKkO3xiDRHhFnw1o= =26WP -----END PGP SIGNATURE----- --------------enig8BCC1E1365E1E9112FCFF675-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 18:35:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59D8016A4CE; Tue, 30 Nov 2004 18:35:56 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D0EE43D3F; Tue, 30 Nov 2004 18:35:56 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAUIZtvr032286; Tue, 30 Nov 2004 10:35:55 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAUIZteg032285; Tue, 30 Nov 2004 10:35:55 -0800 (PST) (envelope-from sgk) Date: Tue, 30 Nov 2004 10:35:55 -0800 From: Steve Kargl To: Scott Long Message-ID: <20041130183555.GA32237@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041129233211.GA27426@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AC6FF8.40501@freebsd.org> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 18:35:56 -0000 On Tue, Nov 30, 2004 at 06:04:56AM -0700, Scott Long wrote: > Steve Kargl wrote: > >On Mon, Nov 29, 2004 at 01:13:41PM -0800, Steve Kargl wrote: > > > >>kmem_suballoc: bad status return of 3 > >>panic: kmem_suballoc > >>cpuid = 0 > >>KDB: stack backtrace: > >>kdb_backtrace() at kdb_backtrace+0x37 > >>panic() at painc+0x1d1 > >>kmem_suballoc() at kmem_suballoc+0x93 > >>kmeminit() at kmeminit+0x16d > >>mi_startuup() at mi_startup+0xb6 > >>btext90 at btext+0x2c > >>KDB: enter: panic > >>[thread pid 0 tid 0] > >> > >>This is a Tyan K8S Pro motherboard with 16 GB of PC2700 > >>Cosair ECC memory. The BIOS was flashed to the latest > >>available from Tyan. The scheduler is 4BSD. There are > >>no ATA devices in the system and no ATA subsystem in > >>the kernel. This a SCSI only box. World and kernel > >>were rebuilt today with CFLAGS=-O -pipe and > >>COPTFLAGS=-O -pipe. > >> > >>If I set hw.physmem="#G" n /boot/loader.conf where # is > >>less than or equal to 8 the box boots up (see dmesg below). > >>If # > 8, then we have the above panic. > >> > >>Any ideas where to look for the a fix? > >> > > > >(dmesg snipped) > >(CC'd to -current because the may impact any system with >8 GB of ram) > > > >As a data point, I've downloaded, burned, and booted the netbsd/amd64 > >ISO image. Netbsd's dmesg shows that netbsd correctly finds 16 GB > >of memory on the system. > > > > I fixed this on i386 a few months ago, and I applied a similar fix to > amd64 on the advice of Peter Wemm. Go beat him up on this one =-) > Well, I have more data and Peter advice may have been correct. >From the beastie menu :-O, I dropped to the loader prompt. If I do set hint.acpi.0.disabled="1" set hw.phymem="6G" The system boots up fine (although I thought AMD64 required acpi). Next, if I do set hint.acpi.0.disabled="1" set hw.phymem="16G" The system starts to boot and dmesg reports the 16 GB of memory, but I rapidly get this panic. Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xffffffff80af6a80 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff802a5814 stack pointer = 0x10:0xffffffff80728a30 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 0 (swapper) [thread pid 0 tid 0] Stopped at isitmychild+0x4: decl %eax db> trace isitmychild() at isitmychild+0x4 isitmydescendant() at isitmydescendant+0x16 witness_checkorder() at witness_checkorder+0x44a _mtx_lock_flags() at _mtx_lock_flags+0x7a lim_hold() at lim_hold+0x29 fork1() at fork1+0xaa0 kthread_create() at kthread_create+0xa3 ktrace_init() at ktrace_init+0xe4 mi_startup() at mi_startup+0xb6 So, it looks like ACPI on this Tyan motherboard is restricting the memory to 8G. -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 18:45:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2106D16A639 for ; Tue, 30 Nov 2004 18:45:21 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8B7C43D55 for ; Tue, 30 Nov 2004 18:45:19 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAUImp6R008357; Tue, 30 Nov 2004 11:48:51 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41ACBFD9.3000507@freebsd.org> Date: Tue, 30 Nov 2004 11:45:45 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Garance A Drosihn References: <41AB3B8A.4040206@magnesium.net> <41AB44F4.1000106@freebsd.org> <20041129162032.GA5785@orion.daedalusnetworks.priv> <20041129.101105.129339938.imp@bsdimp.com> <1101823969.41ac7fe1700d5@netchild.homeip.net> In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Alexander Leidinger cc: freebsd-current cc: "M. Warner Losh" Subject: Re: boot menu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 18:45:21 -0000 Garance A Drosihn wrote: > At 3:12 PM +0100 11/30/04, Alexander Leidinger wrote: > >> Zitat von Garance A Drosihn : >> >>> Another thought came to me last night. We could leave the startup >>> as it is (without a menu), but if someone hits the space bar we >>> could print out a single line which says "Type 'menu' to see a >>> menu of common boot options". That menu would not need any >>> countdown timer on it, because it would only come up when someone >>> had asked for it. And screen-clearing should not be a problem, >>> since the menu only pops up after someone asks for it. >> >> >> This doesn't work. The intend is to make it easy for newbies (and >> tuneable for others). How do newbies know they have to press a key >> to be able to circumvent their problems (e.g. disabling ACPI)? > > > Because the standard one-line prompt tells them to. "press any > key but ENTER to see what boot options you have", or something > like that. It's just a matter of picking the right line or two. > > I personally wouldn't mind having the menu there by default, but > some people have mentioned an issue with the clear-screen in it, > or that a larger menu slows down booting on a serial console. > I'm just trying to suggest ideas which should avoid those issues, > but will still provide a menu for the novice/casual FreeBSD user. > > But at this point I think I've made enough suggestions, so I'm > waiting to see what others think we should do. > So I gave 4 options in another email, but haven't seen any real response to those yet. For a refresher: 1) 'Classic'. Just as it is in 5-STABLE 2) 'Enhanced'. Compound menus, switchable logo or no logo, [Space] re-assigned to Exit. On-line help. Maybe even smart enough to save its own configuration settings. 3) 'Minimal'. No frames, logos, timers, etc. Just the menu options. Possibly auto-selected if it detects that its on the comconsole. Not sure how this would work for sparc64 and alpha, though. 4) 'None'. No menu at all. The plan would be to have these 4 options be selectable in 6-CURRENT. The default would be 'Enhanced'. Scott From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 18:56:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB28A16A4CE; Tue, 30 Nov 2004 18:56:04 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8320643D2F; Tue, 30 Nov 2004 18:56:04 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iAUIuuIQ027202; Tue, 30 Nov 2004 10:56:56 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iAUIuuUu027201; Tue, 30 Nov 2004 10:56:56 -0800 Date: Tue, 30 Nov 2004 10:56:56 -0800 From: Brooks Davis To: Scott Long Message-ID: <20041130185656.GA23281@odin.ac.hmc.edu> References: <41AB3B8A.4040206@magnesium.net> <41AB44F4.1000106@freebsd.org> <20041129162032.GA5785@orion.daedalusnetworks.priv> <20041129.101105.129339938.imp@bsdimp.com> <1101823969.41ac7fe1700d5@netchild.homeip.net> <41ACBFD9.3000507@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <41ACBFD9.3000507@freebsd.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: Alexander Leidinger cc: freebsd-current cc: Garance A Drosihn cc: "M. Warner Losh" Subject: Re: boot menu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 18:56:04 -0000 --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 30, 2004 at 11:45:45AM -0700, Scott Long wrote: > Garance A Drosihn wrote: > >At 3:12 PM +0100 11/30/04, Alexander Leidinger wrote: > > > >>Zitat von Garance A Drosihn : > >> > >>> Another thought came to me last night. We could leave the startup > >>> as it is (without a menu), but if someone hits the space bar we > >>> could print out a single line which says "Type 'menu' to see a > >>> menu of common boot options". That menu would not need any > >>> countdown timer on it, because it would only come up when someone > >>> had asked for it. And screen-clearing should not be a problem, > >>> since the menu only pops up after someone asks for it. > >> > >> > >>This doesn't work. The intend is to make it easy for newbies (and > >>tuneable for others). How do newbies know they have to press a key > >>to be able to circumvent their problems (e.g. disabling ACPI)? > > > > > >Because the standard one-line prompt tells them to. "press any > >key but ENTER to see what boot options you have", or something > >like that. It's just a matter of picking the right line or two. > > > >I personally wouldn't mind having the menu there by default, but > >some people have mentioned an issue with the clear-screen in it, > >or that a larger menu slows down booting on a serial console. > >I'm just trying to suggest ideas which should avoid those issues, > >but will still provide a menu for the novice/casual FreeBSD user. > > > >But at this point I think I've made enough suggestions, so I'm > >waiting to see what others think we should do. > > >=20 > So I gave 4 options in another email, but haven't seen any real response > to those yet. For a refresher: >=20 > 1) 'Classic'. Just as it is in 5-STABLE > 2) 'Enhanced'. Compound menus, switchable logo or no logo, [Space]=20 > re-assigned to Exit. On-line help. Maybe even smart enough to > save its own configuration settings. > 3) 'Minimal'. No frames, logos, timers, etc. Just the menu options. > Possibly auto-selected if it detects that its on the comconsole. Not > sure how this would work for sparc64 and alpha, though. > 4) 'None'. No menu at all. >=20 > The plan would be to have these 4 options be selectable in 6-CURRENT. > The default would be 'Enhanced'. This sounds ideal. I'd prefer to be pretty agressive about falling back to minimal so if we aren't 100% sure we're on a display with well known characteristics (like the BIOS console) we fall back. Specificaly, I'd prefer that all remote consoles including dcons avoid anything more complicated then scrolling. IMO sparc64 should always do minimal. The basic emulated text console is so incrediably crappy as to be useless for anything else (which is probably why the basic interactive commands in Solaris have such simple looking interfaces). -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBrMJ3XY6L6fI4GtQRAt6XAJ4lwARv2XTNbbjIP9eDhA5KVp5tOACfR0X4 7f0fVTBaZ90Z5jjebXuX2SA= =zWK7 -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 19:36:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 551C216A4CE; Tue, 30 Nov 2004 19:36:27 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE4A743D72; Tue, 30 Nov 2004 19:36:26 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAUJaP0n083806; Tue, 30 Nov 2004 14:36:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iAUJaOKF066314; Tue, 30 Nov 2004 14:36:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 230797306E; Tue, 30 Nov 2004 14:36:25 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041130193625.230797306E@freebsd-current.sentex.ca> Date: Tue, 30 Nov 2004 14:36:25 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 19:36:27 -0000 TB --- 2004-11-30 18:14:59 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-30 18:14:59 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-11-30 18:14:59 - checking out the source tree TB --- 2004-11-30 18:14:59 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-11-30 18:14:59 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-30 18:21:40 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-30 18:21:40 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-30 18:21:40 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-30 19:28:37 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-30 19:28:37 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-30 19:28:37 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Nov 30 19:28:37 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/sys_machdep.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/trap.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/tsc.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/uio_machdep.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/uma_machdep.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/amd64/amd64/vm_machdep.c /tinderbox/CURRENT/amd64/amd64/src/sys/amd64/amd64/vm_machdep.c: In function `cpu_reset': /tinderbox/CURRENT/amd64/amd64/src/sys/amd64/amd64/vm_machdep.c:339: warning: unused variable `cnt' *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-11-30 19:36:24 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-30 19:36:24 - ERROR: failed to build generic kernel TB --- 2004-11-30 19:36:24 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 19:42:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C9CA16A4CE; Tue, 30 Nov 2004 19:42:29 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id E19A443D5A; Tue, 30 Nov 2004 19:42:28 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAUJgR46032675; Tue, 30 Nov 2004 11:42:27 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAUJgRZs032674; Tue, 30 Nov 2004 11:42:27 -0800 (PST) (envelope-from sgk) Date: Tue, 30 Nov 2004 11:42:27 -0800 From: Steve Kargl To: "Ketrien I. Saihr-Kenchedra" Message-ID: <20041130194227.GA32604@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041129233211.GA27426@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041130142652.A59122@bahre.achedra.org> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: Scott Long cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 19:42:29 -0000 On Tue, Nov 30, 2004 at 02:35:30PM -0500, Ketrien I. Saihr-Kenchedra wrote: > On Tue, 30 Nov 2004, Steve Kargl wrote: > > > >The system starts to boot and dmesg reports the 16 GB of memory, but > >I rapidly get this panic. > > >So, it looks like ACPI on this Tyan motherboard is restricting > >the memory to 8G. > > I presume you're using CM74SD2048RLP-2700/S DIMMs? (Corsair/Samsung 2GB > ECC Reg'd.) Yes. > More importantly, which BIOS version? You have to run the 2.03 BIOS on > the K8SPro if you're running 16GB. Make sure that ccNUMA support is off > in the BIOS as well - this was a never-ending source of fun on both the > S2882 and S4882's. I can't tell you exactly why, but having ccNUMA on > with the S4882 and S288x's is a never-ending font of panic()s. But the > 2.01 and 2.02 BIOSes on the S2882 are exceptionally miserable. > At least it's not an S4882 1.02: > "DDR 400MHz Memmory Detected" > The BIOS is at 2.03. I haven't tried turning off the ccNUMA support. I'll give it a shot in a moment. -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 19:57:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8650416A4CE; Tue, 30 Nov 2004 19:57:02 +0000 (GMT) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DEF043D5E; Tue, 30 Nov 2004 19:57:02 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iAUJuxoU023700; Tue, 30 Nov 2004 14:57:00 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <41ACBFD9.3000507@freebsd.org> References: <41AB3B8A.4040206@magnesium.net> <41AB44F4.1000106@freebsd.org> <20041129162032.GA5785@orion.daedalusnetworks.priv> <20041129.101105.129339938.imp@bsdimp.com> <1101823969.41ac7fe1700d5@netchild.homeip.net> <41ACBFD9.3000507@freebsd.org> Date: Tue, 30 Nov 2004 14:56:58 -0500 To: Scott Long From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-current@freebsd.org Subject: Re: boot menu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 19:57:02 -0000 At 11:45 AM -0700 11/30/04, Scott Long wrote: >Garance A Drosihn wrote: >> >>I personally wouldn't mind having the menu there by default, but >>some people have mentioned an issue with the clear-screen in it, >>or that a larger menu slows down booting on a serial console. >>I'm just trying to suggest ideas which should avoid those issues, >>but will still provide a menu for the novice/casual FreeBSD user. >> >>But at this point I think I've made enough suggestions, so I'm >>waiting to see what others think we should do. > >So I gave 4 options in another email, but haven't seen any real >response to those yet. Hmm. I do not remember seeing that email, and I can't find it in any of my mailboxes or my trash. I did get the message from Michael saying that the discussion should be moved to freebsd-current, but until this message I haven't seen the discussion pop up here. >For a refresher: > >1) 'Classic'. Just as it is in 5-STABLE >2) 'Enhanced'. Compound menus, switchable logo or no logo, > [Space] re-assigned to Exit. On-line help. Maybe even > smart enough to save its own configuration settings. >3) 'Minimal'. No frames, logos, timers, etc. Just the menu > options. Possibly auto-selected if it detects that its on > the comconsole. Not sure how this would work for sparc64 > and alpha, though. >4) 'None'. No menu at all. > >The plan would be to have these 4 options be selectable in >6-CURRENT. The default would be 'Enhanced'. Seems to me I should have some strong opinion on this, but my main desire is just that *some* helpful menu is available for the novice/casual FreeBSD user. On the minor nitpicking front, I would think that if you have multiple options (like the above), the key sequences would be mostly the same between the options. This implies that the 'classic' menu would also have [space] re-assigned to exit for option #1. And to keep things friendly for novice/casual users, I think that "exit" would include writing out a single-line that tells the user how to get back into the menus. That way, if someone hit space by mistake, they will have a pointer on how to get back to where they were. It does seem like a bunch of extra work to have three different sets of menus, and then have an option to select which menus to use for selecting options. Now that I (finally) have serial consoles on most of my FreeBSD machines, I kinda like the idea of always coming up in a very minimal prompt (more like 4.x), and then having a single boot-loader command which would fire up the helpful menus. Preferably the 'enhanced' menus from your proposal. But if you're willing to do the extra work, I can certainly live with the result... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 20:02:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 460AE16A4CE for ; Tue, 30 Nov 2004 20:02:56 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E409243D5C for ; Tue, 30 Nov 2004 20:02:55 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 4A9977A403; Tue, 30 Nov 2004 12:02:55 -0800 (PST) Message-ID: <41ACD1EF.7020704@elischer.org> Date: Tue, 30 Nov 2004 12:02:55 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Dan Nelson References: <20041128233704.GB62951@NitroPhys.welchsmnet.net> <20041129154805.GD5518@dan.emsphone.com> <41AB8174.4090205@elischer.org> <20041129205408.GH5518@dan.emsphone.com> <41AB9151.8070601@elischer.org> <20041130053040.GL5518@dan.emsphone.com> In-Reply-To: <20041130053040.GL5518@dan.emsphone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: Sean Welch Subject: Re: top under 5.3-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:02:56 -0000 Dan Nelson wrote: >In the last episode (Nov 29), Julian Elischer said: > > >>understood.. but when 'ps' gets the information, it gets each >>thread.. where does the info get stored? the threads may have just >>flashed into existence a fraction of a second ago, and prior to that >>thay may have belonged to a compeltely different process. It's not a >>simple problem. However there may be some relatively "ok" answers if >>we can define well enough what we want to see. For example all >>taking the total cputime for the KSEGRP and dividing it by the number >>of non-sleeping threads might be a possibility. (or some variant of >>that). >> >> > >Is the real problem that %CPU and WCPU are no longer used by the >schedulers in any meaningful way? I thought at one point they were >used to dampen the priority of cpu-intensive proceses. Maybe they >should be removed and replaced with some other counters that can record >cpu usage better. %CPU can certainly be extracted by subtracting the >"struct rusage" values every sampling interval; unixtop does that for >quite a few OSes where %CPU isn't available or is useless. WCPU is >nice to get a longer-term picture of what processes are consistently >using CPU though. I suppose top could maintain its own running average >by averaging its calculated %CPU over an interval, but ps couldn't. > Actually the problem is deper than that. Prior behaviour SHOULD be used by the schedulers but there is no way for us to meaningfully track it for a threaded program. (for the reasons mentionned before). From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 20:15:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DF4F16A4CE; Tue, 30 Nov 2004 20:15:23 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id D639043D45; Tue, 30 Nov 2004 20:15:22 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iAUKFMm1093023; Tue, 30 Nov 2004 12:15:22 -0800 (PST) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.13.1/8.13.1/Submit) id iAUKFMNd093022; Tue, 30 Nov 2004 12:15:22 -0800 (PST) (envelope-from marcel) Date: Tue, 30 Nov 2004 12:15:22 -0800 From: Marcel Moolenaar To: Chris Hedley Message-ID: <20041130201522.GA92745@ns1.xcllnt.net> References: <20041127193532.X15946@teapot.cbhnet> <20041129133825.GL7232@darkness.comp.waw.pl> <20041129183511.GA84117@ns1.xcllnt.net> <20041130153044.E20313@teapot.cbhnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041130153044.E20313@teapot.cbhnet> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: Pawel Jakub Dawidek Subject: Re: GEOM: gpt partitions on a gmirror array possible? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:15:23 -0000 On Tue, Nov 30, 2004 at 03:37:52PM +0000, Chris Hedley wrote: > > > >I guess a change like geom_mbr.c:1.57 is in order, or a more to-the- > >point test for rejecting GPT on MBR or GPT on GPT. > > Any suggestions before I start butchering the file in question? Removal of the following should do it without causing problems: if (gp->rank != 2 && insist == 0) break; In fact, this is the fix I'm considering. The strength of GEOM is that you can create arbitrary layering and nesting and imposing limitations seems counter productive. There may be an advantage to allow GPT on MBR or GPT on GPT even if it's disallowed under EFI. We already allow the use of GPT outside the context of EFI... BTW: I will then probably also enforce that if there's a MBR sector front of the GPT table, it must be a PMBR. Use of GPT on a boot disk is possible by putting a GPT table inside an MBR slice. In a sense, I trade width for depth :-) -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 20:28:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A2BF16A4CE; Tue, 30 Nov 2004 20:28:24 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 017C743D39; Tue, 30 Nov 2004 20:28:24 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iAUKTM32010341; Tue, 30 Nov 2004 12:29:22 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iAUKTMMB010340; Tue, 30 Nov 2004 12:29:22 -0800 Date: Tue, 30 Nov 2004 12:29:22 -0800 From: Brooks Davis To: Marcel Moolenaar Message-ID: <20041130202922.GC1335@odin.ac.hmc.edu> References: <20041127193532.X15946@teapot.cbhnet> <20041129133825.GL7232@darkness.comp.waw.pl> <20041129183511.GA84117@ns1.xcllnt.net> <20041130153044.E20313@teapot.cbhnet> <20041130201522.GA92745@ns1.xcllnt.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="E13BgyNx05feLLmH" Content-Disposition: inline In-Reply-To: <20041130201522.GA92745@ns1.xcllnt.net> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-current@freebsd.org cc: Pawel Jakub Dawidek cc: Chris Hedley Subject: Re: GEOM: gpt partitions on a gmirror array possible? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:28:24 -0000 --E13BgyNx05feLLmH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 30, 2004 at 12:15:22PM -0800, Marcel Moolenaar wrote: > On Tue, Nov 30, 2004 at 03:37:52PM +0000, Chris Hedley wrote: > > > > > >I guess a change like geom_mbr.c:1.57 is in order, or a more to-the- > > >point test for rejecting GPT on MBR or GPT on GPT. > >=20 > > Any suggestions before I start butchering the file in question? >=20 > Removal of the following should do it without causing problems: >=20 > if (gp->rank !=3D 2 && insist =3D=3D 0) > break; >=20 > In fact, this is the fix I'm considering. The strength of GEOM is > that you can create arbitrary layering and nesting and imposing > limitations seems counter productive. There may be an advantage to > allow GPT on MBR or GPT on GPT even if it's disallowed under EFI. > We already allow the use of GPT outside the context of EFI... I think this would be a very good idea. It's quite conceivable that we could end up wanting to put a GPT inside a sunlabel or an Apple partition table. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --E13BgyNx05feLLmH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBrNghXY6L6fI4GtQRAhv2AKCfN0arSBCkKJAIInJzCK3fVjnMcACfc7Gj qO1wC1GViFr9bCzLTYqhZXI= =Uf/+ -----END PGP SIGNATURE----- --E13BgyNx05feLLmH-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 20:30:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19A9516A4CE for ; Tue, 30 Nov 2004 20:30:17 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0146943D41 for ; Tue, 30 Nov 2004 20:30:16 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id AD6B07A403 for ; Tue, 30 Nov 2004 12:30:16 -0800 (PST) Message-ID: <41ACD858.6090801@elischer.org> Date: Tue, 30 Nov 2004 12:30:16 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: remote gdb with firewire. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:30:17 -0000 anyone have good crib sheets on doing this? just go my first firewire setup and looking forward to trying it. From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 20:32:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B217F16A4CE for ; Tue, 30 Nov 2004 20:32:54 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 600BF43D31 for ; Tue, 30 Nov 2004 20:32:54 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iAUKXkwL011476; Tue, 30 Nov 2004 12:33:46 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iAUKXkcB011475; Tue, 30 Nov 2004 12:33:46 -0800 Date: Tue, 30 Nov 2004 12:33:46 -0800 From: Brooks Davis To: Julian Elischer Message-ID: <20041130203346.GD1335@odin.ac.hmc.edu> References: <41ACD858.6090801@elischer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k4f25fnPtRuIRUb3" Content-Disposition: inline In-Reply-To: <41ACD858.6090801@elischer.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: FreeBSD Current Subject: Re: remote gdb with firewire. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:32:54 -0000 --k4f25fnPtRuIRUb3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 30, 2004 at 12:30:16PM -0800, Julian Elischer wrote: > anyone have good crib sheets on doing this? just go my first firewire=20 > setup and looking forward to trying it. The EXAMPLES section of the dconschat manpage has a set of good examples. If you're going to be using the machines for debugging, you'll definitely want to add them to /etc/eui64 so you can access them via host names. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --k4f25fnPtRuIRUb3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBrNkpXY6L6fI4GtQRAnUCAKCljAFnmBFIVv9/+HZPn+5rUqPe8gCgyBKV 0GSxUgCB/3vXnQ0Dvx6f9oo= =Lrhp -----END PGP SIGNATURE----- --k4f25fnPtRuIRUb3-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 20:34:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99FC116A4CE for ; Tue, 30 Nov 2004 20:34:29 +0000 (GMT) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5541443D31 for ; Tue, 30 Nov 2004 20:34:29 +0000 (GMT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.13.1/8.12.9) with ESMTP id iAUKYKK3023305; Tue, 30 Nov 2004 12:34:20 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.13.1/8.12.9) with ESMTP id iAUKYKoU073922; Tue, 30 Nov 2004 12:34:20 -0800 (PST) (envelope-from frank@realtime.exit.com) Received: (from frank@localhost) by realtime.exit.com (8.13.1/8.13.1/Submit) id iAUKYKkx073921; Tue, 30 Nov 2004 12:34:20 -0800 (PST) (envelope-from frank) From: Frank Mayhar Message-Id: <200411302034.iAUKYKkx073921@realtime.exit.com> In-Reply-To: <41ACD858.6090801@elischer.org> To: Julian Elischer Date: Tue, 30 Nov 2004 12:34:20 -0800 (PST) X-Copyright0: Copyright 2004 Frank Mayhar. All Rights Reserved. X-Copyright1: Permission granted for electronic reproduction as Usenet News or email only. X-Mailer: ELM [version 2.4ME+ PL119 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: FreeBSD Current Subject: Re: remote gdb with firewire. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: frank@exit.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:34:29 -0000 Julian Elischer wrote: > anyone have good crib sheets on doing this? just go my first firewire > setup and looking forward to trying it. I found Greg's src/tools/debugscripts/dot.gdbinit and friends helpful, although I hacked on them a bit so they match my idiosyncracies. :-) -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 20:57:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26BEE16A4CE for ; Tue, 30 Nov 2004 20:57:32 +0000 (GMT) Received: from sccimhc91.asp.att.net (sccimhc91.asp.att.net [63.240.76.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98DCB43D5E for ; Tue, 30 Nov 2004 20:57:31 +0000 (GMT) (envelope-from David.Boyd@insightbb.com) Received: from sneezy (12-202-176-78.client.insightbb.com[12.202.176.78]) by sccimhc91.asp.att.net (sccimhc91) with SMTP id <20041130205730i9100rgma7e>; Tue, 30 Nov 2004 20:57:30 +0000 From: "David Boyd" To: Date: Tue, 30 Nov 2004 15:58:24 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal Subject: Panic on shutdown -r now (RESOLVED?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:57:32 -0000 The following problem was reported (by me and others) from about 5.3-BETA4 through 5.3-RELEASE. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++ This problem persisted into 5.3-RELEASE. It may be related to panics reported by others. The problem appears to be related to SMP and HTT. It doesn't occur (for me) with GENERIC. It has been very difficult to obtain a "usable" dump. The system is usually locked tight. Kernel is built with KDB DDB and BREAK_TO_DEBUGGER. Even when the system gets as far as indicating that the panic has occurred, it seldom enters the debugger. Usually, when it does enter the debugger, the system ignores any key input, echoing colon or semicolon when the ENTER key is depressed. Oh, yeah! Once every fifty or so times the system will reboot normally. This problem started during BETA testing ... back around BETA4 or BETA5 as I recall. Here's what I have for today (system is from RC2 ISO image). from serial console: The garbage in the display after "Shutting down ACPI" is "normal" to this problem. ============================================================================ ================= KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RC2 #0: Mon Nov 1 14:48:42 EST 2004 root@comm-server.support.bsd1.net:/usr/src/sys/i386/compile/DEBUG ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2394.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 534970368 (510 MB) avail memory = 513937408 (490 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu1: Failed to attach throttling P_CNT pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf8000000-0xfbffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) uhci0: port 0xcc00-0xcc1f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd400-0xd41f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xd800-0xd81f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 atapci0: port 0xac00-0xac0f,0xb000-0xb003,0xb400-0xb407,0xb800-0xb803,0xbc00-0xbc07 mem 0xfeaf0000-0xfeafffff irq 17 at device 2.0 on pci2 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 rl0: port 0xa800-0xa8ff mem 0xfeadfc00-0xfeadfcff irq 19 at device 3.0 on pci2 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:0d:88:35:39:a0 rl1: port 0xa400-0xa4ff mem 0xfeadf800-0xfeadf8ff irq 18 at device 4.0 on pci2 miibus1: on rl1 rlphy1: on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl1: Ethernet address: 00:0d:88:37:d7:ba fxp0: port 0xa000-0xa03f mem 0xfeade000-0xfeadefff irq 20 at device 8.0 on pci2 miibus2: on fxp0 inphy0: on miibus2 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:11:11:0a:46:7b isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci1 ata1: channel #1 on atapci1 atapci2: port 0xdc00-0xdc0f,0xe000-0xe003,0xe400-0xe407,0xe800-0xe803,0xec00-0xec07 irq 18 at device 31.2 on pci0 ata4: channel #0 on atapci2 ata5: channel #1 on atapci2 pci0: at device 31.3 (no driver attached) pci0: at device 31.5 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 fdc0: port 0x3f7,0x3f4-0x3f5,0x3f2-0x3f3,0x3f0-0x3f1 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xd6800-0xd77ff,0xd5800-0xd67ff,0xcc000-0xd57ff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% acd0: CDROM at ata0-master UDMA33 ata1-slave: FAILURE - ATA_IDENTIFY timed out ata1-slave: FAILURE - ATA_IDENTIFY timed out ata1-master: FAILURE - SETFEATURES SET TRANSFER MODE status=1 error=4 ata1-slave: FAILURE - ATA_IDENTIFY timed out ata1-master: FAILURE - SETFEATURES SET TRANSFER MODE status=1 error=4 afd0: REMOVABLE at ata1-master BIOSPIO ad4: 76319MB [155061/16/63] at ata2-master UDMA100 ad6: 76319MB [155061/16/63] at ata3-master UDMA100 ar0: 76319MB [9729/255/63] status: READY subdisks: disk0 READY on ad4 at ata2-master disk1 READY on ad6 at ata3-master SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ar0s1a Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. kernel dumps on /dev/ar0s1b swapon: adding /dev/ar0s1b as swap device Starting file system checks: /dev/ar0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ar0s1a: clean, 2000849 free (585 frags, 250033 blocks, 0.0% fragmentation) /dev/ar0s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ar0s1d: clean, 3419753 free (40945 frags, 422351 blocks, 1.0% fragmentation) /dev/ar0s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ar0s1e: clean, 8121013 free (461 frags, 1015069 blocks, 0.0% fragmentation) /dev/ar0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ar0s1f: clean, 4061052 free (28 frags, 507628 blocks, 0.0% fragmentation) /dev/ar0s1g: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ar0s1g: clean, 2029028 free (28 frags, 253625 blocks, 0.0% fragmentation) /dev/ar0s1h: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ar0s1h: clean, 3045027 free (27 frags, 380625 blocks, 0.0% fragmentation) /dev/ar0s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ar0s2d: clean, 13470149 free (21 frags, 1683766 blocks, 0.0% fragmentation) Setting hostname: comm-server.support.bsd1.net. lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 Starting dhclient. fxp0: flags=8843 mtu 1500 options=8 inet6 fe80::211:11ff:fe0a:467b%fxp0 prefixlen 64 scopeid 0x3 inet 192.168.210.51 netmask 0xffffff00 broadcast 192.168.210.255 ether 00:11:11:0a:46:7b media: Ethernet autoselect (100baseTX ) status: active Additional routing options: IP gateway=YES. Starting devd. Mounting NFS file systems:. Starting syslogd. Nov 1 15:56:44 comm-server syslogd: kernel boot file is /boot/kernel/kernel Checking for core dump on /dev/ar0s1b ... savecore: no dumps found Setting date via ntp. Looking for host 192.168.210.1 and service ntp host found : free.bsd1.net 1 Nov 15:56:45 ntpdate[312]: step time server 192.168.210.1 offset 1.115163 sec ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout Starting usbd. Starting local daemons:. Updating motd. Configuring syscons: blanktime. Starting sshd. Initial i386 initialization:. Additional ABI support:. Starting cron. Local package initialization:. Additional TCP options:. Starting background file system checks in 60 seconds. Mon Nov 1 15:56:47 EST 2004 FreeBSD/i386 (comm-server.support.bsd1.net) (ttyd0) login: root Password: Nov 1 15:56:52 comm-server login: ROOT LOGIN (root) ON ttyd0 Last login: Mon Nov 1 15:10:59 on ttyd0 Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RC2 (DEBUG) #0: Mon Nov 1 14:48:42 EST 2004 Welcome to FreeBSD! Before seeking technical support, please use the following resources: o Security advisories and updated errata information for all releases are at http://www.FreeBSD.org/releases/ - always consult the ERRATA section for your release first as it's updated frequently. o The Handbook and FAQ documents are at http://www.FreeBSD.org/ and, along with the mailing lists, can be searched by going to http://www.FreeBSD.org/search/. If the doc distribution has been installed, they're also available formatted in /usr/share/doc. If you still have a question or problem, please take the output of `uname -a', along with any relevant error messages, and email it as a question to the questions@FreeBSD.org mailing list. If you are unfamiliar with FreeBSD's directory layout, please refer to the hier(7) manual page. If you are not familiar with manual pages, type `man man'. You may also use sysinstall(8) to re-enter the installation and configuration utility. Edit /etc/motd to change this login announcement. erase ^H, kill ^U, intr ^C status ^T FreeBSD cons25 ttyd0 [comm-server.support.bsd1.net:ttyd0:/root ]> shutdown -r now Shutdown NOW! shutdown: [pid 497] *** FINAL System shutdown message from root@comm-server.support.bsd1.net *** System going down IMMEDIATELY Nov 1 15:56:58 comm-server shutdown: reboot by root: [comm-server.support.bsd1.net:ttyd0:/root ]> System shutdown time has arrived Shutting down daemon processes:. Stopping cron. Shutting down local daemons:. Writing entropy file:. . Nov 1 15:57:00 comm-server syslogd: exiting on signal 15 boot() called on cpu#1 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...4 4 2 2 0 0 0 done No buffers busy after final sync Uptime: 52s Waiting (max 60 seconds) for system process `hpt_wt' to stop...done Shutting down ACPI kk e rFnaetla lt rdaopu b1l2e wfiatuhl ti:n t eerirpu p=t s0 xdci1s9aabcl4ebdc esp = 0x6460c19a ebp = 0x0 cpuid = 1; apic id = 01 panic: double fault cpuid = 1 KDB: enter: panic [thread 100002] Stopped at kdb_enter+0x2b: nop db> whre  ere kdb_enter(c08291f5) at kdb_enter+0x2b panic(c084267e,c08427ef,1,0,0) at panic+0x127 dblfault_handler() at dblfault_handler+0x7a --- trap 0x17, eip = 0xc19ac4bc, esp = 0x6460c19a, ebp = 0 --- _end() at 0xc19ac4bc db> trace kdb_enter(c08291f5) at kdb_enter+0x2b panic(c084267e,c08427ef,1,0,0) at panic+0x127 dblfault_handler() at dblfault_handler+0x7a --- trap 0x17, eip = 0xc19ac4bc, esp = 0x6460c19a, ebp = 0 --- _end() at 0xc19ac4bc db> call doae dump Dumping 510 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 Dump complete 0xf db> reset cpu_reset called on cpu#1 cpu_reset: Restarting BSP cpu_reset_proxy: Stopped CPU 1 from kgdb: ============================================================================ ================= kgdb kernel.debug vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". doadump () at pcpu.h:159 (kgdb) whre  ere #0 doadump () at pcpu.h:159 #1 0xc0460cd6 in db_fncall (dummy1=0, dummy2=0, dummy3=-1064198276, dummy4=0xc0919f64 "\230\237\221À\200%") at ../../../ddb/db_command.c:531 #2 0xc0460ae4 in db_command (last_cmdp=0xc08c7a44, cmd_table=0x0, aux_cmd_tablep=0xc0848104, aux_cmd_tablep_end=0xc0848120) at ../../../ddb/db_command.c:349 #3 0xc0460bac in db_command_loop () at ../../../ddb/db_command.c:455 #4 0xc0462725 in db_trap (type=3, code=0) at ../../../ddb/db_main.c:221 #5 0xc062adc7 in kdb_trap (type=3, code=0, tf=0x1) at ../../../kern/subr_kdb.c:418 #6 0xc07c2f74 in trap (frame= {tf_fs = -1064239080, tf_es = -1067319280, tf_ds = -1065222128, tf_edi = -1065081218, tf_esi = 1, tf_ebp = -1064197916, tf_isp = -1064197936, tf_ebx = -1064197872, tf_edx = 0, tf_ecx = -1056882688, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1067275477, tf_cs = 8, tf_eflags = 16534, tf_esp = -1064197884, tf_ss = -1067371761}) at ../../../i386/i386/trap.c:576 #7 0xc07b0d1a in calltrap () at ../../../i386/i386/exception.s:140 #8 0xc0910018 in sc_buffer.5 () #9 0xc0620010 in umtx_remove (uq=0xc091a110, td=0x0) at ../../../kern/kern_umtx.c:135 #10 0xc061330f in panic (fmt=0xc084267e "double fault") at ../../../kern/kern_shutdown.c:537 #11 0xc07c3566 in dblfault_handler () at ../../../i386/i386/trap.c:838 #12 0x00000000 in ?? () (kgdb) quit [comm-server.support.bsd1.net:ttyd0:/var/crash ]> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++ The following commit seems to have cured the problem. Edit src/sys/kern/kern_shutdown.c Add delta 1.163.2.3 2004.11.29.19.11.36 njl If this fix does, in fact, address this problem, can I expect to see it in an official patch to 5.3-RELEASE? This is the only issue keeping us from upgrading/deploying 5.3-RELEASE on all (twenty-two at last count) of our production servers. I can't get an agreement to deploy 5.3-STABLE from my management, so it's 5.3-RELEASE-px or wait until 5.4-RELEASE. I'd rather not wait. Thanks for any information that you can supply. From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 20:58:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1007616A4CE; Tue, 30 Nov 2004 20:58:29 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89C0643D5A; Tue, 30 Nov 2004 20:58:28 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iAUKwRfO097055; Tue, 30 Nov 2004 15:58:27 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iAUKwQQj010311; Tue, 30 Nov 2004 15:58:26 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id D98667306E; Tue, 30 Nov 2004 15:58:26 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041130205826.D98667306E@freebsd-current.sentex.ca> Date: Tue, 30 Nov 2004 15:58:26 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 20:58:29 -0000 TB --- 2004-11-30 19:36:25 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-30 19:36:25 - starting CURRENT tinderbox run for i386/i386 TB --- 2004-11-30 19:36:25 - checking out the source tree TB --- 2004-11-30 19:36:25 - cd /home/tinderbox/CURRENT/i386/i386 TB --- 2004-11-30 19:36:25 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-30 19:42:58 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-30 19:42:58 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-11-30 19:42:58 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-30 20:49:52 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-30 20:49:52 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-11-30 20:49:52 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Nov 30 20:49:52 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/i386/i386/src/sys -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/altq -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/pf -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /tinderbox/CURRENT/i386/i386/src/sys/i386/i386/sys_machdep.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/i386/i386/src/sys -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/altq -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/pf -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /tinderbox/CURRENT/i386/i386/src/sys/i386/i386/trap.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/i386/i386/src/sys -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/altq -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/pf -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /tinderbox/CURRENT/i386/i386/src/sys/i386/i386/tsc.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/i386/i386/src/sys -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/altq -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/pf -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /tinderbox/CURRENT/i386/i386/src/sys/i386/i386/uio_machdep.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/i386/i386/src/sys -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/altq -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/pf -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /tinderbox/CURRENT/i386/i386/src/sys/i386/i386/vm86.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/i386/i386/src/sys -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/altq -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/pf -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/i386/i386/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /tinderbox/CURRENT/i386/i386/src/sys/i386/i386/vm_machdep.c /tinderbox/CURRENT/i386/i386/src/sys/i386/i386/vm_machdep.c: In function `cpu_reset': /tinderbox/CURRENT/i386/i386/src/sys/i386/i386/vm_machdep.c:470: warning: unused variable `cnt' *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. TB --- 2004-11-30 20:58:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-30 20:58:26 - ERROR: failed to build generic kernel TB --- 2004-11-30 20:58:26 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 21:29:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC80316A4CE for ; Tue, 30 Nov 2004 21:29:45 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAC1443D49 for ; Tue, 30 Nov 2004 21:29:45 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 883 invoked from network); 30 Nov 2004 21:29:45 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 30 Nov 2004 21:29:45 -0000 Received: from [10.50.40.211] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAULTeTt090040; Tue, 30 Nov 2004 16:29:40 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Jeff Roberson Date: Tue, 30 Nov 2004 15:31:18 -0500 User-Agent: KMail/1.6.2 References: <20041120000743.G18094@mail.chesapeake.net> <200411231140.10041.jhb@FreeBSD.org> <20041130012736.A85758@mail.chesapeake.net> In-Reply-To: <20041130012736.A85758@mail.chesapeake.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411301531.18843.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-current@FreeBSD.org cc: current@FreeBSD.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 21:29:46 -0000 On Tuesday 30 November 2004 01:28 am, Jeff Roberson wrote: > On Tue, 23 Nov 2004, John Baldwin wrote: > > On Tuesday 23 November 2004 03:38 am, Peter Holm wrote: > > > On Sat, Nov 20, 2004 at 12:24:10AM -0500, Jeff Roberson wrote: > > > > I have a patch that I would like people to test and review. It's > > > > available here: > > > > > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > > > I have a panic at http://www.holm.cc/stress/log/jeff02.html > > > with GENERIC HEAD from Nov 22 14:40 UTC + your Giantless VFS patch. > > > > > > But the fault does not seem to related to your changes? > > > > Might be an incorrect parameter to mtx_init() that results in a bogus > > pointer eventually for the name of a lock? > > I forgot to call mtx_destroy() before I freed the name. This could have > done it eh? Yes. :) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 21:29:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECE4316A4CF for ; Tue, 30 Nov 2004 21:29:45 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAAA843D39 for ; Tue, 30 Nov 2004 21:29:45 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 883 invoked from network); 30 Nov 2004 21:29:45 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 30 Nov 2004 21:29:45 -0000 Received: from [10.50.40.211] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAULTeTt090040; Tue, 30 Nov 2004 16:29:40 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Jeff Roberson Date: Tue, 30 Nov 2004 15:31:18 -0500 User-Agent: KMail/1.6.2 References: <20041120000743.G18094@mail.chesapeake.net> <200411231140.10041.jhb@FreeBSD.org> <20041130012736.A85758@mail.chesapeake.net> In-Reply-To: <20041130012736.A85758@mail.chesapeake.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411301531.18843.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-current@FreeBSD.org cc: current@FreeBSD.org Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 21:29:46 -0000 On Tuesday 30 November 2004 01:28 am, Jeff Roberson wrote: > On Tue, 23 Nov 2004, John Baldwin wrote: > > On Tuesday 23 November 2004 03:38 am, Peter Holm wrote: > > > On Sat, Nov 20, 2004 at 12:24:10AM -0500, Jeff Roberson wrote: > > > > I have a patch that I would like people to test and review. It's > > > > available here: > > > > > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > > > I have a panic at http://www.holm.cc/stress/log/jeff02.html > > > with GENERIC HEAD from Nov 22 14:40 UTC + your Giantless VFS patch. > > > > > > But the fault does not seem to related to your changes? > > > > Might be an incorrect parameter to mtx_init() that results in a bogus > > pointer eventually for the name of a lock? > > I forgot to call mtx_destroy() before I freed the name. This could have > done it eh? Yes. :) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 21:30:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C30EC16A4D8; Tue, 30 Nov 2004 21:30:09 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7408343D60; Tue, 30 Nov 2004 21:30:07 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAULU6Z4001134; Tue, 30 Nov 2004 13:30:06 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAULU6nP001133; Tue, 30 Nov 2004 13:30:06 -0800 (PST) (envelope-from sgk) Date: Tue, 30 Nov 2004 13:30:06 -0800 From: Steve Kargl To: "Ketrien I. Saihr-Kenchedra" Message-ID: <20041130213006.GA1079@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041129233211.GA27426@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> <20041130194227.GA32604@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041130194227.GA32604@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: Scott Long cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 21:30:10 -0000 On Tue, Nov 30, 2004 at 11:42:27AM -0800, Steve Kargl wrote: > On Tue, Nov 30, 2004 at 02:35:30PM -0500, Ketrien I. Saihr-Kenchedra wrote: > > > More importantly, which BIOS version? You have to run the 2.03 BIOS on > > the K8SPro if you're running 16GB. Make sure that ccNUMA support is off > > in the BIOS as well - this was a never-ending source of fun on both the > > S2882 and S4882's. I can't tell you exactly why, but having ccNUMA on > > with the S4882 and S288x's is a never-ending font of panic()s. But the > > 2.01 and 2.02 BIOSes on the S2882 are exceptionally miserable. > > At least it's not an S4882 1.02: > > "DDR 400MHz Memmory Detected" > > The BIOS is at 2.03. I haven't tried turning off the ccNUMA support. > I'll give it a shot in a moment. > I disabled the only thing in the BIOS that mentions NUMA (under Advanced ACPI Configuration). FreeBSD now sees the 16 GB, but she still panics. A verbose boot shows real memory = 17179869184 (16384 MB) Physical memory chuck(s): 0x0000000000001000 - 0000000000009bfff, 634880 bytes (155 pages) 0x000000000082d000 - 000000000fbfeffff, 4219219968 bytes (1030083 pages) 0x0000000100000000 - 000000003e1fcffff, 12381388800 bytes (3022800 pages) panic: vm_page_insert: page already inserted cpuid = 0 KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x37 panic() at panic+0x1d1 vm_page_insert() at vm_page_insert+0x4e vm_page_alloc() at vm_page_alloc+0x315 vm_page_grab() at vm_page_grab+0x141 kmem_alloc() at kmem_alloc+0x10c vm_ksubmap_init() at vm_ksubmap_init+0x7d cpu_startup() at cpu_startup+0xbc mi_statup() at mi_startup+0xb6 btext() at btext+0x2c -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 23:38:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25FEF16A4CE for ; Tue, 30 Nov 2004 23:38:56 +0000 (GMT) Received: from blackwater.lemis.com (wantadilla.lemis.com [192.109.197.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F3D943D4C for ; Tue, 30 Nov 2004 23:38:54 +0000 (GMT) (envelope-from grog@lemis.com) Received: by blackwater.lemis.com (Postfix, from userid 1004) id 799A78566C; Wed, 1 Dec 2004 10:08:50 +1030 (CST) Date: Wed, 1 Dec 2004 10:08:50 +1030 From: Greg 'groggy' Lehey To: Julian Elischer Message-ID: <20041130233850.GD19922@wantadilla.lemis.com> References: <41ACD858.6090801@elischer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9dgjiU4MmWPVapMU" Content-Disposition: inline In-Reply-To: <41ACD858.6090801@elischer.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 cc: FreeBSD Current Subject: Re: remote gdb with firewire. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 23:38:56 -0000 --9dgjiU4MmWPVapMU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [Format recovered--see http://www.lemis.com/email/email-format.html] Long/short syndrome. On Tuesday, 30 November 2004 at 12:30:16 -0800, Julian Elischer wrote: > anyone have good crib sheets on doing this? just go my first > firewire setup and looking forward to trying it. gdb(4)? Greg -- When replying to this message, please take care not to mutilate the original text. =20 For more information, see http://www.lemis.com/email.html See complete headers for address and phone numbers. --9dgjiU4MmWPVapMU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBrQSKIubykFB6QiMRAqIvAJ9/onGAwnaQDeCBvnE1PLZhtoUXDACggKZ8 woPztM9FiVF4t4PDsUHwmXE= =dn3y -----END PGP SIGNATURE----- --9dgjiU4MmWPVapMU-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 23:48:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AFEE16A4CE for ; Tue, 30 Nov 2004 23:48:25 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EC8443D2D for ; Tue, 30 Nov 2004 23:48:21 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iAUNlnva047587; Wed, 1 Dec 2004 10:17:52 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Wed, 1 Dec 2004 10:17:47 +1030 User-Agent: KMail/1.7.1 References: <41ACD858.6090801@elischer.org> In-Reply-To: <41ACD858.6090801@elischer.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart6055147.jsrhBPQ2S4"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412011017.48261.doconnor@gsoft.com.au> X-Spam-Score: -5.4 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Julian Elischer Subject: Re: remote gdb with firewire. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 23:48:25 -0000 --nextPart6055147.jsrhBPQ2S4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 1 Dec 2004 07:00, Julian Elischer wrote: > anyone have good crib sheets on doing this? just go my first firewire > setup and looking > forward to trying it. gdb(4) has some good stuff (as well as what others mentioned) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart6055147.jsrhBPQ2S4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBrQak5ZPcIHs/zowRAjipAJ9p1La1AY/z1MU4n+XsNcGmGWzOFgCeLPKI 8PAwfpARJhdYz1M+InlgXKY= =FvaC -----END PGP SIGNATURE----- --nextPart6055147.jsrhBPQ2S4-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 30 23:57:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C42E16A4CE; Tue, 30 Nov 2004 23:57:54 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39DDB43D55; Tue, 30 Nov 2004 23:57:54 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by bahre.achedra.org (8.13.1/8.13.1) with ESMTP id iAUJZUl1087734; Tue, 30 Nov 2004 14:35:30 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Tue, 30 Nov 2004 14:35:30 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: Steve Kargl In-Reply-To: <20041130183555.GA32237@troutmask.apl.washington.edu> Message-ID: <20041130142652.A59122@bahre.achedra.org> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/609/Fri Nov 26 15:20:39 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-current@freebsd.org cc: Scott Long cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Nov 2004 23:57:54 -0000 On Tue, 30 Nov 2004, Steve Kargl wrote: > The system starts to boot and dmesg reports the 16 GB of memory, but > I rapidly get this panic. > So, it looks like ACPI on this Tyan motherboard is restricting > the memory to 8G. I presume you're using CM74SD2048RLP-2700/S DIMMs? (Corsair/Samsung 2GB ECC Reg'd.) More importantly, which BIOS version? You have to run the 2.03 BIOS on the K8SPro if you're running 16GB. Make sure that ccNUMA support is off in the BIOS as well - this was a never-ending source of fun on both the S2882 and S4882's. I can't tell you exactly why, but having ccNUMA on with the S4882 and S288x's is a never-ending font of panic()s. But the 2.01 and 2.02 BIOSes on the S2882 are exceptionally miserable. At least it's not an S4882 1.02: "DDR 400MHz Memmory Detected" -Ketrien I. Saihr-Kenchedra From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 02:23:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7836E16A4CE for ; Wed, 1 Dec 2004 02:23:32 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 212B843D39 for ; Wed, 1 Dec 2004 02:23:32 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id C6A22F20CE for ; Tue, 30 Nov 2004 18:23:31 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02655-08 for ; Tue, 30 Nov 2004 18:23:26 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id C9008F1849 for ; Tue, 30 Nov 2004 18:23:25 -0800 (PST) From: Sean McNeil To: current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-wL0iG6djIQ0DyISrxGKa" Date: Tue, 30 Nov 2004 18:23:25 -0800 Message-Id: <1101867805.8266.6.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com Subject: panic today when doing shutdown and boot warnings X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 02:23:32 -0000 --=-wL0iG6djIQ0DyISrxGKa Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I haven't noticed these before so I thought I would mention them: Nov 30 18:01:39 server kernel: Timecounters tick every 1.000 msec Nov 30 18:01:39 server kernel: WARNING: attempt to net_add_domain(local) af= ter domainfinalize() Nov 30 18:01:39 server kernel: WARNING: attempt to net_add_domain(internet6= ) after domainfinalize() Nov 30 18:01:39 server kernel: WARNING: attempt to net_add_domain(route) af= ter domainfinalize() Nov 30 18:01:39 server kernel: WARNING: attempt to net_add_domain(internet)= after domainfinalize() I have no idea what they mean. Plus, with an amd64 kernel compiled just a little while ago I get a drop into the debugger on shutdown: I typed "reboot"... Nov 30 17:56:55 server reboot: rebooted by root Nov 30 18:01:39 server syslogd: kernel boot file is /boot/kernel/kernel Nov 30 18:01:39 server kernel: interrupt total Nov 30 18:01:39 server kernel: irq1: atkbd0 826 Nov 30 18:01:39 server kernel: irq0: clk 3441687 Nov 30 18:01:39 server kernel: irq4: sio0 6 Nov 30 18:01:39 server kernel: irq8: rtc 220405 Nov 30 18:01:39 server kernel: irq14: ata0 162189 Nov 30 18:01:39 server kernel: irq15: ata1 172 Nov 30 18:01:39 server kernel: irq16: re0 42589 Nov 30 18:01:39 server kernel: irq17: fwohci0 1 Nov 30 18:01:39 server kernel: irq19: dc0 2 Nov 30 18:01:39 server kernel: irq20: atapci0 121462 Nov 30 18:01:39 server kernel: irq21: uhci0 uhci1+ 379 Nov 30 18:01:39 server kernel: Total 3989718 Nov 30 18:01:39 server kernel: KDB: stack backtrace: Nov 30 18:01:39 server kernel: hardclock() at hardclock+0x21b Nov 30 18:01:39 server kernel: intr_execute_handlers() at intr_execute_hand= lers+0x102 Nov 30 18:01:39 server kernel: lapic_handle_intr() at lapic_handle_intr+0x2= 1 Nov 30 18:01:39 server kernel: Xapic_isr1() at Xapic_isr1+0x7d Nov 30 18:01:39 server kernel: --- interrupt, rip =3D 0xffffffff8047ab16, r= sp =3D 0xffffffffb188dba0, rbp =3D 0xffffffffb188dbb0 --- Nov 30 18:01:39 server kernel: acpi_cpu_c1() at acpi_cpu_c1+0x6 Nov 30 18:01:39 server kernel: acpi_cpu_idle() at acpi_cpu_idle+0x178 Nov 30 18:01:39 server kernel: idle_proc() at idle_proc+0x9d Nov 30 18:01:39 server kernel: fork_exit() at fork_exit+0x8f Nov 30 18:01:39 server kernel: fork_trampoline() at fork_trampoline+0xe Nov 30 18:01:39 server kernel: --- trap 0, rip =3D 0, rsp =3D 0xffffffffb18= 8dd00, rbp =3D 0 --- I tried to just continue, but I end up back in the debugger again. --=-wL0iG6djIQ0DyISrxGKa Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBrSsdyQsGN30uGE4RAuplAKDgfiV4WZtxke/nZclp6X/Ddbk6OgCg05rZ 7iU+/d4b1rMakdRKmBMDeM0= =JoIG -----END PGP SIGNATURE----- --=-wL0iG6djIQ0DyISrxGKa-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 02:27:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 367C716A4CE for ; Wed, 1 Dec 2004 02:27:33 +0000 (GMT) Received: from av3-2-sn3.vrr.skanova.net (av3-2-sn3.vrr.skanova.net [81.228.9.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id B00C743D55 for ; Wed, 1 Dec 2004 02:27:32 +0000 (GMT) (envelope-from pawel.worach@telia.com) Received: by av3-2-sn3.vrr.skanova.net (Postfix, from userid 502) id E0C9F37E4B; Wed, 1 Dec 2004 03:27:31 +0100 (CET) Received: from smtp1-1-sn3.vrr.skanova.net (smtp1-1-sn3.vrr.skanova.net [81.228.9.177]) by av3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id D1EF137E43 for ; Wed, 1 Dec 2004 03:27:31 +0100 (CET) Received: from d1o402.telia.com (d1o402.telia.com [195.67.227.92]) by smtp1-1-sn3.vrr.skanova.net (Postfix) with ESMTP id C843638007 for ; Wed, 1 Dec 2004 03:27:31 +0100 (CET) Received: by d1o402.telia.com (8.11.1/8.10.1) id iB12RVE13279; Wed, 1 Dec 2004 03:27:31 +0100 (CET) Date: Wed, 1 Dec 2004 03:27:31 +0100 (CET) Message-Id: <200412010227.iB12RVE13279@d1o402.telia.com> X-Authentication-Warning: d1o402.telia.com: www set sender to pawel.worach@telia.com using -f From: "Pawel Worach" To: current@freebsd.org X-Mailer: SF Webmail X-SF-webmail-clientstamp: [80.217.169.233] 2004-12-01 03:27:31 Subject: page fault panic in device_get_softc/acpi_pcib_route_interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pawel Worach List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 02:27:33 -0000 Got this during boot on an IBM x345, three hour old kernel. Last working kernel is from 5 days ago, later than that hangs after probing the mpt controller (don't have the details on that now since this happened while I was about the debug the mpt issue). Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x488-0x48b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: on acpi0 pci0: on pcib0 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x48 fault code = supervisor read, page not present instruction pointer = 0x8:0xc051b827 stack pointer = 0x10:0xc08208f4 frame pointer = 0x10:0xc08209f8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) [thread pid 0 tid 0 ] Stopped at device_get_softc+0x7: movl 0x48(%eax),%eax db> tr Tracing pid 0 tid 0 td 0xc06e4080 device_get_softc(0,0,c0820a28,c0820a3c,2) at device_get_softc+0x7 acpi_pcib_route_interrupt(c1f17d00,c1f8b780,1,c1f7f1d4,1) at acpi_pcib_route_interrupt+0x33c acpi_pcib_acpi_route_interrupt(c1f17d00,c1f8b780,1,c06bc690,c1f8b808) at acpi_pcib_acpi_route_interrupt+0x2f pci_assign_interrupt_method(c1f17a00,c1f8b780,f,2,24) at pci_assign_interrupt_method+0x71 pci_add_child(c1f17a00,c1f8b800,f,2,80) at pci_add_child+0x207 pci_add_children(c1f17a00,0,80,c0820b54,c051dbff) at pci_add_children+0x123 acpi_pci_attach(c1f17a00,c1f4504c,c06b5cdc,c069ed37,0) at acpi_pci_attach+0x86 device_attach(c1f17a00,c1ed6d80,c0820bdc,c07b93fc,c1f17d00) at device_attach+0x2c9 bus_generic_attach(c1f17d00,c07ccea9,0,c0820bcc,0) at bus_generic_attach+0x18 acpi_pcib_attach(c1f17d00,c1f7f1d4,0,c0820c04,c07b4497) at acpi_pcib_attach+0xec acpi_pcib_acpi_attach(c1f17d00,c1f4484c,c06b5cdc,c069ed37,0) at acpi_pcib_acpi_attach+0xf9 device_attach(c1f17d00,2f,c0820cbc,c07b6924,c1ed6d80) at device_attach+0x2c9 bus_generic_attach(c1ed6d80,2e,2f,c1f7ec08,2e) at bus_generic_attach+0x18 acpi_attach(c1ed6d80,c1f4704c,c06b5cdc,c069ed37,0) at acpi_attach+0x7b4 device_attach(c1ed6d80,c1f16000,c0820d18,c066ee8a,c1f16000) at device_attach+0x2c9 bus_generic_attach(c1f16000,c1f1604c,c0820d54,c051cba9,c1f16000) at bus_generic_attach+0x18 nexus_attach(c1f16000,c1f3c84c,c06b5cdc,c069ed37,0) at nexus_attach+0x1a device_attach(c1f16000,c06d2170,c0820d78,c065c068,c1f16880) at device_attach+0x2c9 root_bus_configure(c1f16880,c06afbd2,0,c0820d98,c04cf1c6) at root_bus_configure+0x19 configure(0,0,c1e6f7a4,81ec00,81e000) at configure+0x28 mi_startup() at mi_startup+0xd6 begin() at begin+0x2c -- Pawel From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 04:12:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A171916A4CE for ; Wed, 1 Dec 2004 04:12:27 +0000 (GMT) Received: from mail.animecowboy.com (cdm-208-180-231-109.bcst.cox-internet.com [208.180.231.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id E37F743D5E for ; Wed, 1 Dec 2004 04:12:26 +0000 (GMT) (envelope-from animecowboy@animecowboy.com) Received: from localhost ([]) by mail.animecowboy.com (Merak 7.1.6) with ESMTP id ABA37675 for ; Tue, 30 Nov 2004 22:12:31 -0600 Received: from toran.animecowboy.com (toran.animecowboy.com [10.0.0.15]) by www.animecowboy.com (IMP) with HTTP for ; Tue, 30 Nov 2004 22:12:25 -0600 Message-ID: <1101874345.41ad44a92983e@www.animecowboy.com> Date: Tue, 30 Nov 2004 22:12:25 -0600 From: animecowboy@animecowboy.com To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 10.0.0.15 Subject: smbfs and setuid in 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 04:12:27 -0000 I am running 5.3r11 and I am having difficulty with mount_smbfs. Basically I have a permissions problem that I cannot track down. The remote filesystem mounts correctly, and as root I can view and write to it correctly. The permissions to the base directory were originally 700, and sued to the owner of the base I cannot stat the directory. I have tried changing the owner to another user, but had the same effect. After trying a few things I set the permissions to 750, and I could view and stat the directory. So I think it is some kind of UID bit not getting set correctly. The GID seems to set correctly, and for the moment is being used for a work around. I have mounted this filesystem on a FreeBSD 4.10(almost identical kernel) with no problem using the 700 permission settings. So I'm fairly certain its not the remote server, but just in case, the remote is a win2k pro machine. Thank you. -Brian Bailey From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 04:37:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64EFE16A4CE; Wed, 1 Dec 2004 04:37:40 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32EE843D2F; Wed, 1 Dec 2004 04:37:40 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 763A9512B1; Tue, 30 Nov 2004 20:42:55 -0800 (PST) Date: Tue, 30 Nov 2004 20:42:55 -0800 From: Kris Kennaway To: acpi@FreeBSD.org, current@FreeBSD.org Message-ID: <20041201044255.GA36090@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: panic: Lock ACPI PCI link not exclusively locked X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 04:37:40 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Rebuilt 6.0 kernel tonight, panics at boot: pci_link0: irq 6 on acpi0 panic: Lock ACPI PCI link not exclusively locked @ /a/portbuild/i386/src-client/sys/dev/acpica/acpi_pci_link.c:153 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter+0x32: leal 0(%esi),%esi db> db> tr Tracing pid 0 tid 0 td 0xc07b8260 kdb_enter(c07551c4,c07ba540,c07558db,c0c20a7c,c07b8260) at kdb_enter+0x32 panic(c07558db,c0740d53,c0740d88,99,c0c20b00) at panic+0x14d _sx_assert(c07b4a60,4,c0740d88,99,c1a2e9c0) at _sx_assert+0xfe link_add_crs(c1a2e9c0,c0c20b00,c0c20ac8,2c,c1a2e9c0) at link_add_crs+0x35 AcpiWalkResources(c1950900,c073db16,c047e620,c0c20b00,c195c980) at AcpiWalkResources+0x8d acpi_pci_link_attach(c1a28380,c19bd04c,c077a96c,c0756dc5,0) at acpi_pci_link_attach+0x251 device_attach(c1a28380,c0475100,c0c20b78,c0c20b80,0) at device_attach+0x2c9 prt_attach_devices(c1a08800,c195c400,c195c980,c195c400,c1a0f994) at prt_attach_devices+0xe6 prt_walk_table(c195c400,c0771297,0,c0c20bcc,0) at prt_walk_table+0x3c acpi_pcib_attach(c195c400,c1a0f994,0,c0c20c04,c0473fb7,c0764021,c1945970,c077a96c,c19494a0) at acpi_pcib_attach+0xe4 acpi_pcib_acpi_attach(c195c400,c19b104c,c077a96c,c0756dc5,0) at acpi_pcib_acpi_attach+0xf9 device_attach(c195c400,1fefffff,c0c20cbc,c0476474,c195c980) at device_attach+0x2c9 bus_generic_attach(c195c980,100000,1fefffff,c1a0f9e8,100000) at bus_generic_attach+0x18 acpi_attach(c195c980,c19ca04c,c077a96c,c0756dc5,0) at acpi_attach+0x7b4 device_attach(c195c980,c195ca00,c0c20d18,c070d6da,c195ca00) at device_attach+0x2c9 bus_generic_attach(c195ca00,c195ca4c,c0c20d54,c0574679,c195ca00) at bus_generic_attach+0x18 nexus_attach(c195ca00,c19e084c,c077a96c,c0756dc5,0) at nexus_attach+0x1a device_attach(c195ca00,c07a4190,c0c20d78,c06fff08,c19ac180) at device_attach+0x2c9 root_bus_configure(c19ac180,c077305f,0,c0c20d98,c052ed66) at root_bus_configure+0x19 configure(0,0,c0777508,c1ec00,c1e000) at configure+0x28 mi_startup() at mi_startup+0xd6 begin() at begin+0x2c Kris --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBrUvPWry0BWjoQKURAsRBAJoC2EVUJ17SLoJazULAQpmMn6Ye2QCg4UWW VurJ6zFmQSmrYk86HMdfxEM= =pxSp -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 04:42:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7BA216A4CE for ; Wed, 1 Dec 2004 04:42:53 +0000 (GMT) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63D4343D53 for ; Wed, 1 Dec 2004 04:42:53 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.12.11/8.12.11) with ESMTP id iB14gpmt043571; Tue, 30 Nov 2004 21:42:51 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.12.11/8.12.5/Submit) id iB14gpU2043570; Tue, 30 Nov 2004 21:42:51 -0700 (MST) (envelope-from ken) Date: Tue, 30 Nov 2004 21:42:51 -0700 From: "Kenneth D. Merry" To: Andrew Gallatin Message-ID: <20041201044251.GB43425@nargothrond.kdm.org> References: <20041130035552.GA32924@nargothrond.kdm.org> <16812.29117.221988.730885@grasshopper.cs.duke.edu> <20041201044141.GA43425@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201044141.GA43425@nargothrond.kdm.org> User-Agent: Mutt/1.4.2i X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on nargothrond.kdm.org X-Virus-Status: Clean cc: current@FreeBSD.org Subject: Re: -current hang during boot on SMP machine X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 04:42:53 -0000 [ resend from the address that is actually subscribed to -current ] On Tue, Nov 30, 2004 at 08:12:29 -0500, Andrew Gallatin wrote: > > Have you tried disabling ACPI via hint.acpi.0.disabled="1" in > /boot/loader.conf > > The ACPI on these older machines is pretty bad. I have a very similar > SuperMicro machine w/o SCSI at work which runs 5.3-R fine w/ACPI > disabled. I discovered early in the 5.0 cycle that enabling ACPI > would lead to a console message for each fxp0 interrupt.. That seems to get it working, thanks! It looks like all the devices are probed properly without ACPI. Will I be missing anything important with ACPI disabled? Ken -- Kenneth Merry ken@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 05:19:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D009F16A652 for ; Wed, 1 Dec 2004 05:19:10 +0000 (GMT) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45CE843D54 for ; Wed, 1 Dec 2004 05:19:10 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from ocean.jinmei.org (unknown [2001:200:0:8002:200:39ff:fed7:e2e4]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 3451C15210 for ; Wed, 1 Dec 2004 14:19:05 +0900 (JST) Date: Wed, 01 Dec 2004 14:19:15 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: current@FreeBSD.org User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Subject: malloc(0) returns an invalid address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 05:19:11 -0000 On FreeBSD 5.3 Release (for i386), malloc(3) seems to return an invalid pointer, while the man page says: V Attempting to allocate zero bytes will return a NULL pointer instead of a valid pointer. (The default behavior is to make a minimal allocation and return a pointer to it.) This option is provided for System V compatibility. This option is incompatible with the ``X'' option. In fact, if you compile the following code, #include #include main() { char *p = malloc(0); printf("address of p is %p\n", p); *p = 0; /* XXX */ } the result of the execution would be as follows: % ./a.out address of p is 0x800 zsh: 794 segmentation fault (core dumped) ./a.out Is this a malloc bug? Or is this the intended behavior and the man page description is old? (For that matter, I don't have /etc/malloc.conf or MALLOC_OPTIONS in the local environment.) JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 05:39:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C1DE16A4CE; Wed, 1 Dec 2004 05:39:28 +0000 (GMT) Received: from satie.private.org (qclgw.qcl.t.u-tokyo.ac.jp [133.11.70.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5420A43D31; Wed, 1 Dec 2004 05:39:27 +0000 (GMT) (envelope-from chat95@mac.com) Received: from localhost (localhost [IPv6:::1]) by satie.private.org (8.13.1/8.13.1) with ESMTP id iB15d9NP009461; Wed, 1 Dec 2004 14:39:10 +0900 (JST) (envelope-from chat95@mac.com) Date: Wed, 01 Dec 2004 14:39:09 +0900 (JST) Message-Id: <20041201.143909.971160851.chat95@mac.com> To: rodrigc@crodrigues.org From: NAKATA Maho In-Reply-To: <20040923032045.GA52428@crodrigues.org> References: <20040923032045.GA52428@crodrigues.org> Organization: private X-Mailer: Mew version 3.3 on XEmacs 21.4.14 (Reasonable Discussion) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: sos@freebsd.org Subject: Re: REPORT_KEY ILLEGAL REQUEST: encrypted DVD's under FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 05:39:28 -0000 In Message-ID: <20040923032045.GA52428@crodrigues.org> Craig Rodrigues wrote: Hello, > I tried installing mplayer, xine, and ogle from ports to play > DVD's on my FreeBSD-CURRENT box. All these packages use libdvdcss. > > For some reason, when playing certain encrypted DVD's, things > fail. I am seeing a lot of messages like this in my dmesg: > > acd0: FAILURE - REPORT_KEY ILLEGAL REQUEST asc=0x6f ascq=0x04 error=4 > > This is my brand of DVD player: > acd0: CDRW drive at ata0 as slave I also encountered the exact problem. acd0: DVDR at ata1-master UDMA33 -- NAKATA, Maho From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 05:40:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF2D916A4CE for ; Wed, 1 Dec 2004 05:40:20 +0000 (GMT) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 825DA43D54 for ; Wed, 1 Dec 2004 05:40:20 +0000 (GMT) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v7.1.0.R) with ESMTP id md50000304820.msg for ; Tue, 30 Nov 2004 21:16:33 -0800 From: "David Schwartz" To: Date: Tue, 30 Nov 2004 21:40:25 -0800 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.6604 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Tue, 30 Nov 2004 21:16:33 -0800 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDaemon-Deliver-To: current@FreeBSD.org X-MDAV-Processed: mail1.webmaster.com, Tue, 30 Nov 2004 21:16:36 -0800 Subject: RE: malloc(0) returns an invalid address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: davids@webmaster.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 05:40:20 -0000 > In fact, if you compile the following code, > > #include > #include > > main() > { > char *p = malloc(0); > > printf("address of p is %p\n", p); > *p = 0; /* XXX */ > } > > the result of the execution would be as follows: > > % ./a.out > address of p is 0x800 > zsh: 794 segmentation fault (core dumped) ./a.out > > Is this a malloc bug? Or is this the intended behavior and the man > page description is old? This is the intended behavior but the man page description is correct. The problem is not that the pointer is invalid but that you assumed that it was large enough to hold a 'char' and it is not. DS From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 05:40:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F277C16A4CE; Wed, 1 Dec 2004 05:40:53 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id B543643D55; Wed, 1 Dec 2004 05:40:53 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.51] (adsl-64-171-186-185.dsl.snfc21.pacbell.net [64.171.186.185]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iB15eqC4028325 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Nov 2004 21:40:52 -0800 Message-ID: <41AD5962.4020501@root.org> Date: Tue, 30 Nov 2004 21:40:50 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20041201044255.GA36090@xor.obsecurity.org> In-Reply-To: <20041201044255.GA36090@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@FreeBSD.org cc: current@FreeBSD.org Subject: Re: panic: Lock ACPI PCI link not exclusively locked X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 05:40:54 -0000 Kris Kennaway wrote: > Rebuilt 6.0 kernel tonight, panics at boot: > > pci_link0: irq 6 on acpi0 > panic: Lock ACPI PCI link not exclusively locked @ /a/portbuild/i386/src-client/sys/dev/acpica/acpi_pci_link.c:153 > > KDB: enter: panic > [thread pid 0 tid 0 ] > Stopped at kdb_enter+0x32: leal 0(%esi),%esi > db> > db> tr > Tracing pid 0 tid 0 td 0xc07b8260 > kdb_enter(c07551c4,c07ba540,c07558db,c0c20a7c,c07b8260) at kdb_enter+0x32 > panic(c07558db,c0740d53,c0740d88,99,c0c20b00) at panic+0x14d > _sx_assert(c07b4a60,4,c0740d88,99,c1a2e9c0) at _sx_assert+0xfe > link_add_crs(c1a2e9c0,c0c20b00,c0c20ac8,2c,c1a2e9c0) at link_add_crs+0x35 > AcpiWalkResources(c1950900,c073db16,c047e620,c0c20b00,c195c980) at AcpiWalkResources+0x8d > acpi_pci_link_attach(c1a28380,c19bd04c,c077a96c,c0756dc5,0) at acpi_pci_link_attach+0x251 > device_attach(c1a28380,c0475100,c0c20b78,c0c20b80,0) at device_attach+0x2c9 > prt_attach_devices(c1a08800,c195c400,c195c980,c195c400,c1a0f994) at prt_attach_devices+0xe6 > prt_walk_table(c195c400,c0771297,0,c0c20bcc,0) at prt_walk_table+0x3c > acpi_pcib_attach(c195c400,c1a0f994,0,c0c20c04,c0473fb7,c0764021,c1945970,c077a96c,c19494a0) at acpi_pcib_attach+0xe4 > acpi_pcib_acpi_attach(c195c400,c19b104c,c077a96c,c0756dc5,0) at acpi_pcib_acpi_attach+0xf9 > device_attach(c195c400,1fefffff,c0c20cbc,c0476474,c195c980) at device_attach+0x2c9 > bus_generic_attach(c195c980,100000,1fefffff,c1a0f9e8,100000) at bus_generic_attach+0x18 > acpi_attach(c195c980,c19ca04c,c077a96c,c0756dc5,0) at acpi_attach+0x7b4 > device_attach(c195c980,c195ca00,c0c20d18,c070d6da,c195ca00) at device_attach+0x2c9 > bus_generic_attach(c195ca00,c195ca4c,c0c20d54,c0574679,c195ca00) at bus_generic_attach+0x18 > nexus_attach(c195ca00,c19e084c,c077a96c,c0756dc5,0) at nexus_attach+0x1a > device_attach(c195ca00,c07a4190,c0c20d78,c06fff08,c19ac180) at device_attach+0x2c9 > root_bus_configure(c19ac180,c077305f,0,c0c20d98,c052ed66) at root_bus_configure+0x19 > configure(0,0,c0777508,c1ec00,c1e000) at configure+0x28 > mi_startup() at mi_startup+0xd6 > begin() at begin+0x2c > > Kris This has been partially addressed by David backing out my commit although I will now complete the backout for the !SMP case too. -- Nate From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 06:30:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DA2E16A4CE; Wed, 1 Dec 2004 06:30:56 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2527443D49; Wed, 1 Dec 2004 06:30:53 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iB16UQ9a054689; Wed, 1 Dec 2004 17:00:26 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Wed, 1 Dec 2004 17:00:24 +1030 User-Agent: KMail/1.7.1 References: <20040923032045.GA52428@crodrigues.org> <20041201.143909.971160851.chat95@mac.com> In-Reply-To: <20041201.143909.971160851.chat95@mac.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1294269.gTrA74a7Mq"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412011700.25525.doconnor@gsoft.com.au> X-Spam-Score: -5.7 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: rodrigc@crodrigues.org cc: NAKATA Maho cc: sos@freebsd.org Subject: Re: REPORT_KEY ILLEGAL REQUEST: encrypted DVD's under FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 06:30:56 -0000 --nextPart1294269.gTrA74a7Mq Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 1 Dec 2004 16:09, NAKATA Maho wrote: > > This is my brand of DVD player: > > acd0: CDRW drive at ata0 as slave > > I also encountered the exact problem. > acd0: DVDR at ata1-master UDMA33 Does it actually _play_ after this or not? It could be searching for a key (maybe) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1294269.gTrA74a7Mq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBrWUB5ZPcIHs/zowRAiYxAKCJSeT48VM+HQnwZHTKTk6adRVhAACfRXW/ 0/NqRN8l7/8EjjRi27++4Ns= =eofu -----END PGP SIGNATURE----- --nextPart1294269.gTrA74a7Mq-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 06:32:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D36116A4CE; Wed, 1 Dec 2004 06:32:06 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8898243D2D; Wed, 1 Dec 2004 06:32:05 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (sccrmhc12) with ESMTP id <2004120106320401200i98qee>; Wed, 1 Dec 2004 06:32:04 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) iB16W5w7006780; Wed, 1 Dec 2004 01:32:05 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)iB16W4Pr006779; Wed, 1 Dec 2004 01:32:04 -0500 (EST) (envelope-from rodrigc) Date: Wed, 1 Dec 2004 01:32:04 -0500 From: Craig Rodrigues To: NAKATA Maho Message-ID: <20041201063204.GA6754@crodrigues.org> References: <20040923032045.GA52428@crodrigues.org> <20041201.143909.971160851.chat95@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201.143909.971160851.chat95@mac.com> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: sos@freebsd.org Subject: Re: REPORT_KEY ILLEGAL REQUEST: encrypted DVD's under FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 06:32:06 -0000 On Wed, Dec 01, 2004 at 02:39:09PM +0900, NAKATA Maho wrote: > In Message-ID: <20040923032045.GA52428@crodrigues.org> > > acd0: FAILURE - REPORT_KEY ILLEGAL REQUEST asc=0x6f ascq=0x04 error=4 > > > > This is my brand of DVD player: > > acd0: CDRW drive at ata0 as slave > > I also encountered the exact problem. > acd0: DVDR at ata1-master UDMA33 Hi, Garrett Wollman explained this quite nicely to me. In the MMC-3 standard (SCSI) at T10.org, there is a standard section on sense codes: 6F/04 R MEDIA REGION CODE IS MISMATCHED TO LOGICAL UNIT REGION When you get a new DVD player, the DVD-ROM will adopt the region code of the first DVD that it plays. If you want to change the region code on your DVD drive, you typically need to download proprietary utilities or firmware for your DVD drive. Most DVD drives only allow you to change the region code 5 times. I haven't figured out how to change the firmware on my LITE-ON drive, because LITE-ON only supplies Windows utilities, and my machine is FreeBSD only. -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 06:35:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCBAB16A4CE for ; Wed, 1 Dec 2004 06:35:30 +0000 (GMT) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61B1243D5A for ; Wed, 1 Dec 2004 06:35:30 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from ocean.jinmei.org (unknown [2001:200:0:8002:200:39ff:fed7:e2e4]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 3F5FA15210; Wed, 1 Dec 2004 15:35:29 +0900 (JST) Date: Wed, 01 Dec 2004 15:35:39 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: davids@webmaster.com In-Reply-To: References: User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: current@FreeBSD.org Subject: Re: malloc(0) returns an invalid address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 06:35:31 -0000 >>>>> On Tue, 30 Nov 2004 21:40:25 -0800, >>>>> "David Schwartz" said: >> % ./a.out >> address of p is 0x800 >> zsh: 794 segmentation fault (core dumped) ./a.out >> >> Is this a malloc bug? Or is this the intended behavior and the man >> page description is old? > This is the intended behavior but the man page description is correct. The > problem is not that the pointer is invalid but that you assumed that it was > large enough to hold a 'char' and it is not. I know the line of XXX is not correct; I simply tried to highlight the problem, but I seem to convey the real point. How about this example? main() { char *p = malloc(0), *q; printf("address of p is %p\n", p); printf("the value of p is %c\n", *p); } the execution of this code would be like this: % ./a.out address of p is 0x800 zsh: 645 segmentation fault (core dumped) ./a.out And, more specifically, my real-world problem is that 'ndp -r' fails when it calls sysctl without any IPv6 default routers. The related code of ndp is as follows: int mib[] = { CTL_NET, PF_INET6, IPPROTO_ICMPV6, ICMPV6CTL_ND6_DRLIST }; (...) if (sysctl(mib, sizeof(mib) / sizeof(mib[0]), NULL, &l, NULL, 0) < 0) { err(1, "sysctl(ICMPV6CTL_ND6_DRLIST)"); /*NOTREACHED*/ } buf = malloc(l); if (!buf) { err(1, "malloc"); /*NOTREACHED*/ } if (sysctl(mib, sizeof(mib) / sizeof(mib[0]), buf, &l, NULL, 0) < 0) { err(1, "sysctl(ICMPV6CTL_ND6_DRLIST)"); /*NOTREACHED*/ } The first call to sysctl sets 'l' to 0, since the list is empty. Then the malloc returns '0x800' as a *valid pointer*. But in the second call to sysctl, kernel rejects this pointer at line 1299 of sys/kern/kern_sysctl.c: userland_sysctl(struct thread *td, int *name, u_int namelen, void *old, size_t *oldlenp, int inkernel, void *new, size_t newlen, size_t *retval) { (...) if (old) { --> if (!useracc(old, req.oldlen, VM_PROT_WRITE)) --> return (EFAULT); and so we'll see % ndp -r ndp: sysctl(ICMPV6CTL_ND6_DRLIST): Bad address Note that the same code worked with, e.g., FreeBSD 4.10. So, if we wanted to call 0x800 "a valid pointer just with not-enough-size", it would be fine. But then we need to implement the same logic in the kernel to provide consistent behavior. (I would "fix" the malloc behavior though). JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 07:07:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D5B516A4CE for ; Wed, 1 Dec 2004 07:07:01 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50A2B43D49 for ; Wed, 1 Dec 2004 07:07:01 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iB176x33068380; Wed, 1 Dec 2004 01:06:59 -0600 (CST) (envelope-from dan) Date: Wed, 1 Dec 2004 01:06:59 -0600 From: Dan Nelson To: "JINMEI Tatuya / ?$B?@L@C#:H" Message-ID: <20041201070659.GU5518@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: malloc(0) returns an invalid address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 07:07:01 -0000 In the last episode (Dec 01), JINMEI Tatuya / ?$B?@L@C#:H said: > The first call to sysctl sets 'l' to 0, since the list is empty. Then > the malloc returns '0x800' as a *valid pointer*. But in the second > call to sysctl, kernel rejects this pointer at line 1299 of > sys/kern/kern_sysctl.c: > > userland_sysctl(struct thread *td, int *name, u_int namelen, void *old, > size_t *oldlenp, int inkernel, void *new, size_t newlen, size_t *retval) > { > > (...) > > if (old) { > --> if (!useracc(old, req.oldlen, VM_PROT_WRITE)) > --> return (EFAULT); > > and so we'll see The bug is in useracc, I think. It should probably return true immediately if len is zero, since it's okay to read or write zero bytes from any pointer. A workaround would be to just skip the sysctl if there is nothing to read. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 07:50:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87F2516A4CE for ; Wed, 1 Dec 2004 07:50:07 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2B6D43D1D for ; Wed, 1 Dec 2004 07:50:06 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB17o5XB066198 for ; Wed, 1 Dec 2004 08:50:05 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org From: Poul-Henning Kamp Date: Wed, 01 Dec 2004 08:50:05 +0100 Message-ID: <66197.1101887405@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: [TESTERS] msdosfs patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 07:50:07 -0000 Can some of the people who use msdosfs please test this patch for me ? Poul-Henning Index: fs/msdosfs/denode.h =================================================================== RCS file: /home/ncvs/src/sys/fs/msdosfs/denode.h,v retrieving revision 1.28 diff -u -r1.28 denode.h --- fs/msdosfs/denode.h 8 Sep 2004 13:03:19 -0000 1.28 +++ fs/msdosfs/denode.h 1 Dec 2004 07:48:25 -0000 @@ -138,7 +138,6 @@ struct denode *de_next; /* Hash chain forward */ struct denode **de_prev; /* Hash chain back */ struct vnode *de_vnode; /* addr of vnode we are part of */ - struct vnode *de_devvp; /* vnode of blk dev we live on */ u_long de_flag; /* flag bits */ struct cdev *de_dev; /* device where direntry lives */ u_long de_dirclust; /* cluster of the directory file containing this entry */ Index: fs/msdosfs/msdosfs_denode.c =================================================================== RCS file: /home/ncvs/src/sys/fs/msdosfs/msdosfs_denode.c,v retrieving revision 1.75 diff -u -r1.75 msdosfs_denode.c --- fs/msdosfs/msdosfs_denode.c 29 Oct 2004 10:40:14 -0000 1.75 +++ fs/msdosfs/msdosfs_denode.c 1 Dec 2004 07:48:25 -0000 @@ -258,7 +258,6 @@ nvp->v_data = ldep; ldep->de_vnode = nvp; ldep->de_flag = 0; - ldep->de_devvp = 0; ldep->de_dev = dev; ldep->de_dirclust = dirclust; ldep->de_diroffset = diroffset; @@ -372,8 +371,6 @@ } else nvp->v_type = VREG; ldep->de_modrev = init_va_filerev(); - ldep->de_devvp = pmp->pm_devvp; - VREF(ldep->de_devvp); *depp = ldep; return (0); } @@ -646,10 +643,6 @@ /* * Purge old data structures associated with the denode. */ - if (dep->de_devvp) { - vrele(dep->de_devvp); - dep->de_devvp = 0; - } #if 0 /* XXX */ dep->de_flag = 0; #endif Index: fs/msdosfs/msdosfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/fs/msdosfs/msdosfs_vnops.c,v retrieving revision 1.152 diff -u -r1.152 msdosfs_vnops.c --- fs/msdosfs/msdosfs_vnops.c 15 Nov 2004 09:18:26 -0000 1.152 +++ fs/msdosfs/msdosfs_vnops.c 1 Dec 2004 07:48:25 -0000 @@ -182,7 +182,6 @@ ndirent.de_StartCluster = 0; ndirent.de_FileSize = 0; ndirent.de_dev = pdep->de_dev; - ndirent.de_devvp = pdep->de_devvp; ndirent.de_pmp = pdep->de_pmp; ndirent.de_flag = DE_ACCESS | DE_CREATE | DE_UPDATE; getnanotime(&ts); @@ -1356,7 +1355,6 @@ ndirent.de_StartCluster = newcluster; ndirent.de_FileSize = 0; ndirent.de_dev = pdep->de_dev; - ndirent.de_devvp = pdep->de_devvp; error = createde(&ndirent, pdep, &dep, cnp); if (error) goto bad; @@ -1747,7 +1745,7 @@ int error; if (ap->a_bop != NULL) - *ap->a_bop = &dep->de_devvp->v_bufobj; + *ap->a_bop = &dep->de_pmp->pm_devvp->v_bufobj; if (ap->a_bnp == NULL) return (0); if (ap->a_runp) { -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 08:14:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0064516A4D1 for ; Wed, 1 Dec 2004 08:14:24 +0000 (GMT) Received: from n33.kp.t-systems-sfr.com (n33.kp.t-systems-sfr.com [129.247.16.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3406B43D1F for ; Wed, 1 Dec 2004 08:14:24 +0000 (GMT) (envelope-from harti@freebsd.org) Received: from n81.sp.op.dlr.de (n81g.sp.op.dlr.de [129.247.163.1]) iB18EGU147892; Wed, 1 Dec 2004 09:14:17 +0100 Received: from zeus.nt.op.dlr.de (zeus.nt.op.dlr.de [129.247.173.3]) iB18EGI357596; Wed, 1 Dec 2004 09:14:16 +0100 Received: from beagle.kn.op.dlr.de (opkndnwsbsd178 [129.247.173.178]) by zeus.nt.op.dlr.de (8.11.7+Sun/8.9.1) with ESMTP id iB18FAu29030; Wed, 1 Dec 2004 09:15:10 +0100 (MET) Date: Wed, 1 Dec 2004 09:14:20 +0100 (CET) From: Harti Brandt X-X-Sender: brandt@beagle.kn.op.dlr.de To: animecowboy@animecowboy.com In-Reply-To: <1101874345.41ad44a92983e@www.animecowboy.com> Message-ID: <20041201091330.F655@beagle.kn.op.dlr.de> References: <1101874345.41ad44a92983e@www.animecowboy.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: current@freebsd.org Subject: Re: smbfs and setuid in 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 08:14:25 -0000 On Tue, 30 Nov 2004 animecowboy@animecowboy.com wrote: > I am running 5.3r11 and I am having difficulty with mount_smbfs. Basically I > have a permissions problem that I cannot track down. The remote filesystem > mounts correctly, and as root I can view and write to it correctly. The > permissions to the base directory were originally 700, and sued to the owner of > the base I cannot stat the directory. > > I have tried changing the owner to another user, but had the same effect. After > trying a few things I set the permissions to 750, and I could view and stat the > directory. So I think it is some kind of UID bit not getting set correctly. > The GID seems to set correctly, and for the moment is being used for a work > around. > > I have mounted this filesystem on a FreeBSD 4.10(almost identical kernel) with > no problem using the 700 permission settings. So I'm fairly certain its not the > remote server, but just in case, the remote is a win2k pro machine. Try to use the -u and -g switches to mount_smbfs to specify the user that should access the mounted file system. harti From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 08:45:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2048016A4CE; Wed, 1 Dec 2004 08:45:44 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAF0043D2F; Wed, 1 Dec 2004 08:45:41 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB18jci8036414; Wed, 1 Dec 2004 00:45:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB18jc8j036413; Wed, 1 Dec 2004 00:45:38 -0800 (PST) (envelope-from obrien) Date: Wed, 1 Dec 2004 00:45:37 -0800 From: "David O'Brien" To: "Ketrien I. Saihr-Kenchedra" Message-ID: <20041201084537.GA1621@dragon.nuxi.com> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041130142652.A59122@bahre.achedra.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org cc: Steve Kargl Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 08:45:44 -0000 On Tue, Nov 30, 2004 at 02:35:30PM -0500, Ketrien I. Saihr-Kenchedra wrote: > On Tue, 30 Nov 2004, Steve Kargl wrote: > > > >The system starts to boot and dmesg reports the 16 GB of memory, but > >I rapidly get this panic. > > >So, it looks like ACPI on this Tyan motherboard is restricting > >the memory to 8G. > > I presume you're using CM74SD2048RLP-2700/S DIMMs? (Corsair/Samsung 2GB > ECC Reg'd.) > More importantly, which BIOS version? You have to run the 2.03 BIOS on > the K8SPro if you're running 16GB. Make sure that ccNUMA support is off > in the BIOS as well - this was a never-ending source of fun on both the > S2882 and S4882's. There is no 'ccNUMA' setting in the BIOS. A multi-processor Opteron is a NUMA architecture machine regardless of any BIOS settings. I.E. there is no way to disable that a MP Opteron is a NUMA machine. The setting of interest is should the BIOS round-robin interleave physical addresses across the NUMA nodes[*]. The reference AMI BIOS refers to this as "Node Interleaving". It should be "DISABLED". Or if the BIOS speaks of the SRAT table, it should be "ENABLED". While FreeBSD doesn't use the SRAT table (and cannot until ACPI 3.0 BIOS's); turning on the SRAT turns off node interleaving. There is a CPU errata for older CPU's that can cause problems if you have both memory interleaving turned on and ECC turned enabled in the BIOS. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 09:20:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02C1316A4CE for ; Wed, 1 Dec 2004 09:20:12 +0000 (GMT) Received: from e0-a11.b1.lan.prg.vol.cz (e0-a11.b1.lan.prg.vol.cz [195.122.204.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 361F543D55 for ; Wed, 1 Dec 2004 09:20:11 +0000 (GMT) (envelope-from pav@FreeBSD.org) Received: from pav.hide.vol.cz (localhost [127.0.0.1])iB19K2ZP051618; Wed, 1 Dec 2004 10:20:03 +0100 (CET) (envelope-from pav@FreeBSD.org) Received: (from pav@localhost) by pav.hide.vol.cz (8.13.1/8.13.1/Submit) id iB19K2pK051617; Wed, 1 Dec 2004 10:20:02 +0100 (CET) (envelope-from pav@FreeBSD.org) X-Authentication-Warning: pav.hide.vol.cz: pav set sender to pav@FreeBSD.org using -f From: Pav Lucistnik To: Craig Rodrigues In-Reply-To: <20041201063204.GA6754@crodrigues.org> References: <20040923032045.GA52428@crodrigues.org> <20041201.143909.971160851.chat95@mac.com> <20041201063204.GA6754@crodrigues.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-IrwYoqSfir/09MeWLMM6" Date: Wed, 01 Dec 2004 10:20:01 +0100 Message-Id: <1101892801.51033.6.camel@pav.hide.vol.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port cc: freebsd-current@FreeBSD.org Subject: Re: REPORT_KEY ILLEGAL REQUEST: encrypted DVD's under FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 09:20:12 -0000 --=-IrwYoqSfir/09MeWLMM6 Content-Type: text/plain; charset=ISO8859-2 Content-Transfer-Encoding: quoted-printable Craig Rodrigues p=ED=B9e v st 01. 12. 2004 v 01:32 -0500: > On Wed, Dec 01, 2004 at 02:39:09PM +0900, NAKATA Maho wrote: > > In Message-ID: <20040923032045.GA52428@crodrigues.org>=20 > > > acd0: FAILURE - REPORT_KEY ILLEGAL REQUEST asc=3D0x6f ascq=3D0x04 err= or=3D4 > > >=20 > > > This is my brand of DVD player: > > > acd0: CDRW drive at ata0 as slave > >=20 > > I also encountered the exact problem. > > acd0: DVDR at ata1-master UDMA33 >=20 > Hi, >=20 > Garrett Wollman explained this quite nicely to me. > In the MMC-3 standard (SCSI) at T10.org, there is a > standard section on sense codes: > =20 > 6F/04 R MEDIA REGION CODE IS MISMATCHED TO LOGICAL UNIT RE= GION >=20 > When you get a new DVD player, the DVD-ROM will adopt the region > code of the first DVD that it plays. If you want to change > the region code on your DVD drive, you typically need to download > proprietary utilities or firmware for your DVD drive. > Most DVD drives only allow you to change the region code 5 times. >=20 > I haven't figured out how to change the firmware on my LITE-ON > drive, because LITE-ON only supplies Windows utilities, and my > machine is FreeBSD only. I had good results with FreeDOS bootup from CD-ROM, then swapping CDs for a second one with DOS based Mediatek flashing utility and firmware image. I could whip up a page with downloads and instructions, but it's all easily googlabe. Look for bootdisk.iso, MTKFLASH.EXE and BIN firmwares (unofficial). --=20 Pav Lucistnik Video games don't affect kids, I mean if Pac Man affected us as kids, we'd = all run around in a darkened room munching pills and listening to repetitive mu= sic. -- Kristian Wilson, CEO at Nintendo Gaming Corporation Inc --=-IrwYoqSfir/09MeWLMM6 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Toto je =?iso-8859-2?Q?digit=E1ln=EC?= =?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBrYzBntdYP8FOsoIRAqluAJ4qPHoPhEhEq3iwSQrQeAXbOXF0oACgzY5G xpqMROrMEDs3MDHlauDUCM0= =JO2A -----END PGP SIGNATURE----- --=-IrwYoqSfir/09MeWLMM6-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 09:29:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A07D016A50B; Wed, 1 Dec 2004 09:29:36 +0000 (GMT) Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id F080443D48; Wed, 1 Dec 2004 09:29:35 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd03.aul.t-online.de by mailout06.sul.t-online.com with smtp id 1CZQnm-00042L-02; Wed, 01 Dec 2004 10:29:34 +0100 Received: from Andro-Beta.Leidinger.net (ZkKYawZDren0tgOB6sK0Uh1bZIL7RTjWZJvacQq32ryvcS9ghMDYgC@[217.229.215.172]) by fmrl03.sul.t-online.com with esmtp id 1CZQnY-0T2rIG0; Wed, 1 Dec 2004 10:29:20 +0100 Received: from Andro-Beta.Leidinger.net (localhost [127.0.0.1]) iB19T9Gl008972; Wed, 1 Dec 2004 10:29:09 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: (from www@localhost)iB19T9lw008971; Wed, 1 Dec 2004 10:29:09 +0100 (CET) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: Andro-Beta.Leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from 141.113.101.32 ([141.113.101.32]) by netchild.homeip.net (IMP) with HTTP for ; Wed, 1 Dec 2004 10:29:09 +0100 Message-ID: <1101893349.41ad8ee54c92f@netchild.homeip.net> Date: Wed, 1 Dec 2004 10:29:09 +0100 From: Alexander Leidinger To: Scott Long References: <41AB3B8A.4040206@magnesium.net> <41AB44F4.1000106@freebsd.org> <20041129162032.GA5785@orion.daedalusnetworks.priv> <20041129.101105.129339938.imp@bsdimp.com> <1101823969.41ac7fe1700d5@netchild.homeip.net> <41ACBFD9.3000507@freebsd.org> In-Reply-To: <41ACBFD9.3000507@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.6 / FreeBSD-4.10 X-Originating-IP: 141.113.101.32 X-ID: ZkKYawZDren0tgOB6sK0Uh1bZIL7RTjWZJvacQq32ryvcS9ghMDYgC@t-dialin.net X-TOI-MSGID: c47833df-09f4-4dec-9032-5d1cfc3cba4a cc: freebsd-current cc: Garance A Drosihn cc: "M. Warner Losh" Subject: Re: boot menu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 09:29:36 -0000 Zitat von Scott Long : > > But at this point I think I've made enough suggestions, so I'm > > waiting to see what others think we should do. > > > > So I gave 4 options in another email, but haven't seen any real response > to those yet. For a refresher: Here's your response: yes please! But I'm not sure about the default. I would use the enhenced menu, but it may be better to use the minimal menu per default (at least on the install disks). Bye, Alexander. -- http://www.Leidinger.net/ Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org/ netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 09:47:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EBD316A4CE; Wed, 1 Dec 2004 09:47:37 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81BC843D31; Wed, 1 Dec 2004 09:47:36 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id iB19lpqj090971; Wed, 1 Dec 2004 04:47:51 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Wed, 1 Dec 2004 04:47:51 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: "David O'Brien" In-Reply-To: <20041201084537.GA1621@dragon.nuxi.com> Message-ID: <20041201042900.A88450@bahre.achedra.org> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041201084537.GA1621@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/609/Fri Nov 26 15:20:39 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-current@freebsd.org cc: Steve Kargl cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 09:47:37 -0000 On Wed, 1 Dec 2004, David O'Brien wrote: > There is no 'ccNUMA' setting in the BIOS. A multi-processor Opteron is a > NUMA architecture machine regardless of any BIOS settings. I.E. there is > no way to disable that a MP Opteron is a NUMA machine. > The setting of interest is should the BIOS round-robin interleave > physical addresses across the NUMA nodes[*]. The reference AMI BIOS > refers to this as "Node Interleaving". It should be "DISABLED". Or if > the BIOS speaks of the SRAT table, it should be "ENABLED". While FreeBSD > doesn't use the SRAT table (and cannot until ACPI 3.0 BIOS's); turning on > the SRAT turns off node interleaving. David, trying very hard to be nice, the S2882's a 'Special Case.' Where special should be taken as 'short bus.' VERY short bus. On the S2882/S2885, and even the S4882, the BIOS specifically says, and I quote: 'ccNUMA Support.' No joke. The beauty is that ccNUMA is, you got it, SRAT Table Control, which _disables_ interleave completely. Beautiful, huh? The only way to enable interleave on the S2882/S2885 is to specifically turn 'ccNUMA' off; otherwise it's SRAT only, with no interleave. And no, it's not mentioned anywhere on the S2882s. Only on the S4882, which uses a Phoenix 6.0 reference. (Which Tyan, predictably, did not remove the reference lines _or_ fix the typos on.) The S2882s also use a Phoenix, I believe. So in order to enable Interleave, your only method is that switch. What got me peering curiously here is the placement of the hole; there appears to be a 512MB hole, starting at 4024MB. It certainly is similar to the behavior of 2882 I've looked at; hole is about 1/3rd through memory. On the 2.03 BIOS, still no way to control the PCI hole; that feature is reserved for the S4882 apparently, and even then only size. If the hole _is_ at 4024MB, that would put it past 4096MB and the 4GB limit; on the S2882 the bulk of the peripherals are on the PCI32 bus, not a PCI64 bus. Specifically, disk, fxp(4), bge(4), ACPI, and USB. Presuming I am reading the hole correctly, and bearing in mind that I do not have access to my copy of the PCI2.3 spec, ISTR that the entirety of the PCI memory hole must be within the first 4GB of system memory. (I'd appreciate it if someone could sanity check that.) Presuming that it does need to be within the first 4GB of system memory, I'm wondering if what's being seen here is not a BIOS bug. These boards have a real bad track record with regards to them, so it would not be at all surprising, at least to me. -ksaihr From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 10:38:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C668916A4CE; Wed, 1 Dec 2004 10:38:27 +0000 (GMT) Received: from mail.otel.net (gw3.OTEL.net [212.36.8.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1364443D3F; Wed, 1 Dec 2004 10:38:27 +0000 (GMT) (envelope-from tbyte@OTEL.net) Received: from dragon.otel.net ([212.36.8.135]) by mail.otel.net with esmtp (Exim 4.30; FreeBSD) id 1CZRsL-0007F3-Sp; Wed, 01 Dec 2004 12:38:21 +0200 Message-ID: <41AD9F30.5030004@OTEL.net> Date: Wed, 01 Dec 2004 12:38:40 +0200 From: Iasen Kostov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041117 X-Accept-Language: bg, en-us, en MIME-Version: 1.0 To: Ruslan Ermilov References: <41612915.70209@gmx.de> <20041004142028.O59122@pol.leissner.se> <20041005113936.GD1693@ip.net.ua> In-Reply-To: <20041005113936.GD1693@ip.net.ua> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit cc: max@love2party.net cc: freebsd-current@FreeBSD.org cc: Peter Olsson cc: Sebastian Schulze Struchtrup Subject: Re: High rate traffic silence an em interface. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 10:38:27 -0000 Ruslan Ermilov wrote: >On Mon, Oct 04, 2004 at 02:25:14PM +0200, Peter Olsson wrote: > > >>On Mon, 4 Oct 2004 12:42 +0200, Sebastian Schulze Struchtrup wrote: >> >> >> >>>>This might be my fault! Just committed a fix from Mike Makonnen, that >>>>might solve the problem you are seeing. It's just a missing "!" so it >>>>should be easy to apply to RELENG_5 as well. Please give it a try (and >>>>accept my apology for the headache caused). >>>> >>>> >>>Seems to work for me now, too. >>> >>> >>Just saw this thread now, we also have an em0 card that disappears from >>the network sometimes. Every time it comes back after almost exactly >>3 hours and 50 minutes. Is this the problem that is fixed, and is the >>fix included in RELENG_5 by now? >> >> >> >Yes (as src/sys/dev/em/if_em.c,v 1.44.2.1). > > >Cheers, > > 1.44.2.4 and still disapperaing em0 ... em0@pci2:1:0: class=0x020000 card=0x80f71043 chip=0x10198086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82547EI Gigabit Ethernet Controller (LOM)' class = network subclass = ethernet cvsuped && recompiled last night. FreeBSD XXX.OTEL.net 5.3-STABLE FreeBSD 5.3-STABLE #1: Wed Dec 1 03:45:00 EET 2004 root@LANGW4.OTEL.net:/usr/src/sys/i386/compile/LANGW4 i386 2 times today - down/up fixes it. From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 10:51:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DACE16A4FE for ; Wed, 1 Dec 2004 10:51:22 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id A09F243D45 for ; Wed, 1 Dec 2004 10:51:21 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iB1ApC0N034946; Wed, 1 Dec 2004 05:51:12 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iB1ApBDi034936; Wed, 1 Dec 2004 05:51:11 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Wed, 1 Dec 2004 05:51:11 -0500 (EST) From: Jeff Roberson To: Peter Holm In-Reply-To: <20041130075602.GA72926@peter.osted.lan> Message-ID: <20041201054925.N18185@mail.chesapeake.net> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr><20041123013054.GA38804@peter.osted.lan> <20041130075602.GA72926@peter.osted.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org cc: Ivan Voras Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 10:51:22 -0000 On Tue, 30 Nov 2004, Peter Holm wrote: > On Tue, Nov 30, 2004 at 01:39:01AM -0500, Jeff Roberson wrote: > > > > On Tue, 23 Nov 2004, Peter Holm wrote: > > > > > On Mon, Nov 22, 2004 at 06:46:50AM -0500, Jeff Roberson wrote: > > > > On Mon, 22 Nov 2004, Ivan Voras wrote: > > > > > > > > > Jeff Roberson wrote: > > > > > > > > > > > The short description: > > > > > > This patch removes Giant from the read(), write(), and fstat() syscalls, > > > > > > as well as page faults, and bufdone (io interrupts) when using FFS. It > > > > > > > > > > What is the plan re: RELENG_5? Will things like this (giantless vm, fs) > > > > > be merged into it? > > > > > > > > The giantless vm was already merged back to RELENG_5 and enabled on amd64, > > > > and i386. I hope to merge the giantless vfs back after a month or so of > > > > no problems on -current. I hope to commit it to -current this week. > > > > > > > > I haven't received any feedback from the list though. I hope people are > > > > testing it. Perhaps the silence indicates universal success? :-) > > > > > > > > > > Here's a problem I ran into during stress test: > > > > > > http://www.holm.cc/stress/log/jeff01.html > > > > > > Let me know if you need more gdb output. > > > > Thanks, this is the most serious bug of the couple that were reported. It > > indicates a possible race to flush a buffer. I'm still looking for this. > > What steps did you take to produce this panic? > > > > I ran my kernel stress test: http://www.holm.cc/stress/src/stress.tgz > I stopped using your patch after the two reported problems. > Let me know if you would like me to perform more testing with your patch. Thanks, I think I may have fixed the problems that were exposed via your stress tool. I'll post an updated patch to the list in a moment. I was wondering if you have seen a panic in pmap_invalidate_range via sigexit()? It seems to have been caused by illegal calls to sigexit() from trapsignal(). If you have not reported it yet, I have a copy of a stack here and I can let the responsible people know. Cheers, Jeff > > - Peter > > > > > > > - Peter > > > > > > > > _______________________________________________ > > > > > freebsd-current@freebsd.org mailing list > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > > _______________________________________________ > > > > freebsd-current@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > -- > Peter Holm > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 10:54:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C906B16A4CE for ; Wed, 1 Dec 2004 10:54:50 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B09943D48 for ; Wed, 1 Dec 2004 10:54:50 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iB1Asn0N036220 for ; Wed, 1 Dec 2004 05:54:49 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iB1Asn76036217 for ; Wed, 1 Dec 2004 05:54:49 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Wed, 1 Dec 2004 05:54:49 -0500 (EST) From: Jeff Roberson To: current@freebsd.org Message-ID: <20041201055115.I18185@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 10:54:50 -0000 I have updated the patch at: http://www.chesapeake.net/~jroberson/smpffs.diff It includes bug fixes for a handful of problems that were reported, and a few more that I found myself. It also unwinds giant from open(), which is a very high risk area, but after a few days of working out bugs it seems to be functioning quite well for me. I did a make -j3 buildworld on a box with a lowered maxvnodes. I also let 'stress' run for 8 loops or so until I ran into an unrelated KSE bug. I did some mount/unmount/single user tests as well. Use at your own risk. I still haven't locked quotas, so if you're using quota, don't run with this patch. Thanks, Jeff From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 11:09:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62D6616A4CE for ; Wed, 1 Dec 2004 11:09:07 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id B9A7B43D58 for ; Wed, 1 Dec 2004 11:09:06 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 45280 invoked from network); 1 Dec 2004 11:09:05 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 1 Dec 2004 11:09:05 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB1B94q3078048; Wed, 1 Dec 2004 12:09:04 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB1B94cM078047; Wed, 1 Dec 2004 12:09:04 +0100 (CET) (envelope-from pho) Date: Wed, 1 Dec 2004 12:09:04 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041201110904.GA78023@peter.osted.lan> References: <20041120000743.G18094@mail.chesapeake.net> <41A1C3BD.4010903@fer.hr> <20041122064318.Y18094@mail.chesapeake.net> <20041123013054.GA38804@peter.osted.lan> <20041130013802.J85758@mail.chesapeake.net> <20041130075602.GA72926@peter.osted.lan> <20041201054925.N18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201054925.N18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org cc: Ivan Voras Subject: Re: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 11:09:07 -0000 On Wed, Dec 01, 2004 at 05:51:11AM -0500, Jeff Roberson wrote: > On Tue, 30 Nov 2004, Peter Holm wrote: > > > On Tue, Nov 30, 2004 at 01:39:01AM -0500, Jeff Roberson wrote: > > > > > > On Tue, 23 Nov 2004, Peter Holm wrote: > > > > > > > On Mon, Nov 22, 2004 at 06:46:50AM -0500, Jeff Roberson wrote: > > > > > On Mon, 22 Nov 2004, Ivan Voras wrote: > > > > > > > > > > > Jeff Roberson wrote: > > > > > > > > > > > > > The short description: > > > > > > > This patch removes Giant from the read(), write(), and fstat() syscalls, > > > > > > > as well as page faults, and bufdone (io interrupts) when using FFS. It > > > > > > > > > > > > What is the plan re: RELENG_5? Will things like this (giantless vm, fs) > > > > > > be merged into it? > > > > > > > > > > The giantless vm was already merged back to RELENG_5 and enabled on amd64, > > > > > and i386. I hope to merge the giantless vfs back after a month or so of > > > > > no problems on -current. I hope to commit it to -current this week. > > > > > > > > > > I haven't received any feedback from the list though. I hope people are > > > > > testing it. Perhaps the silence indicates universal success? :-) > > > > > > > > > > > > > Here's a problem I ran into during stress test: > > > > > > > > http://www.holm.cc/stress/log/jeff01.html > > > > > > > > Let me know if you need more gdb output. > > > > > > Thanks, this is the most serious bug of the couple that were reported. It > > > indicates a possible race to flush a buffer. I'm still looking for this. > > > What steps did you take to produce this panic? > > > > > > > I ran my kernel stress test: http://www.holm.cc/stress/src/stress.tgz > > I stopped using your patch after the two reported problems. > > Let me know if you would like me to perform more testing with your patch. > > Thanks, I think I may have fixed the problems that were exposed via your > stress tool. I'll post an updated patch to the list in a moment. I'll test it ASAP. > I was > wondering if you have seen a panic in pmap_invalidate_range via sigexit()? > It seems to have been caused by illegal calls to sigexit() from > trapsignal(). If you have not reported it yet, I have a copy of a stack > here and I can let the responsible people know. > This is a problem I have not encountered, so please do. Regards, - Peter From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 11:25:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56FF516A545 for ; Wed, 1 Dec 2004 11:25:06 +0000 (GMT) Received: from moya.lambermont.dyndns.org (j226018.upc-j.chello.nl [24.132.226.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id C591A43D58 for ; Wed, 1 Dec 2004 11:25:05 +0000 (GMT) (envelope-from hans@lambermont.dyndns.org) Received: from localhost (localhost [127.0.0.1]) by moya.lambermont.dyndns.org (Postfix) with ESMTP id 6983936402 for ; Wed, 1 Dec 2004 12:25:04 +0100 (CET) Received: from moya.lambermont.dyndns.org ([127.0.0.1])port 10024) with ESMTP id 23040-03 for ; Wed, 1 Dec 2004 12:25:04 +0100 (CET) Received: by moya.lambermont.dyndns.org (Postfix, from userid 1001) id F303136401; Wed, 1 Dec 2004 12:25:03 +0100 (CET) Date: Wed, 1 Dec 2004 12:25:03 +0100 To: current@freebsd.org Message-ID: <20041201112503.GA23154@moya.lambermont.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i From: hans@lambermont.dyndns.org (Hans Lambermont) X-Virus-Scanned: by amavisd-new-20030616.p5 at lambermont.dyndns.org Subject: Using /dev/cuad0 locks up -current of Nov 25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 11:25:06 -0000 Hi, When I start jpilot to sync my palm my system locks up. I changed /dev/cuaa0 into /dev/cuad0 in jpilot (http://docs.freebsd.org/cgi/mid.cgi?200410130827.i9D8RKBM082371). jpilot-0.99.7_2 libmal-0.40 6.0-CURRENT #0: Thu Nov 25 18:52:00 CET 2004 src/sys/dev/sio/sio.c 1.456 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Any things to try ? regards, Hans Lambermont -- http://lambermont.webhop.org/ () ASCII-ribbon campaign against vCards, /\ HTML-mail and proprietary formats. From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 13:40:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CD5616A4CE; Wed, 1 Dec 2004 13:40:39 +0000 (GMT) Received: from mailout07.sul.t-online.com (mailout07.sul.t-online.com [194.25.134.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57FDD43D53; Wed, 1 Dec 2004 13:40:38 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd03.aul.t-online.de by mailout07.sul.t-online.com with smtp id 1CZUij-0002ab-00; Wed, 01 Dec 2004 14:40:37 +0100 Received: from Andro-Beta.Leidinger.net (XZZyt0ZHreRn3iudOFvribe8w6hP6fc1VsRXXYVCKWsB6CXbtPP64s@[217.229.215.172]) by fmrl03.sul.t-online.com with esmtp id 1CZUib-26Cem00; Wed, 1 Dec 2004 14:40:29 +0100 Received: from Andro-Beta.Leidinger.net (localhost [127.0.0.1]) iB1DeFkF044906; Wed, 1 Dec 2004 14:40:15 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: (from www@localhost)iB1DeEQn044905; Wed, 1 Dec 2004 14:40:14 +0100 (CET) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: Andro-Beta.Leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from 141.113.101.32 ([141.113.101.32]) by netchild.homeip.net (IMP) with HTTP for ; Wed, 1 Dec 2004 14:40:14 +0100 Message-ID: <1101908414.41adc9be50c73@netchild.homeip.net> Date: Wed, 1 Dec 2004 14:40:14 +0100 From: Alexander Leidinger To: current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="-MOQ1101908412fd6f338b5af8faca0ce8ba33784fec07" User-Agent: Internet Messaging Program (IMP) 3.2.6 / FreeBSD-4.10 X-Originating-IP: 141.113.101.32 X-ID: XZZyt0ZHreRn3iudOFvribe8w6hP6fc1VsRXXYVCKWsB6CXbtPP64s@t-dialin.net X-TOI-MSGID: 77a71b9b-5ddb-46b5-91a5-cd616a7eb281 cc: tode@bpanet.de Subject: Bug in our ru_RU.KOI8-R locale (with patch)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 13:40:39 -0000 This message is in MIME format. ---MOQ1101908412fd6f338b5af8faca0ce8ba33784fec07 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Hi, I got a report that our ru_RU.KOI8-R locale seems to be broken. Attached is a test program (test.pl, tested with perl 5.8.2) and some test input (test.txt) which is supposed to show the problem. I can't read any kyrillic language, so I can't really confirm if the attached patch is the right fix. If you run the test program you should see something like this (strange looking text maybe because of the webmailer I use): ---snip--- Match small (RegEx with i flag): 0 Match small (RegEx without i flag): 8 Match for normal (RegEx with i flag): 17 Match for normal (RegEx without i flag): 9 Case - Check for 'яѓјъшэ' lc() => яѓјъшэ uc() => ЯгиЪШЭ lcfirst() => яѓјъшэ ucfirst() => Яѓјъшэ Case - Check for 'Яѓјъшэ' lc() => яѓјъшэ uc() => ЯгиЪШЭ lcfirst() => яѓјъшэ ucfirst() => Яѓјъшэ ---snip--- I'm told the "Case - Check" parts are correct with the patch, but not without it (lc() -> lower case the entire string; uc() -> upper case the entire string; lcfirst() -> lower case the first character; ...). Can someone please confirm this? If this is correct we've solved only a part of the problem. The other part seems to be related to LC_COLLATE. "Match small" with the i flag (case insensitive matching) shouldn't print 0 when "Match normal" with the i flag doesn't print 0. Any ideas how to solve this? If the patch isn't correct we still have a bug somwhere (please CC perl@freebsd.org then). Why isn't perl able to do a case insensitive match in the ru_RU.KOI8-R locale? BTW.: this affects 4.x (problem noticed here), 5.x and -current (I've tested the patch here). Bye, Alexander. -- http://www.Leidinger.net/ Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org/ netchild @ FreeBSD.org : PGP ID = 72077137 ---MOQ1101908412fd6f338b5af8faca0ce8ba33784fec07 Content-Type: application/octet-stream; name="test.pl" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="test.pl" IyEvdXNyL2Jpbi9lbnYgcGVybAoKdXNlIGxvY2FsZTsKCm15ICRmaWxlCQk9ICd0ZXN0LnR4dCc7 Cm15ICRwdXNoa2luX3NtYWxsCT0gJ+/z+Oro7Sc7Cm15ICRwdXNoa2luX25vcm1hbAk9ICfP8/jq 6O0nOwoKbXkgJGRhdGEJCT0gTG9hZEZpbGUoJGZpbGUpOwoKbXkgJGNvdW50X25vcm1hbF9pCT0g MDsKbXkgJGNvdW50X3NtYWxsX2kJPSAwOwpteSAkY291bnRfbm9ybWFsICAgICAgPSAwOwpteSAk Y291bnRfc21hbGwgICAgICAgPSAwOwoKZm9yZWFjaCBteSAkbGluZSAoQHskZGF0YX0pIHsKCSRj b3VudF9ub3JtYWxfaSsrIGlmICgkbGluZSA9fiBtLyRwdXNoa2luX25vcm1hbC9pc2cpOwoJJGNv dW50X3NtYWxsX2krKyBpZiAoJGxpbmUgPX4gbS8kcHVzaGtpbl9zbWFsbC9pc2cpOwoJJGNvdW50 X25vcm1hbCsrIGlmICgkbGluZSA9fiBtLyRwdXNoa2luX25vcm1hbC9zZyk7CiAgICAgICAgJGNv dW50X3NtYWxsKysgaWYgKCRsaW5lID1+IG0vJHB1c2hraW5fc21hbGwvc2cpOwp9CgpwcmludCAi TWF0Y2ggc21hbGwgKFJlZ0V4IHdpdGggaSBmbGFnKTogJGNvdW50X3NtYWxsX2lcbiI7CnByaW50 ICJNYXRjaCBzbWFsbCAoUmVnRXggd2l0aG91dCBpIGZsYWcpOiAkY291bnRfc21hbGxcbiI7Cgpw cmludCAiTWF0Y2ggZm9yIG5vcm1hbCAoUmVnRXggd2l0aCBpIGZsYWcpOiAkY291bnRfbm9ybWFs X2lcbiI7CnByaW50ICJNYXRjaCBmb3Igbm9ybWFsIChSZWdFeCB3aXRob3V0IGkgZmxhZyk6ICRj b3VudF9ub3JtYWxcblxuIjsKVGVzdENhc2UoJHB1c2hraW5fc21hbGwpOwpUZXN0Q2FzZSgkcHVz aGtpbl9ub3JtYWwpOwoKZXhpdCgwKTsKCgpzdWIgVGVzdENhc2UgewoJbXkgJHN0cmluZwk9IHNo aWZ0KEBfKTsKCXByaW50ICJDYXNlIC0gQ2hlY2sgZm9yIFwnJHN0cmluZ1wnXG4iOwoJcHJpbnQg ImxjKCkgPT4gIi5sYygkc3RyaW5nKS4iXG4iOwoJcHJpbnQgInVjKCkgPT4gIi51Yygkc3RyaW5n KS4iXG4iOwoJcHJpbnQgImxjZmlyc3QoKSA9PiAiLmxjZmlyc3QoJHN0cmluZykuIlxuIjsKCXBy aW50ICJ1Y2ZpcnN0KCkgPT4gIi51Y2ZpcnN0KCRzdHJpbmcpLiJcbiI7CgkKCXByaW50ICJcbiI7 CgoJcmV0dXJuIDE7Cn0KCgpzdWIgTG9hZEZpbGUgewoJbXkgJGZpbGUJPSBzaGlmdChAXyk7Cglt eSBAdmFsdWUJPSAoKTsKCW9wZW4oRklMRSwgIjwkZmlsZSIpOwoJQHZhbHVlCQk9IDxGSUxFPjsK CWNsb3NlKEZJTEUpOwoJY2hvbXAoQHZhbHVlKTsKCXJldHVybiBcQHZhbHVlOwp9Cgo= ---MOQ1101908412fd6f338b5af8faca0ce8ba33784fec07 Content-Type: text/plain; name="test.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="test.txt" 7/P46ujtDQrP8/jq6O0NClRlc3QNClRlc3QNClRFU1QNCnRFU1QNCu/z+Oro7Q0Kz/P46ujtDQpU ZXN0DQpUZXN0DQpURVNUDQp0RVNUDQrv8/jq6O0NCu/z+Oro7Q0K7/P46ujtDQrv8/jq6O0NCs/z +Oro7Q0Kz/P46ujtDQrP8/jq6O0NCs/z+Oro7Q0Kz/P46ujtDQrv8/jq6O0NCs/z+Oro7Q0Kz/P4 6ujtDQrv8/jq6O0NCg0KQ09VTlQgbG93ZXIgOCB1cHBlciA5DQoNCg== ---MOQ1101908412fd6f338b5af8faca0ce8ba33784fec07 Content-Type: application/octet-stream; name="mklocale:ru_RU.KOI8-R.diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="mklocale:ru_RU.KOI8-R.diff" LS0tIC91c3Ivc3JjL3NoYXJlL21rbG9jYWxlL3J1X1JVLktPSTgtUi5zcmMJRnJpIE5vdiAzMCAw NjowNTo1MyAyMDAxCisrKyBydV9SVS5LT0k4LVIuc3JjCVdlZCBEZWMgIDEgMTM6Mzg6NTkgMjAw NApAQCAtMTMsMjcgKzEzLDI3IEBACiBDT05UUk9MCQkweDAwIC0gMHgxZiAweDdmCiBESUdJVAkJ JzAnIC0gJzknCiBHUkFQSAkJMHgyMSAtIDB4N2UgMHg4MCAtIDB4OTkJMHg5YiAtIDB4ZmYKLUxP V0VSCQknYScgLSAneicgMHhhMyAweGMwIC0gMHhkZgorTE9XRVIJCSdhJyAtICd6JyAweGIzIDB4 ZTAgLSAweGZmCiBQVU5DVAkJMHgyMSAtIDB4MmYgMHgzYSAtIDB4NDAgMHg1YiAtIDB4NjAgMHg3 YiAtIDB4N2UKIFNQQUNFCQkweDA5IC0gMHgwZCAweDIwIDB4OWEKLVVQUEVSCQknQScgLSAnWicg MHhiMyAweGUwIC0gMHhmZgorVVBQRVIJCSdBJyAtICdaJyAweGEzIDB4YzAgLSAweGRmCiBYRElH SVQgICAgICAgICAgJzAnIC0gJzknICdhJyAtICdmJyAnQScgLSAnRicKIEJMQU5LCQknICcgJ1x0 JyAweDlhCiBQUklOVAkJMHgyMCAtIDB4N2UgMHg4MCAtIDB4ZmYKIAogTUFQTE9XRVIgICAgICAg CTwnQScgLSAnWicgOiAnYSc+CiBNQVBMT1dFUiAgICAgICAJPCdhJyAtICd6JyA6ICdhJz4KLU1B UExPV0VSCTwweGIzICAweGEzPgotTUFQTE9XRVIgICAgICAgIDwweGEzICAweGEzPgotTUFQTE9X RVIJPDB4ZTAgLSAweGZmIDogMHhjMD4KLU1BUExPV0VSCTwweGMwIC0gMHhkZiA6IDB4YzA+CitN QVBMT1dFUgk8MHhiMyAgMHhiMz4KK01BUExPV0VSICAgICAgICA8MHhhMyAgMHhiMz4KK01BUExP V0VSCTwweGUwIC0gMHhmZiA6IDB4ZTA+CitNQVBMT1dFUgk8MHhjMCAtIDB4ZGYgOiAweGUwPgog CiBNQVBVUFBFUiAgICAgICAJPCdBJyAtICdaJyA6ICdBJz4KIE1BUFVQUEVSICAgICAgIAk8J2En IC0gJ3onIDogJ0EnPgotTUFQVVBQRVIgICAgICAgIDwweGIzICAweGIzPgotTUFQVVBQRVIJPDB4 YTMgIDB4YjM+Ci1NQVBVUFBFUgk8MHhlMCAtIDB4ZmYgOiAweGUwPgotTUFQVVBQRVIJPDB4YzAg LSAweGRmIDogMHhlMD4KK01BUFVQUEVSICAgICAgICA8MHhiMyAgMHhhMz4KK01BUFVQUEVSCTww eGEzICAweGEzPgorTUFQVVBQRVIJPDB4ZTAgLSAweGZmIDogMHhjMD4KK01BUFVQUEVSCTwweGMw IC0gMHhkZiA6IDB4YzA+CiAKIFRPRElHSVQgICAgICAgCTwnMCcgLSAnOScgOiAwPgogVE9ESUdJ VCAgICAgICAJPCdBJyAtICdGJyA6IDEwPgo= ---MOQ1101908412fd6f338b5af8faca0ce8ba33784fec07-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 14:13:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF6CE16A4CE for ; Wed, 1 Dec 2004 14:13:49 +0000 (GMT) Received: from mx1.mail.ru (mx1.mail.ru [194.67.23.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7013243D4C for ; Wed, 1 Dec 2004 14:13:49 +0000 (GMT) (envelope-from DAntrushin@mail.ru) Received: from [81.3.158.67] (port=58763 helo=[129.159.124.237]) by mx1.mail.ru with esmtp id 1CZVEp-000OXj-00; Wed, 01 Dec 2004 17:13:47 +0300 Message-ID: <41ADD1DA.9000509@mail.ru> Date: Wed, 01 Dec 2004 17:14:50 +0300 From: Denis Antrushin User-Agent: Mozilla Thunderbird 0.9 (X11/20041119) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Leidinger References: <1101908414.41adc9be50c73@netchild.homeip.net> In-Reply-To: <1101908414.41adc9be50c73@netchild.homeip.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam: Not detected cc: current@freebsd.org cc: tode@bpanet.de Subject: Re: Bug in our ru_RU.KOI8-R locale (with patch)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 14:13:49 -0000 Alexander Leidinger wrote: > Hi, > > I got a report that our ru_RU.KOI8-R locale seems to be broken. Attached > is a test program (test.pl, tested with perl 5.8.2) and some test input > (test.txt) which is supposed to show the problem. I can't read any > cyrillic language, so I can't really confirm if the attached patch is the > right fix. First of all, test.txt is in CP1251 encoding, not KOI8-R ;-) Second, patch is plain wrong -- it replaces KOI8-R character codes with CP1251 ones. > If you run the test program you should see something like this (strange > looking text maybe because of the webmailer I use): > ---snip--- > Match small (RegEx with i flag): 0 > Match small (RegEx without i flag): 8 > Match for normal (RegEx with i flag): 17 > Match for normal (RegEx without i flag): 9 > > Case - Check for 'яѓјъшэ' > lc() => яѓјъшэ > uc() => ЯгиЪШЭ > lcfirst() => яѓјъшэ > ucfirst() => Яѓјъшэ > > Case - Check for 'Яѓјъшэ' > lc() => яѓјъшэ > uc() => ЯгиЪШЭ > lcfirst() => яѓјъшэ > ucfirst() => Яѓјъшэ > ---snip--- > > I'm told the "Case - Check" parts are correct with the patch, but not > without it (lc() -> lower case the entire string; uc() -> upper case the > entire string; lcfirst() -> lower case the first character; ...). Can > someone please confirm this? This is what test gives me (transliterated to ascii): Case - Check for 'pushkin' lc() => pushkin uc() => PUSHKIN lcfirst() => pushkin ucfirst() => Pushkin Case - Check for 'Pushkin' lc() => pushkin uc() => PUSHKIN lcfirst() => pushkin ucfirst() => Pushkin It seems correct for me... > If this is correct we've solved only a part of the problem. The other > part seems to be related to LC_COLLATE. "Match small" with the i flag > (case insensitive matching) shouldn't print 0 when "Match normal" with > the i flag doesn't print 0. Any ideas how to solve this? > > If the patch isn't correct we still have a bug somwhere (please CC > perl@freebsd.org then). Why isn't perl able to do a case insensitive > match in the ru_RU.KOI8-R locale? > > BTW.: this affects 4.x (problem noticed here), 5.x and -current (I've > tested the patch here). > > Bye, > Alexander. > From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 15:40:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D1FD616A4CE for ; Wed, 1 Dec 2004 15:40:05 +0000 (GMT) Received: from bewilderbeast.blackhelicopters.org (bewilderbeast.blackhelicopters.org [198.22.63.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8349043D78 for ; Wed, 1 Dec 2004 15:40:05 +0000 (GMT) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (mwlucas@localhost [127.0.0.1])iB1Fe2ex016906; Wed, 1 Dec 2004 10:40:02 -0500 (EST) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: (from mwlucas@localhost)iB1Fdk6w016901; Wed, 1 Dec 2004 10:39:46 -0500 (EST) (envelope-from mwlucas) Date: Wed, 1 Dec 2004 10:39:46 -0500 From: "Michael W. Lucas" To: Daniel Eriksson Message-ID: <20041201153946.GA16872@bewilderbeast.blackhelicopters.org> References: <3BE1BF5E-4249-11D9-9F7A-000A95A9A574@nordahl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Spam-Score: (0) X-Scanned-By: MIMEDefang 2.39 cc: freebsd-current@freebsd.org cc: 'Frode Nordahl' Subject: Re: Got rid of my SiI3112A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 15:40:05 -0000 On Mon, Nov 29, 2004 at 10:40:41PM +0100, Daniel Eriksson wrote: > Frode Nordahl wrote: > > > But as things are today, I think it would be best to remove > > support for > > SiI3112A. Especially since the general attitude towards it is > > "it's too > > broke, we don't want to waste any more time on it". > > > > Attempting to use it in a 5.3-RELEASE or 6-CURRENT system will most > > likelly make your system crash and burn, and make your data > > unrecoverable beyond repair. > > I will have to agree with Frode on this one. I recently put -CURRENT on a > machine with an ASUS mobo that had a SiL 3112 controller. Hooking up two > 250GB WD discs to it quickly resulted in timeouts, followed by some strange > messages from geom_stripe (used it to stripe the two discs), followed by > filesystem corruption and panics. Does anyone know if Soren has one of these controllers? Getting him a poorly-supported controller is the first step towards getting it fixed. ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org "I'm sorry, but 'Social Darwinism' is no excuse for killing all of your co-workers." -- Ivan Brunetti http://www.BlackHelicopters.org/~mwlucas/ From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 15:49:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B24216A4CE for ; Wed, 1 Dec 2004 15:49:58 +0000 (GMT) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A4E443D31 for ; Wed, 1 Dec 2004 15:49:58 +0000 (GMT) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v7.1.0.R) with ESMTP id md50000305528.msg for ; Wed, 01 Dec 2004 07:26:13 -0800 From: "David Schwartz" To: Date: Wed, 1 Dec 2004 07:49:54 -0800 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.6604 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Wed, 01 Dec 2004 07:26:13 -0800 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDaemon-Deliver-To: current@FreeBSD.org X-MDAV-Processed: mail1.webmaster.com, Wed, 01 Dec 2004 07:26:13 -0800 cc: current@FreeBSD.org Subject: Re: malloc(0) returns an invalid address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: davids@webmaster.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 15:49:58 -0000 > >>>>> On Tue, 30 Nov 2004 21:40:25 -0800, > >>>>> "David Schwartz" said: > > >> % ./a.out > >> address of p is 0x800 > >> zsh: 794 segmentation fault (core dumped) ./a.out > >> > >> Is this a malloc bug? Or is this the intended behavior and the man > >> page description is old? > > > This is the intended behavior but the man page description > is correct. The > > problem is not that the pointer is invalid but that you assumed > that it was > > large enough to hold a 'char' and it is not. > I know the line of XXX is not correct; I simply tried to highlight the > problem, but I seem to convey the real point. How about this example? > > main() > { > char *p = malloc(0), *q; > > printf("address of p is %p\n", p); > printf("the value of p is %c\n", *p); > } > > the execution of this code would be like this: > > % ./a.out > address of p is 0x800 > zsh: 645 segmentation fault (core dumped) ./a.out This should fault. Although the return value of 'malloc(0)' is a valid pointer, once you cast it to a 'char *', you cannot dereference it because it does not point to a character. This same problem would occur with 'malloc(1)' and 'int *'. > And, more specifically, my real-world problem is that 'ndp -r' fails > when it calls sysctl without any IPv6 default routers. The related > code of ndp is as follows: > > int mib[] = { CTL_NET, PF_INET6, IPPROTO_ICMPV6, > ICMPV6CTL_ND6_DRLIST }; > > (...) > > if (sysctl(mib, sizeof(mib) / sizeof(mib[0]), NULL, &l, > NULL, 0) < 0) { > err(1, "sysctl(ICMPV6CTL_ND6_DRLIST)"); > /*NOTREACHED*/ > } > buf = malloc(l); > if (!buf) { > err(1, "malloc"); > /*NOTREACHED*/ > } > if (sysctl(mib, sizeof(mib) / sizeof(mib[0]), buf, &l, > NULL, 0) < 0) { > err(1, "sysctl(ICMPV6CTL_ND6_DRLIST)"); > /*NOTREACHED*/ > } > > The first call to sysctl sets 'l' to 0, since the list is empty. Then > the malloc returns '0x800' as a *valid pointer*. But in the second > call to sysctl, kernel rejects this pointer at line 1299 of > sys/kern/kern_sysctl.c: > > userland_sysctl(struct thread *td, int *name, u_int namelen, void *old, > size_t *oldlenp, int inkernel, void *new, size_t newlen, > size_t *retval) > { > > (...) > > if (old) { > --> if (!useracc(old, req.oldlen, VM_PROT_WRITE)) > --> return (EFAULT); > > and so we'll see > > % ndp -r > ndp: sysctl(ICMPV6CTL_ND6_DRLIST): Bad address > > Note that the same code worked with, e.g., FreeBSD 4.10. > > So, if we wanted to call 0x800 "a valid pointer just with > not-enough-size", it would be fine. But then we need to implement the > same logic in the kernel to provide consistent behavior. (I would > "fix" the malloc behavior though). The malloc behavior is not broken, so it cannot be fixed. The kernel check semantics in 'useracc' are wrong for zero lengths. DS From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 16:00:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BCC416A4CE for ; Wed, 1 Dec 2004 16:00:51 +0000 (GMT) Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1546843D5C for ; Wed, 1 Dec 2004 16:00:51 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd10.aul.t-online.de by mailout06.sul.t-online.com with smtp id 1CZWuC-0006Kv-01; Wed, 01 Dec 2004 17:00:36 +0100 Received: from Andro-Beta.Leidinger.net (GurYirZTwe0eNu49TsQK9wEnCtrDD0BkW8y60BQTJ6vJCxCd-zaFYM@[217.229.215.172]) by fmrl10.sul.t-online.com with esmtp id 1CZWu4-2GCT0i0; Wed, 1 Dec 2004 17:00:28 +0100 Received: from Andro-Beta.Leidinger.net (localhost [127.0.0.1]) iB1G0Iof065160; Wed, 1 Dec 2004 17:00:18 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: (from www@localhost)iB1G0HEY065159; Wed, 1 Dec 2004 17:00:17 +0100 (CET) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: Andro-Beta.Leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from 141.113.101.32 ([141.113.101.32]) by netchild.homeip.net (IMP) with HTTP for ; Wed, 1 Dec 2004 17:00:17 +0100 Message-ID: <1101916817.41adea91726c7@netchild.homeip.net> Date: Wed, 1 Dec 2004 17:00:17 +0100 From: Alexander Leidinger To: Denis Antrushin References: <1101908414.41adc9be50c73@netchild.homeip.net> <41ADD1DA.9000509@mail.ru> In-Reply-To: <41ADD1DA.9000509@mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.6 / FreeBSD-4.10 X-Originating-IP: 141.113.101.32 X-ID: GurYirZTwe0eNu49TsQK9wEnCtrDD0BkW8y60BQTJ6vJCxCd-zaFYM@t-dialin.net X-TOI-MSGID: 5bef6a25-e889-4944-a898-03fbc8088f89 cc: current@freebsd.org cc: tode@bpanet.de Subject: Re: Bug in our ru_RU.KOI8-R locale (with patch)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 16:00:51 -0000 Zitat von Denis Antrushin : > First of all, test.txt is in CP1251 encoding, not KOI8-R ;-) Fine, this explains why it doesn't look right with KOI8-R. > > ---snip--- > > Match small (RegEx with i flag): 0 > > Match small (RegEx without i flag): 8 > > Match for normal (RegEx with i flag): 17 > > Match for normal (RegEx without i flag): 9 > This is what test gives me (transliterated to ascii): [Case -Check only] What about the case insensitive match? I assume it works as expected too. Thanks, Alexander. -- http://www.Leidinger.net/ Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org/ netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 16:29:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFFD716A4CE for ; Wed, 1 Dec 2004 16:29:57 +0000 (GMT) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F71843D54 for ; Wed, 1 Dec 2004 16:29:57 +0000 (GMT) (envelope-from DAntrushin@mail.ru) Received: from [81.3.158.67] (port=59546 helo=[129.159.124.237]) by mx2.mail.ru with esmtp id 1CZXMZ-0002pk-00; Wed, 01 Dec 2004 19:29:56 +0300 Message-ID: <41ADF1C3.3090902@mail.ru> Date: Wed, 01 Dec 2004 19:30:59 +0300 From: Denis Antrushin User-Agent: Mozilla Thunderbird 0.9 (X11/20041119) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Leidinger References: <1101908414.41adc9be50c73@netchild.homeip.net> <41ADD1DA.9000509@mail.ru> <1101916817.41adea91726c7@netchild.homeip.net> In-Reply-To: <1101916817.41adea91726c7@netchild.homeip.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam: Not detected cc: current@freebsd.org Subject: Re: Bug in our ru_RU.KOI8-R locale (with patch)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 16:29:57 -0000 Alexander Leidinger wrote: > Zitat von Denis Antrushin : > > >>First of all, test.txt is in CP1251 encoding, not KOI8-R ;-) > > > Fine, this explains why it doesn't look right with KOI8-R. > > >>>---snip--- >>>Match small (RegEx with i flag): 0 >>>Match small (RegEx without i flag): 8 >>>Match for normal (RegEx with i flag): 17 >>>Match for normal (RegEx without i flag): 9 > > >>This is what test gives me (transliterated to ascii): > > > [Case -Check only] > > What about the case insensitive match? I assume it works as expected too. 'Match small' print 0 But if I remove 'g' suffix, i.e. use $line =~ m/$pushkin_small/is, then it print 17 > > Thanks, > Alexander. > From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 16:41:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A0CD16A4CE for ; Wed, 1 Dec 2004 16:41:37 +0000 (GMT) Received: from av13-2-sn4.m-sp.skanova.net (av13-2-sn4.m-sp.skanova.net [81.228.10.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C70443D1D for ; Wed, 1 Dec 2004 16:41:36 +0000 (GMT) (envelope-from ertr1013@student.uu.se) Received: by av13-2-sn4.m-sp.skanova.net (Postfix, from userid 502) id 4FD1B37E48; Wed, 1 Dec 2004 17:41:35 +0100 (CET) Received: from smtp4-2-sn4.m-sp.skanova.net (smtp4-2-sn4.m-sp.skanova.net [81.228.10.180]) by av13-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id 3FD3137E42 for ; Wed, 1 Dec 2004 17:41:35 +0100 (CET) Received: from falcon.midgard.homeip.net (h201n1fls24o1048.bredband.comhem.se [212.181.162.201]) by smtp4-2-sn4.m-sp.skanova.net (Postfix) with SMTP id 15BBB37E46 for ; Wed, 1 Dec 2004 17:41:35 +0100 (CET) Received: (qmail 58291 invoked by uid 1001); 1 Dec 2004 16:41:34 -0000 Date: Wed, 1 Dec 2004 17:41:34 +0100 From: Erik Trulsson To: "Michael W. Lucas" Message-ID: <20041201164134.GA58263@falcon.midgard.homeip.net> Mail-Followup-To: "Michael W. Lucas" , Daniel Eriksson , freebsd-current@freebsd.org, 'Frode Nordahl' References: <3BE1BF5E-4249-11D9-9F7A-000A95A9A574@nordahl.net> <20041201153946.GA16872@bewilderbeast.blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201153946.GA16872@bewilderbeast.blackhelicopters.org> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: 'Frode Nordahl' cc: Daniel Eriksson Subject: Re: Got rid of my SiI3112A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 16:41:37 -0000 On Wed, Dec 01, 2004 at 10:39:46AM -0500, Michael W. Lucas wrote: > On Mon, Nov 29, 2004 at 10:40:41PM +0100, Daniel Eriksson wrote: > > Frode Nordahl wrote: > > > > > But as things are today, I think it would be best to remove > > > support for > > > SiI3112A. Especially since the general attitude towards it is > > > "it's too > > > broke, we don't want to waste any more time on it". > > > > > > Attempting to use it in a 5.3-RELEASE or 6-CURRENT system will most > > > likelly make your system crash and burn, and make your data > > > unrecoverable beyond repair. > > > > I will have to agree with Frode on this one. I recently put -CURRENT on a > > machine with an ASUS mobo that had a SiL 3112 controller. Hooking up two > > 250GB WD discs to it quickly resulted in timeouts, followed by some strange > > messages from geom_stripe (used it to stripe the two discs), followed by > > filesystem corruption and panics. > > Does anyone know if Soren has one of these controllers? > > Getting him a poorly-supported controller is the first step towards > getting it fixed. He probably has one. Otherwise I don't think he would write commit-messages like this one for sys/dev/ata/ata-chipset.c: ---- revision 1.50 date: 2003/12/08 09:22:20; author: sos; state: Exp; lines: +3 -1 More errata fixing for the SiI3112A disaster chip: Serialize access to the SATA channels, the chip messes up if both channels are used at the same time. The SiI3112 hereby takes the price as the most crappy SATA chip in existance by a significant amount. My advise to our userbase is to avoid this chip like the plague... ---- I take it that it is not so much a matter of this controller being poorly supported, as of this being a poor controller. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 17:03:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D87FA16A4CE for ; Wed, 1 Dec 2004 17:03:05 +0000 (GMT) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A29D43D31 for ; Wed, 1 Dec 2004 17:03:05 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy.york.ac.uk [144.32.226.160]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id iB1H31Pw020556 for ; Wed, 1 Dec 2004 17:03:01 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.1/8.13.1) with ESMTP id iB1H316E085302 for ; Wed, 1 Dec 2004 17:03:01 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.1/8.13.1/Submit) id iB1H31Qs085301 for freebsd-current@freebsd.org; Wed, 1 Dec 2004 17:03:01 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: freebsd-current@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1101920581.84212.50.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 01 Dec 2004 17:03:01 +0000 X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Subject: tty-related panic on "init 0" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 17:03:06 -0000 Hey, Just got a tty-related panic when running "init 0" over a serial console on FreeBSD 6.0-CURRENT #2: Fri Nov 26 16:59:28 GMT 2004. I was unable to obtain a dump, but have a debug kernel available. Gavin foo# init 0 foo# Shutting down daemon processes:. Stopping cron. Shutting down local daemons:. Writing entropy file:. . Dec 1 16:39:47 Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 00 fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0639bd6 stack pointer = 0x10:0xecd10b58 frame pointer = 0x10:0xecd10b70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 3483 (screen) [thread pid 3483 tid 100148 ] Stopped at ttymodem+0xee: movl 0x4(%eax),%edi db> tr Tracing pid 3483 tid 100148 td 0xc3b6fc00 ttymodem(c35da000) at ttymodem+0xee ptcclose(c44c5200,7,2000,c3b6fc00,c3b6fc00) at ptcclose+0x1a devfs_close(ecd10bc0,c08b78e0,c930c564,7,c4029a80) at devfs_close+0x1ba vn_close(c930c564,7,c4029a80,c3b6fc00,85a) at vn_close+0x5d vn_closefile(c5137a5c,c3b6fc00,c44c6c00,0,ecd10cc0) at vn_closefile+0x44 fdrop_locked(c5137a5c,c3b6fc00,c0870164,c3b6fc70,407) at fdrop_locked+0x79 closef(c5137a5c,c3b6fc00,0,ecd10d40,7) at closef+0x1e close(c3b6fc00,ecd10d14,1,23,246) at close+0x149 syscall(2f,2f,2f,80aa000,80aa000) at syscall+0x128 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (6, FreeBSD ELF32, close), eip = 0x2816766f, esp = 0xbfbfe06c, ebp = 0xbfbfe088 --- From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 17:03:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9301E16A4CF for ; Wed, 1 Dec 2004 17:03:45 +0000 (GMT) Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0903843D4C for ; Wed, 1 Dec 2004 17:03:45 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd04.aul.t-online.de by mailout10.sul.t-online.com with smtp id 1CZXt5-0003kv-00; Wed, 01 Dec 2004 18:03:31 +0100 Received: from Andro-Beta.Leidinger.net (Srg6x+ZegeXJ1RhIz8OIUgvWdw1dovkSlQKwyGueq74VrN2AaxYKr7@[217.229.215.172]) by fmrl04.sul.t-online.com with esmtp id 1CZXsq-0dc8q80; Wed, 1 Dec 2004 18:03:16 +0100 Received: from Andro-Beta.Leidinger.net (localhost [127.0.0.1]) iB1H36kV074120; Wed, 1 Dec 2004 18:03:06 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: (from www@localhost)iB1H368N074119; Wed, 1 Dec 2004 18:03:06 +0100 (CET) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: Andro-Beta.Leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from 141.113.101.32 ([141.113.101.32]) by netchild.homeip.net (IMP) with HTTP for ; Wed, 1 Dec 2004 18:03:06 +0100 Message-ID: <1101920586.41adf94a6387a@netchild.homeip.net> Date: Wed, 1 Dec 2004 18:03:06 +0100 From: Alexander Leidinger To: Denis Antrushin References: <1101908414.41adc9be50c73@netchild.homeip.net> <41ADD1DA.9000509@mail.ru> <1101916817.41adea91726c7@netchild.homeip.net> <41ADF1C3.3090902@mail.ru> In-Reply-To: <41ADF1C3.3090902@mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.6 / FreeBSD-4.10 X-Originating-IP: 141.113.101.32 X-ID: Srg6x+ZegeXJ1RhIz8OIUgvWdw1dovkSlQKwyGueq74VrN2AaxYKr7@t-dialin.net X-TOI-MSGID: c3762173-a6c9-4bdd-8a2e-170cc65f7c26 cc: current@freebsd.org Subject: Re: Bug in our ru_RU.KOI8-R locale (with patch)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 17:03:45 -0000 Zitat von Denis Antrushin : > > What about the case insensitive match? I assume it works as expected too. > 'Match small' print 0 > But if I remove 'g' suffix, i.e. use $line =~ m/$pushkin_small/is, > then it print 17 Thanks, I will discuss this the submitter of the issue now. Bye, Alexander. -- http://www.Leidinger.net/ Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org/ netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 17:59:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDCF016A4CE for ; Wed, 1 Dec 2004 17:59:28 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 679D343D5E for ; Wed, 1 Dec 2004 17:59:28 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 714 invoked from network); 1 Dec 2004 17:59:27 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 1 Dec 2004 17:59:26 -0000 Received: from [10.50.40.211] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iB1HxMp2097433 for ; Wed, 1 Dec 2004 12:59:22 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: current@FreeBSD.org Date: Wed, 1 Dec 2004 12:48:30 -0500 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200412011248.30016.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Updated patch to fix acpi_pci_link handling of DPFs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 17:59:28 -0000 Can folks please test this patch and let me know if there are any problems? Especially if your machine had problems with my earlier commit to acpi_pci_link.c prior to Nate's changes. Thanks! --- //depot/vendor/freebsd/src/sys/dev/acpica/acpi_pci_link.c 2004/12/01 05:50:42 +++ //depot/user/jhb/acpipci/dev/acpica/acpi_pci_link.c 2004/12/01 16:18:48 @@ -57,8 +57,34 @@ * An ACPI PCI link device may contain multiple links. Each link has its * own ACPI resource. _PRT entries specify which link is being used via * the Source Index. + * + * XXX: A note about Source Indices and DPFs: Currently we assume that + * the DPF start and end tags are not counted towards the index that + * Source Index corresponds to. Also, we assume that when DPFs are in use + * they various sets overlap in terms of Indices. Here's an example + * resource list indicating these assumptions: + * + * Resource Index + * -------- ----- + * I/O Port 0 + * Start DPF - + * IRQ 1 + * MemIO 2 + * Start DPF - + * IRQ 1 + * MemIO 2 + * End DPF - + * DMA Channel 3 + * + * The XXX is because I'm not sure if this is a valid assumption to make. + * Further reading of the spec is advised before this hits CVS. */ +/* States during DPF processing. */ +#define DPF_OUTSIDE 0 +#define DPF_FIRST 1 +#define DPF_IGNORE 2 + struct link; struct acpi_pci_link_softc { @@ -80,9 +106,16 @@ ACPI_RESOURCE l_prs_template; }; +struct link_count_request { + int in_dpf; + int count; +}; + struct link_res_request { struct acpi_pci_link_softc *sc; - int count; + int in_dpf; + int res_index; + int link_index; }; MALLOC_DEFINE(M_PCI_LINK, "PCI Link", "ACPI PCI Link structures"); @@ -133,13 +166,36 @@ static ACPI_STATUS acpi_count_irq_resources(ACPI_RESOURCE *res, void *context) { - int *count; + struct link_count_request *req; - count = (int *)context; + req = (struct link_count_request *)context; switch (res->Id) { + case ACPI_RSTYPE_START_DPF: + switch (req->in_dpf) { + case DPF_OUTSIDE: + /* We've started the first DPF. */ + req->in_dpf = DPF_FIRST; + break; + case DPF_FIRST: + /* We've started the second DPF. */ + req->in_dpf = DPF_IGNORE; + break; + } + break; + case ACPI_RSTYPE_END_DPF: + /* We are finished with DPF parsing. */ + KASSERT(req->in_dpf != DPF_OUTSIDE, + ("%s: end dpf when not parsing a dpf", __func__)); + req->in_dpf = DPF_OUTSIDE; + break; case ACPI_RSTYPE_IRQ: case ACPI_RSTYPE_EXT_IRQ: - (*count)++; + /* + * Don't count resources if we are in a DPF set that we are + * ignoring. + */ + if (req->in_dpf != DPF_IGNORE) + req->count++; } return (AE_OK); } @@ -153,12 +209,34 @@ ACPI_SERIAL_ASSERT(pci_link); req = (struct link_res_request *)context; switch (res->Id) { + case ACPI_RSTYPE_START_DPF: + switch (req->in_dpf) { + case DPF_OUTSIDE: + /* We've started the first DPF. */ + req->in_dpf = DPF_FIRST; + break; + case DPF_FIRST: + /* We've started the second DPF. */ + panic( + "%s: Multiple dependent functions within a current resource", + __func__); + break; + } + break; + case ACPI_RSTYPE_END_DPF: + /* We are finished with DPF parsing. */ + KASSERT(req->in_dpf != DPF_OUTSIDE, + ("%s: end dpf when not parsing a dpf", __func__)); + req->in_dpf = DPF_OUTSIDE; + break; case ACPI_RSTYPE_IRQ: case ACPI_RSTYPE_EXT_IRQ: - KASSERT(req->count < req->sc->pl_num_links, - ("link_add_crs: array boundary violation")); - link = &req->sc->pl_links[req->count]; - req->count++; + KASSERT(req->link_index < req->sc->pl_num_links, + ("%s: array boundary violation", __func__)); + link = &req->sc->pl_links[req->link_index]; + link->l_res_index = req->res_index; + req->link_index++; + req->res_index++; if (res->Id == ACPI_RSTYPE_IRQ) { if (res->Data.Irq.NumberOfInterrupts > 0) { KASSERT(res->Data.Irq.NumberOfInterrupts == 1, @@ -177,6 +255,8 @@ if (link->l_irq == 0) link->l_irq = PCI_INVALID_IRQ; break; + default: + req->res_index++; } return (AE_OK); } @@ -195,12 +275,37 @@ ACPI_SERIAL_ASSERT(pci_link); req = (struct link_res_request *)context; switch (res->Id) { + case ACPI_RSTYPE_START_DPF: + switch (req->in_dpf) { + case DPF_OUTSIDE: + /* We've started the first DPF. */ + req->in_dpf = DPF_FIRST; + break; + case DPF_FIRST: + /* We've started the second DPF. */ + req->in_dpf = DPF_IGNORE; + break; + } + break; + case ACPI_RSTYPE_END_DPF: + /* We are finished with DPF parsing. */ + KASSERT(req->in_dpf != DPF_OUTSIDE, + ("%s: end dpf when not parsing a dpf", __func__)); + req->in_dpf = DPF_OUTSIDE; + break; case ACPI_RSTYPE_IRQ: case ACPI_RSTYPE_EXT_IRQ: - KASSERT(req->count < req->sc->pl_num_links, - ("link_add_prs: array boundary violation")); - link = &req->sc->pl_links[req->count]; - req->count++; + /* + * Don't parse resources if we are in a DPF set that we are + * ignoring. + */ + if (req->in_dpf == DPF_IGNORE) + break; + + KASSERT(req->link_index < req->sc->pl_num_links, + ("%s: array boundary violation", __func__)); + link = &req->sc->pl_links[req->link_index]; + req->link_index++; /* * Stash a copy of the resource for later use when doing @@ -288,10 +393,10 @@ acpi_pci_link_attach(device_t dev) { struct acpi_pci_link_softc *sc; - struct link_res_request req; + struct link_count_request creq; + struct link_res_request rreq; ACPI_STATUS status; int i; - int prslinks; sc = device_get_softc(dev); ACPI_SERIAL_BEGIN(pci_link); @@ -300,25 +405,15 @@ * Count the number of current resources so we know how big of * a link array to allocate. */ + creq.in_dpf = DPF_OUTSIDE; + creq.count = 0; status = AcpiWalkResources(acpi_get_handle(dev), "_CRS", - acpi_count_irq_resources, &sc->pl_num_links); + acpi_count_irq_resources, &creq); if (ACPI_FAILURE(status)) - return (ENXIO); - if (sc->pl_num_links == 0) + return (ENXIO); + if (creq.count == 0) return (0); - - /* - * Try to make the number of resources sufficiently large - * for traversal of both _PRS and _CRS. - * - * XXX Temporary fix for out-of-bounds access in prs_add_links(). - * We really need to handle these in separate arrays. -- njl - */ - prslinks = 0; - status = AcpiWalkResources(acpi_get_handle(dev), "_PRS", - acpi_count_irq_resources, &prslinks); - if (prslinks > sc->pl_num_links) - sc->pl_num_links = prslinks; + sc->pl_num_links = creq.count; sc->pl_links = malloc(sizeof(struct link) * sc->pl_num_links, M_PCI_LINK, M_WAITOK | M_ZERO); @@ -326,19 +421,22 @@ for (i = 0; i < sc->pl_num_links; i++) { sc->pl_links[i].l_irq = PCI_INVALID_IRQ; sc->pl_links[i].l_bios_irq = PCI_INVALID_IRQ; - sc->pl_links[i].l_res_index = i; sc->pl_links[i].l_sc = sc; sc->pl_links[i].l_isa_irq = 0; } - req.count = 0; - req.sc = sc; + rreq.in_dpf = DPF_OUTSIDE; + rreq.link_index = 0; + rreq.res_index = 0; + rreq.sc = sc; status = AcpiWalkResources(acpi_get_handle(dev), "_CRS", - link_add_crs, &req); + link_add_crs, &rreq); if (ACPI_FAILURE(status)) goto fail; - req.count = 0; + rreq.in_dpf = DPF_OUTSIDE; + rreq.link_index = 0; + rreq.res_index = 0; status = AcpiWalkResources(acpi_get_handle(dev), "_PRS", - link_add_prs, &req); + link_add_prs, &rreq); if (ACPI_FAILURE(status) && status != AE_NOT_FOUND) goto fail; if (bootverbose) { @@ -432,20 +530,36 @@ return (PCI_INVALID_IRQ); } +/* + * Find the link structure that corresponds to the resource index passed in + * via 'source_index'. + */ +static struct link * +acpi_pci_link_lookup(device_t dev, int source_index) +{ + struct acpi_pci_link_softc *sc; + int i; + + ACPI_SERIAL_ASSERT(pci_link); + sc = device_get_softc(dev); + for (i = 0; i < sc->pl_num_links; i++) + if (sc->pl_links[i].l_res_index == source_index) + return (&sc->pl_links[i]); + return (NULL); +} + void acpi_pci_link_add_reference(device_t dev, int index, device_t pcib, int slot, int pin) { - struct acpi_pci_link_softc *sc; struct link *link; uint8_t bios_irq; /* Bump the reference count. */ ACPI_SERIAL_BEGIN(pci_link); - sc = device_get_softc(dev); - KASSERT(index >= 0 && index < sc->pl_num_links, - ("%s: invalid index %d", __func__, index)); - link = &sc->pl_links[index]; + link = acpi_pci_link_lookup(dev, index); + if (link == NULL) + panic("%s: apparently invalid index %d", __func__, index); link->l_references++; if (link->l_routed) pci_link_interrupt_weights[link->l_irq]++; @@ -486,7 +600,7 @@ ACPI_BUFFER crsbuf, srsbuf; ACPI_STATUS status; struct link *link; - int i; + int i, in_dpf; /* Fetch the _CRS. */ ACPI_SERIAL_ASSERT(pci_link); @@ -508,20 +622,48 @@ srsbuf.Pointer = NULL; link = sc->pl_links; i = 0; + in_dpf = DPF_OUTSIDE; resource = (ACPI_RESOURCE *)crsbuf.Pointer; end = (ACPI_RESOURCE *)((char *)crsbuf.Pointer + crsbuf.Length); for (;;) { switch (resource->Id) { + case ACPI_RSTYPE_START_DPF: + switch (in_dpf) { + case DPF_OUTSIDE: + /* We've started the first DPF. */ + in_dpf = DPF_FIRST; + break; + case DPF_FIRST: + /* We've started the second DPF. */ + panic( + "%s: Multiple dependent functions within a current resource", + __func__); + break; + } + resptr = NULL; + break; + case ACPI_RSTYPE_END_DPF: + /* We are finished with DPF parsing. */ + KASSERT(in_dpf != DPF_OUTSIDE, + ("%s: end dpf when not parsing a dpf", __func__)); + in_dpf = DPF_OUTSIDE; + resptr = NULL; + break; case ACPI_RSTYPE_IRQ: MPASS(i < sc->pl_num_links); MPASS(link->l_prs_template.Id == ACPI_RSTYPE_IRQ); newres = link->l_prs_template; resptr = &newres; resptr->Data.Irq.NumberOfInterrupts = 1; - if (PCI_INTERRUPT_VALID(link->l_irq)) + if (PCI_INTERRUPT_VALID(link->l_irq)) { + KASSERT(link->l_irq < NUM_ISA_INTERRUPTS, + ("%s: can't put non-ISA IRQ %d in legacy IRQ resource type", + __func__, link->l_irq)); resptr->Data.Irq.Interrupts[0] = link->l_irq; - else + } else resptr->Data.Irq.Interrupts[0] = 0; + link++; + i++; break; case ACPI_RSTYPE_EXT_IRQ: MPASS(i < sc->pl_num_links); @@ -534,24 +676,27 @@ link->l_irq; else resource->Data.ExtendedIrq.Interrupts[0] = 0; + link++; + i++; break; default: resptr = resource; } - status = acpi_AppendBufferResource(&srsbuf, resptr); - if (ACPI_FAILURE(status)) { - device_printf(dev, "Unable to build reousrces: %s\n", - AcpiFormatException(status)); - if (srsbuf.Pointer != NULL) - AcpiOsFree(srsbuf.Pointer); - AcpiOsFree(crsbuf.Pointer); - return (status); + if (resptr != NULL) { + status = acpi_AppendBufferResource(&srsbuf, resptr); + if (ACPI_FAILURE(status)) { + device_printf(dev, + "Unable to build reousrces: %s\n", + AcpiFormatException(status)); + if (srsbuf.Pointer != NULL) + AcpiOsFree(srsbuf.Pointer); + AcpiOsFree(crsbuf.Pointer); + return (status); + } } if (resource->Id == ACPI_RSTYPE_END_TAG) break; resource = ACPI_NEXT_RESOURCE(resource); - link++; - i++; if (resource >= end) break; } @@ -577,21 +722,28 @@ for (;;) { if (resource->Id == ACPI_RSTYPE_END_TAG) break; - MPASS(i < sc->pl_num_links); - if (link->l_routed || !PCI_INTERRUPT_VALID(link->l_irq)) - continue; switch (resource->Id) { case ACPI_RSTYPE_IRQ: case ACPI_RSTYPE_EXT_IRQ: - link->l_routed = 1; - acpi_config_intr(dev, resource); - pci_link_interrupt_weights[link->l_irq] += - link->l_references; + MPASS(i < sc->pl_num_links); + + /* + * Only configure the interrupt and update the + * weights if this link has a valid IRQ and was + * previously unrouted. + */ + if (!link->l_routed && + PCI_INTERRUPT_VALID(link->l_irq)) { + link->l_routed = 1; + acpi_config_intr(dev, resource); + pci_link_interrupt_weights[link->l_irq] += + link->l_references; + } + link++; + i++; break; } resource = ACPI_NEXT_RESOURCE(resource); - link++; - i++; if (resource >= end) break; } @@ -702,14 +854,12 @@ int acpi_pci_link_route_interrupt(device_t dev, int index) { - struct acpi_pci_link_softc *sc; struct link *link; - ACPI_SERIAL_BEGIN(pci_link); - sc = device_get_softc(dev); - KASSERT(index >= 0 && index < sc->pl_num_links, - ("%s: invalid index %d", __func__, index)); - link = &sc->pl_links[index]; + ACPI_SERIAL_BEGIN(pci_link); + link = acpi_pci_link_lookup(dev, index); + if (link == NULL) + panic("%s: apparently invalid index %d", __func__, index); /* * If this link device is already routed to an interrupt, just return -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 18:14:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3871C16A4CE for ; Wed, 1 Dec 2004 18:14:34 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 234CF43D48 for ; Wed, 1 Dec 2004 18:14:34 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 14D4472DFC; Wed, 1 Dec 2004 10:14:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 1297472DF8; Wed, 1 Dec 2004 10:14:34 -0800 (PST) Date: Wed, 1 Dec 2004 10:14:34 -0800 (PST) From: Doug White To: Randy Bush In-Reply-To: <16811.9333.99454.679978@ran.psg.com> Message-ID: <20041201101227.O68605@carver.gumbysoft.com> References: <20041123182254.GB10721@ninthgate.net> <20041124232820.J2006@carver.gumbysoft.com> <20041128220455.F40277@carver.gumbysoft.com> <16811.9333.99454.679978@ran.psg.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:14:34 -0000 On Mon, 29 Nov 2004, Randy Bush wrote: > >>> Looks like you just need to set 'dumpdev' in rc.conf. What is your boot > >>> device and swap partition(s)? > >> # grep dump /etc/rc.conf > >> dumpdev="/dev/twed0s1b" # Device name to crashdump to (or NO). > >> dumpdir="/var/crash" # Directory where crash dumps are to be stored > > Hm, this should be getting set; the twe driver supports crashdumps. What > > happens if you run 'dumpon /dev/twed0s1b' manually? > > # dumpon /dev/twed0s1b I think we established before that you were setting the device name bogusly elsewhere so we'll assume this is working now :) > >>> if you turn on session logging in your comm program > >> comm program? it's a cisco 2511 term serv being used as a > >> craft port octopus for 16 devices > > What program are you using to connect to the 2511 to view the console on > > the target? Telnet? Real terminal? :) > > telnet?!?!?!?! you're kidding, right? > > i am using ssh. Oh, they released an IOS image with ssh for those? I've been using Cyclades TSx000 boxes for too long apparently... -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 18:15:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84F6116A4CF; Wed, 1 Dec 2004 18:15:51 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E29843D54; Wed, 1 Dec 2004 18:15:51 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB1IFnYp006279; Wed, 1 Dec 2004 10:15:49 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB1IFnt9006278; Wed, 1 Dec 2004 10:15:49 -0800 (PST) (envelope-from sgk) Date: Wed, 1 Dec 2004 10:15:49 -0800 From: Steve Kargl To: "Ketrien I. Saihr-Kenchedra" Message-ID: <20041201181549.GA6236@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> <20041201084537.GA1621@dragon.nuxi.com> <20041201042900.A88450@bahre.achedra.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201042900.A88450@bahre.achedra.org> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:15:51 -0000 On Wed, Dec 01, 2004 at 04:47:51AM -0500, Ketrien I. Saihr-Kenchedra wrote: > On Wed, 1 Dec 2004, David O'Brien wrote: > > >There is no 'ccNUMA' setting in the BIOS. A multi-processor Opteron is a > >NUMA architecture machine regardless of any BIOS settings. I.E. there is > >no way to disable that a MP Opteron is a NUMA machine. > >The setting of interest is should the BIOS round-robin interleave > >physical addresses across the NUMA nodes[*]. The reference AMI BIOS > >refers to this as "Node Interleaving". It should be "DISABLED". Or if > >the BIOS speaks of the SRAT table, it should be "ENABLED". While FreeBSD > >doesn't use the SRAT table (and cannot until ACPI 3.0 BIOS's); turning on > >the SRAT turns off node interleaving. > > David, trying very hard to be nice, the S2882's a 'Special Case.' > Where special should be taken as 'short bus.' VERY short bus. > > On the S2882/S2885, and even the S4882, the BIOS specifically says, and I > quote: 'ccNUMA Support.' No joke. The beauty is that ccNUMA is, you got > it, SRAT Table Control, which _disables_ interleave completely. Beautiful, > huh? My BIOS does not have "ccNUMA Support" anywhere. During POST I see AMIBIOS 2003(c), American Megatrends, Inc. BIOS Date: 07/07/04 11:11:45 Ver 08.00.10 TYAN High-End Dual AMD Opteron BIOS v2.03 -- Steve From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 18:18:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFFEE16A4CE for ; Wed, 1 Dec 2004 18:18:36 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31B4143D1D for ; Wed, 1 Dec 2004 18:18:36 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CZZ3h-000AxS-S9; Wed, 01 Dec 2004 10:18:33 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16814.2809.359589.972762@ran.psg.com> Date: Wed, 1 Dec 2004 10:18:33 -0800 To: Doug White References: <20041123182254.GB10721@ninthgate.net> <16804.64917.872924.733444@ran.psg.com> <20041124232820.J2006@carver.gumbysoft.com> <16805.38319.825546.497936@ran.psg.com> <20041128220455.F40277@carver.gumbysoft.com> <16811.9333.99454.679978@ran.psg.com> <20041201101227.O68605@carver.gumbysoft.com> cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:18:36 -0000 >>>> # grep dump /etc/rc.conf >>>> dumpdev="/dev/twed0s1b" # Device name to crashdump to (or NO). >>>> dumpdir="/var/crash" # Directory where crash dumps are to be stored >>> Hm, this should be getting set; the twe driver supports crashdumps. What >>> happens if you run 'dumpon /dev/twed0s1b' manually? >> # dumpon /dev/twed0s1b >> # > I think we established before that you were setting the device name > bogusly elsewhere so we'll assume this is working now :) setting is working. but i did not get a crashdump last two crashes. >> i am using ssh. > Oh, they released an IOS image with ssh for those? I've been using > Cyclades TSx000 boxes for too long apparently... uh, for many years. but you have to invoke some incantations to get 3des etc. i have been doing it for so long that i have forgotton what you have to do to get in the door. of course, i also have oob access via craft ports. in fact, it is this path, ssh to the termserv which then goes local serial to craft, that is not easily loggable. randy From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 18:21:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3CDF16A4CE; Wed, 1 Dec 2004 18:21:04 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACFCA43D49; Wed, 1 Dec 2004 18:21:04 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB1IL3Ar006321; Wed, 1 Dec 2004 10:21:03 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB1IL30D006320; Wed, 1 Dec 2004 10:21:03 -0800 (PST) (envelope-from sgk) Date: Wed, 1 Dec 2004 10:21:03 -0800 From: Steve Kargl To: "David O'Brien" Message-ID: <20041201182103.GB6236@troutmask.apl.washington.edu> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> <20041201084537.GA1621@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201084537.GA1621@dragon.nuxi.com> User-Agent: Mutt/1.4.1i cc: "Ketrien I. Saihr-Kenchedra" cc: freebsd-current@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:21:05 -0000 On Wed, Dec 01, 2004 at 12:45:37AM -0800, David O'Brien wrote: > > The setting of interest is should the BIOS round-robin interleave > physical addresses across the NUMA nodes[*]. The reference AMI BIOS > refers to this as "Node Interleaving". It should be "DISABLED". Or if > the BIOS speaks of the SRAT table, it should be "ENABLED". While FreeBSD > doesn't use the SRAT table (and cannot until ACPI 3.0 BIOS's); turning on > the SRAT turns off node interleaving. Thanks for the reply. Unfortunately, setting "ACPI SRAT Support" to ENABLE and having "Node Interleaving" set to DISABLE does not help. I still get the panic if hw.physmem="16G". -- Steve From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 18:25:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33B4516A4CE for ; Wed, 1 Dec 2004 18:25:06 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4132843D3F for ; Wed, 1 Dec 2004 18:25:05 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iB1IOj24023597; Wed, 1 Dec 2004 19:24:48 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <41AE0C62.7090208@DeepCore.dk> Date: Wed, 01 Dec 2004 19:24:34 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Michael W. Lucas" References: <3BE1BF5E-4249-11D9-9F7A-000A95A9A574@nordahl.net> <20041201153946.GA16872@bewilderbeast.blackhelicopters.org> In-Reply-To: <20041201153946.GA16872@bewilderbeast.blackhelicopters.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org cc: 'Frode Nordahl' cc: Daniel Eriksson Subject: Re: Got rid of my SiI3112A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:25:06 -0000 Michael W. Lucas wrote: > On Mon, Nov 29, 2004 at 10:40:41PM +0100, Daniel Eriksson wrote: >=20 >>Frode Nordahl wrote: >> >> >>>But as things are today, I think it would be best to remove=20 >>>support for=20 >>>SiI3112A. Especially since the general attitude towards it is=20 >>>"it's too=20 >>>broke, we don't want to waste any more time on it". >>> >>>Attempting to use it in a 5.3-RELEASE or 6-CURRENT system will most=20 >>>likelly make your system crash and burn, and make your data=20 >>>unrecoverable beyond repair. >> >>I will have to agree with Frode on this one. I recently put -CURRENT on= a >>machine with an ASUS mobo that had a SiL 3112 controller. Hooking up tw= o >>250GB WD discs to it quickly resulted in timeouts, followed by some str= ange >>messages from geom_stripe (used it to stripe the two discs), followed b= y >>filesystem corruption and panics. >=20 >=20 > Does anyone know if Soren has one of these controllers? >=20 > Getting him a poorly-supported controller is the first step towards > getting it fixed. I do have a couble of them actually, both the first revision thats=20 *real* bad, and the second which is a hair better... Needless to say they both work in all my notherboards and with all my=20 SATA disks, alas with the expect occasional timeout and retry... However, I dont have any real crappy HW around, I dont/wont waste my=20 money on that, so that might explain why :) --=20 -S=F8ren From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 18:28:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA4B516A4CE for ; Wed, 1 Dec 2004 18:28:42 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 053EC43D1F for ; Wed, 1 Dec 2004 18:28:42 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iB1ISU7V023665; Wed, 1 Dec 2004 19:28:32 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <41AE0D42.6070503@DeepCore.dk> Date: Wed, 01 Dec 2004 19:28:18 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Erik Trulsson References: <3BE1BF5E-4249-11D9-9F7A-000A95A9A574@nordahl.net> <20041201153946.GA16872@bewilderbeast.blackhelicopters.org> <20041201164134.GA58263@falcon.midgard.homeip.net> In-Reply-To: <20041201164134.GA58263@falcon.midgard.homeip.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org cc: 'Frode Nordahl' cc: Daniel Eriksson Subject: Re: Got rid of my SiI3112A X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:28:42 -0000 Erik Trulsson wrote: > On Wed, Dec 01, 2004 at 10:39:46AM -0500, Michael W. Lucas wrote: >=20 >>On Mon, Nov 29, 2004 at 10:40:41PM +0100, Daniel Eriksson wrote: >> >>>Frode Nordahl wrote: >>> >>> >>>>But as things are today, I think it would be best to remove=20 >>>>support for=20 >>>>SiI3112A. Especially since the general attitude towards it is=20 >>>>"it's too=20 >>>>broke, we don't want to waste any more time on it". >>>> >>>>Attempting to use it in a 5.3-RELEASE or 6-CURRENT system will most=20 >>>>likelly make your system crash and burn, and make your data=20 >>>>unrecoverable beyond repair. >>> >>>I will have to agree with Frode on this one. I recently put -CURRENT o= n a >>>machine with an ASUS mobo that had a SiL 3112 controller. Hooking up t= wo >>>250GB WD discs to it quickly resulted in timeouts, followed by some st= range >>>messages from geom_stripe (used it to stripe the two discs), followed = by >>>filesystem corruption and panics. >> >>Does anyone know if Soren has one of these controllers? >> >>Getting him a poorly-supported controller is the first step towards >>getting it fixed. >=20 >=20 > He probably has one. Otherwise I don't think he would write > commit-messages like this one for sys/dev/ata/ata-chipset.c: > ---- > revision 1.50 > date: 2003/12/08 09:22:20; author: sos; state: Exp; lines: +3 -1 > More errata fixing for the SiI3112A disaster chip: >=20 > Serialize access to the SATA channels, the chip messes up if > both channels are used at the same time. >=20 > The SiI3112 hereby takes the price as the most crappy SATA chip in > existance by a significant amount. >=20 > My advise to our userbase is to avoid this chip like the plague... > ---- >=20 >=20 > I take it that it is not so much a matter of this controller being > poorly supported, as of this being a poor controller. BINGO!! --=20 -S=F8ren From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 18:38:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28DE916A4CE; Wed, 1 Dec 2004 18:38:04 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B22EC43D55; Wed, 1 Dec 2004 18:38:03 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB1Ic0K3051028; Wed, 1 Dec 2004 10:38:00 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB1Ibxtn051027; Wed, 1 Dec 2004 10:37:59 -0800 (PST) (envelope-from obrien) Date: Wed, 1 Dec 2004 10:37:59 -0800 From: "David O'Brien" To: "Ketrien I. Saihr-Kenchedra" Message-ID: <20041201183759.GB48294@dragon.nuxi.com> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <41AC6FF8.40501@freebsd.org> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041130142652.A59122@bahre.achedra.org> <20041201084537.GA1621@dragon.nuxi.com> <20041201042900.A88450@bahre.achedra.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201042900.A88450@bahre.achedra.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org cc: Steve Kargl cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:38:04 -0000 On Wed, Dec 01, 2004 at 04:47:51AM -0500, Ketrien I. Saihr-Kenchedra wrote: > On Wed, 1 Dec 2004, David O'Brien wrote: > > >There is no 'ccNUMA' setting in the BIOS. A multi-processor Opteron is a > >NUMA architecture machine regardless of any BIOS settings. I.E. there is > >no way to disable that a MP Opteron is a NUMA machine. > >The setting of interest is should the BIOS round-robin interleave > >physical addresses across the NUMA nodes[*]. The reference AMI BIOS > >refers to this as "Node Interleaving". It should be "DISABLED". Or if > >the BIOS speaks of the SRAT table, it should be "ENABLED". While FreeBSD > >doesn't use the SRAT table (and cannot until ACPI 3.0 BIOS's); turning on > >the SRAT turns off node interleaving. > > David, trying very hard to be nice, the S2882's a 'Special Case.' > Where special should be taken as 'short bus.' VERY short bus. > > On the S2882/S2885, and even the S4882, the BIOS specifically says, and I > quote: 'ccNUMA Support.' No joke. The beauty is that ccNUMA is, you got > it, SRAT Table Control, which _disables_ interleave completely. Beautiful, > huh? The only way to enable interleave on the S2882/S2885 is to > specifically turn 'ccNUMA' off; otherwise it's SRAT only, with no > interleave. I've seen S2882 BIOS's that don't say "ccNUMA" and my S2885 K8W Thunder certainly doesn't. It's BIOS knobs and explanation are: Interleaving allows memory accesses to be spread out over BANKS on the same node, or across NODES, decreasing access contention. o "Bank Interleaving" o "Node Interleaving" On every Operon BIOS (AMI or Phoenix), the SRAT enabling and Node Interleaving are related -- they are mutually exclusive by design as Node Interleaving lets the BIOS setup the physical memory topology vs. enabling the SRAT which then puts it in the OS's court. Enabling the SRAT doesn't need to and shouldn't disable Bank Interleaving. > And no, it's not mentioned anywhere on the S2882s. Nor in the AMI reference BIOS :-(, which is a shame as more information might better clear things up. > Only on > the S4882, which uses a Phoenix 6.0 reference. (Which Tyan, predictably, > did not remove the reference lines _or_ fix the typos on.) The S2882s > also use a Phoenix, I believe. So in order to enable Interleave, your > only method is that switch. Actually the S2882 uses a AMI BIOS, as does all of Tyan's 2P Opteron boards, except the S2885 variant Tyan makes for the Fujitsu Celsius V810. I like the Fujitsu Celsius V810 Phoenix better, wished it was used on all S2885's. > What got me peering curiously here is the placement of the hole; there > appears to be a 512MB hole, starting at 4024MB. It certainly is similar > to the behavior of 2882 I've looked at; hole is about 1/3rd through > memory. On the 2.03 BIOS, still no way to control the PCI hole; that > feature is reserved for the S4882 apparently, and even then only size. How do you want to control the "memory hole"? It is mandatory in order to map in memory mapped I/O devices. > If the hole _is_ at 4024MB, that would put it past 4096MB and the 4GB > limit; on the S2882 the bulk of the peripherals are on the PCI32 bus, not > a PCI64 bus. Specifically, disk, fxp(4), bge(4), ACPI, and USB. > Presuming I am reading the hole correctly, and bearing in mind that I do > not have access to my copy of the PCI2.3 spec, ISTR that the entirety of > the PCI memory hole must be within the first 4GB of system memory. (I'd > appreciate it if someone could sanity check that.) Correct, the "memory hole" must be below the 4GB mark. http://www.amd.com/us-en/assets/content_type/DownloadableAssets/RichBrunnerClusterWorldpresFINAL.pdf slide 25 is AMD's picture for this. The "hole" is of course an area where memory mapped PCI I/O, APIC, APG GART, etc.. are mapped into the memory address space. Thus RAM cannot be addressed using (mapped into) those memory locations. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 19:15:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E960816A4D1; Wed, 1 Dec 2004 19:15:38 +0000 (GMT) Received: from lakermmtao08.cox.net (lakermmtao08.cox.net [68.230.240.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5650543D53; Wed, 1 Dec 2004 19:15:38 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by lakermmtao08.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041201191530.CGUB28664.lakermmtao08.cox.net@mezz.mezzweb.com>; Wed, 1 Dec 2004 14:15:30 -0500 To: pav@freebsd.org References: <20040923032045.GA52428@crodrigues.org> <20041201.143909.971160851.chat95@mac.com> <20041201063204.GA6754@crodrigues.org> <1101892801.51033.6.camel@pav.hide.vol.cz> Message-ID: Date: Wed, 01 Dec 2004 13:16:06 -0600 From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <1101892801.51033.6.camel@pav.hide.vol.cz> User-Agent: Opera M2/7.54 (Linux, build 751) cc: Craig Rodrigues cc: freebsd-current@freebsd.org Subject: Re: REPORT_KEY ILLEGAL REQUEST: encrypted DVD's under FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 19:15:39 -0000 On Wed, 01 Dec 2004 10:20:01 +0100, Pav Lucistnik wrote: > Craig Rodrigues píše v st 01. 12. 2004 v 01:32 -0500: >> On Wed, Dec 01, 2004 at 02:39:09PM +0900, NAKATA Maho wrote: >> > In Message-ID: <20040923032045.GA52428@crodrigues.org> >> > > acd0: FAILURE - REPORT_KEY ILLEGAL REQUEST asc=0x6f ascq=0x04 >> error=4 >> > > >> > > This is my brand of DVD player: >> > > acd0: CDRW drive at ata0 as slave >> > >> > I also encountered the exact problem. >> > acd0: DVDR at ata1-master UDMA33 >> >> Hi, >> >> Garrett Wollman explained this quite nicely to me. >> In the MMC-3 standard (SCSI) at T10.org, there is a >> standard section on sense codes: >> >> 6F/04 R MEDIA REGION CODE IS MISMATCHED TO LOGICAL UNIT >> REGION >> >> When you get a new DVD player, the DVD-ROM will adopt the region >> code of the first DVD that it plays. If you want to change >> the region code on your DVD drive, you typically need to download >> proprietary utilities or firmware for your DVD drive. >> Most DVD drives only allow you to change the region code 5 times. >> >> I haven't figured out how to change the firmware on my LITE-ON >> drive, because LITE-ON only supplies Windows utilities, and my >> machine is FreeBSD only. > > I had good results with FreeDOS bootup from CD-ROM, then swapping CDs > for a second one with DOS based Mediatek flashing utility and firmware > image. I could whip up a page with downloads and instructions, but it's > all easily googlabe. Look for bootdisk.iso, MTKFLASH.EXE and BIN > firmwares (unofficial). I am planning to create a WinXP livecd with include LtnFlash to disable the RPC (from RPC 2 to RPC 1). Or, I can unhook DVD and put on other machine to do the task with LtnFlash. Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 19:29:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99FF016A4CE; Wed, 1 Dec 2004 19:29:49 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0102A43D1D; Wed, 1 Dec 2004 19:29:49 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id iB1JU6UY092853; Wed, 1 Dec 2004 14:30:06 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Wed, 1 Dec 2004 14:30:06 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: "David O'Brien" In-Reply-To: <20041201183759.GB48294@dragon.nuxi.com> Message-ID: <20041201141150.I88450@bahre.achedra.org> References: <20041129211341.GA26548@troutmask.apl.washington.edu> <20041130183555.GA32237@troutmask.apl.washington.edu> <20041201084537.GA1621@dragon.nuxi.com> <20041201183759.GB48294@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/609/Fri Nov 26 15:20:39 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-current@freebsd.org cc: Steve Kargl cc: freebsd-amd64@freebsd.org Subject: Re: kernel panic with greater that 8 GB of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 19:29:49 -0000 On Wed, 1 Dec 2004, David O'Brien wrote: > I've seen S2882 BIOS's that don't say "ccNUMA" and my S2885 K8W Thunder > certainly doesn't. It's BIOS knobs and explanation are: > Interleaving allows memory accesses to be spread out over BANKS on the > same node, or across NODES, decreasing access contention. > o "Bank Interleaving" > o "Node Interleaving" > On every Operon BIOS (AMI or Phoenix), the SRAT enabling and Node > Interleaving are related -- they are mutually exclusive by design as Node > Interleaving lets the BIOS setup the physical memory topology vs. > enabling the SRAT which then puts it in the OS's court. > Enabling the SRAT doesn't need to and shouldn't disable Bank > Interleaving. Yes, I do indeed stand corrected. Writing emails late at night while tired is something I should probably cut down on. The S2882 I see most often is _not_ a 2.03 BIOS; the 2.03 BIOS refused to even POST with our RAID controller. (Predictably, Tyan's response was 'don't run that BIOS then.') Unfortunately, the S4882 hell is still quite fresh in my mind; the Phoenix 6.0 Ref on those is mutual exclusive. No joke; if SRAT is enabled, actual Bank Interleave is disabled. (The BIOS seems to consider Node/Bank as equal. Not like the S4882 doesn't have enough quirks anyways. :P) Coupled with the 'DDR 400MHz Memmory Detected' line, you can probably guess my opinion of Tyan's BIOS guys at this point. > Nor in the AMI reference BIOS :-(, which is a shame as more information > might better clear things up. Indeed; also better note-taking on my part, but those are on a dead machine right now. ;( > Actually the S2882 uses a AMI BIOS, as does all of Tyan's 2P Opteron > boards, except the S2885 variant Tyan makes for the Fujitsu Celsius V810. > I like the Fujitsu Celsius V810 Phoenix better, wished it was used on all > S2885's. Yeah, I thought they might have used Phoenix because I haven't seen the S2882 rebooted in a good long time. I'd take _anything_ over Tyan's BIOS; it has been nothing but trouble in various ways since day one. > How do you want to control the "memory hole"? It is mandatory in order > to map in memory mapped I/O devices. On the S4882, you have limited control over the PCI Memory Hole. You can set it to Auto, or to a specific size. Auto will size it based on enabled devices in the bios, setting it to a specific value will create a hole of that size. One of those way-too-fine-tuning things. > Correct, the "memory hole" must be below the 4GB mark. > http://www.amd.com/us-en/assets/content_type/DownloadableAssets/RichBrunnerClusterWorldpresFINAL.pdf > slide 25 is AMD's picture for this. The "hole" is of course an area > where memory mapped PCI I/O, APIC, APG GART, etc.. are mapped into the > memory address space. Thus RAM cannot be addressed using (mapped into) > those memory locations. Making me wish I had a way to view PDFs right now. Looking at the presented memory regions: Physical memory chuck(s): 0x0000000000001000 - 0000000000009bfff, 634880 bytes (155 pages) 0x000000000082d000 - 000000000fbfeffff, 4219219968 bytes (1030083 pages) 0x0000000100000000 - 000000003e1fcffff, 12381388800 bytes (3022800 pages) 1000-9bfff is the 640K region. Then a significant gap between 640K and the 4023MB region. Followed by another large gap between the 4023MB region and the 11807MB region. My hex conversion with numbers that large, frankly, sucks, but it looks to me as though the PCI hole is 512MB (e.g.; all onboard devices enabled,) and starting at 4024MB. Which would put the PCI Memory Hole past the 4GB limit. Only explanation for behavior like that, that I can think of, is yet another BIOS bug. -Ketrien I. Saihr-Kenchedra "And I'm going back to bed." From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 19:52:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C59816A4CE for ; Wed, 1 Dec 2004 19:52:32 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 8327B43D46 for ; Wed, 1 Dec 2004 19:52:31 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 58382 invoked from network); 1 Dec 2004 19:52:29 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 1 Dec 2004 19:52:29 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB1JqSBl079673; Wed, 1 Dec 2004 20:52:28 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB1JqS3X079672; Wed, 1 Dec 2004 20:52:28 +0100 (CET) (envelope-from pho) Date: Wed, 1 Dec 2004 20:52:28 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041201195228.GA79652@peter.osted.lan> References: <20041201055115.I18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201055115.I18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 19:52:32 -0000 On Wed, Dec 01, 2004 at 05:54:49AM -0500, Jeff Roberson wrote: > I have updated the patch at: > > http://www.chesapeake.net/~jroberson/smpffs.diff > I got a page fault in kern/vfs_vnops.c:542 due to vp->v_mount == NULL. More info at http://www.holm.cc/stress/log/jeff03.html - Peter > It includes bug fixes for a handful of problems that were reported, and a > few more that I found myself. It also unwinds giant from open(), which is > a very high risk area, but after a few days of working out bugs it seems > to be functioning quite well for me. > > I did a make -j3 buildworld on a box with a lowered maxvnodes. I also let > 'stress' run for 8 loops or so until I ran into an unrelated KSE bug. I > did some mount/unmount/single user tests as well. > > Use at your own risk. I still haven't locked quotas, so if you're using > quota, don't run with this patch. > > Thanks, > Jeff > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 20:14:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C781E16A4CE; Wed, 1 Dec 2004 20:14:34 +0000 (GMT) Received: from lon-mail-3.gradwell.net (lon-mail-3.gradwell.net [193.111.201.127]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAF0543D4C; Wed, 1 Dec 2004 20:14:33 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from cpc3-oxfd4-4-0-cust42.oxfd.cable.ntl.com ([80.3.247.42] helo=mail.cbhnet) 1.156) id 41ae2628.d622.17; Wed, 1 Dec 2004 20:14:32 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.cbhnet (Postfix) with ESMTP id 0A54631B01C; Wed, 1 Dec 2004 20:14:32 +0000 (GMT) Received: from mail.cbhnet ([127.0.0.1]) by localhost (mail.cbhnet [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01026-01; Wed, 1 Dec 2004 20:14:31 +0000 (GMT) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.cbhnet (Postfix) with ESMTP id AB66631AFF5; Wed, 1 Dec 2004 20:14:31 +0000 (GMT) Date: Wed, 1 Dec 2004 20:14:31 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: Marcel Moolenaar In-Reply-To: <20041130201522.GA92745@ns1.xcllnt.net> Message-ID: <20040101195442.Q911@teapot.cbhnet> References: <20041127193532.X15946@teapot.cbhnet> <20041129133825.GL7232@darkness.comp.waw.pl> <20041130153044.E20313@teapot.cbhnet> <20041130201522.GA92745@ns1.xcllnt.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at chrishedley.com cc: freebsd-current@freebsd.org cc: Pawel Jakub Dawidek Subject: Re: GEOM: gpt partitions on a gmirror array possible? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 20:14:34 -0000 On Tue, 30 Nov 2004, Marcel Moolenaar wrote: > On Tue, Nov 30, 2004 at 03:37:52PM +0000, Chris Hedley wrote: >>> >>> I guess a change like geom_mbr.c:1.57 is in order, or a more to-the- >>> point test for rejecting GPT on MBR or GPT on GPT. >> >> Any suggestions before I start butchering the file in question? > > Removal of the following should do it without causing problems: > > if (gp->rank != 2 && insist == 0) > break; ... I made the change to geom/geom_gpt.c and that seems to have done the trick - thanks! I'm really impressed with the help you've given me so quickly. Cheers, Chris. From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 20:28:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5610216A4CE; Wed, 1 Dec 2004 20:28:41 +0000 (GMT) Received: from mail.animecowboy.com (cdm-208-180-231-109.bcst.cox-internet.com [208.180.231.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DB0C43D39; Wed, 1 Dec 2004 20:28:40 +0000 (GMT) (envelope-from animecowboy@animecowboy.com) Received: from localhost ([]) by mail.animecowboy.com (Merak 7.1.6) with ESMTP id ABA37675; Wed, 01 Dec 2004 14:28:42 -0600 Received: from toran.animecowboy.com (toran.animecowboy.com [10.0.0.15]) by www.animecowboy.com (IMP) with HTTP for ; Wed, 1 Dec 2004 14:28:37 -0600 Message-ID: <1101932917.41ae2975cbb94@www.animecowboy.com> Date: Wed, 1 Dec 2004 14:28:37 -0600 From: animecowboy@animecowboy.com To: Harti Brandt References: <1101874345.41ad44a92983e@www.animecowboy.com> <20041201091330.F655@beagle.kn.op.dlr.de> In-Reply-To: <20041201091330.F655@beagle.kn.op.dlr.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 10.0.0.15 cc: current Subject: Re: smbfs and setuid in 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 20:28:41 -0000 > Try to use the -u and -g switches to mount_smbfs to specify the user > that should access the mounted file system. > > harti > The base directory was already set to the user/group I wanted, makeing the defaults to -u -g what I wanted. So as an experiement I set the base dir to root:wheel, and used the -u -g attribs. The results were the same as before. Checking with ls -l(as root) shows the base and the files mounted to the correct user(spamassassin in this case) all with 700. suing to spamassasin and attempting to list the directory gives me .: Permission denied. unmounting, setting base dir permissions to 750(or 770) remounting, suing to spamassasin, ls gives me the contents of the remote mount. Thank you, -Brian From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 20:41:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3487016A4CE for ; Wed, 1 Dec 2004 20:41:18 +0000 (GMT) Received: from 9.hellooperator.net (cpc3-cdif2-3-0-cust202.cdif.cable.ntl.com [81.103.32.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id E90F443D45 for ; Wed, 1 Dec 2004 20:41:17 +0000 (GMT) (envelope-from rasputin@hellooperator.net) Received: from rasputin by 9.hellooperator.net with local (Exim 4.43) id 1CZbHo-00045V-LZ; Wed, 01 Dec 2004 20:41:16 +0000 Date: Wed, 1 Dec 2004 20:41:16 +0000 From: Dick Davies To: Alexey Koptsevich Message-ID: <20041201204116.GN11067@lb.tenfour> References: <20041125181408.GW12945@lb.tenfour> <20041201212407.C82068@astro.ioffe.rssi.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201212407.C82068@astro.ioffe.rssi.ru> User-Agent: Mutt/1.4.2.1i Sender: Dick Davies cc: FreeBSD Current Users Subject: Re: ata1-slave: FAILURE - ATAPI_IDENTIFY timed out - fixed yet? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dick Davies List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 20:41:18 -0000 * Alexey Koptsevich [1225 18:25]: > > Dick, > > Saw your question in the maillist -- have you got it resolved? > It happens to me during installation. [ccing to current for the record] Yes, it's sorted now - I removed the drive, upgraded to the latest RELENG_5 and I now get *3* of the warning messages, and then it boots fine... -- Yeah, well I'm gonna build my own themepark! With blackjack aaand Hookers! Actually, forget the park. And the blackjack. - Bender Rasputin :: Jack of All Trades - Master of Nuns From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 21:11:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB2DD16A4CE for ; Wed, 1 Dec 2004 21:11:58 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D56343D4C for ; Wed, 1 Dec 2004 21:11:58 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iB1LBr0N012183; Wed, 1 Dec 2004 16:11:54 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iB1LBqmN012164; Wed, 1 Dec 2004 16:11:52 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Wed, 1 Dec 2004 16:11:50 -0500 (EST) From: Jeff Roberson To: Peter Holm In-Reply-To: <20041201195228.GA79652@peter.osted.lan> Message-ID: <20041201160351.V18185@mail.chesapeake.net> References: <20041201055115.I18185@mail.chesapeake.net> <20041201195228.GA79652@peter.osted.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 21:11:59 -0000 On Wed, 1 Dec 2004, Peter Holm wrote: > On Wed, Dec 01, 2004 at 05:54:49AM -0500, Jeff Roberson wrote: > > I have updated the patch at: > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > I got a page fault in kern/vfs_vnops.c:542 due to vp->v_mount == NULL. > > More info at http://www.holm.cc/stress/log/jeff03.html The v_mount should only be NULL very briefly for the rootdevvp. What is your setup here? Any filesystems other than devfs and ffs? I think that deadfs might not set a mountpoint either.. DId you do a forced unmount? I think I know how I'm going to have to fix this. > > - Peter > > > It includes bug fixes for a handful of problems that were reported, and a > > few more that I found myself. It also unwinds giant from open(), which is > > a very high risk area, but after a few days of working out bugs it seems > > to be functioning quite well for me. > > > > I did a make -j3 buildworld on a box with a lowered maxvnodes. I also let > > 'stress' run for 8 loops or so until I ran into an unrelated KSE bug. I > > did some mount/unmount/single user tests as well. > > > > Use at your own risk. I still haven't locked quotas, so if you're using > > quota, don't run with this patch. > > > > Thanks, > > Jeff > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- > Peter Holm > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 21:24:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 544B116A4CE for ; Wed, 1 Dec 2004 21:24:03 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2408243D1F for ; Wed, 1 Dec 2004 21:24:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C5DB2512C6; Wed, 1 Dec 2004 13:29:24 -0800 (PST) Date: Wed, 1 Dec 2004 13:29:24 -0800 From: Kris Kennaway To: Jeff Roberson Message-ID: <20041201212924.GA3193@xor.obsecurity.org> References: <20041201055115.I18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt" Content-Disposition: inline In-Reply-To: <20041201055115.I18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 21:24:03 -0000 --pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 01, 2004 at 05:54:49AM -0500, Jeff Roberson wrote: > I have updated the patch at: >=20 > http://www.chesapeake.net/~jroberson/smpffs.diff >=20 > It includes bug fixes for a handful of problems that were reported, and a > few more that I found myself. It also unwinds giant from open(), which is > a very high risk area, but after a few days of working out bugs it seems > to be functioning quite well for me. >=20 > I did a make -j3 buildworld on a box with a lowered maxvnodes. I also let > 'stress' run for 8 loops or so until I ran into an unrelated KSE bug. I > did some mount/unmount/single user tests as well. >=20 > Use at your own risk. I still haven't locked quotas, so if you're using > quota, don't run with this patch. Trying to mount root from nfs: setrootbyname failed panic: mutex Giant not owned at /a/portbuild/i386/src-client/sys/nfsclient/= nfs_vfsops.c:397 KDB: enter: panic [thread pid 1 tid 100003 ] Stopped at kdb_enter+0x32: leal 0(%esi),%esi db> tr Tracing pid 1 tid 100003 td 0xc195e480 kdb_enter(c0716a84,c0778ce0,c0715dfe,d40da9f4,c195e480) at kdb_enter+0x32 panic(c0715dfe,c0716043,c072681a,18d,c1a9e800) at panic+0x14d _mtx_assert(c0777840,1,c072681a,18d,0) at _mtx_assert+0x117 nfs_mountroot(c1a9e800,c195e480,a,d40dac08,d40dab20) at nfs_mountroot+0x3b nfs_omount(c1a9e800,c1b64280,0,c195e480,0) at nfs_omount+0x2a vfs_mountroot_try(c071f372,c0712f2b,205,4b0,c0712f2b) at vfs_mountroot_try+= 0x163 vfs_mountroot(c0777840,1,c0712f2b,207,89097500) at vfs_mountroot+0x134 start_init(0,d40dad48,c07140d7,318,45af0f10) at start_init+0x73 fork_exit(c04f87f0,0,d40dad48) at fork_exit+0xa9 fork_trampoline() at fork_trampoline+0x8 Kris --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBrje0Wry0BWjoQKURAnClAKCLKD5874FI7QwoJspm5D+JDzbETgCeJk0N E0RVimH+Xn9x/qQoYpwqLtc= =vAgN -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 21:48:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3A9216A4CE; Wed, 1 Dec 2004 21:48:19 +0000 (GMT) Received: from mail.evip.pl (mail.evip.com.pl [212.244.157.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id C157743D1D; Wed, 1 Dec 2004 21:48:18 +0000 (GMT) (envelope-from w@evip.pl) Received: from drwebc by mail.evip.pl with drweb-scanned (Exim 4.22) id 1CZcKY-000Cmv-Kv; Wed, 01 Dec 2004 22:48:10 +0100 Received: from w by mail.evip.pl with local (Exim 4.22) id 1CZcKY-000Cmp-HT; Wed, 01 Dec 2004 22:48:10 +0100 Date: Wed, 1 Dec 2004 22:48:10 +0100 From: Wiktor Niesiobedzki To: animecowboy@animecowboy.com Message-ID: <20041201214810.GM63554@mail.evip.pl> References: <1101874345.41ad44a92983e@www.animecowboy.com> <20041201091330.F655@beagle.kn.op.dlr.de> <1101932917.41ae2975cbb94@www.animecowboy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1101932917.41ae2975cbb94@www.animecowboy.com> User-Agent: Mutt/1.5.6i cc: Harti Brandt cc: current Subject: Re: smbfs and setuid in 5.3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 21:48:19 -0000 On Wed, Dec 01, 2004 at 02:28:37PM -0600, animecowboy@animecowboy.com wrote: > > Try to use the -u and -g switches to mount_smbfs to specify the user > > that should access the mounted file system. > > > > harti > > > > The base directory was already set to the user/group I wanted, makeing the > defaults to -u -g what I wanted. So as an experiement I set the base dir to > root:wheel, and used the -u -g attribs. > I can easily reproduce that: Amnesiac# mkdir /testmount Amnesiac# chown w /testmount Amnesiac# chmod 700 /testmount Amnesiac# mount_smbfs //w@portal/share /testmount Password: Amnesiac# ls /testmount .snap bea oracle Amnesiac# ls /testmount/.snap Amnesiac# su - w w@Amnesiac:~$ ls /testmount ls: testmount: Permission denied w@Amnesiac:~$ I think that smbfs is the only FS that does not change the mountpoint access mode, what may I expose a more global problem. But quickly scanning the sourcecode, I still cannot find the source of the problem. And one question arising: w@Amnesiac:~$ kdump| grep -c NAMI 11 w@Amnesiac:~$ ktrace -t n ls /testmount >/dev/null 2>/dev/null w@Amnesiac:~$ kdump| grep -c NAMI 18 Where from this change of calls to NAMI stems? The second output has follwing lines more (at the end of execution): 1750 ls NAMI "/etc/malloc.conf" 1750 ls NAMI "/testmount" 1750 ls NAMI "." 1750 ls NAMI "/testmount" 1750 ls NAMI "/testmount" 1750 ls NAMI "/testmount" 1750 ls NAMI "/testmount" Cheers, Wiktor Niesiobedzki From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 22:02:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9076116A4CE; Wed, 1 Dec 2004 22:02:28 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3BF143D3F; Wed, 1 Dec 2004 22:02:27 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB1M67lv063104; Wed, 1 Dec 2004 15:06:07 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AE3F80.1000506@freebsd.org> Date: Wed, 01 Dec 2004 15:02:40 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "current@freebsd.org" X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=TO_ADDRESS_EQ_REAL autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: hackers@freebsd.org Subject: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 22:02:28 -0000 All, I know that I said last month that we were going to stop promising specific features for the next major release. However, I'd like to throw out a list of things that would be really nice to have in the future, whether its 6.0 or 7.0 or whatever. Most of these tasks are not trivial, but I hope that talking about them will encourage some interest. These are in no particular priority order. I'd also be thrilled if someone wanted to dress this list up in docbook and add it to the webpage. While this is just my personal list, I'd welcome other additions to it (in the sense of significant projects, not just individual PRs or bug fixes that one might be interested in). 1. Keyboard multiplexer. We are running into problems with making ps/2 and USB/bluetooth keyboards work together and work with KVMs. Having a virtual keyboard device that multiplexes the various real keyboard devices and handles hotplug can solve this mess pretty effectively. I know that there has been a lot of talk about this on mailing lists recently but I don't know how much progress is being made so I'm listing it here. 2. New installer. I know some people still consider this a joke, but the reality is that sysinstall is no longer state of the art. It's fairly good at the simple task that it does, but it's becoming harder and harder to fix bugs and extend functionality in it. It's also fairly unfriendly to those of us who haven't been using it since 1995. The DFly folks have some very interesting work in this area (www.bsdinstaller.com) and it would be very good to see if we can collaborate with them on it. 3. Native PCI Express support. I keep on hoping to take care of this, but I never seem to have the time to get past designing it. This task includes 3 parts that are mostly independent. The first is support for the extended PCI config space and memio access method, the second is MSI, and the third is link QOS management. If anyone is interested here, please let me know. 4. Journaled filesystem. While we can debate the merits of speed and data integrety of journalling vs. softupdates, the simple fact remains that softupdates still requires a fsck run on recovery, and the multi-terabyte filesystems that are possible these days make fsck a very long and unpleasant experience, even with bg-fsck. There was work at some point at RPI to add journaling to UFS, but there hasn't been much status on that in a long time. There have also been proposals and works-in-progress to port JFS, ReiserFS, and XFS. Some of these efforts are still alive, but they need to be seen through to completion. But at the risk of opening a can of worms here, I'll say that it's also important to explore non-GPL alternatives. 5. Clustered FS support. SANs are all the rage these days, and clustered filesystems that allow data to be distributed across many storage enpoints and accessed concurrently through the SAN are very powerful. RedHat recently bought Sistina and re-opened the GFS source code, so exploring this would be very interesting. 6. Overhaul CAM, add iSCSI. CAM is very parallel-SCSI centric right now. I have some work-in-progress in Perforce to address this, but it's pretty minimal. The parallel SCSI knowledge needs to be separated out and the stack need to be able to cleanly deal with iSCSI, SCSI, SAS, and maybe even ATA transports. There is a Lucent implementation of iSCSI for FreeBSD 4.x that could be a useful reference, though it's a monolithic stack that doesn't really address the shortcomings of CAM. Having iSCSI infrastructure that supported both hardware and software implementations would be ideal. From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 22:14:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C95A516A4CF for ; Wed, 1 Dec 2004 22:14:44 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF19743D58 for ; Wed, 1 Dec 2004 22:14:43 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 21817 invoked from network); 1 Dec 2004 22:05:52 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 1 Dec 2004 22:05:52 -0000 Message-ID: <41AE424F.1010707@freebsd.org> Date: Wed, 01 Dec 2004 23:14:39 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <41AE3F80.1000506@freebsd.org> In-Reply-To: <41AE3F80.1000506@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 22:14:45 -0000 Scott Long wrote: > All, > > I know that I said last month that we were going to stop promising > specific features for the next major release. However, I'd like to > throw out a list of things that would be really nice to have in the > future, whether its 6.0 or 7.0 or whatever. Most of these tasks are > not trivial, but I hope that talking about them will encourage some > interest. These are in no particular priority order. I'd also be > thrilled if someone wanted to dress this list up in docbook and add > it to the webpage. While this is just my personal list, I'd welcome > other additions to it (in the sense of significant projects, not just > individual PRs or bug fixes that one might be interested in). > > 1. Keyboard multiplexer. We are running into problems with making > ps/2 and USB/bluetooth keyboards work together and work with KVMs. > Having a virtual keyboard device that multiplexes the various real > keyboard devices and handles hotplug can solve this mess pretty > effectively. I know that there has been a lot of talk about this on > mailing lists recently but I don't know how much progress is being made > so I'm listing it here. > > 2. New installer. I know some people still consider this a joke, but > the reality is that sysinstall is no longer state of the art. It's > fairly good at the simple task that it does, but it's becoming harder > and harder to fix bugs and extend functionality in it. It's also > fairly unfriendly to those of us who haven't been using it since 1995. > The DFly folks have some very interesting work in this area > (www.bsdinstaller.com) and it would be very good to see if we can > collaborate with them on it. > > 3. Native PCI Express support. I keep on hoping to take care of this, > but I never seem to have the time to get past designing it. This task > includes 3 parts that are mostly independent. The first is support for > the extended PCI config space and memio access method, the second is > MSI, and the third is link QOS management. If anyone is interested > here, please let me know. > > 4. Journaled filesystem. While we can debate the merits of speed and > data integrety of journalling vs. softupdates, the simple fact remains > that softupdates still requires a fsck run on recovery, and the > multi-terabyte filesystems that are possible these days make fsck a very > long and unpleasant experience, even with bg-fsck. There was work at > some point at RPI to add journaling to UFS, but there hasn't been much > status on that in a long time. There have also been proposals and > works-in-progress to port JFS, ReiserFS, and XFS. Some of these efforts > are still alive, but they need to be seen through to completion. But at > the risk of opening a can of worms here, I'll say that it's also > important to explore non-GPL alternatives. > > 5. Clustered FS support. SANs are all the rage these days, and > clustered filesystems that allow data to be distributed across many > storage enpoints and accessed concurrently through the SAN are very > powerful. RedHat recently bought Sistina and re-opened the GFS source > code, so exploring this would be very interesting. > > 6. Overhaul CAM, add iSCSI. CAM is very parallel-SCSI centric right > now. I have some work-in-progress in Perforce to address this, but it's > pretty minimal. The parallel SCSI knowledge needs to be separated out > and the stack need to be able to cleanly deal with iSCSI, SCSI, SAS, and > maybe even ATA transports. There is a Lucent implementation of iSCSI > for FreeBSD 4.x that could be a useful reference, though it's a > monolithic stack that doesn't really address the shortcomings of CAM. > Having iSCSI infrastructure that supported both hardware and software > implementations would be ideal. Seeing all this storage related stuff is very interesting because I just stumbled across a company making a new digital Cinematography system that has 8Mpix and they say that using this in a day's worth shooting they end up with up to 6.63TB of raw digigal footage. In the end this is 398TB for an average feature movie. The camera delivers the images over quad-infiniband to the recording system at 400MB/s. Pretty impressive. http://www.dalsa.com/dc/workflow/storage.asp -- Andre From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 22:37:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F23016A4CE for ; Wed, 1 Dec 2004 22:37:28 +0000 (GMT) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 0022743D39 for ; Wed, 1 Dec 2004 22:37:27 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 25746 invoked from network); 1 Dec 2004 22:37:26 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 1 Dec 2004 22:37:26 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB1MbPk3080740; Wed, 1 Dec 2004 23:37:25 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB1MbP0C080739; Wed, 1 Dec 2004 23:37:25 +0100 (CET) (envelope-from pho) Date: Wed, 1 Dec 2004 23:37:25 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041201223725.GA80282@peter.osted.lan> References: <20041201055115.I18185@mail.chesapeake.net> <20041201195228.GA79652@peter.osted.lan> <20041201160351.V18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201160351.V18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 22:37:28 -0000 On Wed, Dec 01, 2004 at 04:11:50PM -0500, Jeff Roberson wrote: > On Wed, 1 Dec 2004, Peter Holm wrote: > > > On Wed, Dec 01, 2004 at 05:54:49AM -0500, Jeff Roberson wrote: > > > I have updated the patch at: > > > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > > > > I got a page fault in kern/vfs_vnops.c:542 due to vp->v_mount == NULL. > > > > More info at http://www.holm.cc/stress/log/jeff03.html > > The v_mount should only be NULL very briefly for the rootdevvp. What is > your setup here? Any filesystems other than devfs and ffs? $ mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s1e on /tmp (ufs, NFS exported, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) procfs on /proc (procfs, local) linprocfs on /usr/compat/linux/proc (linprocfs, local) >I think that > deadfs might not set a mountpoint either.. DId you do a forced unmount? No. > I think I know how I'm going to have to fix this. > Got a new one for you: 1) panic: wrong b_bufobj 0 should be 0xc2679c10 2) panic: unexpected clean buffer 0xc6624bc8 http://www.holm.cc/stress/log/jeff04.html - Peter > > > > - Peter > > > > > It includes bug fixes for a handful of problems that were reported, and a > > > few more that I found myself. It also unwinds giant from open(), which is > > > a very high risk area, but after a few days of working out bugs it seems > > > to be functioning quite well for me. > > > > > > I did a make -j3 buildworld on a box with a lowered maxvnodes. I also let > > > 'stress' run for 8 loops or so until I ran into an unrelated KSE bug. I > > > did some mount/unmount/single user tests as well. > > > > > > Use at your own risk. I still haven't locked quotas, so if you're using > > > quota, don't run with this patch. > > > > > > Thanks, > > > Jeff > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > -- > > Peter Holm > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 23:12:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D58DF16A4CF for ; Wed, 1 Dec 2004 23:12:10 +0000 (GMT) Received: from mailserv1.neuroflux.com (mailserv1.neuroflux.com [204.228.228.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66B3743D5F for ; Wed, 1 Dec 2004 23:12:10 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 37751 invoked by uid 89); 1 Dec 2004 23:10:57 -0000 Received: from unknown (HELO www2.neuroflux.com) (127.0.0.1) by localhost with SMTP; 1 Dec 2004 23:10:57 -0000 Received: from 128.101.36.205 (SquirrelMail authenticated user ryans@gamersimpact.com); by www2.neuroflux.com with HTTP; Wed, 1 Dec 2004 16:10:57 -0700 (MST) Message-ID: <19549.128.101.36.205.1101942657.squirrel@128.101.36.205> In-Reply-To: <41AE3F80.1000506@freebsd.org> References: <41AE3F80.1000506@freebsd.org> Date: Wed, 1 Dec 2004 16:10:57 -0700 (MST) From: "Ryan Sommers" To: "Scott Long" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 23:12:11 -0000 Scott Long said: > 2. New installer. I know some people still consider this a joke, but > the reality is that sysinstall is no longer state of the art. It's > fairly good at the simple task that it does, but it's becoming harder > and harder to fix bugs and extend functionality in it. It's also > fairly unfriendly to those of us who haven't been using it since 1995. > The DFly folks have some very interesting work in this area > (www.bsdinstaller.com) and it would be very good to see if we can > collaborate with them on it. I've spent a good deal of time taking notes and diagrams of what I wanted from a new installer. However, time constraints have kept me from actually putting any of it to code yet. I've looked at the DFly installed quite a bit and I like what it offers, however, I have a few complaints with it. Quite honestly I wasn't impressed with the code. Another issue I had with the dfly installer was one point I believe needs to be central to any next-gen installer. Internationalisation. My idea of an installer front-end would use a dynamically loadable language library. All resources of the front-end (ie strings, images, etc) would be packaged into a seperate language-pack. These language-packs can then be grouped together into a language library. A few basic packs would be distributed with the default library but other libraries could easily be substituted to make localized distribution sets with little trouble. The benefit of this is that instead of translating the code you would only need to translate the language-(pack|library). I think this would greatly simplify translation and make a seperation between language and the front-end code. This is where my complaint with Dfly comes in, upon reading the source, there are string constants everywhere. Perhaps I am missing something, but this means that in order to supply localization support much work would need to be done to find some scheme that doesn't mean translating the source. I have quite a bit of notes on seperation and even down to specific methods and sub-libraries necessary for the back-end. Perhaps if I have some time soon I'll put it into a PDF somewhere. Has anyone else put much thought into this? -- Ryan Sommers ryans@gamersimpact.com From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 23:15:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56C4316A4CE for ; Wed, 1 Dec 2004 23:15:01 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4B49943D46 for ; Wed, 1 Dec 2004 23:15:00 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 19473 invoked by uid 65534); 1 Dec 2004 23:14:58 -0000 Received: from pD955F624.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.85.246.36) by mail.gmx.net (mp009) with SMTP; 02 Dec 2004 00:14:58 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iB1NEbRA069932 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 2 Dec 2004 00:14:39 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-current@freebsd.org Date: Thu, 2 Dec 2004 00:14:31 +0100 User-Agent: KMail/1.7.1 References: <41AE3F80.1000506@freebsd.org> <41AE424F.1010707@freebsd.org> In-Reply-To: <41AE424F.1010707@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3251719.gJtNvGkTu7"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412020014.35936.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: hackers@freebsd.org cc: Scott Long Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 23:15:01 -0000 --nextPart3251719.gJtNvGkTu7 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday, 1. December 2004 23:14, Andre Oppermann wrote: > Scott Long wrote: > > All, > > > > I know that I said last month that we were going to stop promising > > specific features for the next major release. However, I'd like to > > throw out a list of things that would be really nice to have in the > > future, whether its 6.0 or 7.0 or whatever. Most of these tasks are > > not trivial, but I hope that talking about them will encourage some > > interest. These are in no particular priority order. I'd also be > > thrilled if someone wanted to dress this list up in docbook and add > > it to the webpage. While this is just my personal list, I'd welcome > > other additions to it (in the sense of significant projects, not just Suspend-to-Disk support. I remember somebody thinking aloud about howit wou= ld=20 be possible to implement it, Linux has got it recently, and it's one heck o= f=20 a feature for mobile computing (but not only). =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart3251719.gJtNvGkTu7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBrlBbXhc68WspdLARAvv7AJ9am+ziTRq8XTc6GkIKqVJu5e0YFgCeNFTB eqEC6xnZ0/jc/+I2M+yH0C8= =weJ6 -----END PGP SIGNATURE----- --nextPart3251719.gJtNvGkTu7-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 23:15:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82F4E16A4D8; Wed, 1 Dec 2004 23:15:30 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5458943D55; Wed, 1 Dec 2004 23:15:30 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 799895128F; Wed, 1 Dec 2004 15:20:52 -0800 (PST) Date: Wed, 1 Dec 2004 15:20:52 -0800 From: Kris Kennaway To: Ryan Sommers Message-ID: <20041201232052.GA35040@xor.obsecurity.org> References: <41AE3F80.1000506@freebsd.org> <19549.128.101.36.205.1101942657.squirrel@128.101.36.205> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: <19549.128.101.36.205.1101942657.squirrel@128.101.36.205> User-Agent: Mutt/1.4.2.1i cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 23:15:30 -0000 --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Dec 01, 2004 at 04:10:57PM -0700, Ryan Sommers wrote: > Another issue I had with the dfly installer was one point I believe needs > to be central to any next-gen installer. Internationalisation. Careful not to pile on so many wishes that achieving anything becomes impossible. Our current installer doesn't do this, so it's not a hard requirement that a better installer should. Kris --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBrlHUWry0BWjoQKURAghzAKDO7eRLHstpiCO5yYwVGOBaEP+oFwCgklXv mFBLlZVUHfY3x2XjEv88ga8= =r4hn -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 23:18:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FC4F16A4CE; Wed, 1 Dec 2004 23:18:53 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA3B343D2D; Wed, 1 Dec 2004 23:18:52 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB1NMXI1063439; Wed, 1 Dec 2004 16:22:33 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AE5169.3000909@freebsd.org> Date: Wed, 01 Dec 2004 16:19:05 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <41AE3F80.1000506@freebsd.org> <19549.128.101.36.205.1101942657.squirrel@128.101.36.205> <20041201232052.GA35040@xor.obsecurity.org> In-Reply-To: <20041201232052.GA35040@xor.obsecurity.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Ryan Sommers cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 23:18:53 -0000 Kris Kennaway wrote: > On Wed, Dec 01, 2004 at 04:10:57PM -0700, Ryan Sommers wrote: > > >>Another issue I had with the dfly installer was one point I believe needs >>to be central to any next-gen installer. Internationalisation. > > > Careful not to pile on so many wishes that achieving anything becomes > impossible. Our current installer doesn't do this, so it's not a hard > requirement that a better installer should. > > Kris Internationalization is actually quite important, and is not easy to bolt on after the fact but is fairly easy to program to once the core is in place. The fact that sysinstall doesn't have it makes it no less important. Now this isn't a reason to reject the DFly work, but it could certainly be a good area for someone to contribute. Scott From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 23:29:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F36516A4CE; Wed, 1 Dec 2004 23:29:12 +0000 (GMT) Received: from s1.stradamotorsports.com (ip30.gte215.dsl-acs2.sea.iinet.com [209.20.215.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3DA443D2F; Wed, 1 Dec 2004 23:29:11 +0000 (GMT) (envelope-from jcw@highperformance.net) Received: from [192.168.1.16] (w16.stradamotorsports.com [192.168.1.16]) iB1NT98m016005; Wed, 1 Dec 2004 15:29:10 -0800 (PST) (envelope-from jcw@highperformance.net) Date: Wed, 01 Dec 2004 15:29:10 -0800 From: "Jason C. Wells" To: Scott Long , current@freebsd.org Message-ID: <98CE9C0241F1FC59BB8F0547@[192.168.1.16]> In-Reply-To: <41AE3F80.1000506@freebsd.org> References: <41AE3F80.1000506@freebsd.org> X-Mailer: Mulberry/3.1.5 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Status: No, hits=-2.0 required=4.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: hackers@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 23:29:12 -0000 --On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long wrote: > 5. Clustered FS support. SANs are all the rage these days, and > clustered filesystems that allow data to be distributed across many > storage enpoints and accessed concurrently through the SAN are very > powerful. RedHat recently bought Sistina and re-opened the GFS source > code, so exploring this would be very interesting. This sounds very close to OpenAFS. I don't know what distinguishes a SAN from other types of NAS. OpenAFS does everything you mentioned in the above paragraph. OpenAFS _almost_ works on FreeBSD right now. Later, Jason C. Wells From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 23:33:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 92AAB16A4CE; Wed, 1 Dec 2004 23:33:30 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F52343D2D; Wed, 1 Dec 2004 23:33:30 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D5226512C8; Wed, 1 Dec 2004 15:38:52 -0800 (PST) Date: Wed, 1 Dec 2004 15:38:52 -0800 From: Kris Kennaway To: "Jason C. Wells" Message-ID: <20041201233852.GA35465@xor.obsecurity.org> References: <41AE3F80.1000506@freebsd.org> <98CE9C0241F1FC59BB8F0547@[192.168.1.16]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline In-Reply-To: <98CE9C0241F1FC59BB8F0547@[192.168.1.16]> User-Agent: Mutt/1.4.2.1i cc: hackers@freebsd.org cc: Scott Long cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 23:33:30 -0000 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 01, 2004 at 03:29:10PM -0800, Jason C. Wells wrote: > --On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long=20 > wrote: >=20 > >5. Clustered FS support. SANs are all the rage these days, and > >clustered filesystems that allow data to be distributed across many > >storage enpoints and accessed concurrently through the SAN are very > >powerful. RedHat recently bought Sistina and re-opened the GFS source > >code, so exploring this would be very interesting. >=20 > This sounds very close to OpenAFS. I don't know what distinguishes a SAN= =20 > from other types of NAS. OpenAFS does everything you mentioned in the=20 > above paragraph. OpenAFS _almost_ works on FreeBSD right now. I'd be very interested to try using this for package builds, btw. Currently I have to rsync a lot of data to the remote build clients, which takes a very long time. Kris --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBrlYMWry0BWjoQKURAuIYAJwP6tHh/UB1YahRTXyGDKuWX8emnACgkTBP wK7YPPoftgaL+Tcrc9IBbtQ= =9SeW -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 23:37:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 874B616A4CE; Wed, 1 Dec 2004 23:37:47 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2A3B43D55; Wed, 1 Dec 2004 23:37:46 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB1NfR3l063532; Wed, 1 Dec 2004 16:41:27 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AE55D7.8020709@freebsd.org> Date: Wed, 01 Dec 2004 16:37:59 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jason C. Wells" References: <41AE3F80.1000506@freebsd.org> <98CE9C0241F1FC59BB8F0547@[192.168.1.16]> In-Reply-To: <98CE9C0241F1FC59BB8F0547@[192.168.1.16]> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: hackers@freebsd.org cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 23:37:47 -0000 Jason C. Wells wrote: > --On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long > wrote: > >> 5. Clustered FS support. SANs are all the rage these days, and >> clustered filesystems that allow data to be distributed across many >> storage enpoints and accessed concurrently through the SAN are very >> powerful. RedHat recently bought Sistina and re-opened the GFS source >> code, so exploring this would be very interesting. > > > This sounds very close to OpenAFS. I don't know what distinguishes a > SAN from other types of NAS. OpenAFS does everything you mentioned in > the above paragraph. OpenAFS _almost_ works on FreeBSD right now. > > Later, > Jason C. Wells Well, AFS requires an intelligent node in front of each disk. True SAN clustering means that you have a web of disks directly connected to the SAN (iSCSI, FibreChannel, etc), and two or more servers on the SAN that see those disks as a single filesystem (actually a bit more complicated than this, but you get the point). If one server goes down, no access to data is lost since the disks can be reached from any other server on the SAN that is participating in the clustered FS. Scott From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 23:43:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A14C16A4CE for ; Wed, 1 Dec 2004 23:43:19 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id D081E43D53 for ; Wed, 1 Dec 2004 23:43:18 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iB1NhI0N081940; Wed, 1 Dec 2004 18:43:18 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iB1NhH6E081928; Wed, 1 Dec 2004 18:43:17 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Wed, 1 Dec 2004 18:43:16 -0500 (EST) From: Jeff Roberson To: Peter Holm In-Reply-To: <20041201223725.GA80282@peter.osted.lan> Message-ID: <20041201184238.K18185@mail.chesapeake.net> References: <20041201055115.I18185@mail.chesapeake.net> <20041201160351.V18185@mail.chesapeake.net> <20041201223725.GA80282@peter.osted.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 23:43:19 -0000 On Wed, 1 Dec 2004, Peter Holm wrote: > On Wed, Dec 01, 2004 at 04:11:50PM -0500, Jeff Roberson wrote: > > On Wed, 1 Dec 2004, Peter Holm wrote: > > > > > On Wed, Dec 01, 2004 at 05:54:49AM -0500, Jeff Roberson wrote: > > > > I have updated the patch at: > > > > > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > > > > > > > I got a page fault in kern/vfs_vnops.c:542 due to vp->v_mount == NULL. > > > > > > More info at http://www.holm.cc/stress/log/jeff03.html > > > > The v_mount should only be NULL very briefly for the rootdevvp. What is > > your setup here? Any filesystems other than devfs and ffs? > $ mount > /dev/ad0s1a on / (ufs, local) > devfs on /dev (devfs, local) > /dev/ad0s1e on /tmp (ufs, NFS exported, local, soft-updates) > /dev/ad0s1f on /usr (ufs, local, soft-updates) > /dev/ad0s1d on /var (ufs, local, soft-updates) > procfs on /proc (procfs, local) > linprocfs on /usr/compat/linux/proc (linprocfs, local) > > >I think that > > deadfs might not set a mountpoint either.. DId you do a forced unmount? > No. > > I think I know how I'm going to have to fix this. > > > > Got a new one for you: > 1) panic: wrong b_bufobj 0 should be 0xc2679c10 > 2) panic: unexpected clean buffer 0xc6624bc8 > > http://www.holm.cc/stress/log/jeff04.html I fixed your last panic. The new patch is up at the same URL. I'll look at these now, thanks. This tool is really working out well. > > - Peter > > > > > > > - Peter > > > > > > > It includes bug fixes for a handful of problems that were reported, and a > > > > few more that I found myself. It also unwinds giant from open(), which is > > > > a very high risk area, but after a few days of working out bugs it seems > > > > to be functioning quite well for me. > > > > > > > > I did a make -j3 buildworld on a box with a lowered maxvnodes. I also let > > > > 'stress' run for 8 loops or so until I ran into an unrelated KSE bug. I > > > > did some mount/unmount/single user tests as well. > > > > > > > > Use at your own risk. I still haven't locked quotas, so if you're using > > > > quota, don't run with this patch. > > > > > > > > Thanks, > > > > Jeff > > > > _______________________________________________ > > > > freebsd-current@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > -- > > > Peter Holm > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > -- > Peter Holm > From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 23:47:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFE3616A4CE; Wed, 1 Dec 2004 23:47:37 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54C8343D31; Wed, 1 Dec 2004 23:47:37 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iB1NlaAD074471; Wed, 1 Dec 2004 17:47:36 -0600 (CST) (envelope-from dan) Date: Wed, 1 Dec 2004 17:47:36 -0600 From: Dan Nelson To: "Jason C. Wells" Message-ID: <20041201234736.GX5518@dan.emsphone.com> References: <41AE3F80.1000506@freebsd.org> <98CE9C0241F1FC59BB8F0547@[192.168.1.16]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <98CE9C0241F1FC59BB8F0547@[192.168.1.16]> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: hackers@freebsd.org cc: Scott Long cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 23:47:37 -0000 In the last episode (Dec 01), Jason C. Wells said: > --On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long > wrote: > > >5. Clustered FS support. SANs are all the rage these days, and > >clustered filesystems that allow data to be distributed across many > >storage enpoints and accessed concurrently through the SAN are very > >powerful. RedHat recently bought Sistina and re-opened the GFS source > >code, so exploring this would be very interesting. > > This sounds very close to OpenAFS. I don't know what distinguishes a > SAN from other types of NAS. OpenAFS does everything you mentioned > in the above paragraph. OpenAFS _almost_ works on FreeBSD right now. OpenAFS is a network-centric system that replicates data across its nodes, I think, and each node has a cache. A clustered filesystem uses a single block of shared storage (usually on a fibre-channel SAN, but you can also use shared scsi on a 2-machine cluster) that all servers access directly. The magic is getting the locking right to make sure the servers don't stomp on each other's data. Extremely useful for server farms that need to share large files, or even lots of small files (webservers for example). -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 23:52:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74BFC16A4CF for ; Wed, 1 Dec 2004 23:52:20 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDB3A43D39 for ; Wed, 1 Dec 2004 23:52:19 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iB1NqJ0N085793; Wed, 1 Dec 2004 18:52:19 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iB1NqJ9D085788; Wed, 1 Dec 2004 18:52:19 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Wed, 1 Dec 2004 18:52:19 -0500 (EST) From: Jeff Roberson To: Peter Holm In-Reply-To: <20041201184238.K18185@mail.chesapeake.net> Message-ID: <20041201185146.W18185@mail.chesapeake.net> References: <20041201055115.I18185@mail.chesapeake.net> <20041201223725.GA80282@peter.osted.lan> <20041201184238.K18185@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 23:52:20 -0000 On Wed, 1 Dec 2004, Jeff Roberson wrote: > On Wed, 1 Dec 2004, Peter Holm wrote: > > > On Wed, Dec 01, 2004 at 04:11:50PM -0500, Jeff Roberson wrote: > > > On Wed, 1 Dec 2004, Peter Holm wrote: > > > > > > > On Wed, Dec 01, 2004 at 05:54:49AM -0500, Jeff Roberson wrote: > > > > > I have updated the patch at: > > > > > > > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > > > > > > > > > > I got a page fault in kern/vfs_vnops.c:542 due to vp->v_mount == NULL. > > > > > > > > More info at http://www.holm.cc/stress/log/jeff03.html > > > > > > The v_mount should only be NULL very briefly for the rootdevvp. What is > > > your setup here? Any filesystems other than devfs and ffs? > > $ mount > > /dev/ad0s1a on / (ufs, local) > > devfs on /dev (devfs, local) > > /dev/ad0s1e on /tmp (ufs, NFS exported, local, soft-updates) > > /dev/ad0s1f on /usr (ufs, local, soft-updates) > > /dev/ad0s1d on /var (ufs, local, soft-updates) > > procfs on /proc (procfs, local) > > linprocfs on /usr/compat/linux/proc (linprocfs, local) > > > > >I think that > > > deadfs might not set a mountpoint either.. DId you do a forced unmount? > > No. > > > I think I know how I'm going to have to fix this. > > > > > > > Got a new one for you: > > 1) panic: wrong b_bufobj 0 should be 0xc2679c10 > > 2) panic: unexpected clean buffer 0xc6624bc8 > > > > http://www.holm.cc/stress/log/jeff04.html > > I fixed your last panic. The new patch is up at the same URL. I'll look > at these now, thanks. This tool is really working out well. Also fixed the unexpected clean buffer. That was mostly just a bad assert. I'm still baffled by wrong bufobj. > > > > > - Peter > > > > > > > > > > - Peter > > > > > > > > > It includes bug fixes for a handful of problems that were reported, and a > > > > > few more that I found myself. It also unwinds giant from open(), which is > > > > > a very high risk area, but after a few days of working out bugs it seems > > > > > to be functioning quite well for me. > > > > > > > > > > I did a make -j3 buildworld on a box with a lowered maxvnodes. I also let > > > > > 'stress' run for 8 loops or so until I ran into an unrelated KSE bug. I > > > > > did some mount/unmount/single user tests as well. > > > > > > > > > > Use at your own risk. I still haven't locked quotas, so if you're using > > > > > quota, don't run with this patch. > > > > > > > > > > Thanks, > > > > > Jeff > > > > > _______________________________________________ > > > > > freebsd-current@freebsd.org mailing list > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > -- > > > > Peter Holm > > > > _______________________________________________ > > > > freebsd-current@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > -- > > Peter Holm > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 00:25:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AEF516A4CE for ; Thu, 2 Dec 2004 00:25:59 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09EBA43D49 for ; Thu, 2 Dec 2004 00:25:59 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id F2B9672DF8; Wed, 1 Dec 2004 16:25:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id EDC7F72DD4; Wed, 1 Dec 2004 16:25:58 -0800 (PST) Date: Wed, 1 Dec 2004 16:25:58 -0800 (PST) From: Doug White To: Joseph Koshy In-Reply-To: <84dead720411300329249d4bf3@mail.gmail.com> Message-ID: <20041201162501.H71481@carver.gumbysoft.com> References: <84dead720411300329249d4bf3@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current Subject: Re: Dual CPU detection problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 00:25:59 -0000 On Tue, 30 Nov 2004, Joseph Koshy wrote: > Strange problem. > > On an IBM xSeries 335 machine with TWO P4 HTT cpus (mptable, dmesg output > enclosed) FreeBSD -CURRENT will sometimes detect both the physical CPUs > and will sometimes detect only one. > > FreeBSD 5.3 reliably detects the 2 physical / 4 logical CPUs that are present. > > Any suggestions on how to debug this? dmesg + mptable + acpidump output in both situations would be a good start. Sounds like one of the physical CPUs might be flakey; you see 2 CPUs since you see the solitary core's hyperthreaded pair. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 00:29:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E50516A4CE; Thu, 2 Dec 2004 00:29:40 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18E0843D53; Thu, 2 Dec 2004 00:29:40 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iB20Tdb6003035; Wed, 1 Dec 2004 16:29:39 -0800 (PST) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.13.1/8.13.1/Submit) id iB20Td43003034; Wed, 1 Dec 2004 16:29:39 -0800 (PST) (envelope-from marcel) Date: Wed, 1 Dec 2004 16:29:39 -0800 From: Marcel Moolenaar To: Scott Long Message-ID: <20041202002939.GA2834@ns1.xcllnt.net> References: <41AE3F80.1000506@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AE3F80.1000506@freebsd.org> User-Agent: Mutt/1.4.2.1i cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 00:29:40 -0000 On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote: > > 1. Keyboard multiplexer. I actually fail to stop thinking about a complete syscons and pcvt replacement. You know, the one and only console implementation that makes all others obsolete. Big plans, little time, yada yada yada... > 2. New installer. It may actually be interesting to see if we can make an expert system for this. When I think about implementing an installer (alas I've been doing that), I'm not so much interested in how things are packaged, or how it looks but rather what needs to be done, when and how all these actions relate and interact with each other. This is especially tricky when actions are triggered by the current configuration of the machine onto which one tries to install. Knowing all the possible activities and their dependencies should help establish a control flow through the installation process in such a way that users get asked only those questions that are relevent and also when it matters. One puts a UI on top of this to get a nice looking installer. At least, that's how I look at it... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 00:39:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CA1116A4CE; Thu, 2 Dec 2004 00:39:48 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8B2343D49; Thu, 2 Dec 2004 00:39:47 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB20hSLB063844; Wed, 1 Dec 2004 17:43:29 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AE6460.6040603@freebsd.org> Date: Wed, 01 Dec 2004 17:40:00 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcel Moolenaar References: <41AE3F80.1000506@freebsd.org> <20041202002939.GA2834@ns1.xcllnt.net> In-Reply-To: <20041202002939.GA2834@ns1.xcllnt.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 00:39:48 -0000 Marcel Moolenaar wrote: > On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote: > >>1. Keyboard multiplexer. > > > I actually fail to stop thinking about a complete syscons and pcvt > replacement. You know, the one and only console implementation that > makes all others obsolete. Big plans, little time, yada yada yada... > > >>2. New installer. > > > It may actually be interesting to see if we can make an expert > system for this. When I think about implementing an installer (alas > I've been doing that), I'm not so much interested in how things are > packaged, or how it looks but rather what needs to be done, when and > how all these actions relate and interact with each other. This is > especially tricky when actions are triggered by the current > configuration of the machine onto which one tries to install. Knowing > all the possible activities and their dependencies should help > establish a control flow through the installation process in such a > way that users get asked only those questions that are relevent and > also when it matters. One puts a UI on top of this to get a nice > looking installer. At least, that's how I look at it... > Yeah, I've had many similar thoughts. The hard part of a new installer, or any complex UI application, is the framework that ties events and actions together. The easy part is writing the modules on top of that that do the discrete actions. While I see quite a few rough edges in the upper layers of the DF installer, it seems like quite a bit of work is going into the framework, and that's why I'm actually so interested in it. Scott From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 01:18:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45CCA16A4CE; Thu, 2 Dec 2004 01:18:09 +0000 (GMT) Received: from drago.fomokka.net (drago.fomokka.net [140.117.205.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01F8D43D53; Thu, 2 Dec 2004 01:18:08 +0000 (GMT) (envelope-from foxfair@drago.fomokka.net) Received: from drago.fomokka.net (ohwnsp@localhost [127.0.0.1]) by drago.fomokka.net (8.12.11/8.12.8) with ESMTP id iB21HwVD081727; Thu, 2 Dec 2004 09:18:01 +0800 (CST) (envelope-from foxfair@drago.fomokka.net) Received: (from foxfair@localhost) by drago.fomokka.net (8.12.11/8.12.8/Submit) id iB21Hwvb081726; Thu, 2 Dec 2004 09:17:58 +0800 (CST) Date: Thu, 2 Dec 2004 09:17:58 +0800 From: Foxfair Hu To: Scott Long Message-ID: <20041202011758.GA81639@drago.fomokka.net> References: <41AE3F80.1000506@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline In-Reply-To: <41AE3F80.1000506@freebsd.org> X-PGP-Fingerprint: 280C A846 CA1B CAC9 DDCF F4CB D553 4BD5 4E9B CA59 X-PGP-KeyID: 1024D/0x4E9BCA59 User-Agent: Mutt/1.5.4i cc: hackers@freebsd.org cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: foxfair@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 01:18:09 -0000 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote: > All, >=20 [....] >=20 > 1. Keyboard multiplexer. We are running into problems with making > ps/2 and USB/bluetooth keyboards work together and work with KVMs. > Having a virtual keyboard device that multiplexes the various real > keyboard devices and handles hotplug can solve this mess pretty > effectively. I know that there has been a lot of talk about this on > mailing lists recently but I don't know how much progress is being made > so I'm listing it here. How about reuse NetBSD's wscons ? I've kept an eye on it and thought it should be a good start for FreeBSD. foxfair --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFBrm1G1VNL1U6bylkRAuU5AKCxy/r9HetJDedMpWKCoeEMUpzYgACfYjtr 5/VsLoa21PEC12e9DeNfI7A= =3uzN -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 01:41:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EAA016A4CE; Thu, 2 Dec 2004 01:41:41 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 263FA43D1D; Thu, 2 Dec 2004 01:41:41 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB21jLWS064056; Wed, 1 Dec 2004 18:45:21 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AE72E0.4080107@freebsd.org> Date: Wed, 01 Dec 2004 18:41:52 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: foxfair@freebsd.org References: <41AE3F80.1000506@freebsd.org> <20041202011758.GA81639@drago.fomokka.net> In-Reply-To: <20041202011758.GA81639@drago.fomokka.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: hackers@freebsd.org cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 01:41:41 -0000 Foxfair Hu wrote: > On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote: > >>All, >> > > [....] > >>1. Keyboard multiplexer. We are running into problems with making >>ps/2 and USB/bluetooth keyboards work together and work with KVMs. >>Having a virtual keyboard device that multiplexes the various real >>keyboard devices and handles hotplug can solve this mess pretty >>effectively. I know that there has been a lot of talk about this on >>mailing lists recently but I don't know how much progress is being made >>so I'm listing it here. > > > How about reuse NetBSD's wscons ? I've kept an eye on it and thought > it should be a good start for FreeBSD. > > > foxfair > If it provides keyboard mux'ing like we need, then please go and give it a shot. Scott From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 03:54:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6676716A4CE; Thu, 2 Dec 2004 03:54:39 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C0B543D60; Thu, 2 Dec 2004 03:54:39 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iB23qHaE078235; Wed, 1 Dec 2004 20:52:17 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 01 Dec 2004 20:53:22 -0700 (MST) Message-Id: <20041201.205322.102612548.imp@bsdimp.com> To: scottl@freebsd.org From: "M. Warner Losh" In-Reply-To: <41AE3F80.1000506@freebsd.org> References: <41AE3F80.1000506@freebsd.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 03:54:39 -0000 In message: <41AE3F80.1000506@freebsd.org> Scott Long writes: : 1. Keyboard multiplexer. We are running into problems with making : ps/2 and USB/bluetooth keyboards work together and work with KVMs. : Having a virtual keyboard device that multiplexes the various real : keyboard devices and handles hotplug can solve this mess pretty : effectively. I know that there has been a lot of talk about this on : mailing lists recently but I don't know how much progress is being made : so I'm listing it here. There aready are multiplexers in the kernel. The problem is that we need a many to one mux that is the OR of all the ones installed. We can current set WHICH keyboard is connected to the mux, but can't say 'ALL OF THEM' at all. I believe that Brooks Davis has said he's working on this. Warner From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 03:59:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C692316A4CE for ; Thu, 2 Dec 2004 03:59:15 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7596E43D1D for ; Thu, 2 Dec 2004 03:59:15 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so764029rnf for ; Wed, 01 Dec 2004 19:59:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ecNY5fjcp5g5tJlJ1en3FgEEZ71So6IuKhh6EO6VE0xa0ZEd7akuIo+iuoXBXwV7UaaRl0vT2ndqaNrBpTFAX/v3FCgwtR/VXIFIrTVp+XZUP1Mnw11KJZv9qpYj3ihZ64IAqF8lDu+5R7z1MhknU/d2dgwYjdkVIrHwgNjN76E= Received: by 10.38.75.28 with SMTP id x28mr588785rna; Wed, 01 Dec 2004 19:59:09 -0800 (PST) Received: by 10.38.15.38 with HTTP; Wed, 1 Dec 2004 19:59:08 -0800 (PST) Message-ID: Date: Wed, 1 Dec 2004 21:59:08 -0600 From: Eric Kjeldergaard To: Poul-Henning Kamp In-Reply-To: <66197.1101887405@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <66197.1101887405@critter.freebsd.dk> cc: current@freebsd.org Subject: Re: [TESTERS] msdosfs patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eric Kjeldergaard List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 03:59:15 -0000 > Can some of the people who use msdosfs please test this patch for me ? > > Poul-Henning Test it for what exactly? (Sorry if I'm being incompetent, I get that way sometimes.) -- If I write a signature, my emails will appear more personalised. From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 05:09:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 548C816A4CE for ; Thu, 2 Dec 2004 05:09:34 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0501E43D54 for ; Thu, 2 Dec 2004 05:09:34 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id B64D4F2148 for ; Wed, 1 Dec 2004 21:09:33 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02063-03 for ; Wed, 1 Dec 2004 21:09:32 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 50AF3F1802 for ; Wed, 1 Dec 2004 21:09:32 -0800 (PST) From: Sean McNeil To: current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-hob8gqayCul+gKbYYmeY" Date: Wed, 01 Dec 2004 21:09:32 -0800 Message-Id: <1101964172.66579.12.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com Subject: need help understanding kse thread issue - signal lockup in slapd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 05:09:34 -0000 --=-hob8gqayCul+gKbYYmeY Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I'm trying to figure out why slapd hangs on shutdown for my amd64 system. It use to exit just fine, but for quite a while now it hangs: /usr/local/etc/rc.d/slapd.sh stop and it just sits there even though it is pretty much closed down. I see 3 threads that appear to be running: (gdb) info thr * 3 LWP 100272 0x000000080142f914 in kse_release () at kse_release.S:2 2 Thread 8 (sleeping) _thr_sched_switch_unlocked (curthread=3D0x633000) at pthread_md.h:226 1 Thread 7 (LWP 100134) 0x000000080142f914 in kse_release () at kse_release.S:2 0x000000080142f914 in kse_release () at kse_release.S:2 2 RSYSCALL(kse_release) (gdb) bt #0 0x000000080142f914 in kse_release () at kse_release.S:2 #1 0x0000000801429e49 in kse_wait (kse=3D0x62b000, td_wait=3D0x0, sigseqno=3D0) at /usr/src/lib/libpthread/thread/thr_kern.c:1843 #2 0x0000000801428078 in kse_sched_multi (kmbx=3D0x62ffa0) at /usr/src/lib/libpthread/thread/thr_kern.c:1039 #3 0x000000080142bfbf in _amd64_enter_uts () at /usr/src/lib/libpthread/arch/amd64/amd64/enter_uts.S:40 [Switching to thread 2 (Thread 8 (sleeping))]#0 _thr_sched_switch_unlocked ( curthread=3D0x633000) at pthread_md.h:226 226 if (ret =3D=3D 0) { Current language: auto; currently c (gdb) bt #0 _thr_sched_switch_unlocked (curthread=3D0x633000) at pthread_md.h:226 #1 0x00000008014275e0 in _thr_sched_switch (curthread=3D0x633000) at /usr/src/lib/libpthread/thread/thr_kern.c:607 #2 0x000000080141acb4 in _pthread_join (pthread=3D0x74d000, thread_return=3D0x0) at /usr/src/lib/libpthread/thread/thr_join.c:133 #3 0x000000080071ad09 in ldap_pvt_thread_join (thread=3D0x80060a070, thread_return=3D0x62b068) at thr_posix.c:165 [Switching to thread 1 (Thread 7 (LWP 100134))]#0 0x000000080142f914 in kse_release () at kse_release.S:2 2 RSYSCALL(kse_release) Current language: auto; currently asm (gdb) bt #0 0x000000080142f914 in kse_release () at kse_release.S:2 #1 0x000000080141e926 in sig_daemon (arg=3D0x7fffffefef70) at /usr/src/lib/libpthread/thread/thr_sig.c:216 #2 0x0000000801427db5 in kse_sched_single (kmbx=3D0x7fffffefef70) at /usr/src/lib/libpthread/thread/thr_kern.c:902 #3 0x0000000000000000 in ?? () Error accessing memory address 0x7fffffeff000: Bad address. Looks like thread 3 is the scheduling thread, thread 1 is the main thread and got the signal but for some reason thread 2 is still waiting to join a thread that isn't there anymore (0x74d000 - Thread 8?). Does anyone have any ideas? If a thread is created joinable, then it should not go away until someone actually joins it, no? --=-hob8gqayCul+gKbYYmeY Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBrqOMyQsGN30uGE4RAtkpAJ9aYw1dG9U+mKKS0a7tCS7Xgm/FHQCdFRnN 17W82CTk2llF+7HVaaWlp54= =HWUy -----END PGP SIGNATURE----- --=-hob8gqayCul+gKbYYmeY-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 05:10:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CB6C16A4CE; Thu, 2 Dec 2004 05:10:30 +0000 (GMT) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id B018943D2D; Thu, 2 Dec 2004 05:10:29 +0000 (GMT) (envelope-from brad@stop.mail-abuse.org) Received: from [10.0.1.2] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.11/8.12.3) with ESMTP id iB25AHa3078692; Thu, 2 Dec 2004 00:10:19 -0500 (EST) (envelope-from brad@stop.mail-abuse.org) Mime-Version: 1.0 Message-Id: In-Reply-To: <20041201233852.GA35465@xor.obsecurity.org> References: <41AE3F80.1000506@freebsd.org><98CE9C0241F1FC59BB8F0547@[192.168 .1.16]> <20041201233852.GA35465@xor.obsecurity.org> Date: Thu, 2 Dec 2004 01:23:57 +0100 To: Kris Kennaway From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: "Jason C. Wells" cc: hackers@freebsd.org cc: Scott Long cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 05:10:30 -0000 At 3:38 PM -0800 2004-12-01, Kris Kennaway quoted Jason C. Wells: >> This sounds very close to OpenAFS. I don't know what distinguishes a SAN >> from other types of NAS. OpenAFS does everything you mentioned in the >> above paragraph. OpenAFS _almost_ works on FreeBSD right now. > > I'd be very interested to try using this for package builds, btw. > Currently I have to rsync a lot of data to the remote build clients, > which takes a very long time. It's interesting that you mention this. I've been giving some thought to how I might be able to dive in and start seriously working on building my UltraSPARC cluster (based on the four U10 clones I have already, plus as many U5s as I can throw into the mix), and I was hoping to find a better solution than NFS, and AFS/Coda/OpenAFS was tops of my list of alternatives to consider. In particular, if I can get this thing working reasonably well, I'd like to turn this into a package building cluster for FreeBSD/UltraSPARC, and maybe see if there are some other applications I can put it to during the idle times. I'm still looking for instructions on how the existing FreeBSD package building clusters are put together. That plus various bits-n-pieces I've found (mostly from Brooks) should help me figure out how to try to build my own. -- Brad Knowles, "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See for more info. From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 05:13:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F088C16A4CE for ; Thu, 2 Dec 2004 05:13:37 +0000 (GMT) Received: from techno.sub.ru (webmail.sub.ru [213.247.139.22]) by mx1.FreeBSD.org (Postfix) with SMTP id C12A843D39 for ; Thu, 2 Dec 2004 05:13:36 +0000 (GMT) (envelope-from tarkhil@webmail.sub.ru) Received: (qmail 22365 invoked by uid 0); 2 Dec 2004 05:13:38 -0000 Received: from webmail.sub.ru (HELO tarkhil.over.ru) (213.247.139.22) by techno.sub.ru with SMTP; 2 Dec 2004 05:13:38 -0000 Date: Thu, 2 Dec 2004 08:13:52 +0300 From: Alex Povolotsky To: freebsd-current@freebsd.org, scottl@freebsd.org Message-Id: <20041202081352.1bfb6be3@tarkhil.over.ru> In-Reply-To: <41AE3F80.1000506@freebsd.org> References: <41AE3F80.1000506@freebsd.org> Organization: sub.ru X-Mailer: Sylpheed version 0.9.9claws (GTK+ 1.2.10; i386-portbld-freebsd4.8) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 05:13:38 -0000 On Wed, 01 Dec 2004 15:02:40 -0700 Scott Long wrote: SL> 4. Journaled filesystem. While we can debate the merits of speed SL> SL> 5. Clustered FS support. SANs are all the rage these days, and Maybe you could also look at unionFS? unionfs -b could be extremly useful for multiple jails... -- Alex. From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 05:41:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C50AF16A4CE for ; Thu, 2 Dec 2004 05:41:51 +0000 (GMT) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FDFC43D66 for ; Thu, 2 Dec 2004 05:41:51 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from ocean.jinmei.org (unknown [2001:200:0:8002:200:39ff:fed7:e2e4]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 57D241521D; Thu, 2 Dec 2004 14:41:49 +0900 (JST) Date: Thu, 02 Dec 2004 14:41:57 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: davids@webmaster.com In-Reply-To: References: User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: current@FreeBSD.org Subject: Re: malloc(0) returns an invalid address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 05:41:51 -0000 >>>>> On Wed, 1 Dec 2004 07:49:54 -0800, >>>>> "David Schwartz" said: >> % ./a.out >> address of p is 0x800 >> zsh: 645 segmentation fault (core dumped) ./a.out > This should fault. Although the return value of 'malloc(0)' is a valid > pointer, once you cast it to a 'char *', you cannot dereference it because > it does not point to a character. This same problem would occur with > 'malloc(1)' and 'int *'. I expected the answer:-) This is probably a matter of the definition of "validness", and I won't argue about this point. (and, of course, it cannot be justified to dereference a zero-length pointer, whether the result is segfault or not) BTW: the "same problem" (of segfault) does actually NOT occur with malloc(1) and int * on FreeBSD 5.3 (i386). I suspect malloc(3) takes a special action with the size of zero. >> So, if we wanted to call 0x800 "a valid pointer just with >> not-enough-size", it would be fine. But then we need to implement the >> same logic in the kernel to provide consistent behavior. (I would >> "fix" the malloc behavior though). > The malloc behavior is not broken, so it cannot be fixed. The kernel check > semantics in 'useracc' are wrong for zero lengths. Okay, I'll be happy as long as the library and the kernel provide the consistent behavior on which pointer is "valid". Thanks, JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp p.s. is it better for me to file a separate bug report on this? From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 05:55:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A41916A4CE; Thu, 2 Dec 2004 05:55:02 +0000 (GMT) Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2649E43D1D; Thu, 2 Dec 2004 05:55:00 +0000 (GMT) (envelope-from jhay@icomtek.csir.co.za) Received: from zibbi.icomtek.csir.co.za (localhost [127.0.0.1]) iB25sua8084933; Thu, 2 Dec 2004 07:54:56 +0200 (SAST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost)iB25ssUj084932; Thu, 2 Dec 2004 07:54:54 +0200 (SAST) (envelope-from jhay) Date: Thu, 2 Dec 2004 07:54:54 +0200 From: John Hay To: Marcel Moolenaar Message-ID: <20041202055454.GA84339@zibbi.icomtek.csir.co.za> References: <41AE3F80.1000506@freebsd.org> <20041202002939.GA2834@ns1.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041202002939.GA2834@ns1.xcllnt.net> User-Agent: Mutt/1.4.1i cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 05:55:02 -0000 > > > > 1. Keyboard multiplexer. > > I actually fail to stop thinking about a complete syscons and pcvt > replacement. You know, the one and only console implementation that > makes all others obsolete. Big plans, little time, yada yada yada... It would be nice if one would still be able to use the keyboards separately too, even if you have to recompile the kernel for that. One nice usage would be on HP's quad kiosk machine. It is a single processor box with 4 x screen, keyboard and mouse, and then 4 people can use it. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 05:56:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F158616A4CE for ; Thu, 2 Dec 2004 05:56:22 +0000 (GMT) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5B0643D55 for ; Thu, 2 Dec 2004 05:56:22 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from [10.9.204.1] (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id 5C94B7B; Thu, 2 Dec 2004 00:56:18 -0500 (EST) From: "Brandon S. Allbery KF8NH" To: JINMEI Tatuya / =?UTF-8?Q?=E7=A5=9E=E6=98=8E=E9=81=94?= =?UTF-8?Q?=E5=93=89?= In-Reply-To: References: Content-Type: text/plain; charset=UTF-8 Message-Id: <1101966976.4877.16.camel@rushlight.kf8nh.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Thu, 02 Dec 2004 00:56:17 -0500 Content-Transfer-Encoding: 8bit cc: current@FreeBSD.org Subject: Re: malloc(0) returns an invalid address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 05:56:23 -0000 On Thu, 2004-12-02 at 00:41, JINMEI Tatuya / 神明é”哉 wrote: > > pointer, once you cast it to a 'char *', you cannot dereference it because > > it does not point to a character. This same problem would occur with > > 'malloc(1)' and 'int *'. > > BTW: the "same problem" (of segfault) does actually NOT occur with > malloc(1) and int * on FreeBSD 5.3 (i386). I suspect malloc(3) takes > a special action with the size of zero. I believe he misspoke; the result is undefined in that case, since it's not generally possible to enforce a writable size of 1 in hardware(*) and malloc() is required to return memory aligned for any fundamental C type regardless of the amount of memory allocated (i.e. malloc(1) isn't permitted to return an odd address on hardware where types larger than (char) must be aligned). With a size of 0 it's easy to cheat: return a "magic" minimal-sized pointer into an unmapped page (or a read-only page, getting you a trap if something tries to assign to it; but I think the low pages in the address space are not mapped for standard demand-paged executables on FreeBSD), and when it's realloc()ed to a non-zero size recognize the "magic" value and return a real chunk of allocated memory. (*) it can be done on some processors/MMUs, on others it can be done for a limited number of addresses (Intel debug registers?), on still others (e.g. Intel 486) the best granularity you can get is 16-byte and it's going to be expensive... -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon univ. KF8NH From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 05:59:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E039116A4CE for ; Thu, 2 Dec 2004 05:59:49 +0000 (GMT) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA1AE43D46 for ; Thu, 2 Dec 2004 05:59:49 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from [10.9.204.1] (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id 5B2D47B; Thu, 2 Dec 2004 00:59:48 -0500 (EST) From: "Brandon S. Allbery KF8NH" To: JINMEI Tatuya / =?UTF-8?Q?=E7=A5=9E=E6=98=8E=E9=81=94?= =?UTF-8?Q?=E5=93=89?= In-Reply-To: <1101966976.4877.16.camel@rushlight.kf8nh.com> References: <1101966976.4877.16.camel@rushlight.kf8nh.com> Content-Type: text/plain Message-Id: <1101967187.4877.19.camel@rushlight.kf8nh.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Thu, 02 Dec 2004 00:59:47 -0500 Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org Subject: Re: malloc(0) returns an invalid address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 05:59:50 -0000 On Thu, 2004-12-02 at 00:56, Brandon S. Allbery KF8NH wrote: > With a size of 0 it's easy to cheat: return a "magic" minimal-sized Correction (what I get for shooting off my mouth at 1am...): "minimal-sized" is meaningless in this context. -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon univ. KF8NH From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 06:33:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61C6A16A4CE; Thu, 2 Dec 2004 06:33:28 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC95343D60; Thu, 2 Dec 2004 06:33:27 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iB26WlhI079977; Wed, 1 Dec 2004 23:32:50 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 01 Dec 2004 23:33:45 -0700 (MST) Message-Id: <20041201.233345.83691449.imp@bsdimp.com> To: jhay@icomtek.csir.co.za From: "M. Warner Losh" In-Reply-To: <20041202055454.GA84339@zibbi.icomtek.csir.co.za> References: <41AE3F80.1000506@freebsd.org> <20041202002939.GA2834@ns1.xcllnt.net> <20041202055454.GA84339@zibbi.icomtek.csir.co.za> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: scottl@freebsd.org cc: current@freebsd.org cc: marcel@xcllnt.net Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 06:33:28 -0000 In message: <20041202055454.GA84339@zibbi.icomtek.csir.co.za> John Hay writes: : > > 1. Keyboard multiplexer. : > : > I actually fail to stop thinking about a complete syscons and pcvt : > replacement. You know, the one and only console implementation that : > makes all others obsolete. Big plans, little time, yada yada yada... : : It would be nice if one would still be able to use the keyboards : separately too, even if you have to recompile the kernel for that. : One nice usage would be on HP's quad kiosk machine. It is a single : processor box with 4 x screen, keyboard and mouse, and then 4 people : can use it. I think that making it just another driver that knows about the keyboard mux would make this possible in the short term... Hmmm, maybe it is time for me to STFU and hack together what I'm thinking :-) Warner From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 06:55:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E780D16A4CF; Thu, 2 Dec 2004 06:55:43 +0000 (GMT) Received: from mindfields.energyhq.es.eu.org (73.Red-213-97-200.pooles.rima-tde.net [213.97.200.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA0E643D31; Thu, 2 Dec 2004 06:55:39 +0000 (GMT) (envelope-from flynn@energyhq.es.eu.org) Received: from scienide.energyhq.es.eu.org (scienide.energyhq.es.eu.org [192.168.100.1]) by mindfields.energyhq.es.eu.org (Postfix) with SMTP id C1BF034FE8; Thu, 2 Dec 2004 07:55:36 +0100 (CET) Date: Thu, 2 Dec 2004 07:55:30 +0100 From: Miguel Mendez To: "Kamal R. Prasad" Message-Id: <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> In-Reply-To: <41AEA4B8.6080508@acm.org> References: <41AE3F80.1000506@freebsd.org> <98CE9C0241F1FC59BB8F0547@[192.168.1.16]> <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> X-Mailer: Sylpheed version 0.9.99-gtk2-20041024 (GTK+ 2.4.13; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Thu__2_Dec_2004_07_55_30_+0100_xTa2dyNsftvMXwT3" cc: jcw@highperformance.net cc: hackers@freebsd.org cc: scottl@freebsd.org cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 06:55:44 -0000 --Signature=_Thu__2_Dec_2004_07_55_30_+0100_xTa2dyNsftvMXwT3 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Thu, 02 Dec 2004 10:44:32 +0530 "Kamal R. Prasad" wrote: [Please don't top-post] > I find X windows to be a bit too compute intensive. Maybe something > like apple's interface would be a good alternative [for those who > don't need X-windows' powerful graphic features]. What makes you think so? X was originally desgined for systems with little memory and processing power, certainly a lot less than today's AMD and Intel space heaters. There are some features that do indeed require more CPU, like antialiasing. That's the price to pay for eye candy. Things like the composite and damage extensions do wonders to help in those areas and make things like true transparency and alpha blending possible. So, in time, X won't be that different from Aqua in its use of hardware. The lack of speed in some apps can be blamed mostly on the toolkits. GTK+ 1.2 was a speed demon, GTK+ 2.x is a lot slower. There are some people working on a fast Pango code path that could make english text rendering fast again. X gives you network transparency out of the box. I used an old SGI Indy as an X term to connect to my FreeBSD box for years, and it worked like a charm over a 10Mbit connection. Replacing X means writing something that's API compatible, or writing an X server on top of your new display system, so that you don't have to throw the thousands of X apps into the trashcan. About some of the other comments in the thread. IMHO using bsdinstaller as a base could be beneficial for both groups and save duplicated work. I'm sure they'll be glad to get internacionalization patches. I agree that a journaled filesystem is really needed if you want to manage multi TiB partitions. As rock solid and tested softupdates is, fsck is not an acceptable solution in this case. Some people were working on a port of XFS, has any progress been made? I tried contacting them some time ago, but never got an answer. Sounds like a very interesting, though. Cheers, -- Miguel Mendez | lea gfx_lib(pc),a1 http://www.energyhq.es.eu.org | moveq #0,d0 PGP Key: 0xDC8514F1 | move.l 4.w,a6 Note: All HTML mail goes to /dev/null | jsr -552(a6) --Signature=_Thu__2_Dec_2004_07_55_30_+0100_xTa2dyNsftvMXwT3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBrrxlnLctrNyFFPERAoDuAKCSUllmrrJ4eaURl0tzPtkEeqtwpACfYRdD tX7U7jnM5i5lY5EfB++TYx8= =HXfX -----END PGP SIGNATURE----- --Signature=_Thu__2_Dec_2004_07_55_30_+0100_xTa2dyNsftvMXwT3-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 07:12:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41FA316A4CE for ; Thu, 2 Dec 2004 07:12:30 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id A1E8D43D5C for ; Thu, 2 Dec 2004 07:12:29 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 39776 invoked from network); 2 Dec 2004 06:58:20 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 2 Dec 2004 06:58:20 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB26wJ4C082472; Thu, 2 Dec 2004 07:58:19 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB26wJCp082471; Thu, 2 Dec 2004 07:58:19 +0100 (CET) (envelope-from pho) Date: Thu, 2 Dec 2004 07:58:19 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041202065819.GA82433@peter.osted.lan> References: <20041201055115.I18185@mail.chesapeake.net> <20041201160351.V18185@mail.chesapeake.net> <20041201223725.GA80282@peter.osted.lan> <20041201184238.K18185@mail.chesapeake.net> <20041201185146.W18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201185146.W18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 07:12:30 -0000 On Wed, Dec 01, 2004 at 06:52:19PM -0500, Jeff Roberson wrote: > On Wed, 1 Dec 2004, Jeff Roberson wrote: > > > On Wed, 1 Dec 2004, Peter Holm wrote: > > > > > On Wed, Dec 01, 2004 at 04:11:50PM -0500, Jeff Roberson wrote: > > > > On Wed, 1 Dec 2004, Peter Holm wrote: > > > > > > > > > On Wed, Dec 01, 2004 at 05:54:49AM -0500, Jeff Roberson wrote: > > > > > > I have updated the patch at: > > > > > > > > > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > > > > > > > > > > > > > I got a page fault in kern/vfs_vnops.c:542 due to vp->v_mount == NULL. > > > > > > > > > > More info at http://www.holm.cc/stress/log/jeff03.html > > > > > > > > The v_mount should only be NULL very briefly for the rootdevvp. What is > > > > your setup here? Any filesystems other than devfs and ffs? > > > $ mount > > > /dev/ad0s1a on / (ufs, local) > > > devfs on /dev (devfs, local) > > > /dev/ad0s1e on /tmp (ufs, NFS exported, local, soft-updates) > > > /dev/ad0s1f on /usr (ufs, local, soft-updates) > > > /dev/ad0s1d on /var (ufs, local, soft-updates) > > > procfs on /proc (procfs, local) > > > linprocfs on /usr/compat/linux/proc (linprocfs, local) > > > > > > >I think that > > > > deadfs might not set a mountpoint either.. DId you do a forced unmount? > > > No. > > > > I think I know how I'm going to have to fix this. > > > > > > > > > > Got a new one for you: > > > 1) panic: wrong b_bufobj 0 should be 0xc2679c10 > > > 2) panic: unexpected clean buffer 0xc6624bc8 > > > > > > http://www.holm.cc/stress/log/jeff04.html > > > > I fixed your last panic. The new patch is up at the same URL. I'll look > > at these now, thanks. This tool is really working out well. > > Also fixed the unexpected clean buffer. That was mostly just a bad > assert. I'm still baffled by wrong bufobj. > OK. I just do not seem to be able to get past the double panic problem: $ grep -A 3 ppanic /tmp/tip11.log ppanic: unexpected clean buffer 0xc6624bc8 cpuid = 0 KDB: enter: panic [thread pid 54 tid 100042 ] -- ppanic: unexpected clean buffer 0xc6667ec0 cpuid = 0 KDB: enter: panic [thread pid 54 tid 100042 ] -- ppanic: unexpected clean buffer 0xc66564e0 cpuid = 0 KDB: enter: panic [thread pid 54 tid 100042 ] so I've just updated with your last patch. - Peter > > > > > > > > - Peter > > > > > > > > > > > > > - Peter > > > > > > > > > > > It includes bug fixes for a handful of problems that were reported, and a > > > > > > few more that I found myself. It also unwinds giant from open(), which is > > > > > > a very high risk area, but after a few days of working out bugs it seems > > > > > > to be functioning quite well for me. > > > > > > > > > > > > I did a make -j3 buildworld on a box with a lowered maxvnodes. I also let > > > > > > 'stress' run for 8 loops or so until I ran into an unrelated KSE bug. I > > > > > > did some mount/unmount/single user tests as well. > > > > > > > > > > > > Use at your own risk. I still haven't locked quotas, so if you're using > > > > > > quota, don't run with this patch. > > > > > > > > > > > > Thanks, > > > > > > Jeff > > > > > > _______________________________________________ > > > > > > freebsd-current@freebsd.org mailing list > > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > > > -- > > > > > Peter Holm > > > > > _______________________________________________ > > > > > freebsd-current@freebsd.org mailing list > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > > > > -- > > > Peter Holm > > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 07:20:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57BE216A4CE for ; Thu, 2 Dec 2004 07:20:49 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA41C43D41 for ; Thu, 2 Dec 2004 07:20:48 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iB27Km0N054944; Thu, 2 Dec 2004 02:20:48 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iB27KlPf054933; Thu, 2 Dec 2004 02:20:47 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Thu, 2 Dec 2004 02:20:46 -0500 (EST) From: Jeff Roberson To: Peter Holm In-Reply-To: <20041202065819.GA82433@peter.osted.lan> Message-ID: <20041202021828.A18185@mail.chesapeake.net> References: <20041201055115.I18185@mail.chesapeake.net> <20041201223725.GA80282@peter.osted.lan> <20041201185146.W18185@mail.chesapeake.net> <20041202065819.GA82433@peter.osted.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 07:20:49 -0000 On Thu, 2 Dec 2004, Peter Holm wrote: > On Wed, Dec 01, 2004 at 06:52:19PM -0500, Jeff Roberson wrote: > > On Wed, 1 Dec 2004, Jeff Roberson wrote: > > > > > On Wed, 1 Dec 2004, Peter Holm wrote: > > > > > > > > > > > Got a new one for you: > > > > 1) panic: wrong b_bufobj 0 should be 0xc2679c10 > > > > 2) panic: unexpected clean buffer 0xc6624bc8 > > > > > > > > http://www.holm.cc/stress/log/jeff04.html > > > > > > I fixed your last panic. The new patch is up at the same URL. I'll look > > > at these now, thanks. This tool is really working out well. > > > > Also fixed the unexpected clean buffer. That was mostly just a bad > > assert. I'm still baffled by wrong bufobj. > > > > OK. I just do not seem to be able to get past the double panic problem: > > $ grep -A 3 ppanic /tmp/tip11.log > ppanic: unexpected clean buffer 0xc6624bc8 > cpuid = 0 > KDB: enter: panic > [thread pid 54 tid 100042 ] > -- > ppanic: unexpected clean buffer 0xc6667ec0 > cpuid = 0 > KDB: enter: panic > [thread pid 54 tid 100042 ] > -- > ppanic: unexpected clean buffer 0xc66564e0 > cpuid = 0 > KDB: enter: panic > [thread pid 54 tid 100042 ] > > so I've just updated with your last patch. Are you just running your stress program? Anything special about your setup? I see that these are valid bugs, but I'm not able to trigger them myself. > > - Peter From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 07:34:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1774416A4CE; Thu, 2 Dec 2004 07:34:02 +0000 (GMT) Received: from hotmail.com (bay2-dav1.bay2.hotmail.com [65.54.246.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id B44DA43D53; Thu, 2 Dec 2004 07:34:01 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 1 Dec 2004 23:34:00 -0800 Message-ID: Received: from 24.24.201.219 by BAY2-DAV1.phx.gbl with DAV; Thu, 02 Dec 2004 07:33:43 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: =?iso-8859-1?Q?S=F8ren_Schmidt?= References: <26249.1100342074@critter.freebsd.dk> <4195E5DB.2070302@DeepCore.dk> <4195FAF2.4050409@DeepCore.dk> Date: Wed, 1 Dec 2004 23:33:45 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-OriginalArrivalTime: 02 Dec 2004 07:34:00.0967 (UTC) FILETIME=[4A9FB170:01C4D841] cc: Garance A Drosihn cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 07:34:02 -0000 I can now assure you guys, that once the patch was applied, I *NEVER* get the WRITE_DMA warning message again. I've been running the server with the patch for over a week now. Question: Is there any chance this patch will make it into a stable release? IMHO, that would be great. I understand that this is "just a warning message" anyway, but still... Zoltan Zoltan Frombach wrote: > I will apply this patch first thing tomorrow. But I don't see how will I > see any difference? Does it put something into a log file? Shouldn't it? The change is that if you see the "WARNING interrupt seen" we know that it was the upper layers that used up the 5 secs of timeout, not that some of it was used by a disk being slow to respond. -Søren > Zoltan > > Poul-Henning Kamp wrote: > >> In message <4195E1FF.5090906@DeepCore.dk>, >> =?ISO-8859-1?Q?S=F8ren_Schmidt?= wri >> tes: >> >> >>>>> Timeout is 5 secs, which is a pretty long time in this context IMHO.. >>>> >>>> >>>> Five seconds counted from when ? >>> >>> >>> Now thats the nasty part :) >>> ATA starts the timeout when the request is issued to the device, so >>> theoretically the disk could take 4.9999 secs to complete the request >>> and then the timeout fires before the taskqueue gets its chance at it, >>> but IMHO thats pretty unlikely... >> >> >> I find that far more likely than kernel threads being stalled for that >> long. ATA disks doing bad-block stuff takes several seconds on some >> of the disks I've had my hands on. >> >>> Anyhow, I can just remove the warning from ATA if that makes anyone >>> happy, since its just a warning and ATA doesn't do anything with it at >>> all. >>> However, IMNHO this points at a problem somewhere that we should better >>> understand and fix instead. >> >> >> I would prefer you reset the timer to five seconds in your interrupt >> routine so we can see exactly on which side of that the time is spent. > > > It would be even better to time how long both ops take and be able to > get that via a sysctl or something (I have that on my TODO list but its > loooong :) ). > > Anyhow resetting it is easy (patch against 5.3R): > > Index: ata-queue.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/ata/ata-queue.c,v > retrieving revision 1.32.2.5 > diff -u -r1.32.2.5 ata-queue.c > --- ata-queue.c 24 Oct 2004 09:27:37 -0000 1.32.2.5 > +++ ata-queue.c 13 Nov 2004 10:44:40 -0000 > @@ -216,6 +216,9 @@ > ata_completed(request, 0); > } > else { > + if (!dumping) > + callout_reset(&request->callout, request->timeout * hz, > + (timeout_t*)ata_timeout, request); > if (request->bio && !(request->flags & ATA_R_TIMEOUT)) { > ATA_DEBUG_RQ(request, "finish bio_taskqueue"); > bio_taskqueue(request->bio, (bio_task_t *)ata_completed, > request); From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 07:49:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1C5F16A4CE for ; Thu, 2 Dec 2004 07:49:11 +0000 (GMT) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 3A6F443D5D for ; Thu, 2 Dec 2004 07:49:11 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 15240 invoked from network); 2 Dec 2004 07:49:10 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 2 Dec 2004 07:49:10 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB27n9of082710; Thu, 2 Dec 2004 08:49:09 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB27n87u082709; Thu, 2 Dec 2004 08:49:08 +0100 (CET) (envelope-from pho) Date: Thu, 2 Dec 2004 08:49:08 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041202074908.GA82634@peter.osted.lan> References: <20041201055115.I18185@mail.chesapeake.net> <20041201160351.V18185@mail.chesapeake.net> <20041201223725.GA80282@peter.osted.lan> <20041201184238.K18185@mail.chesapeake.net> <20041201185146.W18185@mail.chesapeake.net> <20041202065819.GA82433@peter.osted.lan> <20041202021828.A18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041202021828.A18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 07:49:11 -0000 On Thu, Dec 02, 2004 at 02:20:46AM -0500, Jeff Roberson wrote: > On Thu, 2 Dec 2004, Peter Holm wrote: > > > On Wed, Dec 01, 2004 at 06:52:19PM -0500, Jeff Roberson wrote: > > > On Wed, 1 Dec 2004, Jeff Roberson wrote: > > > > > > > On Wed, 1 Dec 2004, Peter Holm wrote: > > > > > > > > > > > > > > Got a new one for you: > > > > > 1) panic: wrong b_bufobj 0 should be 0xc2679c10 > > > > > 2) panic: unexpected clean buffer 0xc6624bc8 > > > > > > > > > > http://www.holm.cc/stress/log/jeff04.html > > > > > > > > I fixed your last panic. The new patch is up at the same URL. I'll look > > > > at these now, thanks. This tool is really working out well. > > > > > > Also fixed the unexpected clean buffer. That was mostly just a bad > > > assert. I'm still baffled by wrong bufobj. > > > > > > > OK. I just do not seem to be able to get past the double panic problem: > > > > $ grep -A 3 ppanic /tmp/tip11.log > > ppanic: unexpected clean buffer 0xc6624bc8 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 54 tid 100042 ] > > -- > > ppanic: unexpected clean buffer 0xc6667ec0 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 54 tid 100042 ] > > -- > > ppanic: unexpected clean buffer 0xc66564e0 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 54 tid 100042 ] > > > > so I've just updated with your last patch. > > Are you just running your stress program? Yes. > Anything special about your > setup? I see that these are valid bugs, but I'm not able to trigger them > myself. > No ... I don't think so. I run on a ASUS P4P800 with a Intel Celeron CPU 1.80GHz CPU and a 76319MB Seagate disk. The config is GENERIC with BREAK_TO_DEBUGGER added. My /etc/sysctl.conf contains kern.threads.virtual_cpu=16 + debug.ddb_use_printf=1. Uptime for the last three double panics were 1h23m12s, 1h1m27s and 4h35m45s. I've just booted with your last patch and will let you know how it goes. - Peter > > > > - Peter -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 07:50:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F34216A4CE for ; Thu, 2 Dec 2004 07:50:46 +0000 (GMT) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA91B43D48 for ; Thu, 2 Dec 2004 07:50:45 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.1/8.13.1) with ESMTP id iB27ob3H067330; Wed, 1 Dec 2004 23:50:38 -0800 (PST) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.1/8.13.1/Submit) id iB27oao2067329; Wed, 1 Dec 2004 23:50:36 -0800 (PST) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: Miguel Mendez In-Reply-To: <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> References: <41AE3F80.1000506@freebsd.org> <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1101973835.66100.15.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 01 Dec 2004 23:50:36 -0800 cc: "Kamal R. Prasad" cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 07:50:46 -0000 On Wed, 2004-12-01 at 22:55, Miguel Mendez wrote: > On Thu, 02 Dec 2004 10:44:32 +0530 > "Kamal R. Prasad" wrote: > > [Please don't top-post] > > > I find X windows to be a bit too compute intensive. Maybe something > > like apple's interface would be a good alternative [for those who > > don't need X-windows' powerful graphic features]. > > What makes you think so? X was originally desgined for systems with > little memory and processing power, certainly a lot less than today's > AMD and Intel space heaters. There are some features that do indeed > require more CPU, like antialiasing. That's the price to pay for eye > candy. Things like the composite and damage extensions do wonders to > help in those areas and make things like true transparency and alpha > blending possible. So, in time, X won't be that different from Aqua in > its use of hardware. > > The lack of speed in some apps can be blamed mostly on the toolkits. > GTK+ 1.2 was a speed demon, GTK+ 2.x is a lot slower. There are some > people working on a fast Pango code path that could make english text > rendering fast again. > > X gives you network transparency out of the box. I used an old SGI Indy > as an X term to connect to my FreeBSD box for years, and it worked like > a charm over a 10Mbit connection. > > Replacing X means writing something that's API compatible, or writing an > X server on top of your new display system, so that you don't have to > throw the thousands of X apps into the trashcan. Let me see if I can come up with a sensible response to this, which I've lost the original message for: We already have the stuff to do all of the pretty Apple eye-candy in X.Org 6.8, with the Composite/Damage/Fixes extensions. The same eye-candy support is a requirement to provide the perception of speed that you get out of other modern graphical systems, by removing the latency for redrawing when moving/mapping windows. You can use xcompmgr -a and compare what that gets you when dragging windows -- it's pretty decent. The problem we hit is when you try to add eye-candy, such as xcompmgr -c (drop shadows, fadey menus, etc.), things bog down. These are exactly the "powerful graphic features" that the combination of Composite and Render allow, and they're just like the operations Apple uses for all of their fancy stuff. The problem is that we aren't hardware-accelerating them currently. I've worked on building a moderately dumb X Server for ATI cards, and it gives apple-like performance on even Rage 128s -- it's not terribly complicated, just a matter of pushing things to hardware and avoiding the ~50x speed penalty of CPU reading from framebuffer. Now what we need to do is get a sensible acceleration architecture into X.Org so we can get these operations in hardware for all of the chipsets that we've got 3d docs or drivers for (ati, some nvidia, 3dfx, intel, mga, trident, sis, savage, gamma, and a bunch of others I'm forgetting). In short: There are no problems with X, except that we need somebody to bring us a sane acceleration architecture. I'm hoping I can get a job doing that this summer, as it'll be a significant undertaking that I can't get to while in my last year of school. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org Thank goodness for the 22nd Amendment From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 08:00:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51B9816A4CF for ; Thu, 2 Dec 2004 08:00:04 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id D528343D2D for ; Thu, 2 Dec 2004 08:00:03 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iB2803i1005013 for ; Thu, 2 Dec 2004 00:00:03 -0800 (PST) (envelope-from marcel@xcllnt.net) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <2C07BD77-4438-11D9-8117-000D93C47836@xcllnt.net> Content-Type: text/plain; charset=US-ASCII; format=flowed To: current@freebsd.org From: Marcel Moolenaar Date: Thu, 2 Dec 2004 00:00:03 -0800 X-Mailer: Apple Mail (2.619) Subject: kernel page fault (null-pointer dereference): flock(2) and NFS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 08:00:04 -0000 itanium% vi geom_gpt.c fatal kernel trap (cpu 0): trap vector = 0x14 (Page Not Present) cr.iip = 0xe000000004546560 cr.ipsr = 0x1010080a6018 (ac,mfl,ic,i,dt,dfh,rt,cpl=0,it,ri=0,bn) cr.isr = 0x400000000 (code=0,vector=0,r,ei=0) cr.ifa = 0x0 curthread = 0xe000000062dae780 pid = 520, comm = vi [thread pid 520 tid 100063 ] Stopped at ufsfifo_write+0x50: [M0] ld8 r14=[r8],0x8 db> tr Tracing pid 520 tid 100063 td 0xe000000062dae780 ufsfifo_write(0xa0000000334c70a8, 0xa0000000334c7048, 0xe000000062dae780, 0xe0000000043cee90) at ufsfifo_write+0x50 vn_rdwr(0x1, 0xe000000063483000, 0xe0000000634831b0, 0x1b0, 0x0, 0x1, 0x1001, 0xe0000000002a3d00) at vn_rdwr+0x670 nfs_dolock(0x0, 0xe000000063483000, 0xe000000004736f40) at nfs_dolock+0x810 nfs_advlock(0xa0000000334c73c0, 0xe00000000428e630, 0x40c, 0x891) at nfs_advlock+0xb0 flock(0xe000000062dae780, 0xa0000000334c74f0, 0xa0000000334c73f0, 0xe000000060805a00) at flock+0x380 syscall(0xa0000000334c7400, 0x6, 0xe000000062dae780, 0xe0000000046ebd70, 0x83, 0xe0000000631b5900, 0xe0000000631b5b18, 0xa0000000334c74e8) at syscall+0x790 epc_syscall_return() at epc_syscall_return db> -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 08:01:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31FA416A56E; Thu, 2 Dec 2004 08:01:13 +0000 (GMT) Received: from smtpq3.home.nl (smtpq3.home.nl [213.51.128.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8ECB143D45; Thu, 2 Dec 2004 08:01:10 +0000 (GMT) (envelope-from dodell@sitetronics.com) Received: from [213.51.128.133] (port=60395 helo=smtp2.home.nl) by smtpq3.home.nl with esmtp (Exim 4.30) id 1CZltl-0000AY-8m; Thu, 02 Dec 2004 09:01:09 +0100 Received: from cc740438-a.deven1.ov.home.nl ([82.75.136.183]:3098 helo=[192.168.1.100]) by smtp2.home.nl with esmtp (Exim 4.30) id 1CZltk-0006xk-92; Thu, 02 Dec 2004 09:01:08 +0100 Message-ID: <41AECBC5.2060608@sitetronics.com> Date: Thu, 02 Dec 2004 09:01:09 +0100 From: "Devon H. O'Dell" User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ryan Sommers References: <41AE3F80.1000506@freebsd.org> <19549.128.101.36.205.1101942657.squirrel@128.101.36.205> In-Reply-To: <19549.128.101.36.205.1101942657.squirrel@128.101.36.205> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AtHome-MailScanner-Information: Please contact support@home.nl for more information X-AtHome-MailScanner: Found to be clean cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 08:01:13 -0000 Ryan Sommers wrote: > Scott Long said: > >>2. New installer. I know some people still consider this a joke, but >>the reality is that sysinstall is no longer state of the art. It's >>fairly good at the simple task that it does, but it's becoming harder >>and harder to fix bugs and extend functionality in it. It's also >>fairly unfriendly to those of us who haven't been using it since 1995. >>The DFly folks have some very interesting work in this area >>(www.bsdinstaller.com) and it would be very good to see if we can >>collaborate with them on it. > > > I've spent a good deal of time taking notes and diagrams of what I wanted > from a new installer. However, time constraints have kept me from actually > putting any of it to code yet. > > I've looked at the DFly installed quite a bit and I like what it offers, > however, I have a few complaints with it. Quite honestly I wasn't > impressed with the code. > > Another issue I had with the dfly installer was one point I believe needs > to be central to any next-gen installer. Internationalisation. My idea of > an installer front-end would use a dynamically loadable language library. > All resources of the front-end (ie strings, images, etc) would be packaged > into a seperate language-pack. These language-packs can then be grouped > together into a language library. A few basic packs would be distributed > with the default library but other libraries could easily be substituted > to make localized distribution sets with little trouble. > > The benefit of this is that instead of translating the code you would only > need to translate the language-(pack|library). I think this would greatly > simplify translation and make a seperation between language and the > front-end code. > > This is where my complaint with Dfly comes in, upon reading the source, > there are string constants everywhere. Perhaps I am missing something, but > this means that in order to supply localization support much work would > need to be done to find some scheme that doesn't mean translating the > source. > > I have quite a bit of notes on seperation and even down to specific > methods and sub-libraries necessary for the back-end. Perhaps if I have > some time soon I'll put it into a PDF somewhere. > > Has anyone else put much thought into this? Yes, we have. I18n is something that we're actively working on implementing, and is something that we take quite seriously. I know that not very many FreeBSD developers use IRC, but we are all available in #dfinstaller on EFNet. We're using gettext for this at the moment. Kind regards, Devon H. O'Dell From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 08:33:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6A0716A4CE for ; Thu, 2 Dec 2004 08:33:55 +0000 (GMT) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C71A43D58 for ; Thu, 2 Dec 2004 08:33:55 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (unknown [82.233.239.98]) by postfix4-2.free.fr (Postfix) with ESMTP id 7E85D23C927; Thu, 2 Dec 2004 09:33:54 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 9A89E412C; Thu, 2 Dec 2004 09:32:55 +0100 (CET) Date: Thu, 2 Dec 2004 09:32:55 +0100 From: Jeremie Le Hen To: Jeff Roberson Message-ID: <20041202083254.GP79919@obiwan.tataz.chchile.org> References: <20041201055115.I18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041201055115.I18185@mail.chesapeake.net> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 08:33:55 -0000 > I have updated the patch at: > > http://www.chesapeake.net/~jroberson/smpffs.diff > > It includes bug fixes for a handful of problems that were reported, and a > few more that I found myself. It also unwinds giant from open(), which is > a very high risk area, but after a few days of working out bugs it seems > to be functioning quite well for me. FYI, I ran your patch since yesterday evening and the uptime is now 10:30. It seems to have successfully passed the nightly periodic stuff. I'm now recompiling my kernel with the third version of your patch, thanks to Peter Holm. Note this is my old notebook, and I don't have heavy applications running on it, except Xorg and Firefox. Here are my mounts: z6po:root# mount /dev/ad0s1a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/md0 on /etc (ufs, local, read-only, union) procfs on /proc (procfs, local) /dev/ad0s1e on /usr (ufs, local) /dev/ad0s1d on /var (ufs, local) 192.168.1.222:/usr/ports on /usr/ports (nfs) 192.168.1.222:/bigone/space on /usr/space (nfs) 192.168.1.222:/usr/home/cvs on /cvs (nfs) Thanks a lot for your work. -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 08:48:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B1FD16A4CE for ; Thu, 2 Dec 2004 08:48:21 +0000 (GMT) Received: from postfix3-2.free.fr (postfix3-2.free.fr [213.228.0.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 039D643D49 for ; Thu, 2 Dec 2004 08:48:21 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (unknown [82.233.239.98]) by postfix3-2.free.fr (Postfix) with ESMTP id 22049C019; Thu, 2 Dec 2004 09:48:20 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 98071412C; Thu, 2 Dec 2004 09:47:20 +0100 (CET) Date: Thu, 2 Dec 2004 09:47:20 +0100 From: Jeremie Le Hen To: Eric Anholt Message-ID: <20041202084720.GQ79919@obiwan.tataz.chchile.org> References: <41AE3F80.1000506@freebsd.org> <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> <1101973835.66100.15.camel@leguin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1101973835.66100.15.camel@leguin> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 08:48:21 -0000 > In short: There are no problems with X, except that we need somebody to > bring us a sane acceleration architecture. I'm hoping I can get a job > doing that this summer, as it'll be a significant undertaking that I > can't get to while in my last year of school. Remember that very recently Microsoft announced on their own website that DirectX was running on the FreeBSD platform :-). [ This is a joke, for those who didn't see the famous web page. ] -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 09:00:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACF5016A4CE; Thu, 2 Dec 2004 09:00:00 +0000 (GMT) Received: from kraid.nerim.net (smtp-104-thursday.nerim.net [62.4.16.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE59643D45; Thu, 2 Dec 2004 08:59:59 +0000 (GMT) (envelope-from e-masson@kisoft-services.com) Received: from srvbsdnanssv.interne.kisoft-services.com (kisoftacces2.net1.nerim.net [62.212.107.52]) by kraid.nerim.net (Postfix) with ESMTP id 758A041B52; Thu, 2 Dec 2004 09:59:58 +0100 (CET) Received: from localhost (localhost [127.0.0.1])06594C37C; Thu, 2 Dec 2004 09:59:58 +0100 (CET) Received: from srvbsdnanssv.interne.kisoft-services.com ([127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63158-07; Thu, 2 Dec 2004 09:59:48 +0100 (CET) Received: by srvbsdnanssv.interne.kisoft-services.com (Postfix, from userid 1001) id 2EE5CC372; Thu, 2 Dec 2004 09:59:48 +0100 (CET) To: Scott Long From: Eric Masson In-Reply-To: <41AE3F80.1000506@freebsd.org> (Scott Long's message of "Wed, 01 Dec 2004 15:02:40 -0700") References: <41AE3F80.1000506@freebsd.org> X-Operating-System: FreeBSD 5.3-STABLE i386 Date: Thu, 02 Dec 2004 09:59:47 +0100 Message-ID: <86d5xtf530.fsf@srvbsdnanssv.interne.kisoft-services.com> User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at interne.kisoft-services.com cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 09:00:00 -0000 >>>>> "Scott" == Scott Long writes: Hi, Scott> 1. Keyboard multiplexer. We are running into problems with Scott> making ps/2 and USB/bluetooth keyboards work together and work Scott> with KVMs. Having a virtual keyboard device that multiplexes the Scott> various real keyboard devices and handles hotplug can solve this Scott> mess pretty effectively. I know that there has been a lot of Scott> talk about this on mailing lists recently but I don't know how Scott> much progress is being made so I'm listing it here. NetBSD's wscons seems to fit in this scheme, OpenBSD has adopted it as well (the most featured implementation is in NetBSD/i386). Scott> 6. Overhaul CAM, add iSCSI. CAM is very parallel-SCSI centric Scott> right now. I have some work-in-progress in Perforce to address Scott> this, but it's pretty minimal. The parallel SCSI knowledge needs Scott> to be separated out and the stack need to be able to cleanly Scott> deal with iSCSI, SCSI, SAS, and maybe even ATA transports. There Scott> is a Lucent implementation of iSCSI for FreeBSD 4.x that could Scott> be a useful reference, though it's a monolithic stack that Scott> doesn't really address the shortcomings of CAM. Having iSCSI Scott> infrastructure that supported both hardware and software Scott> implementations would be ideal. It would be really nice to be able to play in the iscsi field. It seems that work has been done in this area by Wasabi (not published in NetBSD, iirc) Very appealing goals, if only I were a decent coder... Éric Masson -- je pense pas que ce soit toi....tu es bien trop vicieux pour agir de cette façon. Toi ton genre, c'est plus de contacter banque direct en esperant que je n'auras pas mes cadeaux de parrainages!!!!! -+- JD in : Petit neuneu Noël -+- From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 09:16:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8491116A4CE; Thu, 2 Dec 2004 09:16:15 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id A58F343D53; Thu, 2 Dec 2004 09:16:14 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iB29G9eC096258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 2 Dec 2004 12:16:13 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iB29G84F030745 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 12:16:08 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id iB29G4pC030744; Thu, 2 Dec 2004 12:16:04 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Thu, 2 Dec 2004 12:16:04 +0300 From: Gleb Smirnoff To: Sean McNeil , mlaier@freebsd.org, se@freebsd.org Message-ID: <20041202091604.GA30622@cell.sick.ru> References: <1101867805.8266.6.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <1101867805.8266.6.camel@server.mcneil.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Status: Clean cc: current@freebsd.org Subject: Re: panic today when doing shutdown and boot warnings X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 09:16:15 -0000 On Tue, Nov 30, 2004 at 06:23:25PM -0800, Sean McNeil wrote: S> I haven't noticed these before so I thought I would mention them: S> S> Nov 30 18:01:39 server kernel: Timecounters tick every 1.000 msec S> Nov 30 18:01:39 server kernel: WARNING: attempt to net_add_domain(local) after domainfinalize() S> Nov 30 18:01:39 server kernel: WARNING: attempt to net_add_domain(internet6) after domainfinalize() S> Nov 30 18:01:39 server kernel: WARNING: attempt to net_add_domain(route) after domainfinalize() S> Nov 30 18:01:39 server kernel: WARNING: attempt to net_add_domain(internet) after domainfinalize() S> S> I have no idea what they mean. AFAIU, these lines have nothing to do with your panic. However, we should get rid of them. Max, why do you have (domain_init_status < 2) in INVARIANTed case and ((domain_init_status != 0) in default case? + KASSERT(domain_init_status >= 1, + ("attempt to net_add_domain(%s) before domaininit()", + dp->dom_name)); + KASSERT(domain_init_status < 2, + ("attempt to net_add_domain(%s) after domainfinalize()", + dp->dom_name)); +#ifndef INVARIANTS + if (domain_init_status == 0) + printf("WARNING: attempt to net_add_domain(%s) before " + "domaininit()\n", dp->dom_name); + if (domain_init_status != 0) + printf("WARNING: attempt to net_add_domain(%s) after " + "domainfinalize()\n", dp->dom_name); +#endif -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 10:33:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2E8E16A4CE; Thu, 2 Dec 2004 10:33:41 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B5FC43D2D; Thu, 2 Dec 2004 10:33:41 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB2AXerc093693; Thu, 2 Dec 2004 11:33:40 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Scott Long From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 01 Dec 2004 15:02:40 MST." <41AE3F80.1000506@freebsd.org> Date: Thu, 02 Dec 2004 11:33:40 +0100 Message-ID: <93692.1101983620@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 10:33:42 -0000 In message <41AE3F80.1000506@freebsd.org>, Scott Long writes: >All, > >I know that I said last month that we were going to stop promising >specific features for the next major release. However, I'd like to >throw out a list of things that would be really nice to have in the >future, whether its 6.0 or 7.0 or whatever. >[...] >1. Keyboard multiplexer. [...] >2. New installer. [...] >3. Native PCI Express support. [...] >4. Journaled filesystem. [...] >5. Clustered FS support. [...] >6. Overhaul CAM, add iSCSI. [...] I agree on all of the above but I think we also need to have things on the list that doesn't take super hackers, and architectural reviews. So let us add the following points which I think are just as, if not more important for FreeBSDs future: 7. More people writing FreeBSD related articles for online and traditional media. If you have never written a piece about FreeBSD, how about sending something to your local IT trade rag ? Heck, even your local paper will probably run it if you send them a piece. 8. More people stomping for FreeBSD in universities and schools. Have you actually offered the science/IT teachers at the local hi-school to pop around and give a lesson on this open source phenomena to their pupils ? Or call your local college and ask if they need a teaching assistant for their evening courses in IT ? 9. A band of happy 1st line reponders dealing with PRs etc. We're getting better at this, but one way to really gain users is to help them when they need it most: right when they begin. 10. A more dynamic and interesting www.freebsd.org frontpage. Come on, at least we should be able to beat the "Congressional Record" when it comes to being interesting. 11. More people attending BSDcon conferences. Come to BSDcan2005! come to the next EuroBSDcon or AsiaBSDcon. Or make your own mini conference! Many Linux User groups would welcome you if you offered to give a talk about FreeBSD on one of their evenings. 12. Research/Coding grants (3/6/12 months) from the FreeBSD Foundation and other deep(er) pockets to help some of the heavy lifting happen. We're not only in it for the money, but money surely helps. And I'd like to stress that none of the above requires you to get permission from the core team, just go out and do it! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 10:44:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F5F516A4CE for ; Thu, 2 Dec 2004 10:44:26 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35B2643D2D for ; Thu, 2 Dec 2004 10:44:25 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 25878 invoked from network); 2 Dec 2004 10:35:28 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for <>; 2 Dec 2004 10:35:28 -0000 Message-ID: <41AEF204.2070402@freebsd.org> Date: Thu, 02 Dec 2004 11:44:20 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "" References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit cc: current@FreeBSD.org Subject: Re: malloc(0) returns an invalid address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 10:44:26 -0000 JINMEI Tatuya / 神明é”哉 wrote: >>>>>>On Wed, 1 Dec 2004 07:49:54 -0800, >>>>>>"David Schwartz" said: > >>>% ./a.out >>>address of p is 0x800 >>>zsh: 645 segmentation fault (core dumped) ./a.out > >> This should fault. Although the return value of 'malloc(0)' is a valid >>pointer, once you cast it to a 'char *', you cannot dereference it because >>it does not point to a character. This same problem would occur with >>'malloc(1)' and 'int *'. > > I expected the answer:-) This is probably a matter of the definition > of "validness", and I won't argue about this point. (and, of course, > it cannot be justified to dereference a zero-length pointer, whether > the result is segfault or not) > > BTW: the "same problem" (of segfault) does actually NOT occur with > malloc(1) and int * on FreeBSD 5.3 (i386). I suspect malloc(3) takes > a special action with the size of zero. man malloc(3) and look for options 'V' and 'X'. >>>So, if we wanted to call 0x800 "a valid pointer just with >>>not-enough-size", it would be fine. But then we need to implement the >>>same logic in the kernel to provide consistent behavior. (I would >>>"fix" the malloc behavior though). > >> The malloc behavior is not broken, so it cannot be fixed. The kernel check >>semantics in 'useracc' are wrong for zero lengths. > > Okay, I'll be happy as long as the library and the kernel provide the > consistent behavior on which pointer is "valid". -- Andre From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 10:55:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F05316A4CE; Thu, 2 Dec 2004 10:55:07 +0000 (GMT) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCD0143D39; Thu, 2 Dec 2004 10:55:06 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from ocean.jinmei.org (unknown [2001:200:0:8002:200:39ff:fed7:e2e4]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id AE6AE15210; Thu, 2 Dec 2004 19:55:05 +0900 (JST) Date: Thu, 02 Dec 2004 19:55:15 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Andre Oppermann In-Reply-To: <41AEF204.2070402@freebsd.org> References: <41AEF204.2070402@freebsd.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: current@FreeBSD.org Subject: Re: malloc(0) returns an invalid address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 10:55:07 -0000 >>>>> On Thu, 02 Dec 2004 11:44:20 +0100, >>>>> Andre Oppermann said: >> I expected the answer:-) This is probably a matter of the definition >> of "validness", and I won't argue about this point. (and, of course, >> it cannot be justified to dereference a zero-length pointer, whether >> the result is segfault or not) >> >> BTW: the "same problem" (of segfault) does actually NOT occur with >> malloc(1) and int * on FreeBSD 5.3 (i386). I suspect malloc(3) takes >> a special action with the size of zero. > man malloc(3) and look for options 'V' and 'X'. I've already done this, and, sorry, this is irrelevant to this problem. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 10:59:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15D2716A4CE; Thu, 2 Dec 2004 10:59:36 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 715ED43D41; Thu, 2 Dec 2004 10:59:35 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iB2AxYEW015524; Thu, 2 Dec 2004 05:59:34 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iB2AxYre078620; Thu, 2 Dec 2004 05:59:34 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 92CC07306E; Thu, 2 Dec 2004 05:59:34 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041202105934.92CC07306E@freebsd-current.sentex.ca> Date: Thu, 2 Dec 2004 05:59:34 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/614/Wed Dec 1 10:44:43 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Status: Clean Subject: [current tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 10:59:36 -0000 TB --- 2004-12-02 09:45:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-12-02 09:45:00 - starting CURRENT tinderbox run for alpha/alpha TB --- 2004-12-02 09:45:00 - checking out the source tree TB --- 2004-12-02 09:45:00 - cd /home/tinderbox/CURRENT/alpha/alpha TB --- 2004-12-02 09:45:00 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-12-02 09:51:38 - building world (CFLAGS=-O2 -pipe) TB --- 2004-12-02 09:51:38 - cd /home/tinderbox/CURRENT/alpha/alpha/src TB --- 2004-12-02 09:51:38 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-12-02 10:58:32 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-02 10:58:32 - cd /home/tinderbox/CURRENT/alpha/alpha/src TB --- 2004-12-02 10:58:32 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Dec 2 10:58:32 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] /tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica/actypes.h:168:2: #error ACPI_MACHINE_WIDTH not defined /tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica/actypes.h:277:2: #error unknown ACPI_MACHINE_WIDTH In file included from /tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica/acpi.h:129, from /tinderbox/CURRENT/alpha/alpha/src/sys/dev/pci/pci.c:63: /tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica/acmacros.h:377:2: #error unknown ACPI_MACHINE_WIDTH In file included from /tinderbox/CURRENT/alpha/alpha/src/sys/dev/pci/pci.c:64: /tinderbox/CURRENT/alpha/alpha/src/sys/dev/acpica/acpivar.h:31:21: acpi_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/obj/alpha/tinderbox/CURRENT/alpha/alpha/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/obj/alpha/tinderbox/CURRENT/alpha/alpha/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. TB --- 2004-12-02 10:59:34 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-12-02 10:59:34 - ERROR: failed to build generic kernel TB --- 2004-12-02 10:59:34 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 19:28:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E2AF16A4CE for ; Wed, 1 Dec 2004 19:28:57 +0000 (GMT) Received: from av10-1-sn2.hy.skanova.net (av10-1-sn2.hy.skanova.net [81.228.8.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA96F43D48 for ; Wed, 1 Dec 2004 19:28:56 +0000 (GMT) (envelope-from raggen@passagen.se) Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502) id 60C1737F84; Wed, 1 Dec 2004 20:28:55 +0100 (CET) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP id 517C43800A for ; Wed, 1 Dec 2004 20:28:55 +0100 (CET) Received: from trutta (h8n2fls302o1097.telia.com [81.229.196.8]) by smtp4-2-sn2.hy.skanova.net (Postfix) with SMTP id 350A537E46 for ; Wed, 1 Dec 2004 20:28:54 +0100 (CET) Message-Id: <3.0.32.20041201202852.0119a510@m1.431.telia.com> X-Sender: u43111868@m1.431.telia.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 01 Dec 2004 20:28:55 +0100 To: freebsd-current@freebsd.org From: Roger Olofsson Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Mailman-Approved-At: Thu, 02 Dec 2004 13:22:17 +0000 Subject: 6.0-CURRENT and ATAPI_IDENTIFY timed out and VIA MVP3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 19:28:57 -0000 Greetings from Sweden, I've been trying to find more information about the fact that one ata channel has stopped working after I upgraded from 5.2.1-p9 to 6.0 #0. The error comes when booting and looks like this: Dec 1 19:53:25 scomber kernel: ata1-slave: FAILURE - ATAPI_IDENTIFY timed out Dec 1 19:53:30 scomber kernel: ata1-slave: FAILURE - ATAPI_IDENTIFY timed out Dec 1 19:53:35 scomber kernel: ata1-master: FAILURE - ATA_IDENTIFY timed out Dec 1 19:53:40 scomber kernel: ata1-master: FAILURE - ATA_IDENTIFY timed out Needless to say both devices attached to ata1 (cdrom and HD) were found and working fine in 5.2.1-p9. I've tried replacing the cdrom and HD with others and combinations of them but all give same result. Bios finds cdrom and HD fine. When I run atacontrol list I get the following: scomber# atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI revision 3 Slave: ad1 ATA/ATAPI revision 4 ATA channel 1: Master: no device present Slave: no device present And atacontrol reinit 1 gives: scomber# atacontrol reinit 1 Master: no device present Slave: no device present My motherboard is an old Shuttle HOT-591p and has VIA MVP3 chipset for 2 ultra33 dma ide. I would be very grateful for any kinds of leads on solving this problem. It feels terrible to have a 'crippled' FreeBSD. Please answer to my email raggen@passagen.se. From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 14:40:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC2B716A4CE for ; Wed, 1 Dec 2004 14:40:30 +0000 (GMT) Received: from smtp.ruby.ocn.ne.jp (ruby.ocn.ne.jp [222.146.40.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F85943D4C for ; Wed, 1 Dec 2004 14:40:30 +0000 (GMT) (envelope-from toshi@ruby.ocn.ne.jp) Received: from localhost (p6194-ipadfx01sizuokaden.shizuoka.ocn.ne.jp [219.160.179.194]) by smtp.ruby.ocn.ne.jp (Postfix) with ESMTP id D0E814C2F; Wed, 1 Dec 2004 23:40:28 +0900 (JST) Date: Wed, 01 Dec 2004 23:40:07 +0900 (JST) Message-Id: <20041201.234007.226808332.toshi@ruby.ocn.ne.jp> To: current@freebsd.org From: SAITOU Toshihide In-Reply-To: <20041130081804.GA22353@xs4all.nl> References: <20041130081804.GA22353@xs4all.nl> X-GPG-fingerprint: 34B3 0B6A 8520 F5B0 EBC7 69F6 C055 9F8A 0D49 F8FC X-Mailer: Mew version 4.1.50 on Emacs 21.3.50 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 02 Dec 2004 13:22:17 +0000 Subject: Re: bash/readline coredumps X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 14:40:30 -0000 From: Michiel Boland Date: Tue, 30 Nov 2004 09:18:04 +0100 > Lately I am getting core dumps from bash (bash-2.05b.007_2 from ports). > To reproduce: type a command that spans multiple lines, like I couldn't reproduce a core dump by your instruction, but I had possibly experienced a similar/related bash core dump since around 5.3-RELEASE. $ ./bash $ /bin/ls -ld /var/db/pkg/v* Segmentation fault (core dumped) $ gdb ./bash bash.core #0 0x48213499 in memcpy () from /lib/libc.so.5 (gdb) bt #0 0x48213499 in memcpy () from /lib/libc.so.5 #1 0x080ba348 in xmbsrtowcs (dest=0x1d, src=0xbfbfe804, len=0, pstate=0xbfbfe760) at xmbsrtowcs.c:67 #2 0x080ba123 in xstrmatch (pattern=0x0, string=0x8104fe4 "cyrus-sasl-saslauthd-2.1.19", flags=5) at smatch.c:388 #3 0x080b6bcd in glob_vector (pat=0x810182c "v*", dir=0xbfbfe8e0 "/var/db/pkg/", flags=0) at glob.c:491 #4 0x080b7275 in glob_filename (pathname=0x8101820 "/var/db/pkg/v*", flags=0) at glob.c:768 #5 0x0807ff07 in shell_glob_filename (pathname=0x8101850 "/var/db/pkg/v*") at pathexp.c:254 #6 0x0807d10d in expand_word_list_internal (list=0x80ef3c0, eflags=31) at subst.c:6406 #7 0x08066d4b in execute_command_internal (command=0x0, asynchronous=0, pipe_in=-1, pipe_out=-1, fds_to_close=0x81017f0) at execute_cmd.c:2554 #8 0x08068b35 in execute_command (command=0x80ef300) at execute_cmd.c:324 #9 0x0805bb19 in reader_loop () at eval.c:143 #10 0x0805aad1 in main (argc=1, argv=0xbfbfed40, env=0xbfbfed48) at shell.c:680 (gdb) up #1 0x080ba348 in xmbsrtowcs (dest=0x1d, src=0xbfbfe804, len=0, pstate=0xbfbfe760) at xmbsrtowcs.c:67 67 memcpy(mbsbuf, *src, n + 1); (gdb) print mbsbuf $1 = 0x80ef3c0 "cyrus-sasl-saslauthd-2.1.19" (gdb) print src $2 = (const char **) 0xbfbfe804 #6 0x0807d10d in expand_word_list_internal (list=0x80ef3c0, eflags=31) at subst.c:6406 #7 0x08066d4b in execute_command_internal (command=0x0, asynchronous=0, pipe_in=-1, pipe_out=-1, fds_to_close=0x81017f0) at execute_cmd.c:2554 #8 0x08068b35 in execute_command (command=0x80ef300) at execute_cmd.c:324 #9 0x0805bb19 in reader_loop () at eval.c:143 #10 0x0805aad1 in main (argc=1, argv=0xbfbfed40, env=0xbfbfed48) at shell.c:680 (gdb) up #1 0x080ba348 in xmbsrtowcs (dest=0x1d, src=0xbfbfe804, len=0, pstate=0xbfbfe760) at xmbsrtowcs.c:67 67 memcpy(mbsbuf, *src, n + 1); (gdb) print mbsbuf $1 = 0x80ef3c0 "cyrus-sasl-saslauthd-2.1.19" (gdb) print src $2 = (const char **) 0xbfbfe804 (gdb) print *src $3 = 0x8104fe4 "cyrus-sasl-saslauthd-2.1.19" (gdb) print n $4 = 135286784 I finally migrate to bash3 (ports/shells/bash) and it seems ceased/lessened. SAITOU Toshihide From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 00:11:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30E8616A4CE; Thu, 2 Dec 2004 00:11:31 +0000 (GMT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 118EF43D41; Thu, 2 Dec 2004 00:11:31 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id B15E5148D9; Wed, 1 Dec 2004 18:11:30 -0600 (CST) Date: Wed, 1 Dec 2004 18:11:30 -0600 (CST) From: Mark Linimon X-X-Sender: linimon@pancho To: Scott Long In-Reply-To: <41AE3F80.1000506@freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Thu, 02 Dec 2004 13:22:17 +0000 cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 00:11:31 -0000 On Wed, 1 Dec 2004, Scott Long wrote: > 2. New installer. [... sysinstall] is fairly good at the simple > task that it does [ ... ] I'll put my bugmeister-hat on and simply say that query-pr suggests otherwise. I have not spent sufficient time examining each of the PRs to figure out what the breakdown is between 'bugs within sysinstall'/ 'unable to boot FreeBSD on hardware'/'user error' but IMHO the first group contains more than a handful of PRs. (the total # is 142.) This is not to say we should abandon the KISS principle and try to come up with some all-singing/all-dancing "thing"; in fact, the opposite. I'd rather we spent time on making something small and solid which would contain enough of its own documentation to prevent people from tearing their hair out while trying to use it. Unlike much of the rest of the system where we assume users have at least some familiarity with FreeBSD (and a working browser), we have to engineer an installer that assumes that both of those are false. Unfortunately for me I probably will never be able to work on this unless someone wants to pay me to work on FreeBSD full-time; too many other things are ahead of it in my personal FreeBSD queue ... mcl From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 05:14:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DFE516A4CE; Thu, 2 Dec 2004 05:14:51 +0000 (GMT) Received: from ims-1.prv.ampira.com (ims-1.ampira.com [66.179.231.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA4D643D62; Thu, 2 Dec 2004 05:14:50 +0000 (GMT) (envelope-from kamalp@acm.org) Received: from [202.142.94.194] (helo=[172.16.3.26]) by ims-1.prv.ampira.com with asmtp (Exim 4.24) id 1CZjFX-0005S4-KO; Thu, 02 Dec 2004 00:11:28 -0500 Message-ID: <41AEA4B8.6080508@acm.org> Date: Thu, 02 Dec 2004 10:44:32 +0530 From: "Kamal R. Prasad" User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <41AE3F80.1000506@freebsd.org> <98CE9C0241F1FC59BB8F0547@[192.168.1.16]> <41AE55D7.8020709@freebsd.org> In-Reply-To: <41AE55D7.8020709@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 02 Dec 2004 13:22:17 +0000 cc: "Jason C. Wells" cc: hackers@freebsd.org cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 05:14:51 -0000 I find X windows to be a bit too compute intensive. Maybe something like apple's interface would be a good alternative [for those who don't need X-windows' powerful graphic features]. regards -kamal Scott Long wrote: > Jason C. Wells wrote: > >> --On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long >> wrote: >> >>> 5. Clustered FS support. SANs are all the rage these days, and >>> clustered filesystems that allow data to be distributed across many >>> storage enpoints and accessed concurrently through the SAN are very >>> powerful. RedHat recently bought Sistina and re-opened the GFS source >>> code, so exploring this would be very interesting. >> >> >> >> This sounds very close to OpenAFS. I don't know what distinguishes a >> SAN from other types of NAS. OpenAFS does everything you mentioned >> in the above paragraph. OpenAFS _almost_ works on FreeBSD right now. >> >> Later, >> Jason C. Wells > > > Well, AFS requires an intelligent node in front of each disk. True SAN > clustering means that you have a web of disks directly connected to the > SAN (iSCSI, FibreChannel, etc), and two or more servers on the SAN that > see those disks as a single filesystem (actually a bit more complicated > than this, but you get the point). If one server goes down, no access > to data is lost since the disks can be reached from any other server on > the SAN that is participating in the clustered FS. > > Scott > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 11:30:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E70A016A4CE for ; Thu, 2 Dec 2004 11:30:26 +0000 (GMT) Received: from nutty.inf.ed.ac.uk (nutty.inf.ed.ac.uk [129.215.216.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EC0243D1D for ; Thu, 2 Dec 2004 11:30:26 +0000 (GMT) (envelope-from richard@inf.ed.ac.uk) Received: from macintosh.inf.ed.ac.uk (macintosh.inf.ed.ac.uk [129.215.164.64]) by nutty.inf.ed.ac.uk (8.12.8/8.12.8) with ESMTP id iB2BUHPj017281; Thu, 2 Dec 2004 11:30:17 GMT Received: by macintosh.inf.ed.ac.uk (Postfix, from userid 501) id 79B3F1B43CC; Thu, 2 Dec 2004 11:30:17 +0000 (GMT) From: Richard Tobin To: "Brandon S. Allbery KF8NH" , =?UTF-8?Q?=E5=93=89?= In-Reply-To: Brandon S. Allbery KF8NH's message of Thu, 02 Dec 2004 00:56:17 -0500 Organization: just say no X-Mailer: Ream 5.1.51-richard-mac Message-Id: <20041202113017.79B3F1B43CC@macintosh.inf.ed.ac.uk> Date: Thu, 2 Dec 2004 11:30:17 +0000 (GMT) X-Mailman-Approved-At: Thu, 02 Dec 2004 13:22:17 +0000 cc: current@freebsd.org Subject: Re: malloc(0) returns an invalid address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 11:30:27 -0000 > malloc() is required to return memory aligned for any fundamental C > type regardless of the amount of memory allocated (i.e. malloc(1) isn't > permitted to return an odd address on hardware where types larger than > (char) must be aligned). How could a conforming program tell the difference? (And so, why isn't it legal under the as-if rule?) -- Richard From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 13:26:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 994FA16A4CE; Thu, 2 Dec 2004 13:26:51 +0000 (GMT) Received: from altrade.nijmegen.internl.net (altrade.nijmegen.internl.net [217.149.192.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC34743D2D; Thu, 2 Dec 2004 13:26:50 +0000 (GMT) (envelope-from pblok@bsd4all.org) Received: from mail.bsd4all.org by altrade.nijmegen.internl.net via 113-9.bbned.dsl.internl.net [82.215.9.113] with ESMTP id iB2DQl7N019756 (8.12.10/2.04); Thu, 2 Dec 2004 14:26:47 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by mail.bsd4all.org (Postfix) with ESMTP id 94B9A9C; Thu, 2 Dec 2004 14:26:46 +0100 (CET) Received: from mail.bsd4all.org ([127.0.0.1]) by localhost (fwgw [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00863-07; Thu, 2 Dec 2004 14:26:39 +0100 (CET) Received: from ntpc (ntpc [192.168.1.138]) by mail.bsd4all.org (Postfix) with ESMTP id 13FCC85; Thu, 2 Dec 2004 14:26:39 +0100 (CET) From: "Peter Blok" To: "'Scott Long'" , Date: Thu, 2 Dec 2004 14:25:13 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <41AE3F80.1000506@freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTX8aDqii43GAVPRRmNKzED0+X35gAf+iUg Message-Id: <20041202132639.13FCC85@mail.bsd4all.org> X-Virus-Scanned: by amavisd-new at bsd4all.org X-Mailman-Approved-At: Thu, 02 Dec 2004 13:39:44 +0000 cc: hackers@freebsd.org Subject: RE: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 13:26:51 -0000 As far as the iSCSI stuff, I have the Lucent stuff and am trying to use it as a reference to build an iSCSI target. I have been experimenting a bit. The design goal is to have the negotiation stuff running in a user daemon, while the target data handling is completely in the kernel. I was thinking about using netgraph for the network side of things. On the "disk" side of things I am thinking about a geom provider, but not initially. Initially I will send the SCSI CDBs directly to a tape drive that is used for testing purposes. The project I need this for is to offer a FreeBSD connected tape library to a Windoze box with iSCSI and use native NTBACKUP. Later on the FreeBSD target will be geom based. Peter -----Original Message----- From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd-hackers@freebsd.org] On Behalf Of Scott Long Sent: Wednesday, December 01, 2004 11:03 PM To: current@freebsd.org Cc: hackers@freebsd.org Subject: My project wish-list for the next 12 months All, I know that I said last month that we were going to stop promising specific features for the next major release. However, I'd like to throw out a list of things that would be really nice to have in the future, whether its 6.0 or 7.0 or whatever. Most of these tasks are not trivial, but I hope that talking about them will encourage some interest. These are in no particular priority order. I'd also be thrilled if someone wanted to dress this list up in docbook and add it to the webpage. While this is just my personal list, I'd welcome other additions to it (in the sense of significant projects, not just individual PRs or bug fixes that one might be interested in). 1. Keyboard multiplexer. We are running into problems with making ps/2 and USB/bluetooth keyboards work together and work with KVMs. Having a virtual keyboard device that multiplexes the various real keyboard devices and handles hotplug can solve this mess pretty effectively. I know that there has been a lot of talk about this on mailing lists recently but I don't know how much progress is being made so I'm listing it here. 2. New installer. I know some people still consider this a joke, but the reality is that sysinstall is no longer state of the art. It's fairly good at the simple task that it does, but it's becoming harder and harder to fix bugs and extend functionality in it. It's also fairly unfriendly to those of us who haven't been using it since 1995. The DFly folks have some very interesting work in this area (www.bsdinstaller.com) and it would be very good to see if we can collaborate with them on it. 3. Native PCI Express support. I keep on hoping to take care of this, but I never seem to have the time to get past designing it. This task includes 3 parts that are mostly independent. The first is support for the extended PCI config space and memio access method, the second is MSI, and the third is link QOS management. If anyone is interested here, please let me know. 4. Journaled filesystem. While we can debate the merits of speed and data integrety of journalling vs. softupdates, the simple fact remains that softupdates still requires a fsck run on recovery, and the multi-terabyte filesystems that are possible these days make fsck a very long and unpleasant experience, even with bg-fsck. There was work at some point at RPI to add journaling to UFS, but there hasn't been much status on that in a long time. There have also been proposals and works-in-progress to port JFS, ReiserFS, and XFS. Some of these efforts are still alive, but they need to be seen through to completion. But at the risk of opening a can of worms here, I'll say that it's also important to explore non-GPL alternatives. 5. Clustered FS support. SANs are all the rage these days, and clustered filesystems that allow data to be distributed across many storage enpoints and accessed concurrently through the SAN are very powerful. RedHat recently bought Sistina and re-opened the GFS source code, so exploring this would be very interesting. 6. Overhaul CAM, add iSCSI. CAM is very parallel-SCSI centric right now. I have some work-in-progress in Perforce to address this, but it's pretty minimal. The parallel SCSI knowledge needs to be separated out and the stack need to be able to cleanly deal with iSCSI, SCSI, SAS, and maybe even ATA transports. There is a Lucent implementation of iSCSI for FreeBSD 4.x that could be a useful reference, though it's a monolithic stack that doesn't really address the shortcomings of CAM. Having iSCSI infrastructure that supported both hardware and software implementations would be ideal. _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 13:50:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 323FD16A4CE; Thu, 2 Dec 2004 13:50:03 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBAFA43D41; Thu, 2 Dec 2004 13:50:02 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1CZrLM-000Jp8-PS; Thu, 02 Dec 2004 15:50:00 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: "Peter Blok" In-Reply-To: Message from "Peter Blok" <20041202132639.13FCC85@mail.bsd4all.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Dec 2004 15:50:00 +0200 From: Danny Braniss Message-Id: <20041202135002.CBAFA43D41@mx1.FreeBSD.org> cc: hackers@freebsd.org cc: 'Scott Long' cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 13:50:03 -0000 > As far as the iSCSI stuff, I have the Lucent stuff and am trying to use it > as a reference to build an iSCSI target. I have been experimenting a bit. > > The design goal is to have the negotiation stuff running in a user daemon, > while the target data handling is completely in the kernel. I was thinking > about using netgraph for the network side of things. On the "disk" side of > things I am thinking about a geom provider, but not initially. Initially I > will send the SCSI CDBs directly to a tape drive that is used for testing > purposes. The project I need this for is to offer a FreeBSD connected tape > library to a Windoze box with iSCSI and use native NTBACKUP. > > Later on the FreeBSD target will be geom based. > > Peter I would like to help/cooperate, I have a netapp with iSCSI awarness, and if necessary i can get a SAN/iSCSI, and probably some time too. danny From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 13:58:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C98D16A4CE for ; Thu, 2 Dec 2004 13:58:01 +0000 (GMT) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18B9143D48 for ; Thu, 2 Dec 2004 13:58:01 +0000 (GMT) (envelope-from pertti.kosunen@saunalahti.fi) Received: from [127.0.0.1] (KMDCLXI.dsl.saunalahti.fi [62.142.70.61]) by gw02.mail.saunalahti.fi (Postfix) with ESMTP id EAA2883743 for ; Thu, 2 Dec 2004 15:57:59 +0200 (EET) Message-ID: <41AF1F6B.3020407@saunalahti.fi> Date: Thu, 02 Dec 2004 15:58:03 +0200 From: Pertti Kosunen User-Agent: Mozilla Thunderbird 0.9 / FreeBSD 5.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <41612915.70209@gmx.de> <20041004142028.O59122@pol.leissner.se> <20041005113936.GD1693@ip.net.ua> <41AD9F30.5030004@OTEL.net> In-Reply-To: <41AD9F30.5030004@OTEL.net> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 02 Dec 2004 14:28:07 +0000 Subject: Re: High rate traffic silence an em interface. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 13:58:01 -0000 Iasen Kostov wrote: > 1.44.2.4 and still disapperaing em0 ... > > em0@pci2:1:0: class=0x020000 card=0x80f71043 chip=0x10198086 > rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = '82547EI Gigabit Ethernet Controller (LOM)' > class = network > subclass = ethernet I have same problem with re0 (*Edimax* EN-9230TX-32). Dissappears also without any traffic. ifconfig: re0: flags=8843 mtu 1500 options=1b inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255 inet 10.0.0.20 netmask 0xffffffff broadcast 10.0.0.20 ether 00:0e:2e:20:29:7c media: Ethernet autoselect (100baseTX ) status: active pciconf: re0@pci0:13:0: class=0x020000 card=0x816910ec chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class = network subclass = ethernet dmesg: re0: port 0xb400-0xb4ff mem 0xd3800000-0xd38000ff irq 4 at device 13.0 on pci0 miibus1: on re0 rgephy0: on miibus1 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto uname -a: FreeBSD olutseura.ath.cx 5.3-STABLE FreeBSD 5.3-STABLE #0: Sun Nov 21 14:18:23 EET 2004 root@olutseura.ath.cx:/usr/obj/usr/src/sys/OLUTSEURA i386 From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 14:41:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EF5416A4CF for ; Thu, 2 Dec 2004 14:41:53 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7083743D62 for ; Thu, 2 Dec 2004 14:41:52 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 27464 invoked from network); 2 Dec 2004 14:32:53 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 2 Dec 2004 14:32:53 -0000 Message-ID: <41AF29AC.6030401@freebsd.org> Date: Thu, 02 Dec 2004 15:41:48 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <41AE3F80.1000506@freebsd.org> In-Reply-To: <41AE3F80.1000506@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 14:41:53 -0000 Scott Long wrote: > 5. Clustered FS support. SANs are all the rage these days, and > clustered filesystems that allow data to be distributed across many > storage enpoints and accessed concurrently through the SAN are very > powerful. RedHat recently bought Sistina and re-opened the GFS source > code, so exploring this would be very interesting. There are certain steps that can be be taken one at a time. For example it should be relatively easy to mount snapshots (ro) from more than one machine. Next step would be to mount a full 'rw' filesystem as 'ro' on other boxes. This would require cache and sector invalidation broadcasting from the 'rw' box to the 'ro' mounts. The holy grail of course is to mount the same filesystem 'rw' on more than one box, preferrably more than two. This requires some more involved synchronization and locking on top of the cache invalidation. And make sure that the multi-'rw' cluster stays alive if one of the participants freezes and doesn't respond anymore. Scrolling through the UFS/FFS code I think the first one is 2-3 days of work. The second 2-4 weeks and the third 2-3 month to get it right. If someone would throw up the money... -- Andre From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 14:54:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29B6516A4CE for ; Thu, 2 Dec 2004 14:54:04 +0000 (GMT) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 96DF943D1D for ; Thu, 2 Dec 2004 14:54:03 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 33780 invoked from network); 2 Dec 2004 14:54:02 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 2 Dec 2004 14:54:02 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB2Es1fX084815; Thu, 2 Dec 2004 15:54:01 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB2Es09E084814; Thu, 2 Dec 2004 15:54:00 +0100 (CET) (envelope-from pho) Date: Thu, 2 Dec 2004 15:53:58 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041202145358.GA84785@peter.osted.lan> References: <20041201055115.I18185@mail.chesapeake.net> <20041201160351.V18185@mail.chesapeake.net> <20041201223725.GA80282@peter.osted.lan> <20041201184238.K18185@mail.chesapeake.net> <20041201185146.W18185@mail.chesapeake.net> <20041202065819.GA82433@peter.osted.lan> <20041202021828.A18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041202021828.A18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 14:54:04 -0000 On Thu, Dec 02, 2004 at 02:20:46AM -0500, Jeff Roberson wrote: > On Thu, 2 Dec 2004, Peter Holm wrote: > > > On Wed, Dec 01, 2004 at 06:52:19PM -0500, Jeff Roberson wrote: > > > On Wed, 1 Dec 2004, Jeff Roberson wrote: > > > > > > > On Wed, 1 Dec 2004, Peter Holm wrote: > > > > > > > > > > > > > > Got a new one for you: > > > > > 1) panic: wrong b_bufobj 0 should be 0xc2679c10 > > > > > 2) panic: unexpected clean buffer 0xc6624bc8 > > > > > > > > > > http://www.holm.cc/stress/log/jeff04.html > > > > > > > > I fixed your last panic. The new patch is up at the same URL. I'll look > > > > at these now, thanks. This tool is really working out well. > > > > > > Also fixed the unexpected clean buffer. That was mostly just a bad > > > assert. I'm still baffled by wrong bufobj. > > > > > > > OK. I just do not seem to be able to get past the double panic problem: > > > > $ grep -A 3 ppanic /tmp/tip11.log > > ppanic: unexpected clean buffer 0xc6624bc8 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 54 tid 100042 ] > > -- > > ppanic: unexpected clean buffer 0xc6667ec0 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 54 tid 100042 ] > > -- > > ppanic: unexpected clean buffer 0xc66564e0 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 54 tid 100042 ] > > > > so I've just updated with your last patch. > > Are you just running your stress program? Anything special about your > setup? I see that these are valid bugs, but I'm not able to trigger them > myself. > > > > > - Peter After 05:46:18 of stress testing I get a "wrong b_bufobj 0 should be 0xc2e99484" panic. There's not much to go on, as the panic doesn't enter the debugger. Details at http://www.holm.cc/stress/log/jeff05.html -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 15:10:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61F5716A4CE; Thu, 2 Dec 2004 15:10:52 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E56843D55; Thu, 2 Dec 2004 15:10:51 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iB2FAnUu002382 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 2 Dec 2004 18:10:50 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iB2FAmo2033695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 18:10:49 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id iB2FAmXX033694; Thu, 2 Dec 2004 18:10:48 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Thu, 2 Dec 2004 18:10:48 +0300 From: Gleb Smirnoff To: current@freebsd.org, stable@freebsd.org Message-ID: <20041202151048.GA33485@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Status: Clean Subject: [TEST] netgraph callout interface X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 15:10:52 -0000 Dear collegues, we are working on making netgraph ISR mpsafe. To do it we need to fix all (ab)users of bare timeout(9) in src/sys/netgraph. These timeout calls are running in synch with netgraph now because timeout(9) is Giant-locked. As soon as we mark ISR mpsafe, they are going to break. This patch semi-mechanically changes all timeout(9) calls to ng_callout(9), which runs scheduled callouts in netgraph context: http://people.freebsd.org/~glebius/totest/netgraph_callout It can be applied to HEAD or RELENG_5 (not 5.3-RELEASE). It patches the following nodes: ng_bridge.c ng_l2tp.c ng_lmi.c ng_ppp.c ng_pppoe.c ng_tty.c If you are using at least one of them, then I'm asking you to test the patch and respond. Thanks in advance! P.S. Sorry for crossposting. The target users are both RELENG_5 and CURRENT. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 15:18:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48AFE16A4CE for ; Thu, 2 Dec 2004 15:18:07 +0000 (GMT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A00643D45 for ; Thu, 2 Dec 2004 15:18:07 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 9BC8D1D2; Thu, 2 Dec 2004 09:18:06 -0600 (CST) Date: Thu, 2 Dec 2004 09:18:06 -0600 From: Tillman Hodgson To: current@freebsd.org Message-ID: <20041202151806.GI569@seekingfire.com> References: <20041201233852.GA35465@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.6i Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 15:18:07 -0000 On Thu, Dec 02, 2004 at 01:23:57AM +0100, Brad Knowles wrote: > It's interesting that you mention this. I've been giving some > thought to how I might be able to dive in and start seriously working > on building my UltraSPARC cluster (based on the four U10 clones I > have already, plus as many U5s as I can throw into the mix), and I > was hoping to find a better solution than NFS, and AFS/Coda/OpenAFS > was tops of my list of alternatives to consider. I'll second that. every few months I test OpenAFS on FreeBSD and every few months I think it's only a few months away from working ;-) In a Kerberos environment, AFS is a beautiful thing. > In particular, if I can get this thing working reasonably well, > I'd like to turn this into a package building cluster for > FreeBSD/UltraSPARC, and maybe see if there are some other > applications I can put it to during the idle times. That would be handy. My U5 isn't all that fast (mostly due to the IDE crap interface), so building large apps is reasonably annoying. It's one of the few boxes that I do portupgrades monthly (or less) rather than as they come out. -T -- "Nostalgia is a seductive liar." -- George W. Ball From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 15:52:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09ADF16A4CE; Thu, 2 Dec 2004 15:52:55 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA7D443D5D; Thu, 2 Dec 2004 15:52:54 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iB2FqsoA065965; Thu, 2 Dec 2004 10:52:54 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iB2FqsKX096767; Thu, 2 Dec 2004 10:52:54 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 29D237306E; Thu, 2 Dec 2004 10:52:54 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041202155254.29D237306E@freebsd-current.sentex.ca> Date: Thu, 2 Dec 2004 10:52:54 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/614/Wed Dec 1 10:44:43 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Status: Clean Subject: [current tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 15:52:55 -0000 TB --- 2004-12-02 14:37:53 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-12-02 14:37:53 - starting CURRENT tinderbox run for i386/pc98 TB --- 2004-12-02 14:37:53 - checking out the source tree TB --- 2004-12-02 14:37:53 - cd /home/tinderbox/CURRENT/i386/pc98 TB --- 2004-12-02 14:37:53 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-12-02 14:44:31 - building world (CFLAGS=-O2 -pipe) TB --- 2004-12-02 14:44:31 - cd /home/tinderbox/CURRENT/i386/pc98/src TB --- 2004-12-02 14:44:31 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-12-02 15:51:44 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-02 15:51:44 - cd /home/tinderbox/CURRENT/i386/pc98/src TB --- 2004-12-02 15:51:44 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Dec 2 15:51:44 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] awk -f /tinderbox/CURRENT/i386/pc98/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/i386/pc98/src/sys/dev/ppbus/ppbus_if.m -h awk -f /tinderbox/CURRENT/i386/pc98/src/sys/tools/makeobjops.awk /tinderbox/CURRENT/i386/pc98/src/sys/isa/isa_if.m -h if [ -f .olddep ]; then mv .olddep .depend; fi rm -f .newdep /home/tinderbox/CURRENT/i386/pc98/obj/tinderbox/CURRENT/i386/pc98/src/make.i386/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/i386/pc98/src/sys -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/altq -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/pf -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/i386/pc98/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-bounda ry=2 -ffreestanding In file included from /tinderbox/CURRENT/i386/pc98/src/sys/dev/pci/pci.c:64: /tinderbox/CURRENT/i386/pc98/src/sys/dev/acpica/acpivar.h:31:21: acpi_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/obj/pc98/tinderbox/CURRENT/i386/pc98/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/obj/pc98/tinderbox/CURRENT/i386/pc98/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/pc98/src. TB --- 2004-12-02 15:52:54 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-12-02 15:52:54 - ERROR: failed to build generic kernel TB --- 2004-12-02 15:52:54 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 15:56:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CAE816A4CE for ; Thu, 2 Dec 2004 15:56:41 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 4D98B43D58 for ; Thu, 2 Dec 2004 15:56:40 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 71317 invoked from network); 2 Dec 2004 15:56:38 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 2 Dec 2004 15:56:38 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB2Fubug085178; Thu, 2 Dec 2004 16:56:37 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB2Fubpa085177; Thu, 2 Dec 2004 16:56:37 +0100 (CET) (envelope-from pho) Date: Thu, 2 Dec 2004 16:56:37 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041202155637.GA85127@peter.osted.lan> References: <20041201055115.I18185@mail.chesapeake.net> <20041201160351.V18185@mail.chesapeake.net> <20041201223725.GA80282@peter.osted.lan> <20041201184238.K18185@mail.chesapeake.net> <20041201185146.W18185@mail.chesapeake.net> <20041202065819.GA82433@peter.osted.lan> <20041202021828.A18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041202021828.A18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 15:56:41 -0000 On Thu, Dec 02, 2004 at 02:20:46AM -0500, Jeff Roberson wrote: > On Thu, 2 Dec 2004, Peter Holm wrote: > > > On Wed, Dec 01, 2004 at 06:52:19PM -0500, Jeff Roberson wrote: > > > On Wed, 1 Dec 2004, Jeff Roberson wrote: > > > > > > > On Wed, 1 Dec 2004, Peter Holm wrote: > > > > > > > > > > > > > > Got a new one for you: > > > > > 1) panic: wrong b_bufobj 0 should be 0xc2679c10 > > > > > 2) panic: unexpected clean buffer 0xc6624bc8 > > > > > > > > > > http://www.holm.cc/stress/log/jeff04.html > > > > > > > > I fixed your last panic. The new patch is up at the same URL. I'll look > > > > at these now, thanks. This tool is really working out well. > > > > > > Also fixed the unexpected clean buffer. That was mostly just a bad > > > assert. I'm still baffled by wrong bufobj. > > > > > > > OK. I just do not seem to be able to get past the double panic problem: > > > > $ grep -A 3 ppanic /tmp/tip11.log > > ppanic: unexpected clean buffer 0xc6624bc8 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 54 tid 100042 ] > > -- > > ppanic: unexpected clean buffer 0xc6667ec0 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 54 tid 100042 ] > > -- > > ppanic: unexpected clean buffer 0xc66564e0 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 54 tid 100042 ] > > > > so I've just updated with your last patch. > > Are you just running your stress program? Anything special about your > setup? I see that these are valid bugs, but I'm not able to trigger them > myself. > Just got a double panic again: http://www.holm.cc/stress/log/jeff06.html. I think I'll revert to HEAD, just to touch base. -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 15:58:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59D7316A4CE for ; Thu, 2 Dec 2004 15:58:16 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BA0143D1F for ; Thu, 2 Dec 2004 15:58:15 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB2Fw8jl098968; Thu, 2 Dec 2004 16:58:08 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Peter Holm From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 02 Dec 2004 16:56:37 +0100." <20041202155637.GA85127@peter.osted.lan> Date: Thu, 02 Dec 2004 16:58:08 +0100 Message-ID: <98967.1102003088@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: Jeff Roberson cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 15:58:16 -0000 In message <20041202155637.GA85127@peter.osted.lan>, Peter Holm writes: >Just got a double panic again: http://www.holm.cc/stress/log/jeff06.html. >I think I'll revert to HEAD, just to touch base. HEAD is not very happy on my testbox right now, recent ACPI commits seems to have received less than meticulous scrutiny. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 16:01:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D29316A4CE for ; Thu, 2 Dec 2004 16:01:31 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00B9343D2D for ; Thu, 2 Dec 2004 16:01:30 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received-SPF: pass (eva.fit.vutbr.cz: domain of xdivac02@eva.fit.vutbr.cz designates 127.0.0.1 as permitted sender) receiver=eva.fit.vutbr.cz; client_ip=127.0.0.1; envelope-from=xdivac02@eva.fit.vutbr.cz; Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id iB2G1PPb043131 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 2 Dec 2004 17:01:25 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id iB2G1PVc043130 for current@freebsd.org; Thu, 2 Dec 2004 17:01:25 +0100 (CET) Date: Thu, 2 Dec 2004 17:01:25 +0100 From: Divacky Roman To: current@freebsd.org Message-ID: <20041202160125.GA40827@stud.fit.vutbr.cz> References: <41AE3F80.1000506@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AE3F80.1000506@freebsd.org> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 16:01:31 -0000 des@ raised question realting to implementition of anticipatory scheduler.. http://www.cs.rice.edu/~ssiyer/r/antsched/ shouldnt this be integrated or something? On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote: > All, > > I know that I said last month that we were going to stop promising > specific features for the next major release. However, I'd like to > throw out a list of things that would be really nice to have in the > future, whether its 6.0 or 7.0 or whatever. Most of these tasks are > not trivial, but I hope that talking about them will encourage some > interest. These are in no particular priority order. I'd also be > thrilled if someone wanted to dress this list up in docbook and add > it to the webpage. While this is just my personal list, I'd welcome > other additions to it (in the sense of significant projects, not just > individual PRs or bug fixes that one might be interested in). > > 1. Keyboard multiplexer. We are running into problems with making > ps/2 and USB/bluetooth keyboards work together and work with KVMs. > Having a virtual keyboard device that multiplexes the various real > keyboard devices and handles hotplug can solve this mess pretty > effectively. I know that there has been a lot of talk about this on > mailing lists recently but I don't know how much progress is being made > so I'm listing it here. > > 2. New installer. I know some people still consider this a joke, but > the reality is that sysinstall is no longer state of the art. It's > fairly good at the simple task that it does, but it's becoming harder > and harder to fix bugs and extend functionality in it. It's also > fairly unfriendly to those of us who haven't been using it since 1995. > The DFly folks have some very interesting work in this area > (www.bsdinstaller.com) and it would be very good to see if we can > collaborate with them on it. > > 3. Native PCI Express support. I keep on hoping to take care of this, > but I never seem to have the time to get past designing it. This task > includes 3 parts that are mostly independent. The first is support for > the extended PCI config space and memio access method, the second is > MSI, and the third is link QOS management. If anyone is interested > here, please let me know. > > 4. Journaled filesystem. While we can debate the merits of speed and > data integrety of journalling vs. softupdates, the simple fact remains > that softupdates still requires a fsck run on recovery, and the > multi-terabyte filesystems that are possible these days make fsck a very > long and unpleasant experience, even with bg-fsck. There was work at > some point at RPI to add journaling to UFS, but there hasn't been much > status on that in a long time. There have also been proposals and > works-in-progress to port JFS, ReiserFS, and XFS. Some of these efforts > are still alive, but they need to be seen through to completion. But at > the risk of opening a can of worms here, I'll say that it's also > important to explore non-GPL alternatives. > > 5. Clustered FS support. SANs are all the rage these days, and > clustered filesystems that allow data to be distributed across many > storage enpoints and accessed concurrently through the SAN are very > powerful. RedHat recently bought Sistina and re-opened the GFS source > code, so exploring this would be very interesting. > > 6. Overhaul CAM, add iSCSI. CAM is very parallel-SCSI centric right > now. I have some work-in-progress in Perforce to address this, but it's > pretty minimal. The parallel SCSI knowledge needs to be separated out > and the stack need to be able to cleanly deal with iSCSI, SCSI, SAS, and > maybe even ATA transports. There is a Lucent implementation of iSCSI > for FreeBSD 4.x that could be a useful reference, though it's a > monolithic stack that doesn't really address the shortcomings of CAM. > Having iSCSI infrastructure that supported both hardware and software > implementations would be ideal. > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 16:18:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E235316A4CE for ; Thu, 2 Dec 2004 16:18:45 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3035D43D5C for ; Thu, 2 Dec 2004 16:18:45 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iB2GIcVt003525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 2 Dec 2004 19:18:43 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iB2GIbH2034226 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 19:18:38 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id iB2GIbxH034225; Thu, 2 Dec 2004 19:18:37 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Thu, 2 Dec 2004 19:18:37 +0300 From: Gleb Smirnoff To: Michael Reifenberger Message-ID: <20041202161837.GB34136@cell.sick.ru> References: <20041202151048.GA33485@cell.sick.ru> <20041202165401.D21600@fw.reifenberger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20041202165401.D21600@fw.reifenberger.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Status: Clean cc: current@freebsd.org Subject: Re: [TEST] netgraph callout interface X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 16:18:46 -0000 On Thu, Dec 02, 2004 at 05:01:25PM +0100, Michael Reifenberger wrote: M> On Thu, 2 Dec 2004, Gleb Smirnoff wrote: M> ... M> > http://people.freebsd.org/~glebius/totest/netgraph_callout M> > M> >It can be applied to HEAD or RELENG_5 (not 5.3-RELEASE). It patches M> >the following nodes: M> > M> M> I could test the following nodes on my gateway/firewall: M> bpf ether i4bing iface ppp pppoe socket vjc M> as I have both DSL and ISDN connects concurrently. M> M> but as it seems, i4bing (/sys/i4b/drivers/i4b_ing.c) is not M> currently adoptet and my use of FAST_IPSEC would invalidate the M> mpsavetiness... The patch does not enable mpsafeness. It just prepares many nodes to get ready to it. So, the patch should not change anything! The change is mechanical, but I have to test all of them before commiting. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 16:34:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D66116A4CE; Thu, 2 Dec 2004 16:34:50 +0000 (GMT) Received: from athena.softcardsystems.com (mail.softcardsystems.com [12.34.136.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E55D43D4C; Thu, 2 Dec 2004 16:34:50 +0000 (GMT) (envelope-from sah@softcardsystems.com) Received: from athena (athena [12.34.136.114])iB2HUCYR027884; Thu, 2 Dec 2004 12:30:12 -0500 Date: Thu, 2 Dec 2004 12:30:12 -0500 (EST) From: Sam X-X-Sender: sah@athena To: Andre Oppermann In-Reply-To: <41AF29AC.6030401@freebsd.org> Message-ID: References: <41AE3F80.1000506@freebsd.org> <41AF29AC.6030401@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 16:34:50 -0000 On Thu, 2 Dec 2004, Andre Oppermann wrote: > Scott Long wrote: >> 5. Clustered FS support. SANs are all the rage these days, and >> clustered filesystems that allow data to be distributed across many >> storage enpoints and accessed concurrently through the SAN are very >> powerful. RedHat recently bought Sistina and re-opened the GFS source >> code, so exploring this would be very interesting. > > There are certain steps that can be be taken one at a time. For example > it should be relatively easy to mount snapshots (ro) from more than one > machine. Next step would be to mount a full 'rw' filesystem as 'ro' on > other boxes. This would require cache and sector invalidation broadcasting > from the 'rw' box to the 'ro' mounts. The holy grail of course is to mount > the same filesystem 'rw' on more than one box, preferrably more than two. > This requires some more involved synchronization and locking on top of the > cache invalidation. And make sure that the multi-'rw' cluster stays alive > if one of the participants freezes and doesn't respond anymore. > > Scrolling through the UFS/FFS code I think the first one is 2-3 days of > work. The second 2-4 weeks and the third 2-3 month to get it right. > If someone would throw up the money... You might also design in consideration for data redundancy. Right now GFS largely relies on the SAN box to export already redundant RAID disks. GFS sits on a "cluster aware" lvm layer that is supposed to be able to do mirroring and striping, but I'm told it's not stable enough for "production" use. Sam From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 17:41:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 816D916A4CF for ; Thu, 2 Dec 2004 17:41:58 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79E1843D1D for ; Thu, 2 Dec 2004 17:41:57 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 29035 invoked from network); 2 Dec 2004 17:32:57 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 2 Dec 2004 17:32:57 -0000 Message-ID: <41AF53E1.80408@freebsd.org> Date: Thu, 02 Dec 2004 18:41:53 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam References: <41AE3F80.1000506@freebsd.org> <41AF29AC.6030401@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 17:41:58 -0000 Sam wrote: > On Thu, 2 Dec 2004, Andre Oppermann wrote: > >> Scott Long wrote: >> >>> 5. Clustered FS support. SANs are all the rage these days, and >>> clustered filesystems that allow data to be distributed across many >>> storage enpoints and accessed concurrently through the SAN are very >>> powerful. RedHat recently bought Sistina and re-opened the GFS source >>> code, so exploring this would be very interesting. >> >> There are certain steps that can be be taken one at a time. For example >> it should be relatively easy to mount snapshots (ro) from more than one >> machine. Next step would be to mount a full 'rw' filesystem as 'ro' on >> other boxes. This would require cache and sector invalidation >> broadcasting >> from the 'rw' box to the 'ro' mounts. The holy grail of course is to >> mount >> the same filesystem 'rw' on more than one box, preferrably more than two. >> This requires some more involved synchronization and locking on top of >> the >> cache invalidation. And make sure that the multi-'rw' cluster stays >> alive >> if one of the participants freezes and doesn't respond anymore. >> >> Scrolling through the UFS/FFS code I think the first one is 2-3 days of >> work. The second 2-4 weeks and the third 2-3 month to get it right. >> If someone would throw up the money... > > You might also design in consideration for data redundancy. Right now > GFS largely relies on the SAN box to export already redundant RAID > disks. GFS sits on a "cluster aware" lvm layer that is supposed to > be able to do mirroring and striping, but I'm told it's not > stable enough for "production" use. Data redundancy would require a UFS/FFS redesign. I'm 'only' talking about enhancing UFS/FFS but keeping anything ondisk the same (plus some more elements). -- Andre From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 17:50:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABF1416A4CE for ; Thu, 2 Dec 2004 17:50:54 +0000 (GMT) Received: from smtp004.bizmail.sc5.yahoo.com (smtp004.bizmail.sc5.yahoo.com [66.163.175.81]) by mx1.FreeBSD.org (Postfix) with SMTP id 7D1CF43D64 for ; Thu, 2 Dec 2004 17:50:54 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@70.240.198.174 with login) by smtp004.bizmail.sc5.yahoo.com with SMTP; 2 Dec 2004 17:50:54 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 55992614D; Thu, 2 Dec 2004 11:50:53 -0600 (CST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01920-12; Thu, 2 Dec 2004 11:50:50 -0600 (CST) Received: from www.noacks.org (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 9E36B614C; Thu, 2 Dec 2004 11:50:50 -0600 (CST) Received: from 69.53.57.66 (SquirrelMail authenticated user noackjr); by www.noacks.org with HTTP; Thu, 2 Dec 2004 11:50:50 -0600 (CST) Message-ID: <36533.69.53.57.66.1102009850.squirrel@69.53.57.66> In-Reply-To: <20041202160125.GA40827@stud.fit.vutbr.cz> References: <41AE3F80.1000506@freebsd.org> <20041202160125.GA40827@stud.fit.vutbr.cz> Date: Thu, 2 Dec 2004 11:50:50 -0600 (CST) From: "Jon Noack" To: "Divacky Roman" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at noacks.org cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 17:50:54 -0000 Divacky Roman wrote: > des@ raised question realting to implementition of anticipatory > scheduler.. > > http://www.cs.rice.edu/~ssiyer/r/antsched/ > > shouldnt this be integrated or something? I would love to see this happen. It looks like a lot of work is going into revamping storage for 6.x, and this would be great addition. Dr. Druschel was my Operating Systems prof at Rice. He was a good teacher, quite knowledgeable, and a nice guy. I remember talking about anticipatory scheduling in class... ah, fond memories. Jon From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 18:16:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3A5F16A4CE for ; Thu, 2 Dec 2004 18:16:19 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54C5643D5D for ; Thu, 2 Dec 2004 18:16:19 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so318974rns for ; Thu, 02 Dec 2004 10:16:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=Rkz1pfL6iOZcdMIyxzaGXpprzfwG4X4WQjIjSnk3r5xhgEWzTpAXLxDuUpmLI+Za0ut1LVy2mu0SvuEAtTsfRSEFZB/G2A9dWg3LIp2/VpkKdxFezbmJsS9/Y+T220cd0Ww1siwlRx80Qdu0TO7c4niiyYZCCxb6v5unbu/rby4= Received: by 10.38.179.40 with SMTP id b40mr2277769rnf; Thu, 02 Dec 2004 10:16:18 -0800 (PST) Received: by 10.38.8.31 with HTTP; Thu, 2 Dec 2004 10:16:18 -0800 (PST) Message-ID: Date: Fri, 3 Dec 2004 02:16:18 +0800 From: Jiawei Ye To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: WARNING: attempt to net_add_domain(netgraph) after domainfinalize() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jiawei Ye List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 18:16:19 -0000 Warnings started to appear after modifications to uipc_domain.c. The warning used to appear after acpi_cpu in dmesg. Now it happens after user_ppp is run (which I assume is why the netgraph related message appeared) with latest uipc_domain.c commit. Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 19:03:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E413516A4CE; Thu, 2 Dec 2004 19:03:58 +0000 (GMT) Received: from mail21.syd.optusnet.com.au (mail21.syd.optusnet.com.au [211.29.133.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E86643D41; Thu, 2 Dec 2004 19:03:58 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) iB2J3fCC030796 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 3 Dec 2004 06:03:46 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])iB2J3fxP065808; Fri, 3 Dec 2004 06:03:41 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)iB2J3cQY065807; Fri, 3 Dec 2004 06:03:38 +1100 (EST) (envelope-from pjeremy) Date: Fri, 3 Dec 2004 06:03:38 +1100 From: Peter Jeremy To: Miguel Mendez Message-ID: <20041202190337.GY79646@cirb503493.alcatel.com.au> References: <41AE3F80.1000506@freebsd.org> <98CE9C0241F1FC59BB8F0547@[192.168.1.16]> <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> User-Agent: Mutt/1.4.2i cc: jcw@highperformance.net cc: hackers@freebsd.org cc: scottl@freebsd.org cc: "Kamal R. Prasad" cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 19:03:59 -0000 On Thu, 2004-Dec-02 07:55:30 +0100, Miguel Mendez wrote: >On Thu, 02 Dec 2004 10:44:32 +0530 >"Kamal R. Prasad" wrote: >> I find X windows to be a bit too compute intensive. Maybe something >> like apple's interface would be a good alternative [for those who >> don't need X-windows' powerful graphic features]. > >What makes you think so? X was originally desgined for systems with >little memory and processing power, certainly a lot less than today's >AMD and Intel space heaters. Agreed. But I don't think performance is the issue with X. As I see it, there are several major problems with building an X installer: 1) It quite common in the server arena for machines not to have any graphics head and X is incompatible with serial terminals. 2) You need to configure the X server to support your video adapter, mouse, keyboard and screen. Remember, the "standard" basic VGA interface doesn't necessarily exist outside the PC world. There are enough problems with keyboards (see one of Scott's other wishes) without wanting to add mice, screens and video adapters. 3) /stand is ~2.7M on i386. A minimal X environment is going to be 50-70MB. This means 50-70MB less packages on CD1. 4) X is a RAM hog by sysinstall standards. The minimum RAM requirements will go up significantly. Whilst this shouldn't worry current generation hardware, it will make installing FreeBSD on older hardware (486 and P1) very difficult. Yes, X is network aware but this doesn't really help for system installation. You might solve points 1 and 2 but you replace them with the issue of how to bring up the network and arrange appropriate client/server communication and authentication. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 19:13:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0BF216A4CE; Thu, 2 Dec 2004 19:13:04 +0000 (GMT) Received: from smtp-vbr10.xs4all.nl (smtp-vbr10.xs4all.nl [194.109.24.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id D877143D39; Thu, 2 Dec 2004 19:13:03 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) iB2JCwwX094300; Thu, 2 Dec 2004 20:12:58 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.1/8.12.9) with ESMTP id iB2JCvvB029472; Thu, 2 Dec 2004 20:12:57 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.1/8.13.1/Submit) id iB2JCvuS029471; Thu, 2 Dec 2004 20:12:57 +0100 (CET) (envelope-from wb) Date: Thu, 2 Dec 2004 20:12:57 +0100 From: Wilko Bulte To: Scott Long Message-ID: <20041202191257.GA29425@freebie.xs4all.nl> References: <41AE3F80.1000506@freebsd.org> <98CE9C0241F1FC59BB8F0547@[192.168.1.16]> <41AE55D7.8020709@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <41AE55D7.8020709@freebsd.org> X-OS: FreeBSD 4.10-STABLE X-PGP: finger wilko@freebsd.org User-Agent: Mutt/1.5.6i X-Virus-Scanned: by XS4ALL Virus Scanner cc: "Jason C. Wells" cc: hackers@freebsd.org cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 19:13:04 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 01, 2004 at 04:37:59PM -0700, Scott Long wrote.. > Jason C. Wells wrote: > >--On Wednesday, December 01, 2004 3:02 PM -0700 Scott Long=20 > > wrote: > > > >>5. Clustered FS support. SANs are all the rage these days, and > >>clustered filesystems that allow data to be distributed across many > >>storage enpoints and accessed concurrently through the SAN are very > >>powerful. RedHat recently bought Sistina and re-opened the GFS source > >>code, so exploring this would be very interesting. > > > > > >This sounds very close to OpenAFS. I don't know what distinguishes a=20 > >SAN from other types of NAS. OpenAFS does everything you mentioned in= =20 > >the above paragraph. OpenAFS _almost_ works on FreeBSD right now. > > > >Later, > >Jason C. Wells >=20 > Well, AFS requires an intelligent node in front of each disk. True SAN > clustering means that you have a web of disks directly connected to the > SAN (iSCSI, FibreChannel, etc), and two or more servers on the SAN that > see those disks as a single filesystem (actually a bit more complicated > than this, but you get the point). If one server goes down, no access > to data is lost since the disks can be reached from any other server on > the SAN that is participating in the clustered FS. Find a friendly TruCluster somewhere and take a look. Really Neat(tm). Alternatively find a friendly OpenVMS cluster, they have forgotten more about clusters now than Unix will ever learn (I am afraid). While we are talking storage: multipathing support for SANs is a very neat thing to have. Devices uniquely identified by WWN etc. --=20 Wilko Bulte wilko@FreeBSD.org --cWoXeonUoKmBZSoM Content-Type: application/x-pkcs7-signature Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIIOfwYJKoZIhvcNAQcCoIIOcDCCDmwCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC C+swggSmMIICjqADAgECAgMAxq4wDQYJKoZIhvcNAQEEBQAweTEQMA4GA1UEChMHUm9vdCBD QTEeMBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNp Z25pbmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcwHhcN MDQxMTA2MjI0MzE2WhcNMDUxMTA2MjI0MzE2WjAlMSMwIQYJKoZIhvcNAQkBFhR3YkBmcmVl YmllLnhzNGFsbC5ubDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANtHavP0Bn9g xcTO+rGscZxb/+LZcFdERZcV6d358KOHsrysbvvpElwbTgSL4QpviV9a5ju+3dze7YRi0iB7 3JzWbl1G29Q45nydX58eWX++w+RAFlHI0kAwTY612bIqhP+MmRon7W70lw45gQfUzGz/DqdR M/FRNNYhOVYp2wbp6f2ytEaierTv8p201+mLB4SjVJ1vQtu3oVfYZVZeJDoxYn49SrjVejuA yq/lDEO9ykNTp4l7rGJcK+FRAdag5Oi7Tev6cq5DzJiON74W9MR5aqvOLtYo/bh3zKXf5ygy sN8+hJnkAwlaAJ38SnsxKfpy3aFLUuZEn+Ul3oUcarkCAwEAAaOBijCBhzAMBgNVHRMBAf8E AjAAMFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZS RUUgaGVhZCBvdmVyIHRvIGh0dHA6Ly93d3cuQ0FjZXJ0Lm9yZzAfBgNVHREEGDAWgRR3YkBm cmVlYmllLnhzNGFsbC5ubDANBgkqhkiG9w0BAQQFAAOCAgEAlKQNnSd8Jdt58NFTEaY202Qb XEdESmsRBaydVid6K956unv0rtp3GhkegEJEjhSKoN0K0rIIoYeHgiArmZu2wtMoNvKJG7kN bXQ+R8uWJ5CLMbQ8HbEommF2ptrkR72GrXwOnDyjInEB/1lTtLjoBGmk7A+sTpvaB/gUpvRZ ydr7h8XhNwTcYdBEUXBeKkR7N+FzzSHfmYH288i65fmKQX91F/ewoaB627sDLKH/Vt/M8Z/I NcqyPlmGuFSKlR184PKWY78VaA8RtHSsQrr97eSRIa6MOWlvYQyq8fUfcPUfxl45qLlH8s2n FP0O7ZMAHhbypjnRWNg/r+HGsUqUh6EKFRdp70MmSSWYnM3ZzxGBIb9UV1n4+nPUCUx9r1fa DIAc/1LEvcjLSlW6vHus48VAOJelNGfMsdr8VlVafJE0F0nIXRiUdoe5sO45RKCSefqgRSW/ 7nLb7mvBg8u9q5+7VLuCsXEkpgc65dIIUD+2FTXpA2Zb0LSeey5zKC+RYdCYYvLAl9sQwx5E 6FMCkHOMDu5MEJLI0oyjrHjDbt/aE+fUQlJrFmfIUUX4CeQCdvFqrHDRjOT7JVSQB6EqA8VZ zBFLYUlTKdunvFcwR+2gJyHOTqLbM8b+Qb972jaBE6bGPWbK6t9PSdUsf2g1B9CpDSMiuWe7 Ek/XJFe6NY0wggc9MIIFJaADAgECAgEAMA0GCSqGSIb3DQEBBAUAMHkxEDAOBgNVBAoTB1Jv b3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2Vy dCBTaWduaW5nIEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3Jn MB4XDTAzMDMzMDEyMjk0OVoXDTMzMDMyOTEyMjk0OVoweTEQMA4GA1UEChMHUm9vdCBDQTEe MBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25p bmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcwggIiMA0G CSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDOIsDiRn3sNigHUJbyoDNAjEvxO2Y/MeVrAjbb 1nz28YiPTnc2BUGV+QnwEs9GhnNgt25+6MBYZK7NsK1FFwxj+mcK6NbSvz7nmMTwTPrgA7s1 XWwh3p4g2brNZjI3cvr3CPXHzVjJjucOXuo+/hyhFAoVbIaEW2RmKnqpS1N59Yiie+4vCmEr jbJ+TValE+zq2pKerERBHlhgZQVm+MBEvcuU90J+C/dlaJhRBfDzBZEEHRsXguzIV7vDa3qI 8bByzCVbIJHsFgISjzLpFxhI0McFLgIwQrglnAVrP6o6p+tTSPfo0rYHmNwbxjR/f8kcgnoF WCsIW/M4oqsXXWbJmNeeEIui0t10mvdxDHJg381vmDOdljR2PiR6krAOlR5v5qBFOEeq10Ht SrcS9tcbg4oPLtgJtlnXqgT/0pN9aC7di0urWLovjeqVp6DDVIml+9uLUSKdssO+Eb4skYaL lnitINOKLxo/xtBRZYchsRkBZX9FHIf1fNBBTE8pmCH9Mx91DARR+hl329QUHO6Bwx31mLdp BpEi3QBQzIExrBIHezjaaFvmK9R+yV+t6OtyTPMB5Usgv5qmV8qRAAGLoXUhN7VjDWc+Rk9w IGfOxdZZ2wLg8NLLzbpit5BB6N0g5Cm8ZClCyCLceJr/Q+yYGwlRS1pawnHxxMtzqeWhCwID AQABo4IBzjCCAcowHQYDVR0OBBYEFBa1MhvUx/Pg5o7zvdKwOu6yORjRMIGjBgNVHSMEgZsw gZiAFBa1MhvUx/Pg5o7zvdKwOu6yORjRoX2kezB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYD VQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZ4IBADAPBgNVHRMB Af8EBTADAQH/MDIGA1UdHwQrMCkwJ6AloCOGIWh0dHBzOi8vd3d3LmNhY2VydC5vcmcvcmV2 b2tlLmNybDAwBglghkgBhvhCAQQEIxYhaHR0cHM6Ly93d3cuY2FjZXJ0Lm9yZy9yZXZva2Uu Y3JsMDQGCWCGSAGG+EIBCAQnFiVodHRwOi8vd3d3LmNhY2VydC5vcmcvaW5kZXgucGhwP2lk PTEwMFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZS RUUgaGVhZCBvdmVyIHRvIGh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzANBgkqhkiG9w0BAQQFAAOC AgEAKMfunIICulyAEso1Ch2Bb4lqmczyaA9/p+GNWJU+vfIGw5BarLVg9plDAaOIcJydYp2k h69nWA0wNjvmrUjTy3QChnE+4isDaPE0YkBGO1PqKPSs+2aVU4pNXf072WDXynlpO7FlkqbG gYJcnM3rTQGKpd8RVaoVyh83wIKYcGHbanyWo44uVD5PIamQ79yCv9zoRa1NkHMIPJRlsASZ dn/ivMJqFaqXBDck2B6UTm0OUb7WxI/Klm33Q9/oMGUnO3u7Q0NjxEP3suxozOEZjiL7mOF7 Wj4BNzuLCLCi85VOGsubzZqx27Jw8C1K29iw429FSDMS//48MipU98T3ivCII8JH/mR6ccDR HqZjsAd+pC/TAY/cnyu2xgipD5NIJfwS/Z9C3PPEPvZXsNfdadEGdzQKS9LKoP8cxozJFr7E zDI3aHNfCPtR90lTNgUKlQJM8nkaEPbYOnWc8x3xog1wZ4Ybsxb1L+Wk63mG+T0LwnMLpZms b/xnuOUvC6YYJI170Ug1KRhArJNg4ZaGULR6WdiPIQufz4KRxju/a9wHkbmXViOqtmyUxkgG POTOTqrk9i8J3FNvLvx06zpjmcKmrIm8p7JEoA2KEONs8iTL+pufcEcu3hSL1LIgCZaiZPEk HNyhNZwVstS8VS59BvWcDlX0WtaT2natJXNMxUMxggJcMIICWAIBATCBgDB5MRAwDgYDVQQK EwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNB IENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0 Lm9yZwIDAMauMAkGBSsOAwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkq hkiG9w0BCQUxDxcNMDQxMjAyMTkxMjU3WjAjBgkqhkiG9w0BCQQxFgQUBS8MFgypae8xoimB ypmZHPGsP9EwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAw DQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAE ggEAd8bqWjv0XgGXl8vIhbw1kR8cgtrMbfltj0xurd14bMXzFxE0uLbb1C3Eq6nigqmN2Vtn oIM5FG22ir7BH9j7jKdGmC//woLAd20HksazWYhABAsC05E97vhz8BGp6nxgLA9gdwqUJcNe 2uLqVkZmwR9h/ueggkQDRBQfnyWhABpO1yLJX0ND4xA6jjnul597qrN9+TehkaDKKSSwbbS5 Ik+DbgIcW4inFnhcQ6ewrva77Y89v/0h6yvm7IDJT3Yf8mM2xkxvmJxIBGyfKjBbpuphH1u4 3QxagJfTBxHDIZ0jOmmYbadvteIJpZGHpnTPj8lbA9Z+stzzyQrYytSYhw== --cWoXeonUoKmBZSoM-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 19:19:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE7B316A4CE for ; Thu, 2 Dec 2004 19:19:13 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7808743D2D for ; Thu, 2 Dec 2004 19:19:13 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so835402rnf for ; Thu, 02 Dec 2004 11:19:13 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=BAApe33Ht0oVS/lheV0xufhZhJWlldLeFBj9n7h1bKf49pWBpstdG9Xx7zaUVL06SeWyfji2c6N9aizJ3yjUTw4wWpPfCdrv5zITCgCV6uvmRpcnWS8iV7EBSVV+eLSMkox9ATzYQe5uSCKiUbRsn+PuYmSlWz1OyUOYCX6LOc4= Received: by 10.38.150.72 with SMTP id x72mr972049rnd; Thu, 02 Dec 2004 11:19:12 -0800 (PST) Received: by 10.38.15.38 with HTTP; Thu, 2 Dec 2004 11:19:12 -0800 (PST) Message-ID: Date: Thu, 2 Dec 2004 19:19:12 +0000 From: Eric Kjeldergaard To: current@freebsd.org In-Reply-To: <20041202190337.GY79646@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41AE3F80.1000506@freebsd.org> <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> <20041202190337.GY79646@cirb503493.alcatel.com.au> Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eric Kjeldergaard List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 19:19:14 -0000 > Agreed. But I don't think performance is the issue with X. As I see > it, there are several major problems with building an X installer: > 1) It quite common in the server arena for machines not to have any > graphics head and X is incompatible with serial terminals. > 2) You need to configure the X server to support your video adapter, > mouse, keyboard and screen. Remember, the "standard" basic VGA > interface doesn't necessarily exist outside the PC world. There > are enough problems with keyboards (see one of Scott's other wishes) > without wanting to add mice, screens and video adapters. > 3) /stand is ~2.7M on i386. A minimal X environment is going to be > 50-70MB. This means 50-70MB less packages on CD1. > 4) X is a RAM hog by sysinstall standards. The minimum RAM requirements > will go up significantly. Whilst this shouldn't worry current > generation hardware, it will make installing FreeBSD on older hardware > (486 and P1) very difficult. I want to preface by saying that I certainly don't think a GUI installer should replace what FreeBSD ships with now. Having said that: It has been suggested in the past, and may as well be suggested again now, that a liveCD installer be created. I know that amongst desktop/first-time users this would be a welcome addition. I also realise that it isn't FreeBSD's main market (though it is a major consideration). This sort of project could be done with somewhat less knowledge (I think) than sysinstall itself, and would have many classes of systems that simply by nature of being a liveCD it wouldn't have to worry about (I think of headless servers and 486s). Just thought I would toss the idea out to see what people thought of it at this point (as I've not heard much about it for a while, and it seems that many of them were getting ready for 5-STABLE). -- If I write a signature, my emails will appear more personalised. From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 19:29:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 311BF16A4CE; Thu, 2 Dec 2004 19:29:27 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8A7243D54; Thu, 2 Dec 2004 19:29:26 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iB2JTQ8E002306; Thu, 2 Dec 2004 14:29:26 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iB2JTPhH025627; Thu, 2 Dec 2004 14:29:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 7F10E7306E; Thu, 2 Dec 2004 14:29:25 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041202192925.7F10E7306E@freebsd-current.sentex.ca> Date: Thu, 2 Dec 2004 14:29:25 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Status: Clean Subject: [current tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 19:29:27 -0000 TB --- 2004-12-02 18:16:15 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-12-02 18:16:15 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2004-12-02 18:16:15 - checking out the source tree TB --- 2004-12-02 18:16:15 - cd /home/tinderbox/CURRENT/sparc64/sparc64 TB --- 2004-12-02 18:16:15 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-12-02 18:22:46 - building world (CFLAGS=-O2 -pipe) TB --- 2004-12-02 18:22:46 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2004-12-02 18:22:46 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-12-02 19:28:34 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-02 19:28:34 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2004-12-02 19:28:34 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Dec 2 19:28:35 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] /tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica/actypes.h:168:2: #error ACPI_MACHINE_WIDTH not defined /tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica/actypes.h:277:2: #error unknown ACPI_MACHINE_WIDTH In file included from /tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica/acpi.h:129, from /tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/pci/pci.c:63: /tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica/acmacros.h:377:2: #error unknown ACPI_MACHINE_WIDTH In file included from /tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/pci/pci.c:64: /tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/acpica/acpivar.h:31:21: acpi_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2004-12-02 19:29:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-12-02 19:29:25 - ERROR: failed to build generic kernel TB --- 2004-12-02 19:29:25 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 19:34:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E37016A4CE for ; Thu, 2 Dec 2004 19:34:45 +0000 (GMT) Received: from basement.kutulu.org (211.215.33.65.cfl.rr.com [65.33.215.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2F3843D2D for ; Thu, 2 Dec 2004 19:34:44 +0000 (GMT) (envelope-from kutulu@kutulu.org) Received: from [127.0.0.1] (localhost [127.0.0.1]) by basement.kutulu.org (Postfix) with ESMTP id 8D0A6A5; Thu, 2 Dec 2004 14:34:43 -0500 (EST) Message-ID: <41AF6E52.80106@kutulu.org> Date: Thu, 02 Dec 2004 14:34:42 -0500 From: Mike Edenfield User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Kjeldergaard References: <41AE3F80.1000506@freebsd.org> <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> <20041202190337.GY79646@cirb503493.alcatel.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 19:34:45 -0000 Eric Kjeldergaard wrote: >>Agreed. But I don't think performance is the issue with X. As I see >>it, there are several major problems with building an X installer: >>1) It quite common in the server arena for machines not to have any >> graphics head and X is incompatible with serial terminals. >>2) You need to configure the X server to support your video adapter, >> mouse, keyboard and screen. Remember, the "standard" basic VGA >> interface doesn't necessarily exist outside the PC world. There >> are enough problems with keyboards (see one of Scott's other wishes) >> without wanting to add mice, screens and video adapters. >>3) /stand is ~2.7M on i386. A minimal X environment is going to be >> 50-70MB. This means 50-70MB less packages on CD1. >>4) X is a RAM hog by sysinstall standards. The minimum RAM requirements >> will go up significantly. Whilst this shouldn't worry current >> generation hardware, it will make installing FreeBSD on older hardware >> (486 and P1) very difficult. > > > I want to preface by saying that I certainly don't think a GUI > installer should replace what FreeBSD ships with now. Having said > that: It has been suggested in the past, and may as well be suggested > again now, that a liveCD installer be created. I know that amongst > desktop/first-time users this would be a welcome addition. I also > realise that it isn't FreeBSD's main market (though it is a major > consideration). This sort of project could be done with somewhat less > knowledge (I think) than sysinstall itself, and would have many > classes of systems that simply by nature of being a liveCD it wouldn't > have to worry about (I think of headless servers and 486s). Just > thought I would toss the idea out to see what people thought of it at > this point (as I've not heard much about it for a while, and it seems > that many of them were getting ready for 5-STABLE). I've spent the past two weeks installing every open-source OS I could get my hands on into VPC2004 and VMWare virtual machines. There are a few out there which do provide graphical, or pseudo-graphical, installations. Solaris had an X-based install but I suspect Solaris has a much narrower range of hardware it needs to support. Plan9 managed to do some very lightweight installation (that fit on a *floppy*) and was still graphical. I liked their install very much -- it was no-frills console windows, but it provided mouse support and a couple of "informative" extra windows. But this brings up exactly the problem with GUI installers -- the plan9 install didn't support the "graphics adapter" that Virtual PC emulates, and so it just didn't work. For a nice OS like plan9, this isn't a big deal. For an OS like FreeBSD I don't think that would be acceptable. Overall, I installed 10 different OS's, and FreeBSD was probably my second favorite (I did like DFly, as mentioned before). It's straightforward, it guides you through the process fairly well, it does most of the grunt work, it's flexible, it loads and responds fast, and it's got a lot of on-screen assistance. I picked it up and used it, with no documentation, the very first time I installed FBSD anywhere. (Contract to Gentoo, a geek-favorite, which I had to keep their installation handbook open in a browser the entire time). My only real complaint (not minior nit-picks like about the auto-labelling etc) is that it's too easy to move around inside the installation and go the wrong place. I routinely find myself trying to change a simple setting post-install, and somehow triggering the entire extraction process again. DFly's installer is more wizard-like, in that you can't really do things out of order. Otherwise, I would like to see the install stay similar to what it is. --Mike From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 19:48:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D5E016A4CE for ; Thu, 2 Dec 2004 19:48:56 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1432F43D5C for ; Thu, 2 Dec 2004 19:48:56 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so838439rnf for ; Thu, 02 Dec 2004 11:48:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Ki61+4bGgZTa+pxGuHQg7t5soSheBRucbCjxs+R05dXE+VGueJiek9LQdVa0vCwZXKVujPv/YWk0D25471VUqZrPAWFON8yVbmq3HFnoBiEIflCy7ZHF3UA4ZiQVxm/WDen3OV89WJeSxCLDHLOOIfPGK0XegByYKs/0z8vgzjM= Received: by 10.38.96.9 with SMTP id t9mr148987rnb; Thu, 02 Dec 2004 11:48:54 -0800 (PST) Received: by 10.38.15.38 with HTTP; Thu, 2 Dec 2004 11:48:54 -0800 (PST) Message-ID: Date: Thu, 2 Dec 2004 19:48:54 +0000 From: Eric Kjeldergaard To: Scott Long In-Reply-To: <41AE3F80.1000506@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41AE3F80.1000506@freebsd.org> cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eric Kjeldergaard List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 19:48:56 -0000 > 4. Journaled filesystem. While we can debate the merits of speed and > data integrety of journalling vs. softupdates, the simple fact remains > that softupdates still requires a fsck run on recovery, and the > multi-terabyte filesystems that are possible these days make fsck a very > long and unpleasant experience, even with bg-fsck. There was work at > some point at RPI to add journaling to UFS, but there hasn't been much > status on that in a long time. There have also been proposals and > works-in-progress to port JFS, ReiserFS, and XFS. Some of these efforts > are still alive, but they need to be seen through to completion. But at > the risk of opening a can of worms here, I'll say that it's also > important to explore non-GPL alternatives. A thread (http://lists.freebsd.org/pipermail/freebsd-current/2004-October/040904.html )happens to be talking about ro support for the ReiserFS. After having used this for quite some time in a Linux environment, I can't help but notice that it seriously outperforms any other filesystem I've tried on large numbers of littlish files. A beautiful application that I've rather wanted to try for a while was this on the ports tree. The stage of the current implementation is, as I said, read-only. Further, it's currently i386 only. However, I think that there is enough interest in this new (and relatively exciting) filesystem that we may be able to find some developers with time (Possibly including myself) and desire to try to implement write support and do some porting. To ease any qualms with regards to licensing, it appears (http://lists.freebsd.org/pipermail/freebsd-current/2004-October/040998.html) that the current implementation is BSD licensed. -- If I write a signature, my emails will appear more personalised. From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 19:55:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C3A416A4CE for ; Thu, 2 Dec 2004 19:55:02 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21D2443D1F for ; Thu, 2 Dec 2004 19:55:02 +0000 (GMT) (envelope-from jon.drews@gmail.com) Received: by wproxy.gmail.com with SMTP id 37so1280536wra for ; Thu, 02 Dec 2004 11:55:01 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=KFMIeXmJ8T3XOV2H+ywt0+3qgJnFTR9DdXEnKksNZsejlAMhEFgNAFBBY8friWVMoQky3O08cYEdI445CIk0cQM7sl2QWaE+zWjayRmumshSS/PPGnfuYwYjkvGDmZNDkCzxqES31lcU1m+cfxXfsDKG8iw8Ex0cPkCdEF5d0+E= Received: by 10.54.46.2 with SMTP id t2mr727063wrt; Thu, 02 Dec 2004 11:55:01 -0800 (PST) Received: by 10.54.54.2 with HTTP; Thu, 2 Dec 2004 11:55:01 -0800 (PST) Message-ID: <8cb27cbf04120211553b4304bf@mail.gmail.com> Date: Thu, 2 Dec 2004 12:55:01 -0700 From: Jon Drews To: current@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41AE3F80.1000506@freebsd.org> <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> <20041202190337.GY79646@cirb503493.alcatel.com.au> Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jon Drews List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 19:55:02 -0000 On Thu, 2 Dec 2004 19:19:12 +0000, Eric Kjeldergaard wrote: > I want to preface by saying that I certainly don't think a GUI > installer should replace what FreeBSD ships with now. I agree with Eric. As a FreeBSD desktop user, I think (IMHO) that a gui installer is a high cost low yield item. It would take a lot of effort to make it work right. My experience with both YaST and Mandrakes installer was that it took several releases for the bugs to get worked out. IIRC SuSE introduced the GUI YaST2 in 7.0 and I think it was working pretty well by 8.0 but that was over the period of a year. From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 20:06:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9928B16A4CE for ; Thu, 2 Dec 2004 20:06:15 +0000 (GMT) Received: from smtpq1.home.nl (smtpq1.home.nl [213.51.128.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5ED443D45 for ; Thu, 2 Dec 2004 20:06:14 +0000 (GMT) (envelope-from dodell@sitetronics.com) Received: from [213.51.128.135] (port=52989 helo=smtp4.home.nl) by smtpq1.home.nl with esmtp (Exim 4.30) id 1CZxDR-0004CY-IV; Thu, 02 Dec 2004 21:06:13 +0100 Received: from cc740438-a.deven1.ov.home.nl ([82.75.136.183]:4430 helo=[192.168.1.100]) by smtp4.home.nl with esmtp (Exim 4.30) id 1CZxDM-0007gS-L5; Thu, 02 Dec 2004 21:06:08 +0100 Message-ID: <41AF75B1.6070306@sitetronics.com> Date: Thu, 02 Dec 2004 21:06:09 +0100 From: "Devon H. O'Dell" User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jon Drews References: <41AE3F80.1000506@freebsd.org> <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> <20041202190337.GY79646@cirb503493.alcatel.com.au> <8cb27cbf04120211553b4304bf@mail.gmail.com> In-Reply-To: <8cb27cbf04120211553b4304bf@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AtHome-MailScanner-Information: Please contact support@home.nl for more information X-AtHome-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:06:15 -0000 Jon Drews wrote: > On Thu, 2 Dec 2004 19:19:12 +0000, Eric Kjeldergaard wrote: > >>I want to preface by saying that I certainly don't think a GUI >>installer should replace what FreeBSD ships with now. > > > I agree with Eric. As a FreeBSD desktop user, I think (IMHO) that a > gui installer is a high cost low yield item. It would take a lot of > effort to make it work right. My experience with both YaST and > Mandrakes installer was that it took several releases for the bugs to > get worked out. IIRC SuSE introduced the GUI YaST2 in 7.0 and I think > it was working pretty well by 8.0 but that was over the period of a > year. A couple of the features of our installer are that it is scriptable and that all of the handling of the installation is done in the back end. This means that the only bugs which would exist in a GUI front end (assuming the backend works, as it does) to the installer would be problems with the widget library or with how it is used. It'd be pretty simple to extend the installer to use pretty much any graphical toolkit. Its client/server design, in that sense, makes it very suitable for any purpose. FWIW, I saw on another response to this thread that the installer should be based on a Live CD. Ours is, and is used in the FreeSBIE project to install FreeBSD to the disk, if desired. Kind regards, Devon H. O'Dell From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 20:13:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C80216A4CE for ; Thu, 2 Dec 2004 20:13:14 +0000 (GMT) Received: from athena.softcardsystems.com (mail.softcardsystems.com [12.34.136.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE6B143D53 for ; Thu, 2 Dec 2004 20:13:13 +0000 (GMT) (envelope-from sah@softcardsystems.com) Received: from athena (athena [12.34.136.114])iB2L8fgf029310; Thu, 2 Dec 2004 16:08:41 -0500 Date: Thu, 2 Dec 2004 16:08:41 -0500 (EST) From: Sam X-X-Sender: sah@athena To: Eric Kjeldergaard In-Reply-To: Message-ID: References: <41AE3F80.1000506@freebsd.org> <41AE55D7.8020709@freebsd.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:13:14 -0000 > I want to preface by saying that I certainly don't think a GUI > installer should replace what FreeBSD ships with now. Having said > that: It has been suggested in the past, and may as well be suggested > again now, that a liveCD installer be created. I know that amongst > desktop/first-time users this would be a welcome addition. I also > realise that it isn't FreeBSD's main market (though it is a major > consideration). This sort of project could be done with somewhat less > knowledge (I think) than sysinstall itself, and would have many > classes of systems that simply by nature of being a liveCD it wouldn't > have to worry about (I think of headless servers and 486s). Just > thought I would toss the idea out to see what people thought of it at > this point (as I've not heard much about it for a while, and it seems > that many of them were getting ready for 5-STABLE). I like the idea of having a separate boot-CD for those wishing to get a fancy GUI installer -- just so long as you can still boot from CD1 and get a text-based version, no matter how rudimentary. From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 20:25:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77EFD16A4CE for ; Thu, 2 Dec 2004 20:25:44 +0000 (GMT) Received: from mail.crypta.net (mail.crypta.net [83.136.131.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CF6743D2D for ; Thu, 2 Dec 2004 20:25:43 +0000 (GMT) (envelope-from ah@crypta.net) Received: by mail.crypta.net (Postfix, from userid 1001) id 1D9B5ECD434; Thu, 2 Dec 2004 21:25:41 +0100 (CET) Date: Thu, 2 Dec 2004 21:25:41 +0100 From: Andy Hilker To: current@freebsd.org Message-ID: <20041202202541.GA52937@mail.crypta.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0xEC6E1071 X-PGP-Fingerprint: 9B2E 5892 AD93 D5C5 FB8E 3912 35D6 951B EC6E 1071 Organization: cryptobank - Andy Hilker Subject: linuxthreads broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:25:44 -0000 Hi, i am running mysqld 4.1 with linuxthreads since i experience more stability and performance than without linuxthreads before a few months. now linuxthreads port is broken (see below). do someone has a patch or knows how to fix it? btw. does mysqld 4.1 runs now good on smp machines with current? maybe i will give a new try on this... bye, Andy -- cd /usr/ports/devel/linuxthreads/work/linuxthreads-2.2.3_16/libstdc++ ; /usr/bin/env USING_GCC3=true SHELL=/bin/sh PORTOBJFORMAT=elf PREFIX=/usr/local LOCALBASE=/usr/local X11BASE=/usr/X11R6 MOTIFLIB="-L/usr/X11R6/lib -lXm -lXp" LIBDIR="/usr/lib" CFLAGS="-O -pipe -DKVA_PAGES=640 -march=pentium4" CXXFLAGS="-O -pipe -DKVA_PAGES=640 -march=pentium4" MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install -s -o root -g wheel -m 555" BSD_INSTALL_SCRIPT="install -o root -g wheel -m 555" BSD_INSTALL_DATA="install -o root -g wheel -m 444" BSD_INSTALL_MAN="install -o root -g wheel -m 444" make Warning: Object directory not changed from original /usr/ports/devel/linuxthreads/work/linuxthreads-2.2.3_16/libstdc++ c++ -O -pipe -DKVA_PAGES=640 -march=pentium4 -D_PTHREADS -I../ -I../sysdeps/i386 -I../sysdeps/pthread -I../sysdeps/unix/sysv/linux -DIN_GLIBCPP_V3 -DHAVE_CONFIG_H -I/usr/src/gnu/lib/libstdc++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/libsupc++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcc -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include -fno-implicit-templates -ffunction-sections -fdata-sections -Wno-deprecated -c /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/allocator.cc In file included from /usr/include/c++/3.3/bits/stl_alloc.h:91, from /usr/include/c++/3.3/memory:55, from /usr/src/contrib/libstdc++/src/allocator.cc:35: /usr/src/contrib/libstdc++/include/bits/atomicity.h:33:30: bits/atomic_word.h: No such file or directory In file included from /usr/include/c++/3.3/bits/stl_alloc.h:91, from /usr/include/c++/3.3/memory:55, from /usr/src/contrib/libstdc++/src/allocator.cc:35: /usr/src/contrib/libstdc++/include/bits/atomicity.h:39: error: syntax error before `(' token /usr/src/contrib/libstdc++/include/bits/atomicity.h:43: error: syntax error before `*' token In file included from /usr/include/c++/3.3/memory:55, from /usr/src/contrib/libstdc++/src/allocator.cc:35: /usr/include/c++/3.3/bits/stl_alloc.h:353: error: syntax error before `;' token /usr/include/c++/3.3/bits/stl_alloc.h:382: error: syntax error before `;' token /usr/include/c++/3.3/bits/stl_alloc.h:452: error: syntax error before `<' token /usr/include/c++/3.3/bits/stl_alloc.h:452: error: `__threads' was not declared in this scope /usr/include/c++/3.3/bits/stl_alloc.h:452: error: `__inst' was not declared in this scope /usr/include/c++/3.3/bits/stl_alloc.h:452: error: template argument 1 is invalid /usr/include/c++/3.3/bits/stl_alloc.h:452: error: template argument 2 is invalid /usr/include/c++/3.3/bits/stl_alloc.h:601: error: syntax error before `<' token /usr/include/c++/3.3/bits/stl_alloc.h:601: error: `__threads' was not declared in this scope /usr/include/c++/3.3/bits/stl_alloc.h:601: error: `__inst' was not declared in this scope /usr/include/c++/3.3/bits/stl_alloc.h:601: error: template argument 1 is invalid /usr/include/c++/3.3/bits/stl_alloc.h:601: error: template argument 2 is invalid /usr/include/c++/3.3/bits/stl_alloc.h:602: error: braces around scalar initializer for `int' /usr/include/c++/3.3/bits/stl_alloc.h:602: error: ignoring extra initializers for `int' In file included from /usr/src/contrib/libstdc++/src/allocator.cc:37: /usr/src/contrib/libstdc++/include/ext/pool_allocator.h:122: error: syntax error before `;' token /usr/src/contrib/libstdc++/include/ext/pool_allocator.h:184: error: syntax error before `<' token /usr/src/contrib/libstdc++/include/ext/pool_allocator.h:184: error: `_Tp' was not declared in this scope /usr/src/contrib/libstdc++/include/ext/pool_allocator.h:184: error: template argument 1 is invalid /usr/src/contrib/libstdc++/include/ext/pool_allocator.h:184: error: ISO C++ forbids declaration of `_S_force_new' with no type *** Error code 1 Stop in /usr/ports/devel/linuxthreads/work/linuxthreads-2.2.3_16/libstdc++. *** Error code 1 From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 20:39:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB69716A4CE for ; Thu, 2 Dec 2004 20:39:31 +0000 (GMT) Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9868643D41 for ; Thu, 2 Dec 2004 20:39:31 +0000 (GMT) (envelope-from roberthuff@rcn.com) Received: from 209-6-197-67.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([209.6.197.67] helo=jerusalem.litteratus.org.litteratus.org) by smtp03.mrf.mail.rcn.net with esmtp (Exim 3.35 #7) id 1CZxja-0007g4-00 for current@freebsd.org; Thu, 02 Dec 2004 15:39:27 -0500 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16815.31852.46550.983276@jerusalem.litteratus.org> Date: Thu, 2 Dec 2004 15:34:52 -0500 To: current@freebsd.org In-Reply-To: <20041202002939.GA2834@ns1.xcllnt.net> References: <20041202002939.GA2834@ns1.xcllnt.net> X-Mailer: VM 7.17 under 21.5 (beta16) "celeriac" XEmacs Lucid Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:39:31 -0000 Marcel Moolenaar writes: > > 1. Keyboard multiplexer. > > I actually fail to stop thinking about a complete syscons and > pcvt replacement. You know, the one and only console > implementation that makes all others obsolete. Big plans, little > time, yada yada yada... As long as we're talking about keyboards ... may I add "Get the boot code to recognize USB keyboards." (Unless this has already happened and I missed the meno. Again.) Robert Huff From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 20:47:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A4E316A526; Thu, 2 Dec 2004 20:47:50 +0000 (GMT) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE7C543D1F; Thu, 2 Dec 2004 20:47:48 +0000 (GMT) (envelope-from netch@lucky.net) Received: from burka.carrier.kiev.ua (netch@localhost [127.0.0.1]) by burka.carrier.kiev.ua with ESMTP id iB2KladX087628; Thu, 2 Dec 2004 22:47:37 +0200 (EET) (envelope-from netch@burka.carrier.kiev.ua) Received: (from netch@localhost) by burka.carrier.kiev.ua (8.12.11/8.12.11/Submit) id iB2KlaRj087625; Thu, 2 Dec 2004 22:47:36 +0200 (EET) (envelope-from netch) Date: Thu, 2 Dec 2004 22:47:36 +0200 From: Valentin Nechayev To: Scott Long Message-ID: <20041202204735.GA74249@lucky.net> References: <41AE3F80.1000506@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <41AE3F80.1000506@freebsd.org> X-42: On X-Verify-Sender: Address has been verified (burka.carrier.kiev.ua) X-Antivirus: Dr.Web (R) for Mail Servers on kozlik.carrier.kiev.ua host X-Antivirus-Code: 100000 cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: netch@lucky.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:47:50 -0000 Wed, Dec 01, 2004 at 15:02:40, scottl wrote about "My project wish-list fo= r the next 12 months":=20 [...] > 2. New installer. I know some people still consider this a joke, but > the reality is that sysinstall is no longer state of the art. It's > fairly good at the simple task that it does, but it's becoming harder > and harder to fix bugs and extend functionality in it. It's also > fairly unfriendly to those of us who haven't been using it since 1995. > The DFly folks have some very interesting work in this area > (www.bsdinstaller.com) and it would be very good to see if we can > collaborate with them on it. If we're going to discuss admin-friendiness... - Resplit distribution sets. It's simply shame when unpacking base overwrit= es existing log files (e.g. during binary upgrade). At least /etc and /var/log _must_ be separated. Also, I consider openbsd scheme to be pleasant: separate build tools set (gcc, binutils, etc.) =66rom main functioning set. As maximum, convert them into packages and register along with ports. - Fix the most ugly sysinstall features. E.g. setting active flags on all partitions by default, along with setting MBR, leads to unbootable system. This was _constant_ students' error on FreeBSD administration courses. - Provide more administrative tools. For now, one can't see interface queue lengths, netgraph queue lens, tune their sizes, calculate memory occupied by a bunch of processes without multiple counting shared pages... -netch- From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 20:50:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9342E16A4CE for ; Thu, 2 Dec 2004 20:50:03 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 427D243D1F for ; Thu, 2 Dec 2004 20:50:03 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iB2KpP87025023; Thu, 2 Dec 2004 12:51:25 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iB2KpO9s025022; Thu, 2 Dec 2004 12:51:24 -0800 Date: Thu, 2 Dec 2004 12:51:24 -0800 From: Brooks Davis To: Robert Huff Message-ID: <20041202205124.GA18122@odin.ac.hmc.edu> References: <20041202002939.GA2834@ns1.xcllnt.net> <16815.31852.46550.983276@jerusalem.litteratus.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline In-Reply-To: <16815.31852.46550.983276@jerusalem.litteratus.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:50:03 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 02, 2004 at 03:34:52PM -0500, Robert Huff wrote: >=20 > Marcel Moolenaar writes: >=20 > > > 1. Keyboard multiplexer. > > =20 > > I actually fail to stop thinking about a complete syscons and > > pcvt replacement. You know, the one and only console > > implementation that makes all others obsolete. Big plans, little > > time, yada yada yada... >=20 > As long as we're talking about keyboards ... may I add "Get the > boot code to recognize USB keyboards." > (Unless this has already happened and I missed the meno. > Again.) The code reconginzes the keyboard, you just can't use it by default. That's what the mux will fix. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBr4BMXY6L6fI4GtQRArGVAKDduVgAAhiKN8n+bVfEwcqVg7BduACg14Kr C+dPIoqzzkuUBquol/UVa0E= =AH1l -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 20:50:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AAE816A4E4 for ; Thu, 2 Dec 2004 20:50:19 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8920A43D41 for ; Thu, 2 Dec 2004 20:50:19 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB2Ks5en068314; Thu, 2 Dec 2004 13:54:05 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AF8017.4000206@freebsd.org> Date: Thu, 02 Dec 2004 13:50:31 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Huff References: <20041202002939.GA2834@ns1.xcllnt.net> <16815.31852.46550.983276@jerusalem.litteratus.org> In-Reply-To: <16815.31852.46550.983276@jerusalem.litteratus.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:50:28 -0000 Robert Huff wrote: > Marcel Moolenaar writes: > > >> > 1. Keyboard multiplexer. >> >> I actually fail to stop thinking about a complete syscons and >> pcvt replacement. You know, the one and only console >> implementation that makes all others obsolete. Big plans, little >> time, yada yada yada... > > > As long as we're talking about keyboards ... may I add "Get the > boot code to recognize USB keyboards." > (Unless this has already happened and I missed the meno. > Again.) > > > Robert Huff > Are you talking about putting a minimal USB stack into the boot loader? That _certainly_ cannot fit into boot0, and I doubt that it can fit into boot1. It might be possible for boot2/BTX/loader, but that's also quite a bit of work. I take it that your BIOS does not provide keyboard emulation for you? If not, I guess that it makes it difficult to boot to DOS. Scott From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 20:52:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D30816A4CE for ; Thu, 2 Dec 2004 20:52:38 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D33943D5C for ; Thu, 2 Dec 2004 20:52:38 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so844657rnf for ; Thu, 02 Dec 2004 12:52:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=NieV4Bn50vC/x7NwH7F9NHuAVkSwmC74z5jFOT+BFWvaXxR23/P10hS46XhZ5dhR1ZOnrLIqzF/2rGqMtL4C8J8Mw62L4QKrQDHnpCAnT1pDffA2tqljHtRX6cATbzfmphdy9asK2NRUa6ny9lb7lYeFVRlDpfFdRTfj/BZVZ7o= Received: by 10.38.77.68 with SMTP id z68mr1028173rna; Thu, 02 Dec 2004 12:52:36 -0800 (PST) Received: by 10.38.15.38 with HTTP; Thu, 2 Dec 2004 12:52:36 -0800 (PST) Message-ID: Date: Thu, 2 Dec 2004 20:52:36 +0000 From: Eric Kjeldergaard To: current@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41AE3F80.1000506@freebsd.org> <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> <20041202190337.GY79646@cirb503493.alcatel.com.au> <8cb27cbf04120211553b4304bf@mail.gmail.com> <41AF75B1.6070306@sitetronics.com> Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eric Kjeldergaard List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 20:52:38 -0000 > FWIW, I saw on another response to this thread that the installer should > be based on a Live CD. Ours is, and is used in the FreeSBIE project to > install FreeBSD to the disk, if desired. Ooh, ooh, do tell. I had no idea that one existed. Does it allow for simple base installs? In fact, does it have about the same featureset as sysinstall? Do I get a link? Please self-promote :) I'm sure I'm not alone in the desire for a GUI installer as an option (not a replacement, again...need to reiterate that I love the ability to install fBSD in 8 minutes on a 200mhz machine via a familiar ncurses interface) for desktop users. -- If I write a signature, my emails will appear more personalised. -- If I write a signature, my emails will appear more personalised. From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 21:00:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D799C16A4CE; Thu, 2 Dec 2004 21:00:16 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0E6B43D46; Thu, 2 Dec 2004 21:00:16 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iB2L1c9c026435; Thu, 2 Dec 2004 13:01:38 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iB2L1cBP026434; Thu, 2 Dec 2004 13:01:38 -0800 Date: Thu, 2 Dec 2004 13:01:38 -0800 From: Brooks Davis To: Valentin Nechayev Message-ID: <20041202210138.GA25979@odin.ac.hmc.edu> References: <41AE3F80.1000506@freebsd.org> <20041202204735.GA74249@lucky.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <20041202204735.GA74249@lucky.net> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:00:17 -0000 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 02, 2004 at 10:47:36PM +0200, Valentin Nechayev wrote: > Wed, Dec 01, 2004 at 15:02:40, scottl wrote about "My project wish-list = for the next 12 months":=20 >=20 > [...] > > 2. New installer. I know some people still consider this a joke, but > > the reality is that sysinstall is no longer state of the art. It's > > fairly good at the simple task that it does, but it's becoming harder > > and harder to fix bugs and extend functionality in it. It's also > > fairly unfriendly to those of us who haven't been using it since 1995. > > The DFly folks have some very interesting work in this area > > (www.bsdinstaller.com) and it would be very good to see if we can > > collaborate with them on it. >=20 > If we're going to discuss admin-friendiness... >=20 > - Resplit distribution sets. It's simply shame when unpacking base overwr= ites > existing log files (e.g. during binary upgrade). > At least /etc and /var/log _must_ be separated. Also, I consider openbsd > scheme to be pleasant: separate build tools set (gcc, binutils, etc.) > from main functioning set. > As maximum, convert them into packages and register along with ports. The log files shouldn't be there at all. I'm planning to remove all of them from the distribution sets and do the creation during boot. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBr4KxXY6L6fI4GtQRAn7EAKDjuRWirLIbCgY8sOwmJPc0mJnIuQCfbDfO +Vu+sWV0qgluuVvCsLC6jDM= =lj75 -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 21:16:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC25516A4CE for ; Thu, 2 Dec 2004 21:16:02 +0000 (GMT) Received: from just.puresimplicity.net (just.puresimplicity.net [140.177.207.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D32D43D3F for ; Thu, 2 Dec 2004 21:16:02 +0000 (GMT) (envelope-from hemi@puresimplicity.net) Received: from just.puresimplicity.net (localhost.puresimplicity.net [127.0.0.1])iB2LG147013430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 15:16:01 -0600 (CST) (envelope-from hemi@just.puresimplicity.net) Received: (from hemi@localhost) by just.puresimplicity.net (8.13.1/8.13.1/Submit) id iB2LG1Ll013429; Thu, 2 Dec 2004 15:16:01 -0600 (CST) (envelope-from hemi) Date: Thu, 2 Dec 2004 15:16:01 -0600 From: Josh Tolbert To: Robert Huff Message-ID: <20041202211601.GA12673@just.puresimplicity.net> References: <20041202002939.GA2834@ns1.xcllnt.net> <16815.31852.46550.983276@jerusalem.litteratus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16815.31852.46550.983276@jerusalem.litteratus.org> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:16:03 -0000 On Thu, Dec 02, 2004 at 03:34:52PM -0500, Robert Huff wrote: > > Marcel Moolenaar writes: > > > > 1. Keyboard multiplexer. > > > > I actually fail to stop thinking about a complete syscons and > > pcvt replacement. You know, the one and only console > > implementation that makes all others obsolete. Big plans, little > > time, yada yada yada... > > As long as we're talking about keyboards ... may I add "Get the > boot code to recognize USB keyboards." > (Unless this has already happened and I missed the meno. > Again.) > > > Robert Huff As long as we're talking about keyboards, re-vamping the console driver, etc., can something be done with psm? FreeBSD is the only OS that requires me to pass flags to psm to get my mouse to behave properly on my KVM switch, and the flag I use (0x200) forces "true" PS/2 mode, disabling the wheel and such. Granted, the only other OSes I've had on KVM switches with FreeBSD machines are Windows, Linux and OS/X, but it still seems like something's amiss with psm. Thanks, Josh -- Josh Tolbert hemi@puresimplicity.net || http://www.puresimplicity.net/~hemi/ If your sysadmin's not being fascist, you're paying him too much. --Sam Greenfield From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 21:28:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B10516A4CE for ; Thu, 2 Dec 2004 21:28:46 +0000 (GMT) Received: from duchess.speedfactory.net (duchess.speedfactory.net [66.23.201.84]) by mx1.FreeBSD.org (Postfix) with SMTP id E78CA43D48 for ; Thu, 2 Dec 2004 21:28:45 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 25541 invoked by uid 89); 2 Dec 2004 21:28:44 -0000 Received: from duchess.speedfactory.net (66.23.201.84) by duchess.speedfactory.net with SMTP; 2 Dec 2004 21:28:44 -0000 Received: (qmail 21553 invoked by uid 89); 2 Dec 2004 21:27:19 -0000 Received: from unknown (HELO palm.tree.com) (66.23.216.49) by duchess.speedfactory.net with SMTP; 2 Dec 2004 21:27:19 -0000 Received: from [127.0.0.1] (localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id iB2LRI9k041977; Thu, 2 Dec 2004 16:27:18 -0500 (EST) (envelope-from ups@tree.com) From: Stephan Uphoff To: Andre Oppermann In-Reply-To: <41AF29AC.6030401@freebsd.org> References: <41AE3F80.1000506@freebsd.org> <41AF29AC.6030401@freebsd.org> Content-Type: text/plain Message-Id: <1102022838.11465.7735.camel@palm.tree.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 02 Dec 2004 16:27:18 -0500 Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:28:46 -0000 On Thu, 2004-12-02 at 09:41, Andre Oppermann wrote: > Scott Long wrote: > > 5. Clustered FS support. SANs are all the rage these days, and > > clustered filesystems that allow data to be distributed across many > > storage enpoints and accessed concurrently through the SAN are very > > powerful. RedHat recently bought Sistina and re-opened the GFS source > > code, so exploring this would be very interesting. > > There are certain steps that can be be taken one at a time. For example > it should be relatively easy to mount snapshots (ro) from more than one > machine. Next step would be to mount a full 'rw' filesystem as 'ro' on > other boxes. This would require cache and sector invalidation broadcasting > from the 'rw' box to the 'ro' mounts. Mhhh .. if you plan to invalidate at the disk block cache layer then you will run into race conditions with UFS/FFS (Especially with remove operations) I was once called in to evaluate such a multiple reader/single writer system based on an UFS like file system and block layer invalidation and had to convince management to kill it. (It appeared to work and actually made it though internal and customer acceptance testing before failing horrible in the field). If you send me more details on your proposed cache and sector invalidation/cluster design I will be happy to review it. > The holy grail of course is to mount > the same filesystem 'rw' on more than one box, preferrably more than two. > This requires some more involved synchronization and locking on top of the > cache invalidation. And make sure that the multi-'rw' cluster stays alive > if one of the participants freezes and doesn't respond anymore. > > Scrolling through the UFS/FFS code I think the first one is 2-3 days of > work. The second 2-4 weeks and the third 2-3 month to get it right. > If someone would throw up the money... From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 21:33:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6CE016A4CE; Thu, 2 Dec 2004 21:33:41 +0000 (GMT) Received: from kraid.nerim.net (smtp-104-thursday.nerim.net [62.4.16.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C4F943D39; Thu, 2 Dec 2004 21:33:41 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from [192.168.1.11] (dumbbell.net1.nerim.net [80.65.225.171]) by kraid.nerim.net (Postfix) with ESMTP id A143941564; Thu, 2 Dec 2004 22:33:38 +0100 (CET) Message-ID: <41AF8A18.8090303@club-internet.fr> Date: Thu, 02 Dec 2004 22:33:12 +0100 From: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041108 X-Accept-Language: fr, en-us, en MIME-Version: 1.0 To: Eric Kjeldergaard References: <41AE3F80.1000506@freebsd.org> In-Reply-To: X-Enigmail-Version: 0.89.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE049E5719DC1280CD4096CD9" cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:33:42 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE049E5719DC1280CD4096CD9 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Eric Kjeldergaard wrote: >> 4. Journaled filesystem. > > The stage of the current implementation is, as I said, read-only. > Further, it's currently i386 only. In theory, it shouldn't be tied to i386, but I never tested it somewhere else unfortunately. > However, I think that there is enough interest in this new (and > relatively exciting) filesystem that we may be able to find some > developers with time (Possibly including myself) and desire to try to > implement write support and do some porting. To ease any qualms > with regards to licensing, it appears > (http://lists.freebsd.org/pipermail/freebsd-current/2004-October/040998.html) > that the current implementation is BSD licensed. Not exactly. Only the mount_reiserfs command is under BSD. The kernel module is GPL. I don't know neither JFS nor XFS, but Reiser4 may be a great candidate too (the current port is ReiserFS 3.6 only). It sure doesn't have the maturity of ReiserFS but brings nice features. Jean-Seb --------------enigE049E5719DC1280CD4096CD9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBr4oza+xGJsFYOlMRAmTAAJkBotrMQiU3+FFQ8fAo1x+CjpnvPgCfbdVl HvIEvl4AbkKlzbwmRDYnaDs= =V9jN -----END PGP SIGNATURE----- --------------enigE049E5719DC1280CD4096CD9-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 21:41:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 162C916A4CE for ; Thu, 2 Dec 2004 21:41:37 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C84043D54 for ; Thu, 2 Dec 2004 21:41:36 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so849669rnf for ; Thu, 02 Dec 2004 13:41:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=EEDUKAdGBwIf8pDHSHqmPI1HVxeVCy7b5QuDW7HNQSE8aSmrupYXrr+Yzl47F9ARfG4UMHRRPbrakW61j5ku/b06678pgAwTm4880LJKjR1sXoc0O+w2iwISmoHEc7TuydkSPRn2Zmxsu4ybr0RNLy2tu+00lDhJVsQRM0WUgkk= Received: by 10.38.15.61 with SMTP id 61mr1040214rno; Thu, 02 Dec 2004 13:41:35 -0800 (PST) Received: by 10.38.15.38 with HTTP; Thu, 2 Dec 2004 13:41:35 -0800 (PST) Message-ID: Date: Thu, 2 Dec 2004 21:41:35 +0000 From: Eric Kjeldergaard To: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= In-Reply-To: <41AF8A18.8090303@club-internet.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41AE3F80.1000506@freebsd.org> <41AF8A18.8090303@club-internet.fr> cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eric Kjeldergaard List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:41:37 -0000 > >> 4. Journaled filesystem. > > > > The stage of the current implementation is, as I said, read-only. > > Further, it's currently i386 only. > > In theory, it shouldn't be tied to i386, but I never tested it somewhere > else unfortunately. > Got that from the reiserfs port which says it doesn't compile other than under i386. > > However, I think that there is enough interest in this new (and > > relatively exciting) filesystem that we may be able to find some > > developers with time (Possibly including myself) and desire to try to > > implement write support and do some porting. To ease any qualms > > with regards to licensing, it appears > > (http://lists.freebsd.org/pipermail/freebsd-current/2004-October/040998.html) > > that the current implementation is BSD licensed. > > Not exactly. Only the mount_reiserfs command is under BSD. The kernel > module is GPL. > Oh, I'm sorry. I guess I read quickly and w/o thinking enough. I suppose that would put is near square 1. > I don't know neither JFS nor XFS, but Reiser4 may be a great candidate > too (the current port is ReiserFS 3.6 only). It sure doesn't have the > maturity of ReiserFS but brings nice features. That would be nice if the support could be gathered for it. I do like it better than XFS (which I've tried). -- If I write a signature, my emails will appear more personalised. From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 21:43:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 266C716A4CE; Thu, 2 Dec 2004 21:43:09 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90EE443D5A; Thu, 2 Dec 2004 21:43:08 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB2Lks5N068636; Thu, 2 Dec 2004 14:46:54 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AF8C78.8050806@freebsd.org> Date: Thu, 02 Dec 2004 14:43:20 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephan Uphoff References: <41AE3F80.1000506@freebsd.org> <41AF29AC.6030401@freebsd.org> <1102022838.11465.7735.camel@palm.tree.com> In-Reply-To: <1102022838.11465.7735.camel@palm.tree.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: hackers@freebsd.org cc: Andre Oppermann cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:43:09 -0000 Stephan Uphoff wrote: > On Thu, 2004-12-02 at 09:41, Andre Oppermann wrote: > >>Scott Long wrote: >> >>>5. Clustered FS support. SANs are all the rage these days, and >>>clustered filesystems that allow data to be distributed across many >>>storage enpoints and accessed concurrently through the SAN are very >>>powerful. RedHat recently bought Sistina and re-opened the GFS source >>>code, so exploring this would be very interesting. >> >>There are certain steps that can be be taken one at a time. For example >>it should be relatively easy to mount snapshots (ro) from more than one >>machine. Next step would be to mount a full 'rw' filesystem as 'ro' on >>other boxes. This would require cache and sector invalidation broadcasting >>from the 'rw' box to the 'ro' mounts. > > > Mhhh .. if you plan to invalidate at the disk block cache layer then you > will run into race conditions with UFS/FFS (Especially with remove > operations) > I was once called in to evaluate such a multiple reader/single writer > system based on an UFS like file system and block layer invalidation and > had to convince management to kill it. (It appeared to work and actually > made it though internal and customer acceptance testing before failing > horrible in the field). > > If you send me more details on your proposed cache and sector > invalidation/cluster design I will be happy to review it. > > > >>The holy grail of course is to mount >>the same filesystem 'rw' on more than one box, preferrably more than two. >>This requires some more involved synchronization and locking on top of the >>cache invalidation. And make sure that the multi-'rw' cluster stays alive >>if one of the participants freezes and doesn't respond anymore. >> >>Scrolling through the UFS/FFS code I think the first one is 2-3 days of >>work. The second 2-4 weeks and the third 2-3 month to get it right. >>If someone would throw up the money... > > Although I don't know the specifics of your experience, I can easily imagine how hard it would be to make this work on UFS. Common operations like walking a file path to the root are nearly impossible to do reliably without an overbearing amount of synchronization. Then you have all of the problems synchronizing buffered data and metadata. Softupdates would be a nightmare, if not impossible. Scott From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 21:51:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A677816A4CE; Thu, 2 Dec 2004 21:51:26 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33A1043D5E; Thu, 2 Dec 2004 21:51:26 +0000 (GMT) (envelope-from marks@ripe.net) Received: by postman.ripe.net (Postfix, from userid 8) id 9B013246D0; Thu, 2 Dec 2004 22:51:25 +0100 (CET) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 96F4D24654; Thu, 2 Dec 2004 22:51:24 +0100 (CET) Received: from ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id iB2LpOLE026697; Thu, 2 Dec 2004 22:51:24 +0100 Received: (nullmailer pid 1983 invoked by uid 1001); Thu, 02 Dec 2004 21:51:23 -0000 Date: Thu, 2 Dec 2004 22:51:23 +0100 From: Mark Santcroos To: Poul-Henning Kamp Message-ID: <20041202215123.GA1512@laptop.6bone.nl> References: <200412012316.iB1NGcmu024834@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412012316.iB1NGcmu024834@repoman.freebsd.org> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.000012 / -5.9 X-RIPE-Signature: 71756f56c269b583650694a44bf8b248 cc: current@freebsd.org Subject: VOP_* changes causes NULL ptr dereference for acl_get_file(3) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:51:26 -0000 I need at least the following patch to keep my system alive. A simple call to acl_get_file(3) is enough to crash the machine. You will have to think a bit more about how you want to initialize stuff or about better defaults for cases like ACLs. Mark ==== //depot/projects/custom/kern/vfs_default.c#35 - /home/marks/proj/perforce/projects/custom/kern/vfs_default.c ==== @@ -95,6 +95,7 @@ .vop_revoke = VOP_PANIC, .vop_strategy = vop_nostrategy, .vop_unlock = vop_stdunlock, + .vop_getacl = VOP_EINVAL, }; /* -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 21:51:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C28716A4CE for ; Thu, 2 Dec 2004 21:51:38 +0000 (GMT) Received: from komquats.com (S0106002078125c0c.gv.shawcable.net [24.108.146.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id D133443D45 for ; Thu, 2 Dec 2004 21:51:36 +0000 (GMT) (envelope-from Cy.Schubert@komquats.com) Received: from cwsys.cwsent.com (cwsys [10.1.1.1]) by komquats.com (Postfix) with ESMTP id 0A8F44C5ED; Thu, 2 Dec 2004 13:51:35 -0800 (PST) Received: from cwsys (localhost [127.0.0.1]) by cwsys.cwsent.com (8.13.1/8.13.1) with ESMTP id iB2LpUwj032531; Thu, 2 Dec 2004 13:51:34 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Message-Id: <200412022151.iB2LpUwj032531@cwsys.cwsent.com> X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.komquats.com/ To: Tillman Hodgson In-Reply-To: Message from Tillman Hodgson <20041123220009.GJ88293@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Dec 2004 13:51:30 -0800 Sender: Cy.Schubert@komquats.com cc: freebsd-current@freebsd.org Subject: Re: krb5 port: -current behaves differently than 4.X w.r.t rsh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Cy Schubert List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:51:38 -0000 Under 5.3 & 6.0 bind in kcmd returns EPERM. In my case there is no firewall involved as the hosts are all on the same network. I believe that this is some sort of kernel issue when a wildcard IP:port is passed to bind(2). Cheers, Cy Schubert Web: http://www.komquats.com and http://www.bcbodybuilder.com FreeBSD UNIX: Web: http://www.FreeBSD.org BC Government: "Lift long enough and I believe arrogance is replaced by humility and fear by courage and selfishness by generosity and rudeness by compassion and caring." -- Dave Draper In message <20041123220009.GJ88293@seekingfire.com>, Tillman Hodgson writes: > Howdy folks, > > [I'm not sure that ports@ is the right place for this, but thought I'd > start here and see what happens.] > > I run a couple of Kerberos realms. I recently installed some new 5.3R > machines and then immediately upgraded them to -current. Cursory testing > (I know, I know) seemed to show that the MIT Kerberos port > (security/krb5) was working correctly. Over time, I've found a > difference between it and my older 4.X systems. > > While kinit, kdestroy, klist, kerberos telnet and ftp, and other basic > tools work correctly, the kerberos rsh client (not the server, it's > fine) doesn't seem to work. > > Here's a a 4-stable box connecting via rsh to anotehr 4-stable box as > well as to a -current box: > > [root@athena ~]# rsh -x coyote uname -a > This rsh session is encrypting input/output data transmissions. > FreeBSD coyote.seekingfire.com 4.10-STABLE FreeBSD 4.10-STABLE #0: Thu Nov 18 > 13:10:32 CST 2004 > toor@athena.seekingfire.prv:/usr/obj/usr/src/sys/COYOTE i386 > > [root@athena ~]# rsh -x backforty uname -a > This rsh session is encrypting input/output data transmissions. > FreeBSD backforty.seekingfire.prv 6.0-CURRENT FreeBSD 6.0-CURRENT #2: Fri Nov > 19 08:03:52 CST 2004 > tillman@backforty.seekingfire.prv:/usr/obj/usr/src/sys/BACKFORTY i386 > > When I try to connect from the -current box ('backforty' from the > example above) outwards to either type of box I get a failure: > > $ rsh -x coyote uptime > socket: protocol error or closed connection in circuit setup > > $ rsh -x caliban uptime > socket: protocol error or closed connection in circuit setup > > (caliban is another -current box). > > The auth.log on the server-side system shows: > > Nov 23 15:55:10 athena kshd[4565]: connect second port: Connection refused > > Note that all otehr client Kerberos apps work: I can telnet -x, ftp -x, > rlogin, etc to my hearts connect. Only rsh displays this behaviour. > > I've confirmed that I'm running the right rsh binary: > > $ which rsh > /usr/local/krb5/bin/rsh > > And I've confirmed that they're both running up-to-date ports trees and > the most current version fo security/krb5. > > I've googled for the auth.log message. It seems that the connection > "back" for stderr is being denied. By what, I don't know ... the host > backforty isn't runnign any sort of firewall: > > root@backforty# ipfw list > ipfw: getsockopt(IP_FW_GET): Protocol not available > root@backforty# ipfstat -hin > open: No such file or directory > root@backforty# pfctl -s rules > pfctl: /dev/pf: No such file or directory > > Any ideas? > > -T > > > -- > >I've gone through over-stressed to physical exhaustion... what's next? > Tuesday > - A.S.R. quote (Simon Burr & Kyle Hearn) > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 21:52:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D68E216A4CE for ; Thu, 2 Dec 2004 21:52:07 +0000 (GMT) Received: from komquats.com (S0106002078125c0c.gv.shawcable.net [24.108.146.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EF0A43D48 for ; Thu, 2 Dec 2004 21:52:05 +0000 (GMT) (envelope-from Cy.Schubert@komquats.com) Received: from cwsys.cwsent.com (cwsys [10.1.1.1]) by komquats.com (Postfix) with ESMTP id 111984C5F4 for ; Thu, 2 Dec 2004 13:52:04 -0800 (PST) Received: from cwsys (localhost [127.0.0.1]) by cwsys.cwsent.com (8.13.1/8.13.1) with ESMTP id iB2Lq3OL032895 for ; Thu, 2 Dec 2004 13:52:04 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Resent-Message-Id: <200412022152.iB2Lq3OL032895@cwsys.cwsent.com> Message-Id: <200412022152.iB2Lq3OL032895@cwsys.cwsent.com> X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.komquats.com/ To: Tillman Hodgson In-Reply-To: Message from Tillman Hodgson <20041123220009.GJ88293@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Dec 2004 13:51:30 -0800 Sender: Cy.Schubert@komquats.com Resent-To: freebsd-current@freebsd.org Resent-Date: Thu, 02 Dec 2004 13:52:03 -0800 Resent-From: Cy Schubert cc: freebsd-current@freebsd.org Subject: Re: krb5 port: -current behaves differently than 4.X w.r.t rsh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Cy Schubert List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:52:08 -0000 Under 5.3 & 6.0 bind in kcmd returns EPERM. In my case there is no firewall involved as the hosts are all on the same network. I believe that this is some sort of kernel issue when a wildcard IP:port is passed to bind(2). Cheers, Cy Schubert Web: http://www.komquats.com and http://www.bcbodybuilder.com FreeBSD UNIX: Web: http://www.FreeBSD.org BC Government: "Lift long enough and I believe arrogance is replaced by humility and fear by courage and selfishness by generosity and rudeness by compassion and caring." -- Dave Draper In message <20041123220009.GJ88293@seekingfire.com>, Tillman Hodgson writes: > Howdy folks, > > [I'm not sure that ports@ is the right place for this, but thought I'd > start here and see what happens.] > > I run a couple of Kerberos realms. I recently installed some new 5.3R > machines and then immediately upgraded them to -current. Cursory testing > (I know, I know) seemed to show that the MIT Kerberos port > (security/krb5) was working correctly. Over time, I've found a > difference between it and my older 4.X systems. > > While kinit, kdestroy, klist, kerberos telnet and ftp, and other basic > tools work correctly, the kerberos rsh client (not the server, it's > fine) doesn't seem to work. > > Here's a a 4-stable box connecting via rsh to anotehr 4-stable box as > well as to a -current box: > > [root@athena ~]# rsh -x coyote uname -a > This rsh session is encrypting input/output data transmissions. > FreeBSD coyote.seekingfire.com 4.10-STABLE FreeBSD 4.10-STABLE #0: Thu Nov 18 > 13:10:32 CST 2004 > toor@athena.seekingfire.prv:/usr/obj/usr/src/sys/COYOTE i386 > > [root@athena ~]# rsh -x backforty uname -a > This rsh session is encrypting input/output data transmissions. > FreeBSD backforty.seekingfire.prv 6.0-CURRENT FreeBSD 6.0-CURRENT #2: Fri Nov > 19 08:03:52 CST 2004 > tillman@backforty.seekingfire.prv:/usr/obj/usr/src/sys/BACKFORTY i386 > > When I try to connect from the -current box ('backforty' from the > example above) outwards to either type of box I get a failure: > > $ rsh -x coyote uptime > socket: protocol error or closed connection in circuit setup > > $ rsh -x caliban uptime > socket: protocol error or closed connection in circuit setup > > (caliban is another -current box). > > The auth.log on the server-side system shows: > > Nov 23 15:55:10 athena kshd[4565]: connect second port: Connection refused > > Note that all otehr client Kerberos apps work: I can telnet -x, ftp -x, > rlogin, etc to my hearts connect. Only rsh displays this behaviour. > > I've confirmed that I'm running the right rsh binary: > > $ which rsh > /usr/local/krb5/bin/rsh > > And I've confirmed that they're both running up-to-date ports trees and > the most current version fo security/krb5. > > I've googled for the auth.log message. It seems that the connection > "back" for stderr is being denied. By what, I don't know ... the host > backforty isn't runnign any sort of firewall: > > root@backforty# ipfw list > ipfw: getsockopt(IP_FW_GET): Protocol not available > root@backforty# ipfstat -hin > open: No such file or directory > root@backforty# pfctl -s rules > pfctl: /dev/pf: No such file or directory > > Any ideas? > > -T > > > -- > >I've gone through over-stressed to physical exhaustion... what's next? > Tuesday > - A.S.R. quote (Simon Burr & Kyle Hearn) > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 21:53:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50BA916A4CE for ; Thu, 2 Dec 2004 21:53:39 +0000 (GMT) Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10ECA43D55 for ; Thu, 2 Dec 2004 21:53:39 +0000 (GMT) (envelope-from roberthuff@rcn.com) Received: from 209-6-197-67.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com ([209.6.197.67] helo=jerusalem.litteratus.org.litteratus.org) by smtp03.mrf.mail.rcn.net with esmtp (Exim 3.35 #7) id 1CZytN-0002B2-00 for current@freebsd.org; Thu, 02 Dec 2004 16:53:38 -0500 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16815.36304.188670.238045@jerusalem.litteratus.org> Date: Thu, 2 Dec 2004 16:49:04 -0500 To: current@freebsd.org In-Reply-To: <41AF8017.4000206@freebsd.org> References: <20041202002939.GA2834@ns1.xcllnt.net> <16815.31852.46550.983276@jerusalem.litteratus.org> <41AF8017.4000206@freebsd.org> X-Mailer: VM 7.17 under 21.5 (beta16) "celeriac" XEmacs Lucid Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:53:39 -0000 Scott Long writes: > Are you talking about putting a minimal USB stack into the boot > loader? That _certainly_ cannot fit into boot0, and I doubt that > it can fit into boot1. It might be possible for > boot2/BTX/loader, but that's also quite a bit of work. As far as I know - and I would _love_ to be wrong - USB keyboards are not recognized before the kernel proper loads. This means I have to keep a PS2 keybaord attached to interrupt the countdown and make the jump to sub-ligh\\\\\, er. single user. I have no idea what stage of the boot process this is; all I know I have to use two keyboards where I should only need one. > I take it that your BIOS does not provide keyboard emulation for > you? If not, I guess that it makes it difficult to boot to DOS. The motherboard is an Asus P4S533 with an Award BIOS. I can't take the machine down to check on any keyboard emulation settings. (And the box has always been 100% Microsoft-free.) Robert Huff From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 22:24:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6498516A4CF for ; Thu, 2 Dec 2004 22:24:09 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AFDB43D49 for ; Thu, 2 Dec 2004 22:24:08 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 31306 invoked from network); 2 Dec 2004 22:15:06 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 2 Dec 2004 22:15:06 -0000 Message-ID: <41AF9603.9060902@freebsd.org> Date: Thu, 02 Dec 2004 23:24:03 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephan Uphoff References: <41AE3F80.1000506@freebsd.org> <41AF29AC.6030401@freebsd.org> <1102022838.11465.7735.camel@palm.tree.com> In-Reply-To: <1102022838.11465.7735.camel@palm.tree.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 22:24:09 -0000 Stephan Uphoff wrote: > On Thu, 2004-12-02 at 09:41, Andre Oppermann wrote: > >>Scott Long wrote: >> >>>5. Clustered FS support. SANs are all the rage these days, and >>>clustered filesystems that allow data to be distributed across many >>>storage enpoints and accessed concurrently through the SAN are very >>>powerful. RedHat recently bought Sistina and re-opened the GFS source >>>code, so exploring this would be very interesting. >> >>There are certain steps that can be be taken one at a time. For example >>it should be relatively easy to mount snapshots (ro) from more than one >>machine. Next step would be to mount a full 'rw' filesystem as 'ro' on >>other boxes. This would require cache and sector invalidation broadcasting >>from the 'rw' box to the 'ro' mounts. > > Mhhh .. if you plan to invalidate at the disk block cache layer then you > will run into race conditions with UFS/FFS (Especially with remove > operations) > I was once called in to evaluate such a multiple reader/single writer > system based on an UFS like file system and block layer invalidation and > had to convince management to kill it. (It appeared to work and actually > made it though internal and customer acceptance testing before failing > horrible in the field). > > If you send me more details on your proposed cache and sector > invalidation/cluster design I will be happy to review it. It obviously doesn't work only the disk block level. For the rw+ro(n) case you have to invalidate updated/changed inodes (file and directory inodes) as well as associated data blocks. Alternatively you could invalidate all related data blocks together with the inode but that would kill performance for files that are simply appended (like log files). -- Andre From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 22:37:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BC4E16A4CE for ; Thu, 2 Dec 2004 22:37:11 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAF4943D54 for ; Thu, 2 Dec 2004 22:37:10 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 31381 invoked from network); 2 Dec 2004 22:28:08 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 2 Dec 2004 22:28:08 -0000 Message-ID: <41AF9912.7040701@freebsd.org> Date: Thu, 02 Dec 2004 23:37:06 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <41AE3F80.1000506@freebsd.org> <41AF29AC.6030401@freebsd.org> <1102022838.11465.7735.camel@palm.tree.com> <41AF8C78.8050806@freebsd.org> In-Reply-To: <41AF8C78.8050806@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: "current@freebsd.org" cc: Stephan Uphoff Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 22:37:11 -0000 Scott Long wrote: > Stephan Uphoff wrote: > >> On Thu, 2004-12-02 at 09:41, Andre Oppermann wrote: >> >>> The holy grail of course is to mount >>> the same filesystem 'rw' on more than one box, preferrably more than >>> two. >>> This requires some more involved synchronization and locking on top >>> of the >>> cache invalidation. And make sure that the multi-'rw' cluster stays >>> alive >>> if one of the participants freezes and doesn't respond anymore. >>> >>> Scrolling through the UFS/FFS code I think the first one is 2-3 days of >>> work. The second 2-4 weeks and the third 2-3 month to get it right. >>> If someone would throw up the money... > > Although I don't know the specifics of your experience, I can easily > imagine how hard it would be to make this work on UFS. Common > operations like walking a file path to the root are nearly impossible to > do reliably without an overbearing amount of synchronization. Then you > have all of the problems synchronizing buffered data and metadata. You don't do it the fully synchronized way. The semantics will be somewhat like with NFS. Reading in the filesystem does not invoke synchronization. Only writing, or actually intending to write something, requires synchro- nization with all other machines in the filesystem cluster. Synchronization ensures that writes to a directory or file are properly serialized and that caches are invalidated at the same time. > Softupdates would be a nightmare, if not impossible. To the contrary. It provides a nice place to link code into and it helps to keep performance up to good levels. Any inode changes entering the softdep code would cause a message to all other machines informing them of the change. If another one wants to update the same inode or something dependend on it it has to wait until you have written it to disk. His backnotification would of course move this inode to the front of the softdep work queue to not stall your request. As long as you don't want to have mmap() work across machines with contents in memory but not yet written to disk things stay pretty much sane. -- Andre From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 23:37:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A2B316A4CE; Thu, 2 Dec 2004 23:37:26 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 385A743D39; Thu, 2 Dec 2004 23:37:26 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB2NZEKt072206; Thu, 2 Dec 2004 18:35:14 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iB2NZEd2072203; Thu, 2 Dec 2004 23:35:14 GMT (envelope-from robert@fledge.watson.org) Date: Thu, 2 Dec 2004 23:35:14 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Mark Santcroos In-Reply-To: <20041202215123.GA1512@laptop.6bone.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Poul-Henning Kamp cc: current@FreeBSD.org Subject: Re: VOP_* changes causes NULL ptr dereference for acl_get_file(3) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 23:37:26 -0000 On Thu, 2 Dec 2004, Mark Santcroos wrote: > I need at least the following patch to keep my system alive. A simple > call to acl_get_file(3) is enough to crash the machine. > > You will have to think a bit more about how you want to initialize stuff > or about better defaults for cases like ACLs. Should probably be using VOP_EOPNOTSUPP rather than VOP_EINVAL, I think. Also, it's likely that if you need a vop_getacl entry here, you probably also want a vop_setacl and a vop_checkacl entry. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > Mark > > ==== //depot/projects/custom/kern/vfs_default.c#35 - /home/marks/proj/perforce/projects/custom/kern/vfs_default.c ==== > @@ -95,6 +95,7 @@ > .vop_revoke = VOP_PANIC, > .vop_strategy = vop_nostrategy, > .vop_unlock = vop_stdunlock, > + .vop_getacl = VOP_EINVAL, > }; > > /* > > -- > RIPE NCC - Delft University of Technology - The FreeBSD Project > marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 00:21:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84E8D16A4CE; Fri, 3 Dec 2004 00:21:24 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 680CB43D2F; Fri, 3 Dec 2004 00:21:24 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 303E42A8D5; Thu, 2 Dec 2004 16:21:24 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id C5CE3E2B3; Thu, 2 Dec 2004 16:21:23 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iB30LNbg048800; Thu, 2 Dec 2004 16:21:23 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iB30LH2s048799; Thu, 2 Dec 2004 16:21:17 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-current@freebsd.org Date: Thu, 2 Dec 2004 16:21:17 -0800 User-Agent: KMail/1.7.1 References: <20041202002939.GA2834@ns1.xcllnt.net> <41AF8017.4000206@freebsd.org> <16815.36304.188670.238045@jerusalem.litteratus.org> In-Reply-To: <16815.36304.188670.238045@jerusalem.litteratus.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412021621.17783.peter@wemm.org> cc: Robert Huff cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 00:21:24 -0000 On Thursday 02 December 2004 01:49 pm, Robert Huff wrote: > Scott Long writes: > > Are you talking about putting a minimal USB stack into the boot > > loader? That _certainly_ cannot fit into boot0, and I doubt that > > it can fit into boot1. It might be possible for > > boot2/BTX/loader, but that's also quite a bit of work. > > As far as I know - and I would _love_ to be wrong - USB > keyboards are not recognized before the kernel proper loads. This > means I have to keep a PS2 keybaord attached to interrupt the > countdown and make the jump to sub-ligh\\\\\, er. single user. I > have no idea what stage of the boot process this is; all I know I > have to use two keyboards where I should only need one. > > > I take it that your BIOS does not provide keyboard emulation for > > you? If not, I guess that it makes it difficult to boot to DOS. > > The motherboard is an Asus P4S533 with an Award BIOS. I can't > take the machine down to check on any keyboard emulation settings. > (And the box has always been 100% Microsoft-free.) This is an ASUS bug, possibly a bug in the reference bioses. They have a whitelist of MBR partition types to decide what to do about USB keyboards. What is supposed to happen is that the bios keyboard and video calls work with the usb keyboard. Bioses also have a 'legacy' keyboard hardware emulation to simulate PS/2 keyboard hardware using the usb keyboard. This feature is meaninless to us in boot1 / loader / etc because we are a normal bios client like msdos. However, if the bios sees partition type 165 (FreeBSD), it freaks out and completely shuts down all USB support. Even for the bios keyboard service calls. If you boot MSDOS, for example.. the bios keyboard service calls are not disabled and keep working. Asus seems to be the worst offender in this area recently. This misfeature appeared on their newer Athlon64 boards and now you've reported it on their P4 boards.. Grrrrr. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 00:21:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84E8D16A4CE; Fri, 3 Dec 2004 00:21:24 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 680CB43D2F; Fri, 3 Dec 2004 00:21:24 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 303E42A8D5; Thu, 2 Dec 2004 16:21:24 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id C5CE3E2B3; Thu, 2 Dec 2004 16:21:23 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iB30LNbg048800; Thu, 2 Dec 2004 16:21:23 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iB30LH2s048799; Thu, 2 Dec 2004 16:21:17 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-current@freebsd.org Date: Thu, 2 Dec 2004 16:21:17 -0800 User-Agent: KMail/1.7.1 References: <20041202002939.GA2834@ns1.xcllnt.net> <41AF8017.4000206@freebsd.org> <16815.36304.188670.238045@jerusalem.litteratus.org> In-Reply-To: <16815.36304.188670.238045@jerusalem.litteratus.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412021621.17783.peter@wemm.org> cc: Robert Huff cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 00:21:24 -0000 On Thursday 02 December 2004 01:49 pm, Robert Huff wrote: > Scott Long writes: > > Are you talking about putting a minimal USB stack into the boot > > loader? That _certainly_ cannot fit into boot0, and I doubt that > > it can fit into boot1. It might be possible for > > boot2/BTX/loader, but that's also quite a bit of work. > > As far as I know - and I would _love_ to be wrong - USB > keyboards are not recognized before the kernel proper loads. This > means I have to keep a PS2 keybaord attached to interrupt the > countdown and make the jump to sub-ligh\\\\\, er. single user. I > have no idea what stage of the boot process this is; all I know I > have to use two keyboards where I should only need one. > > > I take it that your BIOS does not provide keyboard emulation for > > you? If not, I guess that it makes it difficult to boot to DOS. > > The motherboard is an Asus P4S533 with an Award BIOS. I can't > take the machine down to check on any keyboard emulation settings. > (And the box has always been 100% Microsoft-free.) This is an ASUS bug, possibly a bug in the reference bioses. They have a whitelist of MBR partition types to decide what to do about USB keyboards. What is supposed to happen is that the bios keyboard and video calls work with the usb keyboard. Bioses also have a 'legacy' keyboard hardware emulation to simulate PS/2 keyboard hardware using the usb keyboard. This feature is meaninless to us in boot1 / loader / etc because we are a normal bios client like msdos. However, if the bios sees partition type 165 (FreeBSD), it freaks out and completely shuts down all USB support. Even for the bios keyboard service calls. If you boot MSDOS, for example.. the bios keyboard service calls are not disabled and keep working. Asus seems to be the worst offender in this area recently. This misfeature appeared on their newer Athlon64 boards and now you've reported it on their P4 boards.. Grrrrr. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 00:24:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1402A16A4CE; Fri, 3 Dec 2004 00:24:23 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDC5043D5C; Fri, 3 Dec 2004 00:24:22 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id AABFB2A7EA; Thu, 2 Dec 2004 16:24:22 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 3C453E2B3; Thu, 2 Dec 2004 16:24:22 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iB30OLRS048868; Thu, 2 Dec 2004 16:24:21 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iB30OL4F048867; Thu, 2 Dec 2004 16:24:21 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-hackers@freebsd.org, foxfair@freebsd.org Date: Thu, 2 Dec 2004 16:24:21 -0800 User-Agent: KMail/1.7.1 References: <41AE3F80.1000506@freebsd.org> <20041202011758.GA81639@drago.fomokka.net> In-Reply-To: <20041202011758.GA81639@drago.fomokka.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412021624.21655.peter@wemm.org> cc: hackers@freebsd.org cc: Scott Long cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 00:24:23 -0000 On Wednesday 01 December 2004 05:17 pm, Foxfair Hu wrote: > On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote: > > All, > > [....] > > > 1. Keyboard multiplexer. We are running into problems with making > > ps/2 and USB/bluetooth keyboards work together and work with KVMs. > > Having a virtual keyboard device that multiplexes the various real > > keyboard devices and handles hotplug can solve this mess pretty > > effectively. I know that there has been a lot of talk about this > > on mailing lists recently but I don't know how much progress is > > being made so I'm listing it here. > > How about reuse NetBSD's wscons ? I've kept an eye on it and > thought it should be a good start for FreeBSD. Only if it has 100% identical look/feel to syscons. ie: same key maps, same ioctl's, same Xserver interface, same escape codes, etc. If not, then over my dead body! -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 00:29:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9172316A4CE; Fri, 3 Dec 2004 00:29:10 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3921043D2F; Fri, 3 Dec 2004 00:29:10 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB30WvkI069240; Thu, 2 Dec 2004 17:32:57 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AFB35D.4090300@freebsd.org> Date: Thu, 02 Dec 2004 17:29:17 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Wemm References: <41AE3F80.1000506@freebsd.org> <20041202011758.GA81639@drago.fomokka.net> <200412021624.21655.peter@wemm.org> In-Reply-To: <200412021624.21655.peter@wemm.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: hackers@freebsd.org cc: freebsd-hackers@freebsd.org cc: foxfair@freebsd.org cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 00:29:10 -0000 Peter Wemm wrote: > On Wednesday 01 December 2004 05:17 pm, Foxfair Hu wrote: > >>On Wed, Dec 01, 2004 at 03:02:40PM -0700, Scott Long wrote: >> >>>All, >> >>[....] >> >> >>>1. Keyboard multiplexer. We are running into problems with making >>>ps/2 and USB/bluetooth keyboards work together and work with KVMs. >>>Having a virtual keyboard device that multiplexes the various real >>>keyboard devices and handles hotplug can solve this mess pretty >>>effectively. I know that there has been a lot of talk about this >>>on mailing lists recently but I don't know how much progress is >>>being made so I'm listing it here. >> >> How about reuse NetBSD's wscons ? I've kept an eye on it and >>thought it should be a good start for FreeBSD. > > > Only if it has 100% identical look/feel to syscons. ie: same key maps, > same ioctl's, same Xserver interface, same escape codes, etc. If not, > then over my dead body! > What if it's 100% identical except for the [Space] key, which becomes the console pause key? =-) Scott From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 02:03:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24C8116A4CE for ; Fri, 3 Dec 2004 02:03:57 +0000 (GMT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F18F43D46 for ; Fri, 3 Dec 2004 02:03:56 +0000 (GMT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.13.1/8.13.1) with ESMTP id iB323tne059182; Thu, 2 Dec 2004 21:03:55 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.13.1/8.13.1/Submit) id iB323t2p059181; Thu, 2 Dec 2004 21:03:55 -0500 (EST) (envelope-from barney) Date: Thu, 2 Dec 2004 21:03:55 -0500 From: Barney Wolff To: Peter Wemm Message-ID: <20041203020355.GA59029@pit.databus.com> References: <20041202002939.GA2834@ns1.xcllnt.net> <41AF8017.4000206@freebsd.org> <16815.36304.188670.238045@jerusalem.litteratus.org> <200412021621.17783.peter@wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412021621.17783.peter@wemm.org> User-Agent: Mutt/1.5.6i X-Scanned-By: MIMEDefang 2.48 on 127.0.0.1 cc: freebsd-current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 02:03:57 -0000 On Thu, Dec 02, 2004 at 04:21:17PM -0800, Peter Wemm wrote: > > However, if the bios sees partition type 165 (FreeBSD), it freaks out > and completely shuts down all USB support. Even for the bios keyboard > service calls. > > If you boot MSDOS, for example.. the bios keyboard service calls are not > disabled and keep working. Pardon a naive question, but what would happen with a FreeBSD partition whose type said something other than 165? What in fbsd checks the partition type once booting starts? -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 02:26:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AC7A16A4CE for ; Fri, 3 Dec 2004 02:26:01 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34B8543D46 for ; Fri, 3 Dec 2004 02:26:01 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB32Tja4069695; Thu, 2 Dec 2004 19:29:45 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AFCEC1.1090403@freebsd.org> Date: Thu, 02 Dec 2004 19:26:09 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Barney Wolff References: <20041202002939.GA2834@ns1.xcllnt.net> <41AF8017.4000206@freebsd.org> <16815.36304.188670.238045@jerusalem.litteratus.org> <200412021621.17783.peter@wemm.org> <20041203020355.GA59029@pit.databus.com> In-Reply-To: <20041203020355.GA59029@pit.databus.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 02:26:01 -0000 Barney Wolff wrote: > On Thu, Dec 02, 2004 at 04:21:17PM -0800, Peter Wemm wrote: > >>However, if the bios sees partition type 165 (FreeBSD), it freaks out >>and completely shuts down all USB support. Even for the bios keyboard >>service calls. >> >>If you boot MSDOS, for example.. the bios keyboard service calls are not >>disabled and keep working. > > > Pardon a naive question, but what would happen with a FreeBSD partition > whose type said something other than 165? What in fbsd checks the > partition type once booting starts? > It's very a fundamental value for being able to find and mount the partitions at boot. Scott From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 02:31:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98A9F16A4CE for ; Fri, 3 Dec 2004 02:31:41 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C52043D45 for ; Fri, 3 Dec 2004 02:31:41 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iB32VW1d002232; Thu, 2 Dec 2004 21:31:32 -0500 Mime-Version: 1.0 Message-Id: Date: Thu, 2 Dec 2004 21:31:31 -0500 To: freebsd-current@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= Subject: Another twist on WRITE_DMA issues... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 02:31:41 -0000 In a different thread, I (garance) wrote: > >At 10:30 PM +0100 11/18/04, S=F8ren Schmidt wrote: >>Garance A Drosihn wrote: >> >>>I am trying to pin down problems "FAILURE - WRITE_DMA timed out" >>>in a new PC that I have. I had some local shop build this for me, >>>and apparently there were "a few" miscommunications in what I >>>thought I asked for, and what they actually built. >>> >>>The machine ended up with two SATA controllers: >>> atapci0: -- on the motherboard >>> atapci1: -- on a PCI card >> >>I think its the other way around, the VIA chip is part of the >>motherboard chipset, the SiI is a "loose" PCI compatible chip. > >Ugh. You are correct. Somewhere along the line I got the two >mixed up. So now have I removed the PCI-based SATA card, and >connected the Western Digital hard disk to the on-board SATA. >I have just done a complete buildworld/installworld cycle for >5.3-STABLE. I did not see a single WRITE_DMA time-out message. So far so good. >But looking around the web for awhile, it looks like this model of >Western Digital is not a native SATA drive. So I think I will >replace it just to avoid any further hassles, even though I did not >get any errors with this drive once I was using the right controller. I have now switched from that Western Digital drive to a Seagate Barracuda 7200.7 120-gig (ST3120026AS). The drive seems to be working fairly well, but now I sometimes see some combination like the following three lines: Dec 2 20:29:50 kernel: Interrupt storm detected on "irq20: atapci0"; throttling interrupt source Dec 2 20:29:54 kernel: ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D20627679 Dec 2 20:29:54 kernel: ad4: FAILURE - WRITE_DMA timed out Where atapci0: And ad4: 114473MB [232581/16/63] at ata2-master SATA150 This does not come up often, and it usually doesn't cause any noticeable problem. As it luck would have it, the one time it has caused problems is during installworlds. I just did 18 buildworlds in a row without any problem. I built and installed the new kernel, rebooted into single-user, and the system paniced early in the installworld. I rebooted into single-user again, and this time it was *almost* finished with installworld when the system simply hung after a "ad4: FAILURE - WRITE_DMA timed out" message. Now I'm back up in multi-user mode, and I just completed another buildworld without any problem. I did get the above set of messages, but nothing after that. (I did see several sets of WRITE_DMA error messages during the installworlds). This is on a recent snapshot of 5.3-stable. Should I just switch back to the western digital? Or is it that the new disk is fast enough that the kernel *thinks* something is wrong with it, and starts throttling it? Or maybe I have a bad SATA cable? If it wasn't for the panics/hangs during installworld, I would think that everything was working quite well. Of course, that is about the worst time to be getting system panics! I tried getting a core dump of the panic, but 'call doadump' complained that no dump device had been set. I'm now looking at /etc/rc.d/dumpon so I should know how to set that up the next time I'm in single-user mode. -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 02:49:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCA2316A4CE; Fri, 3 Dec 2004 02:49:18 +0000 (GMT) Received: from smtp.vzavenue.net (smtp.vzavenue.net [66.171.59.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F8A043D1F; Fri, 3 Dec 2004 02:49:18 +0000 (GMT) (envelope-from jr@opal.com) Received: from linwhf.opal.com (126.79.171.66.subscriber.vzavenue.net [66.171.79.126]) by smtp.vzavenue.net (MOS 3.4.3-CR) with ESMTP id BMG11088; Thu, 2 Dec 2004 21:49:05 -0500 (EST) Received: from linwhf.opal.com (localhost [127.0.0.1]) by linwhf.opal.com (8.13.1/8.13.1) with ESMTP id iB32n4A0007179 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Thu, 2 Dec 2004 21:49:04 -0500 (EST) (envelope-from jr@linwhf.opal.com) Received: (from jr@localhost) by linwhf.opal.com (8.13.1/8.13.1/Submit) id iB32n4kp007178; Thu, 2 Dec 2004 21:49:04 -0500 (EST) (envelope-from jr) Date: Thu, 2 Dec 2004 21:49:04 -0500 From: "J.R. Oldroyd" To: Scott Long Message-ID: <20041203024904.GO55358@linwhf.opal.com> References: <41AE3F80.1000506@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41AE3F80.1000506@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Junkmail-Status: score=0/50, host=smtp.vzavenue.net cc: hackers@freebsd.org cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 02:49:18 -0000 How about some form of streamlined video input support? I realize Linux's v4l model doesn't fit too well here, but what they have done there provides support for all sorts of common video devices, and makes them all available to pretty much any program that wants video input. FreeBSD is far behind in this area. -jr On Dec 01, 15:02, Scott Long wrote: > All, > > I know that I said last month that we were going to stop promising > specific features for the next major release. However, I'd like to > throw out a list of things that would be really nice to have in the > future, whether its 6.0 or 7.0 or whatever. Most of these tasks are > not trivial, but I hope that talking about them will encourage some > interest. These are in no particular priority order. I'd also be > thrilled if someone wanted to dress this list up in docbook and add > it to the webpage. While this is just my personal list, I'd welcome > other additions to it (in the sense of significant projects, not just > individual PRs or bug fixes that one might be interested in). > From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 05:38:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F32DE16A4CE; Fri, 3 Dec 2004 05:38:14 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 819B843D49; Fri, 3 Dec 2004 05:38:14 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iB35cDdm011973; Fri, 3 Dec 2004 00:38:13 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iB35cD26001220; Fri, 3 Dec 2004 00:38:13 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 56F217306E; Fri, 3 Dec 2004 00:38:13 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041203053813.56F217306E@freebsd-current.sentex.ca> Date: Fri, 3 Dec 2004 00:38:13 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/588/Sun Nov 14 19:06:21 2004 clamav-milter version 0.80j on clamscanner3 X-Virus-Scanned: ClamAV 0.80/614/Wed Dec 1 10:44:43 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 05:38:15 -0000 TB --- 2004-12-03 04:15:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-12-03 04:15:00 - starting CURRENT tinderbox run for alpha/alpha TB --- 2004-12-03 04:15:00 - checking out the source tree TB --- 2004-12-03 04:15:00 - cd /home/tinderbox/CURRENT/alpha/alpha TB --- 2004-12-03 04:15:00 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-12-03 04:21:40 - building world (CFLAGS=-O2 -pipe) TB --- 2004-12-03 04:21:40 - cd /home/tinderbox/CURRENT/alpha/alpha/src TB --- 2004-12-03 04:21:40 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-12-03 05:36:22 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-03 05:36:22 - cd /home/tinderbox/CURRENT/alpha/alpha/src TB --- 2004-12-03 05:36:22 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Dec 3 05:36:23 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] /tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica/actypes.h:168:2: #error ACPI_MACHINE_WIDTH not defined /tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica/actypes.h:277:2: #error unknown ACPI_MACHINE_WIDTH In file included from /tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica/acpi.h:129, from /tinderbox/CURRENT/alpha/alpha/src/sys/dev/pci/pci.c:63: /tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica/acmacros.h:377:2: #error unknown ACPI_MACHINE_WIDTH In file included from /tinderbox/CURRENT/alpha/alpha/src/sys/dev/pci/pci.c:64: /tinderbox/CURRENT/alpha/alpha/src/sys/dev/acpica/acpivar.h:31:21: acpi_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/obj/alpha/tinderbox/CURRENT/alpha/alpha/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/obj/alpha/tinderbox/CURRENT/alpha/alpha/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. *** Error code 1 Stop in /tinderbox/CURRENT/alpha/alpha/src. TB --- 2004-12-03 05:38:12 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-12-03 05:38:12 - ERROR: failed to build generic kernel TB --- 2004-12-03 05:38:12 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 05:55:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7E0716A4CE for ; Fri, 3 Dec 2004 05:55:56 +0000 (GMT) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9624A43D48 for ; Fri, 3 Dec 2004 05:55:56 +0000 (GMT) (envelope-from ken@nargothrond.kdm.org) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.12.11/8.12.11) with ESMTP id iB35tsSD061851; Thu, 2 Dec 2004 22:55:54 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.12.11/8.12.5/Submit) id iB35ts90061850; Thu, 2 Dec 2004 22:55:54 -0700 (MST) (envelope-from ken) Date: Thu, 2 Dec 2004 22:55:54 -0700 From: "Kenneth D. Merry" To: Andrew Gallatin Message-ID: <20041203055554.GA61823@nargothrond.kdm.org> References: <20041130035552.GA32924@nargothrond.kdm.org> <16812.29117.221988.730885@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16812.29117.221988.730885@grasshopper.cs.duke.edu> User-Agent: Mutt/1.4.2i X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on nargothrond.kdm.org X-Virus-Status: Clean cc: current@FreeBSD.org Subject: Re: -current hang during boot on SMP machine X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 05:55:57 -0000 On Tue, Nov 30, 2004 at 08:12:29 -0500, Andrew Gallatin wrote: > > Have you tried disabling ACPI via hint.acpi.0.disabled="1" in > /boot/loader.conf > > The ACPI on these older machines is pretty bad. I have a very similar > SuperMicro machine w/o SCSI at work which runs 5.3-R fine w/ACPI > disabled. I discovered early in the 5.0 cycle that enabling ACPI > would lead to a console message for each fxp0 interrupt.. FWIW, with -current from today (December 2nd), I can boot with ACPI enabled and things seem to work. Ken -- Kenneth Merry ken@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 06:13:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16FBA16A4CE; Fri, 3 Dec 2004 06:13:59 +0000 (GMT) Received: from pimout1-ext.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5752B43D1D; Fri, 3 Dec 2004 06:13:58 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-68-123-122-146.dsl.snfc21.pacbell.net [68.123.122.146])iB36Dt6M128768; Fri, 3 Dec 2004 01:13:57 -0500 Message-ID: <41B00422.4060404@elischer.org> Date: Thu, 02 Dec 2004 22:13:54 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: Scott Long References: <20041202002939.GA2834@ns1.xcllnt.net> <16815.31852.46550.983276@jerusalem.litteratus.org> <41AF8017.4000206@freebsd.org> In-Reply-To: <41AF8017.4000206@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Robert Huff cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 06:13:59 -0000 Scott Long wrote: > Robert Huff wrote: > >> Marcel Moolenaar writes: >> >> >>> > 1. Keyboard multiplexer. >>> >>> I actually fail to stop thinking about a complete syscons and >>> pcvt replacement. You know, the one and only console >>> implementation that makes all others obsolete. Big plans, little >>> time, yada yada yada... >> >> >> >> As long as we're talking about keyboards ... may I add "Get the >> boot code to recognize USB keyboards." >> (Unless this has already happened and I missed the meno. >> Again.) >> >> >> Robert Huff >> > > Are you talking about putting a minimal USB stack into the boot loader? > That _certainly_ cannot fit into boot0, and I doubt that it can fit into > boot1. It might be possible for boot2/BTX/loader, but that's also quite > a bit of work. I take it that your BIOS does not provide keyboard > emulation for you? If not, I guess that it makes it difficult to boot > to DOS. that's what "Legacy USB support" is in the BIOS. > > Scott > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 07:07:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BD6F16A4CE; Fri, 3 Dec 2004 07:07:18 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id B075D43D5D; Fri, 3 Dec 2004 07:07:17 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB377FAw013074; Fri, 3 Dec 2004 08:07:15 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 02 Dec 2004 23:35:14 GMT." Date: Fri, 03 Dec 2004 08:07:15 +0100 Message-ID: <13073.1102057635@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@FreeBSD.org Subject: Re: VOP_* changes causes NULL ptr dereference for acl_get_file(3) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 07:07:18 -0000 Can you try this patch instead: Index: kern/vfs_default.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_default.c,v retrieving revision 1.109 diff -u -r1.109 vfs_default.c --- kern/vfs_default.c 1 Dec 2004 23:16:36 -0000 1.109 +++ kern/vfs_default.c 3 Dec 2004 07:06:35 -0000 @@ -72,6 +72,8 @@ struct vop_vector default_vnodeops = { .vop_default = NULL, + .vop_bypass = VOP_EOPNOTSUPP, + .vop_advlock = VOP_EINVAL, .vop_bmap = vop_stdbmap, .vop_close = VOP_NULL, @@ -79,7 +81,7 @@ .vop_destroyvobject = vop_stddestroyvobject, .vop_fsync = VOP_NULL, .vop_getpages = vop_stdgetpages, - .vop_getvobject = vop_stdgetvobject, + .vop_getvobject = vop_stdgetvobject, .vop_getwritemount = vop_stdgetwritemount, .vop_inactive = vop_stdinactive, .vop_ioctl = VOP_ENOTTY, In message , Robe rt Watson writes: >On Thu, 2 Dec 2004, Mark Santcroos wrote: > >> I need at least the following patch to keep my system alive. A simple >> call to acl_get_file(3) is enough to crash the machine. >> >> You will have to think a bit more about how you want to initialize stuff >> or about better defaults for cases like ACLs. > >Should probably be using VOP_EOPNOTSUPP rather than VOP_EINVAL, I think. >Also, it's likely that if you need a vop_getacl entry here, you probably >also want a vop_setacl and a vop_checkacl entry. > >Robert N M Watson FreeBSD Core Team, TrustedBSD Projects >robert@fledge.watson.org Principal Research Scientist, McAfee Research > > >> >> Mark >> >> ==== //depot/projects/custom/kern/vfs_default.c#35 - /home/marks/proj/perforce/projects/custom/kern/vfs_default.c ==== >> @@ -95,6 +95,7 @@ >> .vop_revoke = VOP_PANIC, >> .vop_strategy = vop_nostrategy, >> .vop_unlock = vop_stdunlock, >> + .vop_getacl = VOP_EINVAL, >> }; >> >> /* >> >> -- >> RIPE NCC - Delft University of Technology - The FreeBSD Project > marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 07:08:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4773D16A4CE for ; Fri, 3 Dec 2004 07:08:25 +0000 (GMT) Received: from smtpq2.home.nl (smtpq2.home.nl [213.51.128.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDBDF43D55 for ; Fri, 3 Dec 2004 07:08:24 +0000 (GMT) (envelope-from dodell@sitetronics.com) Received: from [213.51.128.134] (port=58984 helo=smtp3.home.nl) by smtpq2.home.nl with esmtp (Exim 4.30) id 1Ca7YE-0001Lb-ON; Fri, 03 Dec 2004 08:08:22 +0100 Received: from cc740438-a.deven1.ov.home.nl ([82.75.136.183]:3086 helo=[192.168.1.100]) by smtp3.home.nl with esmtp (Exim 4.30) id 1Ca7YC-0008Lk-4H; Fri, 03 Dec 2004 08:08:20 +0100 Message-ID: <41B010E5.4080201@sitetronics.com> Date: Fri, 03 Dec 2004 08:08:21 +0100 From: "Devon H. O'Dell" User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Kjeldergaard References: <41AE3F80.1000506@freebsd.org> <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> <20041202190337.GY79646@cirb503493.alcatel.com.au> <8cb27cbf04120211553b4304bf@mail.gmail.com> <41AF75B1.6070306@sitetronics.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AtHome-MailScanner-Information: Please contact support@home.nl for more information X-AtHome-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 07:08:25 -0000 Eric Kjeldergaard wrote: >>FWIW, I saw on another response to this thread that the installer should >>be based on a Live CD. Ours is, and is used in the FreeSBIE project to >>install FreeBSD to the disk, if desired. > > > Ooh, ooh, do tell. I had no idea that one existed. Does it > allow for simple base installs? In fact, does it have about the same > featureset as sysinstall? Do I get a link? Please self-promote :) > I'm sure I'm not alone in the desire for a GUI installer as an option > (not a replacement, again...need to reiterate that I love the ability > to install fBSD in 8 minutes on a 200mhz machine via a familiar > ncurses interface) for desktop users. > > > > -- > If I write a signature, my emails will appear more personalised. I believe it's to be shipped with the FreeSBIE 1.1 release. It used to be on www.livebsd.com, but I think Scott (Ullrich) removed it (or I may be wrong). You can obviously check out its functionality for DragonFly BSD (the interface when installing FreeSBIE is the same). The FreeSBIE project is at http://www.freesbie.org Have fun! :) Devon H. O'Dell From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 08:31:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EE0B16A4CE; Fri, 3 Dec 2004 08:31:27 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id B202243D2F; Fri, 3 Dec 2004 08:31:26 +0000 (GMT) (envelope-from marks@ripe.net) Received: by postman.ripe.net (Postfix, from userid 8) id 2578C24BC4; Fri, 3 Dec 2004 09:31:26 +0100 (CET) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 3A0C724B9F; Fri, 3 Dec 2004 09:31:25 +0100 (CET) Received: from ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id iB38VPLE023985; Fri, 3 Dec 2004 09:31:25 +0100 Received: (nullmailer pid 755 invoked by uid 1001); Fri, 03 Dec 2004 07:55:07 -0000 Date: Fri, 3 Dec 2004 08:55:07 +0100 From: Mark Santcroos To: Poul-Henning Kamp Message-ID: <20041203075507.GA709@laptop.6bone.nl> References: <13073.1102057635@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13073.1102057635@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.000166 / -5.9 X-RIPE-Signature: 351b4b6a5b800e3691dd0d271fb415e2 cc: Robert Watson cc: current@FreeBSD.org Subject: Re: VOP_* changes causes NULL ptr dereference for acl_get_file(3) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 08:31:27 -0000 On Fri, Dec 03, 2004 at 08:07:15AM +0100, Poul-Henning Kamp wrote: > Can you try this patch instead: Yep, that looks like the generic fix. Mark -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 08:35:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05CD116A4CF for ; Fri, 3 Dec 2004 08:35:07 +0000 (GMT) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 4F98D43D5A for ; Fri, 3 Dec 2004 08:35:06 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 7353 invoked from network); 3 Dec 2004 08:35:05 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 3 Dec 2004 08:35:05 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB38Z4Un093004; Fri, 3 Dec 2004 09:35:04 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB38YxkI093000; Fri, 3 Dec 2004 09:34:59 +0100 (CET) (envelope-from pho) Date: Fri, 3 Dec 2004 09:34:58 +0100 From: Peter Holm To: Poul-Henning Kamp Message-ID: <20041203083458.GA92652@peter.osted.lan> References: <20041202155637.GA85127@peter.osted.lan> <98967.1102003088@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <98967.1102003088@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org cc: Jeff Roberson Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 08:35:07 -0000 On Thu, Dec 02, 2004 at 04:58:08PM +0100, Poul-Henning Kamp wrote: > In message <20041202155637.GA85127@peter.osted.lan>, Peter Holm writes: > > >Just got a double panic again: http://www.holm.cc/stress/log/jeff06.html. > >I think I'll revert to HEAD, just to touch base. > > HEAD is not very happy on my testbox right now, recent ACPI commits seems > to have received less than meticulous scrutiny. > Hmm ... I've reverted Jeff's patch (so I'm now back to HEAD from Dec 1 10:04 UTC). I have not seen any buf related panics, during the last 16 of testing, only a few "sleeping thread owns a non-sleepable lock". Jeff, have you been able to recreate any of the panics I found? > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 08:42:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7729816A4CE; Fri, 3 Dec 2004 08:42:52 +0000 (GMT) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABC7F43D39; Fri, 3 Dec 2004 08:42:51 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.1/8.13.1) with ESMTP id iB38bbCw070942; Fri, 3 Dec 2004 00:37:38 -0800 (PST) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.1/8.13.1/Submit) id iB38bTvF070941; Fri, 3 Dec 2004 00:37:29 -0800 (PST) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: David Xu In-Reply-To: <41AFC2EE.9080404@freebsd.org> References: <41AE3F80.1000506@freebsd.org> <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> <1101973835.66100.15.camel@leguin> <41AFC2EE.9080404@freebsd.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1102063049.66100.71.camel@leguin> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 03 Dec 2004 00:37:29 -0800 cc: "Kamal R. Prasad" cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 08:42:52 -0000 On Thu, 2004-12-02 at 17:35, David Xu wrote: > I maybe jump onto wrong thread, but FreeBSD's lack of > graphics framebuffer which is in Linux really kicked away > lots of embedded projects, one is QT-embedded which > simple can not be run on FreeBSD, many embedded projects > here just need it. We do definitely need framebuffer. But I think we'd be best served by trying to drag mode-setting code out of the X Server and into a userland library, rather than integrating it all into the kernel. (At most, implement a simple fixed mode supported everywhere in the kernel for intial boot, then a userland system of some sort takes over after that). Mode-setting code is huge, easy to mess up, and I don't think we have the resources to do it well. However, if someone (I fear doing this myself) were to get it into a userland library, we could probably convince the X Server to use it, and maybe even Linux kernel folks, and end up keeping all grahpics driver developers focused on a single codebase rather than split across many OSes or kernel versus X Server. Here's why I personally think this is really important: We've got Mesa-solo laying around -- OpenGL hardware acceleration on top of a framebuffer, if FreeBSD just had a framebuffer system. Then we've got the Xglx server, which runs on top of an OpenGL implementation and provides at least some of the Render acceleration that I was talking about in the parent message. Also, a number of X Server folks want to get mode-setting moved out of the X Server entirely -- let it be configured by system daemons, probably controlled over dbus. It would be very nice if FreeBSD happened to be ready for what Linux people would like to do. -- Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org Thank goodness for the 22nd Amendment From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 09:04:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D0AF16A4CE for ; Fri, 3 Dec 2004 09:04:02 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CE4F43D60 for ; Fri, 3 Dec 2004 09:04:02 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iB393x0N058877; Fri, 3 Dec 2004 04:03:59 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iB393xEg058874; Fri, 3 Dec 2004 04:03:59 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Fri, 3 Dec 2004 04:03:58 -0500 (EST) From: Jeff Roberson To: Peter Holm In-Reply-To: <20041203083458.GA92652@peter.osted.lan> Message-ID: <20041203040206.R18185@mail.chesapeake.net> References: <20041202155637.GA85127@peter.osted.lan> <98967.1102003088@critter.freebsd.dk> <20041203083458.GA92652@peter.osted.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 09:04:02 -0000 On Fri, 3 Dec 2004, Peter Holm wrote: > On Thu, Dec 02, 2004 at 04:58:08PM +0100, Poul-Henning Kamp wrote: > > In message <20041202155637.GA85127@peter.osted.lan>, Peter Holm writes: > > > > >Just got a double panic again: http://www.holm.cc/stress/log/jeff06.html. > > >I think I'll revert to HEAD, just to touch base. > > > > HEAD is not very happy on my testbox right now, recent ACPI commits seems > > to have received less than meticulous scrutiny. > > > > Hmm ... > > I've reverted Jeff's patch (so I'm now back to HEAD from Dec 1 10:04 UTC). > I have not seen any buf related panics, during the last 16 of testing, only > a few "sleeping thread owns a non-sleepable lock". Jeff, have you been able > to recreate any of the panics I found? Some of the earlier ones, but not the b_bufobj panic yet. I have been busy on other things for a bit though. I hope to reproduce that soon so I can fix it. I will have a new patch in an hour or two that removes Giant from the remaining syscalls. I'm going to do some shakeout here before I post it. > > > -- > > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > > phk@FreeBSD.ORG | TCP/IP since RFC 956 > > FreeBSD committer | BSD since 4.3-tahoe > > Never attribute to malice what can adequately be explained by incompetence. > > -- > Peter Holm > From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 09:50:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECD4116A4CE; Fri, 3 Dec 2004 09:50:53 +0000 (GMT) Received: from smtp1.jazztel.es (smtp1.jazztel.es [62.14.3.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E4C943D54; Fri, 3 Dec 2004 09:50:53 +0000 (GMT) (envelope-from josemi@freebsd.jazztel.es) Received: from antivirus by smtp1.jazztel.es with antivirus id 1CaA5m-0000YT-00 Fri, 03 Dec 2004 10:51:10 +0100 Received: from [212.106.254.37] (helo=rguez.homeunix.net) by smtp1.jazztel.es with esmtp id 1CaA5l-0000Xc-00 Fri, 03 Dec 2004 10:51:09 +0100 Received: from redesjm.local (orion.redesjm.local [192.168.254.16]) by rguez.homeunix.net (8.13.1/8.13.1) with ESMTP id iB39oolD000818; Fri, 3 Dec 2004 10:50:50 +0100 (CET) (envelope-from freebsd@redesjm.local) Received: from localhost (localhost [[UNIX: localhost]]) by redesjm.local (8.13.1/8.13.1/Submit) id iB39oqiW001149; Fri, 3 Dec 2004 10:50:52 +0100 (CET) (envelope-from freebsd@redesjm.local) From: Jose M Rodriguez To: freebsd-hackers@freebsd.org Date: Fri, 3 Dec 2004 10:50:50 +0100 User-Agent: KMail/1.7.1 References: <41AE3F80.1000506@freebsd.org> <20041201232052.GA35040@xor.obsecurity.org> <41AE5169.3000909@freebsd.org> In-Reply-To: <41AE5169.3000909@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200412031050.52137.freebsd@redesjm.local> X-AntiVirus: checked by AntiVir Milter (version: 1.1; AVE: 6.28.0.19; VDF: 6.28.0.103; host: antares.redesjm.local) X-Virus-Scanned: by antivirus cc: Ryan Sommers cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" cc: Kris Kennaway Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 09:50:54 -0000 El Jueves, 2 de Diciembre de 2004 00:19, Scott Long escribi=F3: > Kris Kennaway wrote: > > On Wed, Dec 01, 2004 at 04:10:57PM -0700, Ryan Sommers wrote: > >>Another issue I had with the dfly installer was one point I believe > >> needs to be central to any next-gen installer. > >> Internationalisation. > > > > Careful not to pile on so many wishes that achieving anything > > becomes impossible. Our current installer doesn't do this, so it's > > not a hard requirement that a better installer should. > > > > Kris > > Internationalization is actually quite important, and is not easy to > bolt on after the fact but is fairly easy to program to once the core > is in place. The fact that sysinstall doesn't have it makes it no > less important. Now this isn't a reason to reject the DFly work, but > it could certainly be a good area for someone to contribute. > > Scott > Sure. I can confirm this. But this issue must be take with care. 1.- This is an overall effort that, IMHO, must begin with a real i18n=20 ports work. Actual ports doesn't have a well defined i18n behavior. 2.- this covers several unrelated issues: - i18n, lang related issues. iso8859-1, unicode, arabic ... - l10n, locale related issues (country specific). - base system oper (try hack arround loader with a foreing keyboard). About the base system, I have really bad experiences with i18n/locale=20 support in boot/system works. This must be a low priority task. But I'll be really glad to see some basic foreing keyboard/console=20 support in boot/loader as: boot> keyb sp =2D- josemi From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 10:33:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72D6716A4CE for ; Fri, 3 Dec 2004 10:33:04 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9873743D5C for ; Fri, 3 Dec 2004 10:33:03 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iB3AX20N086995 for ; Fri, 3 Dec 2004 05:33:02 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iB3AX1U0086991 for ; Fri, 3 Dec 2004 05:33:02 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Fri, 3 Dec 2004 05:33:01 -0500 (EST) From: Jeff Roberson To: current@freebsd.org Message-ID: <20041203052824.K18185@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: SMP FFS Part 3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 10:33:04 -0000 This patch removes Giant from every file related syscall. It fixes all known bugs except for one which Peter Holm has seen after very long periods of extreme load, and a nfs netbooting problem that I haven't yet looked in to. I can buildworld -j3 for hours on my dual opteron without issues. I hope to fix the remaining problems in a day or two. http://www.chesapeake.net/~jroberson/smpffs.diff Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 12:33:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C77CE16A4CE for ; Fri, 3 Dec 2004 12:33:06 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B66E43D39 for ; Fri, 3 Dec 2004 12:33:06 +0000 (GMT) (envelope-from olgeni@FreeBSD.org) Received: from freefall.freebsd.org (olgeni@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iB3CX6Ov055305 for ; Fri, 3 Dec 2004 12:33:06 GMT (envelope-from olgeni@freefall.freebsd.org) Received: (from olgeni@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iB3CX6CT055304 for freebsd-current@freebsd.org; Fri, 3 Dec 2004 12:33:06 GMT (envelope-from olgeni) Date: Fri, 3 Dec 2004 12:33:06 GMT From: Jimmy Olgeni Message-Id: <200412031233.iB3CX6CT055304@freefall.freebsd.org> To: freebsd-current@freebsd.org Subject: Siemens RX300, SMP/ACPI trouble X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 12:33:06 -0000 Hello everybody, I'm having some big trouble with SMP and a Siemens-Fujitsu RX300 server. If I disable the second processor from the BIOS, the uniprocessor configuration (GENERIC) works fine. Using both processors (still with GENERIC), I get an ATAPI_IDENTIFY timeout, then lots of timeouts on the ahd driver. This happens with both RELENG_5_3 and RELENG_5. The same goes for the SMP configuration, so maybe it's not related to SMP but there's something wrong with ACPI/MADT & C. I made a diff from "boot -hv", UP to SMP, but I couldn't figure out what is happening here. I would be grateful if somebody could offer any clue, as I'm supposed to get this working as soon as possible, or it's Red Hat time. I uploaded the original logs here: http://people.freebsd.org/~olgeni/ Thanks a lot :) 30c30 < MADT: Found CPU APIC ID 0 ACPI ID 1: disabled --- > MADT: Found CPU APIC ID 0 ACPI ID 1: enabled 86c86,88 < MADT: Ignoring local NMI routed to ACPI CPU 1 --- > lapic0: Routing NMI -> LINT1 > lapic0: LINT1 trigger: edge > lapic0: LINT1 polarity: active-high 157c159,160 < ACPI timer looks GOOD min = 2, max = 4, width = 2 --- > ACPI timer looks BAD min = 2, max = 5, width = 3 > ACPI timer looks BAD min = 2, max = 5, width = 3 164d166 < ACPI timer looks GOOD min = 2, max = 4, width = 2 455c457 < sio0: irq maps: 0x21 0x29 0x21 0x21 --- > sio0: irq maps: 0x2021 0x2029 0x2021 0x2021 458c460 < sio1: irq maps: 0x21 0x31 0x21 0x21 --- > sio1: irq maps: 0x2021 0x2031 0x2021 0x2021 552,561c554,565 < ata1-master: pio=0x0c wdma=0x22 udma=0x42 cable=40pin < ata1-master: setting PIO4 on ServerWorks CSB6 chip < ata1-master: setting UDMA33 on ServerWorks CSB6 chip < acd0: DVDROM drive at ata1 as master < acd0: read 1722KB/s (4134KB/s), 256KB buffer, UDMA33 < acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet < acd0: Writes: < acd0: Audio: play, 256 volume levels < acd0: Mechanism: ejectable tray, unlocked < acd0: Medium: no/blank disc --- > ata1: reiniting channel .. > ata1: reset tp1 mask=03 ostat0=50 ostat1=01 > ata1-master: stat=0x00 err=0x01 lsb=0x14 msb=0xeb > ata1-slave: stat=0x01 err=0x04 lsb=0x00 msb=0x00 > ata1: reset tp2 stat0=00 stat1=01 devices=0x4 > ata1: resetting done .. > ata1: reiniting channel .. > ata1-master: FAILURE - ATAPI_IDENTIFY timed out > ata1: reiniting channel .. > ata1-master: FAILURE - ATAPI_IDENTIFY timed out > ata1: device config done .. > ata1-master: FAILURE - ATAPI_IDENTIFY timed out From owner-freebsd-current@FreeBSD.ORG Thu Dec 2 18:03:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E77016A4D2; Thu, 2 Dec 2004 18:03:01 +0000 (GMT) Received: from ims-1.prv.ampira.com (ims-1.ampira.com [66.179.231.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3519143D31; Thu, 2 Dec 2004 18:03:00 +0000 (GMT) (envelope-from kamalp@acm.org) Received: from [202.142.94.194] (helo=[172.16.3.26]) by ims-1.prv.ampira.com with asmtp (Exim 4.24) id 1CZvEy-0004MZ-Im; Thu, 02 Dec 2004 12:59:41 -0500 Message-ID: <41AF58CE.10904@acm.org> Date: Thu, 02 Dec 2004 23:32:54 +0530 From: "Kamal R. Prasad" User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andre Oppermann References: <41AE3F80.1000506@freebsd.org> <41AF29AC.6030401@freebsd.org> <41AF53E1.80408@freebsd.org> In-Reply-To: <41AF53E1.80408@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 03 Dec 2004 12:50:56 +0000 cc: Sam cc: hackers@freebsd.org cc: Scott Long cc: "current@freebsd.org" Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 18:03:01 -0000 Andre Oppermann wrote: > Sam wrote: > >> On Thu, 2 Dec 2004, Andre Oppermann wrote: >> >>> Scott Long wrote: >>> >>>> 5. Clustered FS support. SANs are all the rage these days, and >>>> clustered filesystems that allow data to be distributed across many >>>> storage enpoints and accessed concurrently through the SAN are very >>>> powerful. RedHat recently bought Sistina and re-opened the GFS source >>>> code, so exploring this would be very interesting. >>> >>> >>> There are certain steps that can be be taken one at a time. For >>> example >>> it should be relatively easy to mount snapshots (ro) from more than one >>> machine. Next step would be to mount a full 'rw' filesystem as 'ro' on >>> other boxes. This would require cache and sector invalidation >>> broadcasting >>> from the 'rw' box to the 'ro' mounts. The holy grail of course is >>> to mount >>> the same filesystem 'rw' on more than one box, preferrably more than >>> two. >>> This requires some more involved synchronization and locking on top >>> of the >>> cache invalidation. And make sure that the multi-'rw' cluster stays >>> alive >>> if one of the participants freezes and doesn't respond anymore. >>> >>> Scrolling through the UFS/FFS code I think the first one is 2-3 days of >>> work. The second 2-4 weeks and the third 2-3 month to get it right. >>> If someone would throw up the money... >> >> >> You might also design in consideration for data redundancy. Right now >> GFS largely relies on the SAN box to export already redundant RAID >> disks. GFS sits on a "cluster aware" lvm layer that is supposed to >> be able to do mirroring and striping, but I'm told it's not >> stable enough for "production" use. > > > Data redundancy would require a UFS/FFS redesign. I'm 'only' talking > about enhancing UFS/FFS but keeping anything ondisk the same (plus > some more elements). > If you add redundancy code into UFS/FFS, that will slow down its performance (even for those not seeking redundancy). A better way would be to have another filesystem implementation like VxFS (veritas filesystem). Im not sure if they have published papers/put their techniques into public domain. regards -kamal From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 05:28:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A0BF16A4CE for ; Fri, 3 Dec 2004 05:28:42 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31E8143D5C for ; Fri, 3 Dec 2004 05:28:42 +0000 (GMT) (envelope-from matt.thyer@gmail.com) Received: by wproxy.gmail.com with SMTP id 57so42792wri for ; Thu, 02 Dec 2004 21:28:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=e4bwL/in1PoaxNvk7ONU7hY8pGExTotGSvcZt6gbM6AbGbzsh1YRxED2zBpuoZbQ44EEcJRJ4YAiKaPv7M48oV45acGfVhSxjyaz8D3Kla0it5e6ue06DfanpLQrJN/S6FiNW+BP4Y/jxkluMeEOM6sAZtRrpSvFb4W3rwygTMA= Received: by 10.54.52.42 with SMTP id z42mr1679043wrz; Thu, 02 Dec 2004 21:28:41 -0800 (PST) Received: by 10.54.18.37 with HTTP; Thu, 2 Dec 2004 21:28:40 -0800 (PST) Message-ID: Date: Fri, 3 Dec 2004 15:58:40 +1030 From: Matt Thyer To: Kris Kennaway In-Reply-To: <20041127185732.GA35366@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041127185732.GA35366@xor.obsecurity.org> X-Mailman-Approved-At: Fri, 03 Dec 2004 12:50:56 +0000 cc: current@freebsd.org Subject: Kernel hangs at "Timecounters tick every 1.000 msec" with APIC enabled (Was: Re: Why don't the packages get built for the runtime dependencies of the package I am building ?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Matt Thyer List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 05:28:42 -0000 Thankyou Kris, I'll try this as soon as I can get a build of -CURRENT that boots on my Athlon XP NForce 2 system. Unfortunately it's hanging again near the end of device probing (which means I have to disable APIC in the BIOS again). With APIC enabled in the BIOS this is as far as the kernel gets: sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1992033718 Hz quality 800 Timecounters tick every 1.000 msec With APIC disabled in the BIOS the system boots fine. This has been a problem in the past but not for quite a while. On Sat, 27 Nov 2004 10:57:32 -0800, Kris Kennaway wrote: > On Sat, Nov 27, 2004 at 01:17:09PM +1030, Matt Thyer wrote: > > > > Surely there is a simple way to have the runtime dependency packages > > built as well. > > > > Is this possible, or do I have to write my own script to recursively > > determine the runtime dependencies and build those packages first ? > > Does 'make package-recursive' not work? > > Kris From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 10:43:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A89916A4CE for ; Fri, 3 Dec 2004 10:43:33 +0000 (GMT) Received: from draft.nq.nu (203-173-42-29.perm.iinet.net.au [203.173.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A75143D2F for ; Fri, 3 Dec 2004 10:43:32 +0000 (GMT) (envelope-from warren@draft.nq.nu) Received: from www.slingo.nq.nu (localhost [127.0.0.1]) by draft.nq.nu (8.12.10/8.12.8) with ESMTP id iB3AhHF6091789 for ; Fri, 3 Dec 2004 20:43:17 +1000 (EST) (envelope-from warren@draft.nq.nu) From: "Warren Liddell" To: freebsd-current@freebsd.org Date: Fri, 3 Dec 2004 20:43:17 +1000 Message-Id: <20041203104130.M61393@slingo.nq.nu> X-Mailer: Open WebMail 2.32 20040525 X-OriginatingIP: 10.100.2.10 (warren) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Fri, 03 Dec 2004 12:50:56 +0000 Subject: Build error when installing py24-qt-3.13 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 10:43:33 -0000 The following is what occurs .. any ideas as to what is happening is welcomed. ============= ===> Building for py24-qt-3.13 c++ -c -pipe -fPIC -O -pipe -Wall -W -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I. - I/usr/local/include -I/usr/local/include/python2.4 -I/usr/X11R6/include -o sipqtQString.o sipqtQString.cpp sip/qt/qstring.sip: In function `int convertTo_QString(PyObject*, void**, int*)': sip/qt/qstring.sip:854: error: conversion from `long unsigned int' to `const QChar' is ambiguous /usr/X11R6/include/qstring.h:295: note: candidates are: QChar::QChar(int) /usr/X11R6/include/qstring.h:289: note: QChar::QChar(uint) /usr/X11R6/include/qstring.h:283: note: QChar::QChar(short int) /usr/X11R6/include/qstring.h:277: note: QChar::QChar(ushort) /usr/X11R6/include/qstring.h:258: note: QChar::QChar(uchar) /usr/X11R6/include/qstring.h:252: note: QChar::QChar(char) *** Error code 1 Stop in /usr/ports/x11-toolkits/py-qt/work/PyQt-x11-gpl-3.13/qt. *** Error code 1 Stop in /usr/ports/x11-toolkits/py-qt/work/PyQt-x11-gpl-3.13. *** Error code 1 Stop in /usr/ports/x11-toolkits/py-qt. *** Error code 1 Stop in /usr/ports/net/qtorrent. -- Open WebMail Project (http://openwebmail.org) From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 13:26:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C08916A4CE for ; Fri, 3 Dec 2004 13:26:27 +0000 (GMT) Received: from shim2.irt.drexel.edu (shim2.irt.drexel.edu [144.118.29.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id B106943D67 for ; Fri, 3 Dec 2004 13:26:26 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from conversion-daemon.shim2.irt.drexel.edu by shim2.irt.drexel.edu (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I8500J01DPUWL@shim2.irt.drexel.edu> for current@freebsd.org; Fri, 03 Dec 2004 08:26:26 -0500 (EST) Received: from vorpal.math.drexel.edu (vorpal.math.drexel.edu [129.25.6.250]) by shim2.irt.drexel.edu (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I8500GOKEO1U7@shim2.irt.drexel.edu> for current@freebsd.org; Fri, 03 Dec 2004 08:26:25 -0500 (EST) Received: from localhost (vorpal.math.drexel.edu [129.25.6.250]) iB3DNnIW001228 for ; Fri, 03 Dec 2004 08:23:49 -0500 (EST envelope-from jsmith@drexel.edu) Date: Fri, 03 Dec 2004 08:25:21 -0500 From: "Justin R. Smith" To: current@freebsd.org Message-id: <1102080321.1144.1.camel@localhost> Organization: Drexel University MIME-version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-type: text/plain Content-transfer-encoding: 7BIT Subject: Sound stopped working X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 13:26:27 -0000 My uname: FreeBSD jsmith.org 5.3-STABLE FreeBSD 5.3-STABLE #0: Mon Nov 29 10:44:52 EST 2004 jsmith@jsmith.org:/usr/obj/usr/src/sys/MYKERNEL i386 A couple of rebuilds ago, sound stopped working. The sound devices get created but no sound actually comes out of the speakers. Sound continues to work in Windows, so I don't think it's a hardware problem. My dmesg: FreeBSD 5.3-STABLE #0: Mon Nov 29 10:44:52 EST 2004 jsmith@jsmith.org:/usr/obj/usr/src/sys/MYKERNEL Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2400.18-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febfbff real memory = 1073725440 (1023 MB) avail memory = 1032712192 (984 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: port 0x530-0x537 on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe8000000-0xebffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 nvidia0: mem 0xf0000000-0xf7ffffff,0xe7000000-0xe7ffffff irq 16 at device 0.0 on pci1 nvidia0: [GIANT-LOCKED] isab0: at device 2.0 on pci0 isa0: on isab0 ohci0: mem 0xe6800000-0xe6800fff irq 20 at device 2.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ulpt0: Canon S600, rev 1.10/2.20, addr 2, iclass 7/1 ulpt0: using bi-directional mode ohci1: mem 0xe6000000-0xe6000fff irq 23 at device 2.3 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered atapci0: port 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.5 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 sis0: port 0xb000-0xb0ff mem 0xe5800000-0xe5800fff irq 22 at device 3.0 on pci0 miibus0: on sis0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:e0:18:94:ce:14 pcm0: port 0xa800-0xa8ff irq 17 at device 5.0 on pci0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 orm0: at iomem 0xc0000-0xcffff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 2400184756 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ad0: 38172MB [77557/16/63] at ata0-master UDMA100 ad1: 39205MB [79656/16/63] at ata0-slave UDMA100 acd0: CDRW at ata1-master PIO4 acd1: DVDROM at ata1-slave UDMA40 cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ata1 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present Mounting root from ufs:/dev/ad1s1a ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled pid 58286 (totem-video-thumbna), uid 500: exited on signal 11 (core dumped) Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...5 5 5 4 4 2 2 0 0 0 done No buffers busy after final sync Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #0: Mon Nov 29 10:44:52 EST 2004 jsmith@jsmith.org:/usr/obj/usr/src/sys/MYKERNEL Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2400.18-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febfbff real memory = 1073725440 (1023 MB) avail memory = 1032712192 (984 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: port 0x530-0x537 on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe8000000-0xebffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 nvidia0: mem 0xf0000000-0xf7ffffff,0xe7000000-0xe7ffffff irq 16 at device 0.0 on pci1 nvidia0: [GIANT-LOCKED] isab0: at device 2.0 on pci0 isa0: on isab0 ohci0: mem 0xe6800000-0xe6800fff irq 20 at device 2.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ulpt0: Canon S600, rev 1.10/2.20, addr 2, iclass 7/1 ulpt0: using bi-directional mode ohci1: mem 0xe6000000-0xe6000fff irq 23 at device 2.3 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered atapci0: port 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.5 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 sis0: port 0xb000-0xb0ff mem 0xe5800000-0xe5800fff irq 22 at device 3.0 on pci0 miibus0: on sis0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:e0:18:94:ce:14 pcm0: port 0xa800-0xa8ff irq 17 at device 5.0 on pci0 I think this is the sound driver^^^^^ fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 orm0: at iomem 0xc0000-0xcffff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 2400180100 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ad0: 38172MB [77557/16/63] at ata0-master UDMA100 ad1: 39205MB [79656/16/63] at ata0-slave UDMA100 acd0: CDRW at ata1-master PIO4 acd1: DVDROM at ata1-slave UDMA40 cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 16.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ata1 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present Mounting root from ufs:/dev/ad1s1a ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled Cat /dev/sndstat returns: FreeBSD Audio Driver (newpcm) Installed devices: pcm0: at io 0xa800 irq 17 kld snd_cmi (1p/1r/0v channels duplex default) Any suggestions? -- Time blows wildly against my door | Justin R. Smith Stirring discarded sorrows | Mathematics Department Like dead leaves of summers past | Drexel University Shadows of what went before | Philadelphia, PA 19104 Making way for new tomorrows | New hopes, new fears, | Office: (215) 895-1847 and new ways that last | URL: vorpal.math.drexel.edu From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 17:01:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F060F16A4CE for ; Fri, 3 Dec 2004 17:01:11 +0000 (GMT) Received: from annibale.willystudios.com (annibale.willystudios.com [216.120.241.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F43C43D5D for ; Fri, 3 Dec 2004 17:01:11 +0000 (GMT) (envelope-from stucchi@willystudios.com) Received: by annibale.willystudios.com (Postfix, from userid 1003) id 7E5FF4F4A9; Fri, 3 Dec 2004 17:58:28 +0100 (CET) Received: from max.willystudios.com (host20-123.pool80116.interbusiness.it [80.116.123.20]) by annibale.willystudios.com (Postfix) with ESMTP id 935FE4F429; Fri, 3 Dec 2004 17:58:27 +0100 (CET) Received: by max.willystudios.com (Postfix, from userid 1000) id 9AA8F827; Fri, 3 Dec 2004 18:02:17 +0100 (CET) Date: Fri, 3 Dec 2004 18:02:17 +0100 From: Massimiliano Stucchi To: "Devon H. O'Dell" Message-ID: <20041203170217.GA59168@willystudios.com> References: <41AE55D7.8020709@freebsd.org> <41AEA4B8.6080508@acm.org> <20041202075530.3b33db1b.flynn@energyhq.es.eu.org> <20041202190337.GY79646@cirb503493.alcatel.com.au> <8cb27cbf04120211553b4304bf@mail.gmail.com> <41AF75B1.6070306@sitetronics.com> <41B010E5.4080201@sitetronics.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j" Content-Disposition: inline In-Reply-To: <41B010E5.4080201@sitetronics.com> X-Operating-System: FreeBSD 4.10-STABLE X-URL: http://www.willystudios.com/max/ X-Organization: WillyStudios.com User-Agent: Mutt/1.5.6i X-Bogosity: No, tests=bogofilter, spamicity=0.500000, version=0.92.8 cc: Eric Kjeldergaard cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: stucchi@willystudios.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 17:01:12 -0000 --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 031204, 08:08, Devon H. O'Dell wrote: > > I believe it's to be shipped with the FreeSBIE 1.1 release. It used to=20 > be on www.livebsd.com, but I think Scott (Ullrich) removed it (or I may= =20 > be wrong). You can obviously check out its functionality for DragonFly=20 > BSD (the interface when installing FreeSBIE is the same). Yup, it will be shipped with FreeSBIE-1.1, which is due in a couple days, one we work out final settings. Get ready for it Ciao ! --=20 Massimiliano Stucchi WillyStudios.com stucchi@willystudios.com Http://www.willystudios.com/max/ --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBsJwZFwcpJfdZDoERAk73AJ9gPrZf6MLMCbi0ivNlkOO3EkmTYQCfYrWN qRatrprbQ9rI23qd2iOHBug= =z10z -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 17:35:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E095216A4CE for ; Fri, 3 Dec 2004 17:35:21 +0000 (GMT) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EBF943D53 for ; Fri, 3 Dec 2004 17:35:20 +0000 (GMT) (envelope-from pbowen@fastmail.fm) Received: from frontend3.messagingengine.com (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id 75321C3E7CE for ; Fri, 3 Dec 2004 12:35:19 -0500 (EST) X-Sasl-enc: mG9HjlFHDIDzxIL8RXLuRg 1102095319 Received: from fastmail.fm (unknown [207.160.232.85]) by frontend3.messagingengine.com (Postfix) with ESMTP id 676B7247F3 for ; Fri, 3 Dec 2004 12:35:19 -0500 (EST) Message-ID: <41B0A3AF.50701@fastmail.fm> Date: Fri, 03 Dec 2004 11:34:39 -0600 From: Patrick Bowen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Setting DMA for DVD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 17:35:22 -0000 Hi all: I'm running 6.0 (rebuilt last night) on a dell C600 laptop. I've been trying to set DMA on for my DVD in loader.conf with the following, per the handbook; hw.ata.atapi_dma="1" Unfortunately when I reboot, the drive is back to PIO4. I can set it maually with; atacontrol mode 1 wdma2 biospio but, of course it reverts on reboot. How do I make this persistent across reboots. Thanks in advance... Patrick From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 17:52:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7177E16A4CE for ; Fri, 3 Dec 2004 17:52:22 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id CE13843D54 for ; Fri, 3 Dec 2004 17:52:21 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 12623 invoked from network); 3 Dec 2004 17:52:20 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 3 Dec 2004 17:52:20 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB3HqJLR096095; Fri, 3 Dec 2004 18:52:19 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB3HqIWE096094; Fri, 3 Dec 2004 18:52:18 +0100 (CET) (envelope-from pho) Date: Fri, 3 Dec 2004 18:52:18 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041203175218.GA96071@peter.osted.lan> References: <20041203052824.K18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041203052824.K18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP FFS Part 3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 17:52:22 -0000 On Fri, Dec 03, 2004 at 05:33:01AM -0500, Jeff Roberson wrote: > This patch removes Giant from every file related syscall. It fixes all > known bugs except for one which Peter Holm has seen after very long > periods of extreme load, and a nfs netbooting problem that I haven't yet > looked in to. I can buildworld -j3 for hours on my dual opteron without > issues. I hope to fix the remaining problems in a day or two. > > http://www.chesapeake.net/~jroberson/smpffs.diff > Fatal trap 12: page fault while in kernel mode in kern/kern_proc.c:694 http://www.holm.cc/stress/log/jeff07.html (a dup of jeff02.html?) > Cheers, > Jeff > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 17:56:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08FD116A4CE for ; Fri, 3 Dec 2004 17:56:18 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA6F443D4C for ; Fri, 3 Dec 2004 17:56:17 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B6860512CC; Fri, 3 Dec 2004 10:01:56 -0800 (PST) Date: Fri, 3 Dec 2004 10:01:56 -0800 From: Kris Kennaway To: Peter Holm Message-ID: <20041203180156.GA25520@xor.obsecurity.org> References: <20041202155637.GA85127@peter.osted.lan> <98967.1102003088@critter.freebsd.dk> <20041203083458.GA92652@peter.osted.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e" Content-Disposition: inline In-Reply-To: <20041203083458.GA92652@peter.osted.lan> User-Agent: Mutt/1.4.2.1i cc: Jeff Roberson cc: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: SMP VFS Part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 17:56:18 -0000 --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 03, 2004 at 09:34:58AM +0100, Peter Holm wrote: > On Thu, Dec 02, 2004 at 04:58:08PM +0100, Poul-Henning Kamp wrote: > > In message <20041202155637.GA85127@peter.osted.lan>, Peter Holm writes: > >=20 > > >Just got a double panic again: http://www.holm.cc/stress/log/jeff06.ht= ml. > > >I think I'll revert to HEAD, just to touch base. > >=20 > > HEAD is not very happy on my testbox right now, recent ACPI commits see= ms > > to have received less than meticulous scrutiny. > >=20 >=20 > Hmm ... >=20 > I've reverted Jeff's patch (so I'm now back to HEAD from Dec 1 10:04 UTC). > I have not seen any buf related panics, during the last 16 of testing, on= ly > a few "sleeping thread owns a non-sleepable lock". That one's phk's bug. Kris --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBsKoUWry0BWjoQKURAgi0AJ98XVywOVczyHVXfb6Bw4J/ZUNpzgCgho2k ylPmLrbM9CDLMUgxwDKKRfY= =RSJm -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 17:57:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9566C16A4CE for ; Fri, 3 Dec 2004 17:57:13 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CCE943D53 for ; Fri, 3 Dec 2004 17:57:13 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D8A60512C7; Fri, 3 Dec 2004 10:02:51 -0800 (PST) Date: Fri, 3 Dec 2004 10:02:51 -0800 From: Kris Kennaway To: Warren Liddell Message-ID: <20041203180251.GB25520@xor.obsecurity.org> References: <20041203104130.M61393@slingo.nq.nu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="St7VIuEGZ6dlpu13" Content-Disposition: inline In-Reply-To: <20041203104130.M61393@slingo.nq.nu> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: Build error when installing py24-qt-3.13 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 17:57:13 -0000 --St7VIuEGZ6dlpu13 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Dec 03, 2004 at 08:43:17PM +1000, Warren Liddell wrote: > The following is what occurs .. any ideas as to what is happening is welcomed. > ============= Looks like it (and a few dozen other ports) don't build with python 2.4. See bsd.python.mk and try building with 2.3. Kris --St7VIuEGZ6dlpu13 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBsKpKWry0BWjoQKURAtqHAJ4hvo93XbUjj5TlqfXROjg8QRos2wCcCEzC NjM8AQ2wck7G9wgWVwpqlH0= =z+Gg -----END PGP SIGNATURE----- --St7VIuEGZ6dlpu13-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 19:00:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAE7716A4CF for ; Fri, 3 Dec 2004 19:00:48 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 4CF8843D48 for ; Fri, 3 Dec 2004 19:00:48 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 32554 invoked from network); 3 Dec 2004 19:00:47 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 3 Dec 2004 19:00:47 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB3J0kRC096776; Fri, 3 Dec 2004 20:00:46 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB3J0kSH096775; Fri, 3 Dec 2004 20:00:46 +0100 (CET) (envelope-from pho) Date: Fri, 3 Dec 2004 20:00:46 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041203190046.GA96758@peter.osted.lan> References: <20041203052824.K18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041203052824.K18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP FFS Part 3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 19:00:49 -0000 On Fri, Dec 03, 2004 at 05:33:01AM -0500, Jeff Roberson wrote: > This patch removes Giant from every file related syscall. It fixes all > known bugs except for one which Peter Holm has seen after very long > periods of extreme load, and a nfs netbooting problem that I haven't yet > looked in to. I can buildworld -j3 for hours on my dual opteron without > issues. I hope to fix the remaining problems in a day or two. > > http://www.chesapeake.net/~jroberson/smpffs.diff > Here's the double panic again: panpanic: bremfree: buffer not on a queue. panic: wrong b_bufobj 0 should be 0xc1dda034 http://www.holm.cc/stress/log/jeff08.html > Cheers, > Jeff > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 19:18:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 078CC16A4CE for ; Fri, 3 Dec 2004 19:18:26 +0000 (GMT) Received: from peedub.jennejohn.org (J90a3.j.pppool.de [85.74.144.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D63B43D55 for ; Fri, 3 Dec 2004 19:18:25 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.1/8.11.6) with ESMTP id iB3JIKr0029486; Fri, 3 Dec 2004 20:18:21 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200412031918.iB3JIKr0029486@peedub.jennejohn.org> X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Patrick Bowen In-reply-to: Your message of "Fri, 03 Dec 2004 11:34:39 CST." <41B0A3AF.50701@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Dec 2004 20:18:20 +0100 From: Gary Jennejohn cc: freebsd-current@freebsd.org Subject: Re: Setting DMA for DVD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gary Jennejohn List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 19:18:26 -0000 Patrick Bowen writes: > atacontrol mode 1 wdma2 biospio > Put this line into /etc/rc.local. I do very similar things that way. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 19:24:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D672E16A4CE for ; Fri, 3 Dec 2004 19:24:35 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50DD143D1D for ; Fri, 3 Dec 2004 19:24:35 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB3JSQ6E085018; Fri, 3 Dec 2004 12:28:26 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41B0BD7D.30506@freebsd.org> Date: Fri, 03 Dec 2004 12:24:45 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Justin R. Smith" References: <1102080321.1144.1.camel@localhost> In-Reply-To: <1102080321.1144.1.camel@localhost> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org Subject: Re: Sound stopped working X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 19:24:36 -0000 If you back out rev 1.59.2.2 of /sys/i386/i386/busdma_machdep.c, does it work again? Scott Justin R. Smith wrote: > My uname: > > FreeBSD jsmith.org 5.3-STABLE FreeBSD 5.3-STABLE #0: Mon Nov 29 10:44:52 > EST 2004 jsmith@jsmith.org:/usr/obj/usr/src/sys/MYKERNEL i386 > > A couple of rebuilds ago, sound stopped working. The sound devices get > created but no sound actually comes out of the speakers. Sound continues > to work in Windows, so I don't think it's a hardware problem. > > My dmesg: > > FreeBSD 5.3-STABLE #0: Mon Nov 29 10:44:52 EST 2004 > jsmith@jsmith.org:/usr/obj/usr/src/sys/MYKERNEL > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2400.18-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 > > Features=0x3febfbff > real memory = 1073725440 (1023 MB) > avail memory = 1032712192 (984 MB) > ACPI APIC Table: > ioapic0 irqs 0-23 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 > cpu0: port 0x530-0x537 on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: mem 0xe8000000-0xebffffff at device > 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > nvidia0: mem > 0xf0000000-0xf7ffffff,0xe7000000-0xe7ffffff irq 16 at device 0.0 on pci1 > nvidia0: [GIANT-LOCKED] > isab0: at device 2.0 on pci0 > isa0: on isab0 > ohci0: mem 0xe6800000-0xe6800fff irq 20 at > device 2.2 on pci0 > ohci0: [GIANT-LOCKED] > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 3 ports with 3 removable, self powered > ulpt0: Canon S600, rev 1.10/2.20, addr 2, iclass 7/1 > ulpt0: using bi-directional mode > ohci1: mem 0xe6000000-0xe6000fff irq 23 at > device 2.3 on pci0 > ohci1: [GIANT-LOCKED] > usb1: OHCI version 1.0, legacy support > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 3 ports with 3 removable, self powered > atapci0: port > 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.5 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > sis0: port 0xb000-0xb0ff mem > 0xe5800000-0xe5800fff irq 22 at device 3.0 on pci0 > miibus0: on sis0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sis0: Ethernet address: 00:e0:18:94:ce:14 > pcm0: port 0xa800-0xa8ff irq 17 at device 5.0 on pci0 > fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on > acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq > 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/16 bytes threshold > ppbus0: on ppc0 > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4 > orm0: at iomem 0xc0000-0xcffff on isa0 > pmtimer0 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > isa0 > Timecounter "TSC" frequency 2400184756 Hz quality 800 > Timecounters tick every 10.000 msec > acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% > ad0: 38172MB [77557/16/63] at ata0-master > UDMA100 > ad1: 39205MB [79656/16/63] at ata0-slave > UDMA100 > acd0: CDRW at ata1-master PIO4 > acd1: DVDROM at ata1-slave UDMA40 > cd0 at ata1 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI-0 device > cd0: 16.000MB/s transfers > cd0: Attempt to query device size failed: NOT READY, Medium not present > cd1 at ata1 bus 0 target 1 lun 0 > cd1: Removable CD-ROM SCSI-0 device > cd1: 3.300MB/s transfers > cd1: Attempt to query device size failed: NOT READY, Medium not present > Mounting root from ufs:/dev/ad1s1a > ipfw2 initialized, divert disabled, rule-based forwarding disabled, > default to deny, logging disabled > pid 58286 (totem-video-thumbna), uid 500: exited on signal 11 (core > dumped) > Waiting (max 60 seconds) for system process `vnlru' to stop...done > Waiting (max 60 seconds) for system process `bufdaemon' to stop...done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining...5 5 5 4 4 2 2 0 0 0 done > No buffers busy after final sync > Copyright (c) 1992-2004 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.3-STABLE #0: Mon Nov 29 10:44:52 EST 2004 > jsmith@jsmith.org:/usr/obj/usr/src/sys/MYKERNEL > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2400.18-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 > > Features=0x3febfbff > real memory = 1073725440 (1023 MB) > avail memory = 1032712192 (984 MB) > ACPI APIC Table: > ioapic0 irqs 0-23 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 > cpu0: port 0x530-0x537 on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: mem 0xe8000000-0xebffffff at device > 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > nvidia0: mem > 0xf0000000-0xf7ffffff,0xe7000000-0xe7ffffff irq 16 at device 0.0 on pci1 > nvidia0: [GIANT-LOCKED] > isab0: at device 2.0 on pci0 > isa0: on isab0 > ohci0: mem 0xe6800000-0xe6800fff irq 20 at > device 2.2 on pci0 > ohci0: [GIANT-LOCKED] > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 3 ports with 3 removable, self powered > ulpt0: Canon S600, rev 1.10/2.20, addr 2, iclass 7/1 > ulpt0: using bi-directional mode > ohci1: mem 0xe6000000-0xe6000fff irq 23 at > device 2.3 on pci0 > ohci1: [GIANT-LOCKED] > usb1: OHCI version 1.0, legacy support > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 3 ports with 3 removable, self powered > atapci0: port > 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.5 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > sis0: port 0xb000-0xb0ff mem > 0xe5800000-0xe5800fff irq 22 at device 3.0 on pci0 > miibus0: on sis0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > sis0: Ethernet address: 00:e0:18:94:ce:14 > > > > pcm0: port 0xa800-0xa8ff irq 17 at device 5.0 on pci0 > > I think this is the sound driver^^^^^ > > fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on > acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq > 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/16 bytes threshold > ppbus0: on ppc0 > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4 > orm0: at iomem 0xc0000-0xcffff on isa0 > pmtimer0 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > isa0 > Timecounter "TSC" frequency 2400180100 Hz quality 800 > Timecounters tick every 10.000 msec > acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% > ad0: 38172MB [77557/16/63] at ata0-master > UDMA100 > ad1: 39205MB [79656/16/63] at ata0-slave > UDMA100 > acd0: CDRW at ata1-master PIO4 > acd1: DVDROM at ata1-slave UDMA40 > cd0 at ata1 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI-0 device > cd0: 16.000MB/s transfers > cd0: Attempt to query device size failed: NOT READY, Medium not present > cd1 at ata1 bus 0 target 1 lun 0 > cd1: Removable CD-ROM SCSI-0 device > cd1: 3.300MB/s transfers > cd1: Attempt to query device size failed: NOT READY, Medium not present > Mounting root from ufs:/dev/ad1s1a > ipfw2 initialized, divert disabled, rule-based forwarding disabled, > default to deny, logging disabled > > Cat /dev/sndstat returns: > > FreeBSD Audio Driver (newpcm) > Installed devices: > pcm0: at io 0xa800 irq 17 kld snd_cmi (1p/1r/0v > channels duplex > default) > > > Any suggestions? > > From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 21:16:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41E8D16A4CE for ; Fri, 3 Dec 2004 21:16:54 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id C93C143D48 for ; Fri, 3 Dec 2004 21:16:53 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iB3LGr0N056333; Fri, 3 Dec 2004 16:16:53 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iB3LGqHh056322; Fri, 3 Dec 2004 16:16:52 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Fri, 3 Dec 2004 16:16:51 -0500 (EST) From: Jeff Roberson To: Peter Holm In-Reply-To: <20041203190046.GA96758@peter.osted.lan> Message-ID: <20041203161541.B18185@mail.chesapeake.net> References: <20041203052824.K18185@mail.chesapeake.net> <20041203190046.GA96758@peter.osted.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: SMP FFS Part 3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 21:16:54 -0000 On Fri, 3 Dec 2004, Peter Holm wrote: > On Fri, Dec 03, 2004 at 05:33:01AM -0500, Jeff Roberson wrote: > > This patch removes Giant from every file related syscall. It fixes all > > known bugs except for one which Peter Holm has seen after very long > > periods of extreme load, and a nfs netbooting problem that I haven't yet > > looked in to. I can buildworld -j3 for hours on my dual opteron without > > issues. I hope to fix the remaining problems in a day or two. > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > Here's the double panic again: > panpanic: bremfree: buffer not on a queue. > panic: wrong b_bufobj 0 should be 0xc1dda034 > > http://www.holm.cc/stress/log/jeff08.html Well, I'm glad that there is nothing new. I'm going to add some tracing so we can track this down. I haven't yet reproduced it, so hopefully you can get some ktr data out of it. I'll let you know when I have some debugging tools. > > > Cheers, > > Jeff > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- > Peter Holm > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 21:17:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6F8516A4CE for ; Fri, 3 Dec 2004 21:17:51 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72CF743D2F for ; Fri, 3 Dec 2004 21:17:51 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iB3LHn0N056869; Fri, 3 Dec 2004 16:17:50 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iB3LHncp056860; Fri, 3 Dec 2004 16:17:49 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Fri, 3 Dec 2004 16:17:48 -0500 (EST) From: Jeff Roberson To: Peter Holm In-Reply-To: <20041203175218.GA96071@peter.osted.lan> Message-ID: <20041203161658.Y18185@mail.chesapeake.net> References: <20041203052824.K18185@mail.chesapeake.net> <20041203175218.GA96071@peter.osted.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: SMP FFS Part 3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 21:17:52 -0000 On Fri, 3 Dec 2004, Peter Holm wrote: > On Fri, Dec 03, 2004 at 05:33:01AM -0500, Jeff Roberson wrote: > > This patch removes Giant from every file related syscall. It fixes all > > known bugs except for one which Peter Holm has seen after very long > > periods of extreme load, and a nfs netbooting problem that I haven't yet > > looked in to. I can buildworld -j3 for hours on my dual opteron without > > issues. I hope to fix the remaining problems in a day or two. > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > Fatal trap 12: page fault while in kernel mode in kern/kern_proc.c:694 > http://www.holm.cc/stress/log/jeff07.html (a dup of jeff02.html?) Can you get me a stack trace from the blocked thread? > > > Cheers, > > Jeff > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- > Peter Holm > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 22:16:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0813916A4CF for ; Fri, 3 Dec 2004 22:16:50 +0000 (GMT) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 6F33743D4C for ; Fri, 3 Dec 2004 22:16:49 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 66115 invoked from network); 3 Dec 2004 22:16:48 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 3 Dec 2004 22:16:48 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB3MGlh6097436; Fri, 3 Dec 2004 23:16:47 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB3MGl7G097435; Fri, 3 Dec 2004 23:16:47 +0100 (CET) (envelope-from pho) Date: Fri, 3 Dec 2004 23:16:46 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041203221646.GA97365@peter.osted.lan> References: <20041203052824.K18185@mail.chesapeake.net> <20041203175218.GA96071@peter.osted.lan> <20041203161658.Y18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041203161658.Y18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP FFS Part 3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 22:16:50 -0000 On Fri, Dec 03, 2004 at 04:17:48PM -0500, Jeff Roberson wrote: > On Fri, 3 Dec 2004, Peter Holm wrote: > > > On Fri, Dec 03, 2004 at 05:33:01AM -0500, Jeff Roberson wrote: > > > This patch removes Giant from every file related syscall. It fixes all > > > known bugs except for one which Peter Holm has seen after very long > > > periods of extreme load, and a nfs netbooting problem that I haven't yet > > > looked in to. I can buildworld -j3 for hours on my dual opteron without > > > issues. I hope to fix the remaining problems in a day or two. > > > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > > > > Fatal trap 12: page fault while in kernel mode in kern/kern_proc.c:694 > > http://www.holm.cc/stress/log/jeff07.html (a dup of jeff02.html?) > > Can you get me a stack trace from the blocked thread? > OK. (kgdb) p td $9 = (struct thread *) 0xc2550180 (kgdb) p/d (*td.td_proc).p_pid $10 = 11895 (kgdb) btp 11895 frame 0 at 0xcf87877c: ebp cf8787cc, eip 0xc0615ad5 : add $0xc,%esp frame 1 at 0xcf8787cc: ebp cf8787f4, eip 0xc062dcb5 : pop %ebx frame 2 at 0xcf8787f4: ebp cf878820, eip 0xc0607d5e <_mtx_lock_sleep+166>: add $0x18,%esp frame 3 at 0xcf878820: ebp cf87884c, eip 0xc0607e7c <_mtx_lock_flags+136>: or $0x8,%esi frame 4 at 0xcf87884c: ebp cf8788d8, eip 0xc072c488 : mov 0xffffffe8(%ebp),%esi frame 5 at 0xcf8788d8: ebp cf878a40, eip 0xc075375a : add $0x10,%esp frame 6 at 0xcf878a40: ebp cf878a54, eip 0xc0753d9d : test %eax,%eax frame 7 at 0xcf878a54: ebp cf878b30, eip 0xc066fc38 : pop %ecx frame 8 at 0xcf878b30: ebp cf878b4c, eip 0xc066fe9e : leave frame 9 at 0xcf878b4c: ebp cf878cc8, eip 0xc0665f24 : add $0x10,%esp frame 10 at 0xcf878cc8: ebp cf878cec, eip 0xc0666852 : mov %eax,%esi frame 11 at 0xcf878cec: ebp cf878d40, eip 0xc07b48d0 : mov %eax,%ebx > > > > > Cheers, > > > Jeff > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > -- > > Peter Holm > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 22:18:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6192916A4CE for ; Fri, 3 Dec 2004 22:18:11 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id C317243D60 for ; Fri, 3 Dec 2004 22:18:10 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 97704 invoked from network); 3 Dec 2004 22:18:09 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 3 Dec 2004 22:18:09 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB3MI9Jn097451; Fri, 3 Dec 2004 23:18:09 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB3MI8xq097450; Fri, 3 Dec 2004 23:18:08 +0100 (CET) (envelope-from pho) Date: Fri, 3 Dec 2004 23:18:08 +0100 From: Peter Holm To: Jeff Roberson Message-ID: <20041203221808.GB97365@peter.osted.lan> References: <20041203052824.K18185@mail.chesapeake.net> <20041203190046.GA96758@peter.osted.lan> <20041203161541.B18185@mail.chesapeake.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041203161541.B18185@mail.chesapeake.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: SMP FFS Part 3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 22:18:11 -0000 On Fri, Dec 03, 2004 at 04:16:51PM -0500, Jeff Roberson wrote: > On Fri, 3 Dec 2004, Peter Holm wrote: > > > On Fri, Dec 03, 2004 at 05:33:01AM -0500, Jeff Roberson wrote: > > > This patch removes Giant from every file related syscall. It fixes all > > > known bugs except for one which Peter Holm has seen after very long > > > periods of extreme load, and a nfs netbooting problem that I haven't yet > > > looked in to. I can buildworld -j3 for hours on my dual opteron without > > > issues. I hope to fix the remaining problems in a day or two. > > > > > > http://www.chesapeake.net/~jroberson/smpffs.diff > > > > > Here's the double panic again: > > panpanic: bremfree: buffer not on a queue. > > panic: wrong b_bufobj 0 should be 0xc1dda034 > > > > http://www.holm.cc/stress/log/jeff08.html > > Well, I'm glad that there is nothing new. I'm going to add some tracing > so we can track this down. I haven't yet reproduced it, so hopefully you > can get some ktr data out of it. I'll let you know when I have some > debugging tools. > Great! > > > > > Cheers, > > > Jeff > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > -- > > Peter Holm > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Fri Dec 3 23:50:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E962616A4CE; Fri, 3 Dec 2004 23:50:52 +0000 (GMT) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93E6843D5D; Fri, 3 Dec 2004 23:50:52 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 9F55612B140; Fri, 3 Dec 2004 19:50:47 -0400 (AST) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 85852-10; Fri, 3 Dec 2004 23:50:47 +0000 (GMT) Received: from ganymede.hub.org (blk-222-46-91.eastlink.ca [24.222.46.91]) by hub.org (Postfix) with ESMTP id C865D12B13D; Fri, 3 Dec 2004 19:50:46 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id 33FB346198; Fri, 3 Dec 2004 19:50:45 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 32FF346195; Fri, 3 Dec 2004 19:50:45 -0400 (AST) Date: Fri, 3 Dec 2004 19:50:45 -0400 (AST) From: "Marc G. Fournier" To: Don Lewis In-Reply-To: <200410010407.i91471ts042635@gw.catspoiler.org> Message-ID: <20041203194816.Q87096@ganymede.hub.org> References: <200410010407.i91471ts042635@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org cc: stable@Freebsd.org cc: current@FreeBSD.org Subject: Re: fsck_ffs patch testers wanted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 23:50:53 -0000 I'd just like to post a follow up to this, and thanks ... one of our servers crashed tonight, after being up and running for ~67days ... normally, I'd be cursing, because after *that* long, the fsck would take about 12 hours or so ... The server rebooted, fsck'd and dump'd a core file in <60 minutes ... Thanks Don ... On Thu, 30 Sep 2004, Don Lewis wrote: > On 30 Sep, Marc G. Fournier wrote: >> >> Would you be willing to post a 4.x version of this, or send me one, that I >> can test, since I'm the one that seems lucky to get the "glacially slow" >> fsck's :( > > I was planning on posting a 4.x version sometime after I did the commit > to -CURRENT and it had time to get well exercised by the masses. My > plan is to allow about a month of testing between the commit to -CURRENT > and the MFC. ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 03:46:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E86F16A4CE for ; Sat, 4 Dec 2004 03:46:00 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 020E143D31 for ; Sat, 4 Dec 2004 03:46:00 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CaQrv-0005XA-DC for freebsd-current@freebsd.org; Fri, 03 Dec 2004 19:45:59 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16817.13046.982719.724355@ran.psg.com> Date: Fri, 3 Dec 2004 19:45:58 -0800 To: FreeBSD Current Subject: quota report discrepancy X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 03:46:00 -0000 # quota -v -g uucp Disk quotas for group uucp (gid 66): Filesystem usage quota limit grace files quota limit grace /var/spool 19400 0 0 2966 0 50000 # repquota /var/spool Block limits File limits User used soft hard grace used soft hard grace root -- 38 0 0 - 23 0 0 - mailnull -- 128290 0 0 - 956 0 0 - uucp -- 19402 0 0 - 2967 0 0 - why does the hard group file limit for uucp not show in the second report? randy From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 08:43:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C22AD16A4CE for ; Sat, 4 Dec 2004 08:43:25 +0000 (GMT) Received: from wattres.watt.com (wattres.watt.com [66.93.133.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FB0A43D67 for ; Sat, 4 Dec 2004 08:43:25 +0000 (GMT) (envelope-from steve@Watt.COM) Received: from wattres.watt.com (localhost.watt.com [127.0.0.1]) by wattres.watt.com (8.13.1/8.13.1) with ESMTP id iB48hOXb067880 for ; Sat, 4 Dec 2004 00:43:24 -0800 (PST) (envelope-from steve@wattres.watt.com) Received: (from steve@localhost) by wattres.watt.com (8.13.1/8.13.1/Submit) id iB48hOAv067879 for freebsd-current@freebsd.org; Sat, 4 Dec 2004 00:43:24 -0800 (PST) (envelope-from steve) Message-Id: <200412040843.iB48hOAv067879@wattres.watt.com> From: steve@Watt.COM (Steve Watt) Date: Sat, 4 Dec 2004 00:43:24 -0800 X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: freebsd-current@freebsd.org Subject: Zen of devfs configuration? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 08:43:25 -0000 Is there an article somewhere on the general intent of devfs.conf vs devfs.rules? I'm trying to figure out how to give users access to the CD-ROM so they can rip audio CDs without suid binaries or other elevated permissions. The rule I've got in mind is pretty simple (and works): # devfs ruleset 10 # devfs rule add path 'acd0t*' mode 0644 # devfs rule applyset # devfs rule show 100 path acd0t* mode 644 And I want to make it stick on reboot in some "correct" fashion. Thx, -- Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.8" / 37N 20' 14.9" Internet: steve @ Watt.COM Whois: SW32 Free time? There's no such thing. It just comes in varying prices... From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 08:57:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FA6216A4CE for ; Sat, 4 Dec 2004 08:57:12 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id A021B43D60 for ; Sat, 4 Dec 2004 08:57:11 +0000 (GMT) (envelope-from graycells@gmail.com) Received: by wproxy.gmail.com with SMTP id 37so9263wra for ; Sat, 04 Dec 2004 00:57:10 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=mfcq8IvSMnoPIskfV/TqZ+J5ZVudkbIPAvaAshe12UCMvUVEr9E+zeyGrhk4Qc+olSib14oanyhM8eQaTwNCFbY1EVuIQOMCL2Pbles3AOPdpFdcafYBcO//JwA9FFlcMM27QhxNMRRYAwebO0EokS0edmKbh7CeEzibeErA48c= Received: by 10.54.48.4 with SMTP id v4mr246344wrv; Sat, 04 Dec 2004 00:57:10 -0800 (PST) Received: by 10.54.47.51 with HTTP; Sat, 4 Dec 2004 00:57:10 -0800 (PST) Message-ID: Date: Sat, 4 Dec 2004 17:57:10 +0900 From: bsjang To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: ukbd problem.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: bsjang List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 08:57:12 -0000 when i plug and unplug several times, i can get following panic. (right after unplugging) ukbd_timeout + 0x18 softclock() ... i am sure that ukbd_timeout() is untimeout()ed in ukbd_term() and then, kbd is free()ed. but ukbed_timeout() is unexpectedly timeout()ed. where is problem...? thank you in advance From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 10:08:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68D5716A4CE for ; Sat, 4 Dec 2004 10:08:19 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1CA043D3F for ; Sat, 4 Dec 2004 10:08:18 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB4A8HX5037475 for ; Sat, 4 Dec 2004 11:08:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org From: Poul-Henning Kamp Date: Sat, 04 Dec 2004 11:08:17 +0100 Message-ID: <37474.1102154897@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 10:08:19 -0000 http://phk.freebsd.dk/patch/rootfs.patch Please test and review. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 10:51:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6243816A4CF for ; Sat, 4 Dec 2004 10:51:27 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4A7F643D45 for ; Sat, 4 Dec 2004 10:51:26 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 17806 invoked by uid 65534); 4 Dec 2004 10:51:23 -0000 Received: from pD95D89F6.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.93.137.246) by mail.gmx.net (mp001) with SMTP; 04 Dec 2004 11:51:23 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iB4ApBcr034396 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 4 Dec 2004 11:51:12 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-current@freebsd.org, Gary Jennejohn Date: Sat, 4 Dec 2004 11:51:05 +0100 User-Agent: KMail/1.7.1 References: <200412031918.iB3JIKr0029486@peedub.jennejohn.org> In-Reply-To: <200412031918.iB3JIKr0029486@peedub.jennejohn.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1155407.Cta6mjIxTA"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412041151.10022.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: Patrick Bowen Subject: Re: Setting DMA for DVD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 10:51:27 -0000 --nextPart1155407.Cta6mjIxTA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday, 3. December 2004 20:18, Gary Jennejohn wrote: > Patrick Bowen writes: > > atacontrol mode 1 wdma2 biospio > > Put this line into /etc/rc.local. I do very similar things that way. The atapi driver will only enable dma on atapi devices if they claim to at= =20 least support UDMA33/UDMA2. This behaviour was changed from 4.x (S=F8ren te= lls=20 me) because too many old devices which report bogus capabilities failed wit= h=20 the wdma modes. If your device works fine with wdma, you'll need to enable = it=20 yourself (Gary's suggestion is a good way to do it). =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1155407.Cta6mjIxTA Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBsZadXhc68WspdLARAtvzAJ9Y6AgkLNcKHqb2Vo4/P2gcvCzPvgCgpGxg 919IriTPfzKvShPHzINLT4A= =60Ls -----END PGP SIGNATURE----- --nextPart1155407.Cta6mjIxTA-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 11:28:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B74EA16A4CE for ; Sat, 4 Dec 2004 11:28:43 +0000 (GMT) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2533E43D66 for ; Sat, 4 Dec 2004 11:28:43 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id iB4BSfPw007883 for ; Sat, 4 Dec 2004 11:28:41 GMT Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.12.9p2/8.12.9) with ESMTP id iB4BSeCu081152 for ; Sat, 4 Dec 2004 11:28:41 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from localhost (gavin@localhost)iB4BSec7081149 for ; Sat, 4 Dec 2004 11:28:40 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Sat, 4 Dec 2004 11:28:40 +0000 (GMT) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: freebsd-current@freebsd.org In-Reply-To: <1101920581.84212.50.camel@buffy.york.ac.uk> Message-ID: <20041204110815.E80797@ury.york.ac.uk> References: <1101920581.84212.50.camel@buffy.york.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Subject: Re: tty-related panic on "init 0" - race? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 11:28:43 -0000 On Wed, 1 Dec 2004, Gavin Atkinson wrote: > Just got a tty-related panic when running "init 0" over a serial console > on FreeBSD 6.0-CURRENT #2: Fri Nov 26 16:59:28 GMT 2004. I was unable > to obtain a dump, but have a debug kernel available. Oops, i've had a busy week and forgot all about investigating this further. Looks like this might be a race to me. > foo# init 0 > foo# Shutting down daemon processes:. > Stopping cron. > Shutting down local daemons:. > Writing entropy file:. > . > Dec 1 16:39:47 > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 00 > fault virtual address = 0x4 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0639bd6 addr2line 0xc0639bd6 -e kernel.debug /usr/src/sys/kern/tty.c:1653 File is src/sys/kern/tty.c,v 1.242 2004/11/16 17:41:16 dds Function is ttymodem(): 1643 /* 1644 * Lost carrier. 1645 */ 1646 CLR(tp->t_state, TS_CARR_ON); 1647 if (ISSET(tp->t_state, TS_ISOPEN) && 1648 !ISSET(tp->t_cflag, CLOCAL)) { 1649 SET(tp->t_state, TS_ZOMBIE); 1650 CLR(tp->t_state, TS_CONNECTED); 1651 if (tp->t_session) { 1652 sx_slock(&proctree_lock); 1653 --> if (tp->t_session->s_leader) { 1654 struct proc *p; 1655 1656 p = tp->t_session->s_leader; 1657 PROC_LOCK(p); 1658 psignal(p, SIGHUP); 1659 PROC_UNLOCK(p); So, assuming that line is correct, it looks like tp->t_session became null between testing it (on line 1651) and using it (1653). Disassembling the kernel.debug confirms it is this - that t_session has to be null. c0639bce: e8 a1 90 fd ff call c0612c74 <_sx_slock> c0639bd3: 8b 46 74 mov 0x74(%esi),%eax c0639bd6** 8b 78 04 mov 0x4(%eax),%edi c0639bd9: 83 c4 0c add $0xc,%esp c0639bdc: 85 ff test %edi,%edi c0639bde: 75 1c jne c0639bfc So are we looking at a race here? Otherwise I cannot seem to see any way this could have happened. > [thread pid 3483 tid 100148 ] > Stopped at ttymodem+0xee: movl 0x4(%eax),%edi > db> tr > Tracing pid 3483 tid 100148 td 0xc3b6fc00 > ttymodem(c35da000) at ttymodem+0xee > ptcclose(c44c5200,7,2000,c3b6fc00,c3b6fc00) at ptcclose+0x1a > devfs_close(ecd10bc0,c08b78e0,c930c564,7,c4029a80) at devfs_close+0x1ba > vn_close(c930c564,7,c4029a80,c3b6fc00,85a) at vn_close+0x5d > vn_closefile(c5137a5c,c3b6fc00,c44c6c00,0,ecd10cc0) at vn_closefile+0x44 > fdrop_locked(c5137a5c,c3b6fc00,c0870164,c3b6fc70,407) at fdrop_locked+0x79 > closef(c5137a5c,c3b6fc00,0,ecd10d40,7) at closef+0x1e > close(c3b6fc00,ecd10d14,1,23,246) at close+0x149 > syscall(2f,2f,2f,80aa000,80aa000) at syscall+0x128 > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (6, FreeBSD ELF32, close), eip = 0x2816766f, esp = 0xbfbfe06c, ebp = 0xbfbfe088 --- Anything else I can do? Gavin From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 11:56:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 586BB16A4CE for ; Sat, 4 Dec 2004 11:56:14 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBFEA43D1D for ; Sat, 4 Dec 2004 11:56:13 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB4Brw33026918; Sat, 4 Dec 2004 06:53:58 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iB4BrwVv026915; Sat, 4 Dec 2004 11:53:58 GMT (envelope-from robert@fledge.watson.org) Date: Sat, 4 Dec 2004 11:53:58 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Randy Bush In-Reply-To: <16817.13046.982719.724355@ran.psg.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD Current Subject: Re: quota report discrepancy X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 11:56:14 -0000 On Fri, 3 Dec 2004, Randy Bush wrote: > # quota -v -g uucp > Disk quotas for group uucp (gid 66): > Filesystem usage quota limit grace files quota limit grace > /var/spool 19400 0 0 2966 0 50000 > > # repquota /var/spool Do you mean repquota -g? > Block limits File limits > User used soft hard grace used soft hard grace > root -- 38 0 0 - 23 0 0 - > mailnull -- 128290 0 0 - 956 0 0 - > uucp -- 19402 0 0 - 2967 0 0 - > > why does the hard group file limit for uucp not show in the second report? > > randy > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 12:51:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DC4416A4CE for ; Sat, 4 Dec 2004 12:51:53 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C220543D2F for ; Sat, 4 Dec 2004 12:51:52 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB4CnZPb027498; Sat, 4 Dec 2004 07:49:35 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iB4CnZCc027495; Sat, 4 Dec 2004 12:49:35 GMT (envelope-from robert@fledge.watson.org) Date: Sat, 4 Dec 2004 12:49:35 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jeff Roberson In-Reply-To: <20041203052824.K18185@mail.chesapeake.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: SMP FFS Part 3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 12:51:53 -0000 On Fri, 3 Dec 2004, Jeff Roberson wrote: > This patch removes Giant from every file related syscall. It fixes all > known bugs except for one which Peter Holm has seen after very long > periods of extreme load, and a nfs netbooting problem that I haven't yet > looked in to. I can buildworld -j3 for hours on my dual opteron without > issues. I hope to fix the remaining problems in a day or two. > > http://www.chesapeake.net/~jroberson/smpffs.diff In installed the latest patch on a box a couple of minutes ago, and began a second update of a CVS tree over NFS to an NFS-mounted directory, got this: hippy# cvs -q update -dP panic: lock (sleep mutex) Giant not locked @ kern/vfs_lookup.c:220 cpuid = 0 KDB: enter: panic [thread pid 1117 tid 100168 ] Stopped at kdb_enter+0x2c: leave db> bt No such command db> trace Tracing pid 1117 tid 100168 td 0xc2b23c00 kdb_enter(c081ddbe,100,c2b23c00,c2b23c70,c08de5a0) at kdb_enter+0x2c panic(c0821748,c0835631,c082e79d,c0825f81,dc) at panic+0x17f witness_unlock(c08de5a0,8,c0825f78,dc) at witness_unlock+0x170 _mtx_unlock_flags(c08de5a0,0,c0825f78,dc) at _mtx_unlock_flags+0x3b namei(ef1ffc30,80c2000,1000000,0,c2731bdc) at namei+0x5f0 stat(c2b23c00,ef1ffd14,2,1,212) at stat+0x4a syscall(2f,2f,2f,80c40dc,80c1402) at syscall+0x128 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (188, FreeBSD ELF32, stat), eip = 0x282d8747, esp = 0xbfbfe8cc, ebp = 0xbfbfeb78 --- db> show locks db> show pcpu cpuid = 0 curthread = 0xc2b23c00: pid 1117 "cvs" curpcb = 0xef1ffda0 fpcurthread = none idlethread = 0xc2281a80: pid 14 "idle: cpu0" APIC ID = 0 currentldt = 0x30 spin locks held: The first update of the same tree didn't cause a problem, so maybe it's a path we hit the second time due to cached lookups/etc? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 13:08:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79CA116A4D1 for ; Sat, 4 Dec 2004 13:08:33 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5D9143D5A for ; Sat, 4 Dec 2004 13:08:32 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB4D6Fb4027698; Sat, 4 Dec 2004 08:06:15 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iB4D6Fv4027695; Sat, 4 Dec 2004 13:06:15 GMT (envelope-from robert@fledge.watson.org) Date: Sat, 4 Dec 2004 13:06:15 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jeff Roberson In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: SMP FFS Part 3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 13:08:34 -0000 On Sat, 4 Dec 2004, Robert Watson wrote: > The first update of the same tree didn't cause a problem, so maybe it's > a path we hit the second time due to cached lookups/etc? A little bit more information from gdb: (kgdb) bt #0 doadump () at pcpu.h:159 #1 0xc0460cba in db_fncall (dummy1=-1067294688, dummy2=0, dummy3=-1, dummy4=0xef1ff9cc "") at ../../../ddb/db_command.c:531 #2 0xc0461050 in db_command_loop () at ../../../ddb/db_command.c:349 #3 0xc0462a7c in db_trap (type=3, code=0) at ../../../ddb/db_main.c:221 #4 0xc06263e6 in kdb_trap (type=3, code=0, tf=0xef1ffaf4) at ../../../kern/subr_kdb.c:421 #5 0xc07b420c in trap (frame= {tf_fs = -283181032, tf_es = -1067319280, tf_ds = -1065287664, tf_edi = 0, tf_esi = 1, tf_ebp = -283116748, tf_isp = -283116768, tf_ebx = -283116704, tf_edx = -1065230914, tf_ecx = -1064437184, tf_eax = -1065222375, tf_trapno = 3, tf_err = 0, tf_eip = -1067294688, tf_cs = 8, tf_eflags = 642, tf_esp = -283116716, tf_ss = -1067387953}) at ../../../i386/i386/trap.c:573 #6 0xc07a2d6a in calltrap () at ../../../i386/i386/exception.s:140 #7 0xef1f0018 in ?? () #8 0xc0620010 in blst_leaf_alloc (scan=0x0, blk=1102741364158, count=0) at ../../../kern/subr_blist.c:394 #9 0xc060f3cf in panic (fmt=0x282
) at ../../../kern/kern_shutdown.c:538 #10 0xc062f1b8 in witness_unlock (lock=0xc08de5a0, flags=8, file=0xc0825f81 "kern/vfs_lookup.c", line=220) at ../../../kern/subr_witness.c:1105 #11 0xc0607f83 in _mtx_unlock_flags (m=0xc08de5a0, opts=0, file=0xc0825f78 "../../../kern/vfs_lookup.c", line=220) at ../../../kern/kern_mutex.c:296 #12 0xc065c26c in namei (ndp=0x1) at ../../../kern/vfs_lookup.c:220 #13 0xc06686fe in stat (td=0xc2b23c00, uap=0xef1ffd14) at ../../../kern/vfs_syscalls.c:2091 #14 0xc07b4650 in syscall (frame= {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 135020764, tf_esi = 135009282, tf_ebp = -1077941384, tf_isp = -283116172, tf_ebx = 674566284, tf_edx = 33619715, tf_ecx = 135012361, tf_eax = 188, tf_trapno = 12, tf_err = 2, tf_eip = 674072391, tf_cs = 31, tf_eflags = 530, tf_esp = -1077942068, tf_ss = 47}) at ../../../i386/i386/trap.c:951 #15 0xc07a2dbf in Xint0x80_syscall () at ../../../i386/i386/exception.s:201 #16 0x0000002f in ?? () #44 0xc061f6ff in sched_switch (td=0x80c1402, newtd=0x2835108c, flags=Cannot access memory at address 0xbfbfeb88 ) at ../../../kern/sched_4bsd.c:865 In the stat() frame: (kgdb) inspect nd $3 = {ni_dirp = 0x80c2000
, ni_segflg = 16777216, ni_startdir = 0x0, ni_rootdir = 0xc2731bdc, ni_topdir = 0x0, ni_vp = 0xc2731bdc, ni_dvp = 0xc277a8a0, ni_pathlen = 1, ni_next = 0xc280000b "", ni_loopcnt = 0, ni_cnd = {cn_nameiop = 0, cn_flags = 2154692, cn_thread = 0xc2b23c00, cn_cred = 0xc2934280, cn_pnbuf = 0xc2800000 "../../../..", cn_nameptr = 0xc2800009 "..", cn_namelen = 2, cn_consume = 0}} Looks like cvs was looking up all theway to the root, from an NFS subdir to a UFS root. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 14:34:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11F0416A4CE; Sat, 4 Dec 2004 14:34:03 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6E4543D53; Sat, 4 Dec 2004 14:34:02 +0000 (GMT) (envelope-from DougB@freebsd.org) Received: from pc254-91.icanncapetown.co.za ([196.25.91.254]) by comcast.net (rwcrmhc13) with ESMTP id <2004120414335801500mabgqe>; Sat, 4 Dec 2004 14:33:59 +0000 Date: Sat, 4 Dec 2004 16:33:40 +0200 (SAST) From: Doug Barton To: freebsd-current@freebsd.org Message-ID: <20041204163103.M787@cp254-91.vpnaapncrgbja.pb.mn> Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-658044418-1102170798=:787" Subject: panic: Inconsistent vnode bufstrategy X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 14:34:03 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-658044418-1102170798=:787 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT I'm using mount_ntfs to read data off my winxp partition on a dual boot system. For a week or so I've been getting a panic, which I've finally been able to get a dump for: #0 doadump () at pcpu.h:159 #1 0xc043effb in db_fncall (dummy1=-280897440, dummy2=0, dummy3=16, dummy4=0xef41d858 "Ô½eÀ\034öjÀ\034PlÀ") at /usr/local/src/sys/ddb/db_command.c:531 #2 0xc043f49d in db_command_loop () at /usr/local/src/sys/ddb/db_command.c:349 #3 0xc0441128 in db_trap (type=3, code=0) at /usr/local/src/sys/ddb/db_main.c:221 #4 0xc0525c91 in kdb_trap (type=0, code=0, tf=0xef41d98c) at /usr/local/src/sys/kern/subr_kdb.c:421 #5 0xc066b7de in trap (frame= {tf_fs = -1066729448, tf_es = 16, tf_ds = -280952816, tf_edi = 256, tf_esi = -1066707518, tf_ebp = -280897068, tf_isp = -280897096, tf_ebx = 0, tf_edx = 0, tf_ecx = -1066364320, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1068345190, tf_cs = 8, tf_eflags = 662, tf_esp = -1066723986, tf_ss = -1066732210}) at /usr/local/src/sys/i386/i386/trap.c:573 #6 0xc065dc2a in calltrap () at /usr/local/src/sys/i386/i386/exception.s:140 #7 0xc06b0018 in ?? () #8 0x00000010 in ?? () #9 0xef410010 in ?? () #10 0x00000100 in ?? () #11 0xc06b55c2 in ?? () #12 0xef41d9d4 in ?? () #13 0xef41d9b8 in ?? () #14 0x00000000 in ?? () #15 0x00000000 in ?? () #16 0xc0709260 in shutdown_howto () #17 0x00000012 in ?? () #18 0x00000003 in ?? () #19 0x00000000 in ?? () #20 0xc052589a in kdb_enter (msg=0x0) at cpufunc.h:56 #21 0xc050b78b in panic (fmt=0xc06b55c2 "Inconsistent vnode bufstrategy") at /usr/local/src/sys/kern/kern_shutdown.c:538 #22 0xc055c31b in bufstrategy (bo=0x0, bp=0xd6308b48) at /usr/local/src/sys/kern/vfs_bio.c:3832 #23 0xc063e9ac in vnode_pager_generic_getpages (vp=0xc3ad49b4, m=0xef41dc84, bytecount=-701461688, reqpage=0) at buf.h:414 #24 0xc0560d83 in vop_stdgetpages (ap=0x0) at /usr/local/src/sys/kern/vfs_default.c:612 #25 0xc063e130 in vnode_pager_getpages (object=0xc2fd9a50, m=0x0, count=1, reqpage=0) at vnode_if.h:1638 #26 0xc0625e1f in vm_fault (map=0xc2f1f4b0, vaddr=680919040, fault_type=1 '\001', fault_flags=0) at vm_pager.h:130 #27 0xc066b42c in trap_pfault (frame=0xef41dd48, usermode=1, eva=680919040) at /usr/local/src/sys/i386/i386/trap.c:701 #28 0xc066b8b5 in trap (frame= {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 68, tf_esi = 0, tf_ebp = -1077941720, tf_isp = -280896140, tf_ebx = 5141, tf_edx = 680919040, tf_ecx = -4096, tf_eax = 672530432, tf_trapno = 12, tf_err = 4, tf_eip = 134517224, tf_cs = 31, tf_eflags = 66067, tf_esp = -1077941904, tf_ss = 47}) at /usr/local/src/sys/i386/i386/trap.c:313 #29 0xc065dc2a in calltrap () at /usr/local/src/sys/i386/i386/exception.s:140 #30 0x0000002f in ?? () #31 0x0000002f in ?? () #32 0x0000002f in ?? () #33 0x00000044 in ?? () #34 0x00000000 in ?? () #35 0xbfbfea28 in ?? () #36 0xef41dd74 in ?? () #37 0x00001415 in ?? () #38 0x28960000 in ?? () #39 0xfffff000 in ?? () #40 0x28160000 in ?? () #41 0x0000000c in ?? () #42 0x00000004 in ?? () #43 0x080491e8 in ?? () #44 0x0000001f in ?? () #45 0x00010213 in ?? () #46 0xbfbfe970 in ?? () #47 0x0000002f in ?? () #48 0x2f2f2f2f in ?? () #49 0x2f2f2f2f in ?? () #50 0x2f2f2f2f in ?? () #51 0x2f2f2f2f in ?? () #52 0x2cf2b000 in ?? () #53 0xc2ed71f8 in ?? () #54 0xc2d83180 in ?? () #55 0xef41dc8c in ?? () #56 0xef41dc6c in ?? () #57 0xc2282300 in ?? () #58 0xc051dc89 in sched_switch (td=0x0, newtd=0x1415, flags=Cannot access memory at address 0xbfbfea38 ) at /usr/local/src/sys/kern/sched_4bsd.c:865 Previous frame inner to this frame (corrupt stack?) HTH, Doug -- This .signature sanitized for your protection --0-658044418-1102170798=:787-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 15:33:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27F4016A4CE for ; Sat, 4 Dec 2004 15:33:58 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA06843D41 for ; Sat, 4 Dec 2004 15:33:57 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB4FVeJQ029185; Sat, 4 Dec 2004 10:31:40 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iB4FVecF029182; Sat, 4 Dec 2004 15:31:40 GMT (envelope-from robert@fledge.watson.org) Date: Sat, 4 Dec 2004 15:31:39 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jeff Roberson In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: SMP FFS Part 3 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 15:33:58 -0000 On Sat, 4 Dec 2004, Robert Watson wrote: > On Sat, 4 Dec 2004, Robert Watson wrote: > > > The first update of the same tree didn't cause a problem, so maybe it's > > a path we hit the second time due to cached lookups/etc? > > A little bit more information from gdb: FYI, got an almost identical panic installing a replacement kernel from a build in NFS: cc -O -pipe -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /data/stock/7/src/sys/i386/compile/MAC/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g -I/data/stock/7/src/sys/i386/compile/MAC -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /data/stock/7/src/sys/modules/3dfx/../../dev/tdfx/tdfx_pci.c panic: lock (sleep mutex) Giant not locked @ kern/vfs_lookup.c:220 cpuid = 0 KDB: enter: panic [thread pid 5462 tid 100250 ] Stopped at kdb_enter+0x2c: leave db> trace Tracing pid 5462 tid 100250 td 0xc354f000 kdb_enter(c081ddbe,100,c354f000,c354f070,c08de5a0) at kdb_enter+0x2c panic(c0821748,c0835631,c082e79d,c0825f81,dc) at panic+0x17f witness_unlock(c08de5a0,8,c0825f78,dc) at witness_unlock+0x170 _mtx_unlock_flags(c08de5a0,0,c0825f78,dc) at _mtx_unlock_flags+0x3b namei(ef326c30,84f6400,1000000,0,c275d228) at namei+0x5f0 stat(c354f000,ef326d14,2,11,282) at stat+0x4a syscall(2f,84a002f,bfbf002f,8443401,84350dc) at syscall+0x128 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (188, FreeBSD ELF32, stat), eip = 0x82ce523, esp = 0xbfbfe15c, ebp = 0xbfbfe3e8 --- db> show lockedvnods Locked vnodes 0xc275d228: tag ufs, type VDIR usecount 109, writecount 0, refcount 1 mountedhere 0 flags (VV_ROOT|VV_OBJBUF) lock type ufs: EXCL (count 1) by thread 0xc354f000 (pid 5462) ino 2, on dev da0s1a (228, 6) Looks like maybe it's the '..' transition in path lookup from a file system that requires Giant to one that doesn't? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 17:50:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9946A16A4CE; Sat, 4 Dec 2004 17:50:07 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60C7E43D1D; Sat, 4 Dec 2004 17:50:07 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cae2o-000HQT-SB; Sat, 04 Dec 2004 09:50:06 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16817.63694.362551.290448@ran.psg.com> Date: Sat, 4 Dec 2004 09:50:06 -0800 To: Robert Watson References: <16817.13046.982719.724355@ran.psg.com> cc: FreeBSD Current Subject: Re: quota report discrepancy X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 17:50:07 -0000 >> # repquota /var/spool > Do you mean repquota -g? i don't think so # repquota -g uucp repquota: uucp not found in fstab randy From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 23:13:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D37C116A4CE for ; Sat, 4 Dec 2004 23:13:54 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9491C43D4C for ; Sat, 4 Dec 2004 23:13:54 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 7D77872DD4; Sat, 4 Dec 2004 15:13:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 78D9872DCB; Sat, 4 Dec 2004 15:13:52 -0800 (PST) Date: Sat, 4 Dec 2004 15:13:52 -0800 (PST) From: Doug White To: Andy Hilker In-Reply-To: <20041202202541.GA52937@mail.crypta.net> Message-ID: <20041204151311.E434@carver.gumbysoft.com> References: <20041202202541.GA52937@mail.crypta.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: linuxthreads broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 23:13:54 -0000 On Thu, 2 Dec 2004, Andy Hilker wrote: > > Hi, > > i am running mysqld 4.1 with linuxthreads since i experience more > stability and performance than without linuxthreads before a few > months. > > now linuxthreads port is broken (see below). do someone has a patch > or knows how to fix it? > btw. does mysqld 4.1 runs now good on smp machines with current? > maybe i will give a new try on this... This appears to be missing an include path. atomic_word.h is found in src/contrib/libstdc++/config/cpu/generic/atomic_word.h, and that path isn't in the compile command line. > > bye, > Andy > > > -- > > cd /usr/ports/devel/linuxthreads/work/linuxthreads-2.2.3_16/libstdc++ ; /usr/bin/env USING_GCC3=true SHELL=/bin/sh PORTOBJFORMAT=elf PREFIX=/usr/local LOCALBASE=/usr/local X11BASE=/usr/X11R6 MOTIFLIB="-L/usr/X11R6/lib -lXm -lXp" LIBDIR="/usr/lib" CFLAGS="-O -pipe -DKVA_PAGES=640 -march=pentium4" CXXFLAGS="-O -pipe -DKVA_PAGES=640 -march=pentium4" MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install -s -o root -g wheel -m 555" BSD_INSTALL_SCRIPT="install -o root -g wheel -m 555" BSD_INSTALL_DATA="install -o root -g wheel -m 444" BSD_INSTALL_MAN="install -o root -g wheel -m 444" make > Warning: Object directory not changed from original /usr/ports/devel/linuxthreads/work/linuxthreads-2.2.3_16/libstdc++ > c++ -O -pipe -DKVA_PAGES=640 -march=pentium4 -D_PTHREADS -I../ -I../sysdeps/i386 -I../sysdeps/pthread -I../sysdeps/unix/sysv/linux -DIN_GLIBCPP_V3 -DHAVE_CONFIG_H -I/usr/src/gnu/lib/libstdc++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/libsupc++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/gcc -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include -fno-implicit-templates -ffunction-sections -fdata-sections -Wno-deprecated -c /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/src/allocator.cc > In file included from /usr/include/c++/3.3/bits/stl_alloc.h:91, > from /usr/include/c++/3.3/memory:55, > from /usr/src/contrib/libstdc++/src/allocator.cc:35: > /usr/src/contrib/libstdc++/include/bits/atomicity.h:33:30: bits/atomic_word.h: No such file or directory > In file included from /usr/include/c++/3.3/bits/stl_alloc.h:91, > from /usr/include/c++/3.3/memory:55, > from /usr/src/contrib/libstdc++/src/allocator.cc:35: > /usr/src/contrib/libstdc++/include/bits/atomicity.h:39: error: syntax error > before `(' token > /usr/src/contrib/libstdc++/include/bits/atomicity.h:43: error: syntax error > before `*' token > In file included from /usr/include/c++/3.3/memory:55, > from /usr/src/contrib/libstdc++/src/allocator.cc:35: > /usr/include/c++/3.3/bits/stl_alloc.h:353: error: syntax error before `;' token > /usr/include/c++/3.3/bits/stl_alloc.h:382: error: syntax error before `;' token > /usr/include/c++/3.3/bits/stl_alloc.h:452: error: syntax error before `<' token > /usr/include/c++/3.3/bits/stl_alloc.h:452: error: `__threads' was not declared > in this scope > /usr/include/c++/3.3/bits/stl_alloc.h:452: error: `__inst' was not declared in > this scope > /usr/include/c++/3.3/bits/stl_alloc.h:452: error: template argument 1 is > invalid > /usr/include/c++/3.3/bits/stl_alloc.h:452: error: template argument 2 is > invalid > /usr/include/c++/3.3/bits/stl_alloc.h:601: error: syntax error before `<' token > /usr/include/c++/3.3/bits/stl_alloc.h:601: error: `__threads' was not declared > in this scope > /usr/include/c++/3.3/bits/stl_alloc.h:601: error: `__inst' was not declared in > this scope > /usr/include/c++/3.3/bits/stl_alloc.h:601: error: template argument 1 is > invalid > /usr/include/c++/3.3/bits/stl_alloc.h:601: error: template argument 2 is > invalid > /usr/include/c++/3.3/bits/stl_alloc.h:602: error: braces around scalar > initializer for `int' > /usr/include/c++/3.3/bits/stl_alloc.h:602: error: ignoring extra initializers > for `int' > In file included from /usr/src/contrib/libstdc++/src/allocator.cc:37: > /usr/src/contrib/libstdc++/include/ext/pool_allocator.h:122: error: syntax > error before `;' token > /usr/src/contrib/libstdc++/include/ext/pool_allocator.h:184: error: syntax > error before `<' token > /usr/src/contrib/libstdc++/include/ext/pool_allocator.h:184: error: `_Tp' was > not declared in this scope > /usr/src/contrib/libstdc++/include/ext/pool_allocator.h:184: error: template > argument 1 is invalid > /usr/src/contrib/libstdc++/include/ext/pool_allocator.h:184: error: ISO C++ > forbids declaration of `_S_force_new' with no type > *** Error code 1 > > Stop in /usr/ports/devel/linuxthreads/work/linuxthreads-2.2.3_16/libstdc++. > *** Error code 1 > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 23:43:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7B8416A4CE for ; Sat, 4 Dec 2004 23:43:14 +0000 (GMT) Received: from zaphod.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63F0443D54 for ; Sat, 4 Dec 2004 23:43:14 +0000 (GMT) (envelope-from simon@zaphod.nitro.dk) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id A915211A5F; Sun, 5 Dec 2004 00:43:13 +0100 (CET) Date: Sun, 5 Dec 2004 00:43:13 +0100 From: "Simon L. Nielsen" To: Poul-Henning Kamp Message-ID: <20041204234313.GJ778@zaphod.nitro.dk> References: <37474.1102154897@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J+eNKFoVC4T1DV3f" Content-Disposition: inline In-Reply-To: <37474.1102154897@critter.freebsd.dk> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 23:43:14 -0000 --J+eNKFoVC4T1DV3f Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.12.04 11:08:17 +0100, Poul-Henning Kamp wrote: >=20 > http://phk.freebsd.dk/patch/rootfs.patch >=20 > Please test and review. When I compile this on amd64 it fails with: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall -Wredundant-= decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-= arith -Winline -Wcast-qual -fformat-extensions -std=3Dc99 -g -nostdinc -I-= -I. -I/d/FreeBSD/test-src/sys -I/d/FreeBSD/test-src/sys/contrib/dev/acpic= a -I/d/FreeBSD/test-src/sys/contrib/altq -I/d/FreeBSD/test-src/sys/contrib/= ipfilter -I/d/FreeBSD/test-src/sys/contrib/pf -I/d/FreeBSD/test-src/sys/con= trib/dev/ath -I/d/FreeBSD/test-src/sys/contrib/dev/ath/freebsd -I/d/FreeBSD= /test-src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -fi= nline-limit=3D8000 --param inline-unit-growth=3D100 --param large-function-= growth=3D1000 -fno-omit-frame-pointer -mcmodel=3Dkernel -mno-red-zone -mf= pmath=3D387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-async= hronous-unwind-tables -ffreestanding -Werror /d/FreeBSD/test-src/sys/nfscl= ient/nfs_vfsops.c /d/FreeBSD/test-src/sys/nfsclient/nfs_vfsops.c: In function `nfs_mount': /d/FreeBSD/test-src/sys/nfsclient/nfs_vfsops.c:690: warning: passing arg 4 = of `vfs_getopt' from incompatible pointer type i386 compiles fine (just haven't gotten around to testing the kernel yet). --=20 Simon L. Nielsen --J+eNKFoVC4T1DV3f Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBskuRh9pcDSc1mlERAvxhAJwJu//f0Xfxu70pLqorjiIlbE2WFgCferfh R8N+0sc1Qj3peHrbVRaMilI= =lSO0 -----END PGP SIGNATURE----- --J+eNKFoVC4T1DV3f--