From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 02:53:58 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C232316A41C for ; Sun, 5 Jun 2005 02:53:58 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (berlin-qwest.village.org [168.103.84.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70B6043D55 for ; Sun, 5 Jun 2005 02:53:56 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j552opx6057155; Sat, 4 Jun 2005 20:50:52 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 04 Jun 2005 20:51:38 -0600 (MDT) Message-Id: <20050604.205138.89664988.imp@bsdimp.com> To: dipjyoti.saikia@gmail.com From: "M. Warner Losh" In-Reply-To: References: 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: freebsd-hackers@freebsd.org Subject: Re: NMI handlers ?? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 02:53:58 -0000 In message: Dipjyoti Saikia writes: : I am working on IPMI watchdog implementation . The problem that I am : facing is that in case of improper system shutdown or powerfail the : watchdog keeps running and the next time system boots up , BIOS : complains of FRB2 timeout and fails one of the CPU's ( Working on SMP : system ) . : : My idea is to handle NMI generated by abruptly pushing power button : and disabling the timer in the routine. : : Can we have a handlers for NMI ?? I am not very sure what is happening : inside the kernel when NMI is delivered . : : Please provide me some inputs. We did this at timing solutions. Here are a few notes: (1) You must disable the F00F_HACK with the kernel config file. (2) We had to hack the nmi code to allow multiple refiring of the nmi routine in the chipset. These hacks are evidentially fairly chipset specific. We were using the #IOCHK line on the ISA bus to accomplish this. I don't think that you'll need to worry about this. (3) You need some kind of NMI handler. You can do almost nothing in this handler. The following code is from 4.x. nmiReset is set elsewhere. #include /* miscellaneous macros */ #include /* CPP macros */ /* XXX: not very portable! */ #define KDSEL 0x10 /* kernel data selector */ .text ALIGN_TEXT .globl Xtscnmidrv Xtscnmidrv: pushl %eax pushl %ecx pushl %edx pushl %ds movl $KDSEL, %eax movl %eax, %ds /* read the timestamp counter */ .byte 0x0f, 0x31 /* RDTSC */ movl %edx, tsHi movl %eax, tsLo /* update the counter */ incl nmiCounter /* * XXX: It is necessary to drop the NMI level on the driving * card at this point IF we wish to use 'NMI_CREATE_EDGE' */ .globl nmiReset movl nmiReset, %eax testl %eax, %eax /* XXX: we should really just permanently disable NMIs in this case */ je skip call *%eax skip: /* diddle the IOCHK# NMI registers */ inb $0x61, %al /* current PORT-B contents */ /* XXX: need to test source bits, assume IOCHK# for now... */ andb $0x0f, %al /* PIIX wants upper bits 0 on write */ orb $0x08, %al /* IOCHK# high to clear */ outb %al, $0x61 andb $0x07, %al /* IOCHK# low to enable */ outb %al, $0x61 /* restore registers */ popl %ds popl %edx popl %ecx popl %eax iret .data ALIGN_DATA .globl nmiCounter nmiCounter: .long 0 .globl timeStamp timeStamp: tsLo: .long 0 tsHi: .long 0 4) We have to establish the handler: /* Install the custom TSC NMI handler. */ setidt( 2, &IDTVEC(tscnmidrv), SDT_SYS386IGT, SEL_KPL, GSEL(GCODE_SEL, SEL_KPL) ); and set nmiReset when you arm the nmi source and clear it if you ever disarm it. nmiReset should be set to the function you want to call. I'm not sure what the right sequence of inb/outb is for your chipset... Warner From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 02:54:05 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C4F416A442; Sun, 5 Jun 2005 02:54:05 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (berlin-qwest.village.org [168.103.84.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C61243D55; Sun, 5 Jun 2005 02:54:04 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j552rJmS057165; Sat, 4 Jun 2005 20:53:20 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 04 Jun 2005 20:54:06 -0600 (MDT) Message-Id: <20050604.205406.98086467.imp@bsdimp.com> To: omestre@freeshell.org From: "M. Warner Losh" In-Reply-To: <20050603195256.GE2065@pro-pae-5513.procergs.reders> References: <20050603195256.GE2065@pro-pae-5513.procergs.reders> 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: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: USB CDC ACM X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 02:54:05 -0000 I beleive that umodem implements the usb cdc acm interface. Warner From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 05:35:22 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A305316A41C for ; Sun, 5 Jun 2005 05:35:22 +0000 (GMT) (envelope-from fbsd.hackers@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4904B43D4C for ; Sun, 5 Jun 2005 05:35:22 +0000 (GMT) (envelope-from fbsd.hackers@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so1463355rne for ; Sat, 04 Jun 2005 22:35:21 -0700 (PDT) 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:content-disposition:references; b=AxXWOOdc+f9xbVTsZTNlvDWdOrBRfEC1BvnUJkrUqIFLUW0WYKZ6IbKFr2Yf78cb9YpzDTNCsdBd/7skc5e1HIZ+9/UdP7zQTfuevn6m85BwFwsaPYnfKgXSpP8hn0JXwcH3DHfkq5lBABrHxs38IIkA9EkUa735f+HHDwX637I= Received: by 10.38.137.4 with SMTP id k4mr158395rnd; Sat, 04 Jun 2005 22:35:21 -0700 (PDT) Received: by 10.38.11.11 with HTTP; Sat, 4 Jun 2005 22:35:21 -0700 (PDT) Message-ID: Date: Sun, 5 Jun 2005 01:35:21 -0400 From: Pablo Mora To: Victor Balada Diaz , freebsd-hackers@freebsd.org In-Reply-To: <20050604181730.GB49520@pato.euesrg02.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050604181730.GB49520@pato.euesrg02.net> Cc: Subject: Re: help me with C languaje please, re: files. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pablo Mora List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 05:35:22 -0000 #include #include int main(void) { FILE *p_to_f; char buf[1024]; int i, j =3D 0; p_to_f =3D fopen("test","r"); if(p_to_f =3D=3D NULL) { perror("fopen"); exit(EXIT_FAILURE); } for(i =3D 0; i < 4 && !feof(p_to_f); i++) { fgets(buf,1024,p_to_f); printf("%s", buf); } fclose(p_to_f); return 0; } I expect that be well what I did. Thanks Victor. PD Corrigeme Si hay algo malo. :D --=20 Concepci=F3n, Chile. From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 11:32:13 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAEC216A41C for ; Sun, 5 Jun 2005 11:32:13 +0000 (GMT) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp809.mail.ukl.yahoo.com (smtp809.mail.ukl.yahoo.com [217.12.12.199]) by mx1.FreeBSD.org (Postfix) with SMTP id DC1BF43D48 for ; Sun, 5 Jun 2005 11:32:12 +0000 (GMT) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 28027 invoked from network); 5 Jun 2005 11:32:11 -0000 Received: from unknown (HELO w2fzz0vc01.aah-go-on.com) (thomas.sparrevohn@hg1.btinternet.com@81.157.123.116 with plain) by smtp809.mail.ukl.yahoo.com with SMTP; 5 Jun 2005 11:32:09 -0000 From: Thomas Sparrevohn To: freebsd-hackers@freebsd.org Date: Sun, 5 Jun 2005 12:31:57 +0100 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_tKuoCrLaLn4cyIl" Message-Id: <200506051231.57725.Thomas.Sparrevohn@btinternet.com> Subject: Debugging UMA allocation X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Thomas.Sparrevohn@btinternet.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 11:32:13 -0000 --Boundary-00=_tKuoCrLaLn4cyIl Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi One of the changes introduced after the 27/05 causes a panic in the initial boot phases in the The panic occurs on my Dell Lattitude C640 when using both my own kernel and the GENERIC kernel. The panic is _mtx_lock_sleep: Recursed on non-recursive mutex in system map I have traced the trigger panic to the first call to uma_zcreate in procinit called from proc0_init - I have just cvs-supped again but the error is still there Unfortunately because it happend before anything is up and running I have no way of producing a kernel dump and as the problem does not seem to be widely reported I assume it is specific to this Dell Laptop type The dmesg included are provided as reference only for the last good compilation of the that I know off e.g. the kernel I know that boots - I have been trying for about 2-3 days which should narrow down the time Can anybody give any advise on how to progress? --Boundary-00=_tKuoCrLaLn4cyIl Content-Type: text/plain; charset="us-ascii"; name="acpidump.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="acpidump.txt" /* RSD PTR: OEM=DELL, ACPI_Rev=1.0x (0) RSDT=0x000fde64, cksum=47 */ /* RSDT: Length=40, Revision=1, Checksum=165, OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d4010c, Creator ID=ASL, Creator Revision=0x61 Entries={ 0x000fde90 } */ /* FACP: Length=116, Revision=1, Checksum=188, OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d4010c, Creator ID=ASL, Creator Revision=0x61 FACS=0x3ffff800, DSDT=0xfffe4000 INT_MODEL=PIC Preferred_PM_Profile=Unspecified (0) SCI_INT=9 SMI_CMD=0xb2, ACPI_ENABLE=0x70, ACPI_DISABLE=0x71, S4BIOS_REQ=0x97 PSTATE_CNT=0x80 PM1a_EVT_BLK=0x800-0x803 PM1a_CNT_BLK=0x804-0x805 PM2_CNT_BLK=0x820-0x820 PM_TMR_BLK=0x808-0x80b GPE0_BLK=0x828-0x82b GPE1_BLK=0x82c-0x82f, GPE1_BASE=16 P_LVL2_LAT=50 us, P_LVL3_LAT=2000 us FLUSH_SIZE=0, FLUSH_STRIDE=0 DUTY_OFFSET=1, DUTY_WIDTH=3 DAY_ALRM=0, MON_ALRM=0, CENTURY=0 IAPC_BOOT_ARCH= Flags={WBINVD,PROC_C1,PWR_BUTTON,SLP_BUTTON,DCK_CAP} */ /* FACS: Length=64, HwSig=0x000000ff, Firm_Wake_Vec=0x00000000 Global_Lock= Flags=S4BIOS Version=0 */ /* DSDT: Length=12700, Revision=1, Checksum=38, OEMID=INT430, OEM Table ID=SYSFexxx, OEM Revision=0x1001, Creator ID=MSFT, Creator Revision=0x100000e */ --Boundary-00=_tKuoCrLaLn4cyIl Content-Type: text/plain; charset="us-ascii"; name="dmesg.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg.txt" 0 255 N 0 9 10 11 pci_link1: irq 11 on acpi0 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 5 7 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 pci_link2: irq 11 on acpi0 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 9 10 11 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 9 10 11 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 9 10 11 pci_link3: irq 11 on acpi0 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 5 7 9 10 11 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 5 7 9 10 11 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 5 7 9 10 11 ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) cpu0: port 0x530-0x537 on acpi0 acpi_perf0: on cpu0 acpi_throttle0: on cpu0 acpi_throttle0: P_CNT from P_BLK 0x8e0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x8086, dev=0x1a30, revid=0x04 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 3, range 32, base e8000000, size 26, enabled found-> vendor=0x8086, dev=0x1a31, revid=0x04 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x0e (3500 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x2482, revid=0x02 bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[20]: type 4, range 32, base 0000bf80, size 5, enabled pcib0: matched entry for 0.29.INTA (src \\_SB_.PCI0.LNKA:0) pcib0: slot 29 INTA routed to irq 11 via \\_SB_.PCI0.LNKA found-> vendor=0x8086, dev=0x2484, revid=0x02 bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 map[20]: type 4, range 32, base 0000bf40, size 5, enabled pcib0: matched entry for 0.29.INTB (src \\_SB_.PCI0.LNKD:0) pcib0: slot 29 INTB routed to irq 11 via \\_SB_.PCI0.LNKD found-> vendor=0x8086, dev=0x2487, revid=0x02 bus=0, slot=29, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=11 map[20]: type 4, range 32, base 0000bf20, size 5, enabled pcib0: matched entry for 0.29.INTC (src \\_SB_.PCI0.LNKC:0) pcib0: slot 29 INTC routed to irq 11 via \\_SB_.PCI0.LNKC found-> vendor=0x8086, dev=0x2448, revid=0x42 bus=0, slot=30, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x06 (1500 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x248c, revid=0x02 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x010f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x248a, revid=0x02 bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[20]: type 4, range 32, base 0000bfa0, size 4, enabled map[24]: type 1, range 32, base 00000000, size 10, memory disabled found-> vendor=0x8086, dev=0x2485, revid=0x02 bus=0, slot=31, func=5 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 map[10]: type 4, range 32, base 0000d800, size 8, enabled map[14]: type 4, range 32, base 0000dc40, size 6, enabled pcib0: matched entry for 0.31.INTB (src \\_SB_.PCI0.LNKB:0) pci_link1: Picked IRQ 9 with weight 0 pcib0: slot 31 INTB routed to irq 9 via \\_SB_.PCI0.LNKB found-> vendor=0x8086, dev=0x2486, revid=0x02 bus=0, slot=31, func=6 class=07-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 map[10]: type 4, range 32, base 0000d400, size 8, enabled map[14]: type 4, range 32, base 0000d080, size 7, enabled pcib0: matched entry for 0.31.INTB (src \\_SB_.PCI0.LNKB:0) pcib0: slot 31 INTB routed to irq 9 via \\_SB_.PCI0.LNKB agp0: mem 0xe8000000-0xebffffff at device 0.0 on pci0 agp0: Reserved 0x4000000 bytes for rid 0x10 type 3 at 0xe8000000 agp0: allocating GATT for aperture of size 64M pcib1: at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xc000-0xcfff pcib1: memory decode 0xfc000000-0xfdffffff pcib1: prefetched decode 0xe0000000-0xe7ffffff pci1: on pcib1 pci1: physical bus=1 found-> vendor=0x1002, dev=0x4c57, revid=0x00 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x01a7, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 3, range 32, base e0000000, size 27, enabled pcib1: (null) requested memory range 0xe0000000-0xe7ffffff: good map[14]: type 4, range 32, base 0000c000, size 8, enabled pcib1: (null) requested I/O range 0xc000-0xc0ff: in range map[18]: type 1, range 32, base fcff0000, size 16, enabled pcib1: (null) requested memory range 0xfcff0000-0xfcffffff: good pcib1: matched entry for 1.0.INTA (src \\_SB_.PCI0.LNKA:0) pcib1: slot 0 INTA routed to irq 11 via \\_SB_.PCI0.LNKA pci1: at device 0.0 (no driver attached) uhci0: port 0xbf80-0xbf9f irq 11 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xbf80 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 0xbf40-0xbf5f irq 11 at device 29.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xbf40 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 0xbf20-0xbf3f irq 11 at device 29.2 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0xbf20 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 pcib2: at device 30.0 on pci0 pcib2: secondary bus 2 pcib2: subordinate bus 16 pcib2: I/O decode 0xe000-0xffff pcib2: memory decode 0xf4000000-0xfbffffff pcib2: prefetched decode 0xfff00000-0xfffff pcib2: Subtractively decoded bridge. pci2: on pcib2 pci2: physical bus=2 found-> vendor=0x10b7, dev=0x9200, revid=0x78 bus=2, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x0a (2500 ns), maxlat=0x0a (2500 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000ec80, size 7, enabled pcib2: (null) requested I/O range 0xec80-0xecff: in range map[14]: type 1, range 32, base f8fffc00, size 7, enabled pcib2: (null) requested memory range 0xf8fffc00-0xf8fffc7f: good pcib2: matched entry for 2.0.INTA (src \\_SB_.PCI0.LNKC:0) pcib2: slot 0 INTA routed to irq 11 via \\_SB_.PCI0.LNKC found-> vendor=0x104c, dev=0xac51, revid=0x00 bus=2, slot=1, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0000, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x40 (16000 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base 00000000, size 12, memory disabled found-> vendor=0x104c, dev=0xac51, revid=0x00 bus=2, slot=1, func=1 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0000, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x40 (16000 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base 00000000, size 12, memory disabled found-> vendor=0x104c, dev=0xac50, revid=0x01 bus=2, slot=3, func=0 class=06-07-00, hdrtype=0x02, mfdev=0 cmdreg=0x0007, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x40 (16000 ns), maxlat=0x03 (750 ns) intpin=a, irq=11 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base 00000000, size 12, enabled pcib2: matched entry for 2.3.INTA (src \\_SB_.PCI0.LNKB:0) pcib2: slot 3 INTA routed to irq 9 via \\_SB_.PCI0.LNKB found-> vendor=0x10b7, dev=0x9200, revid=0x78 bus=2, slot=8, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x0a (2500 ns), maxlat=0x0a (2500 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000ec00, size 7, enabled pcib2: (null) requested I/O range 0xec00-0xec7f: in range map[14]: type 1, range 32, base f8fff800, size 7, enabled pcib2: (null) requested memory range 0xf8fff800-0xf8fff87f: good pcib2: matched entry for 2.8.INTA (src \\_SB_.PCI0.LNKC:0) pcib2: slot 8 INTA routed to irq 11 via \\_SB_.PCI0.LNKC xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xec80-0xecff mem 0xf8fffc00-0xf8fffc7f irq 11 at device 0.0 on pci2 xl0: Reserved 0x80 bytes for rid 0x14 type 3 at 0xf8fffc00 xl0: using memory mapped I/O xl0: media options word: a xl0: found MII/AUTO miibus0: on xl0 ukphy0: on miibus0 ukphy0: OUI 0x00105a, model 0x0000, rev. 0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: bpf attached xl0: Ethernet address: 00:0b:db:07:25:10 xl0: [MPSAFE] cbb0: at device 1.0 on pci2 pcib2: cbb0 requested memory range 0xf4000000-0xfbffffff: good cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xf4000000 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib2: matched entry for 2.1.INTA (src \\_SB_.PCI0.LNKD:0) pcib2: slot 1 INTA routed to irq 11 via \\_SB_.PCI0.LNKD cbb0: [MPSAFE] cbb0: PCI Configuration space: 0x00: 0xac51104c 0x02100007 0x06070000 0x00822008 0x10: 0xf4000000 0x020000a0 0x20040400 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x0740010b 0x40: 0x012a1028 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x2024d025 0x00000000 0x00000000 0x01261222 0x90: 0x6064a6c0 0x00000000 0x00000000 0x00000000 0xa0: 0xfe110001 0x00c00000 0x00000000 0x00000017 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 cbb1: at device 1.1 on pci2 pcib2: cbb1 requested memory range 0xf4000000-0xfbffffff: good cbb1: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xf4001000 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pcib2: matched entry for 2.1.INTA (src \\_SB_.PCI0.LNKD:0) pcib2: slot 1 INTA routed to irq 11 via \\_SB_.PCI0.LNKD cbb1: [MPSAFE] cbb1: PCI Configuration space: 0x00: 0xac51104c 0x02100007 0x06070000 0x00822008 0x10: 0xf4001000 0x020000a0 0x20050500 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x0740010b 0x40: 0x012a1028 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x2024d025 0x00000000 0x00000000 0x01261222 0x90: 0x6064a6c0 0x00000000 0x00000000 0x00000000 0xa0: 0xfe110001 0x00c00000 0x00000000 0x00000017 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 cbb2: irq 9 at device 3.0 on pci2 pcib2: cbb2 requested memory range 0xf4000000-0xfbffffff: good cbb2: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0xf4002000 cardbus2: on cbb2 pccard2: <16-bit PCCard bus> on cbb2 cbb2: [MPSAFE] cbb2: PCI Configuration space: 0x00: 0xac50104c 0x02100007 0x06070001 0x00022008 0x10: 0xf4002000 0x020000a0 0x20040302 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x07400109 0x40: 0xab0112a3 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x0044b060 0x00000000 0x00000000 0x01000002 0x90: 0x616000c0 0x00000000 0x00000000 0x00000000 0xa0: 0xfe110001 0x00c00000 0x0000000f 0x0000001b 0xb0: 0x08000000 0x00000000 0x00000000 0x00000000 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 xl1: <3Com 3c905C-TX Fast Etherlink XL> port 0xec00-0xec7f mem 0xf8fff800-0xf8fff87f irq 11 at device 8.0 on pci2 xl1: Reserved 0x80 bytes for rid 0x14 type 3 at 0xf8fff800 xl1: using memory mapped I/O xl1: media options word: a xl1: found MII/AUTO miibus1: on xl1 ukphy1: on miibus1 ukphy1: OUI 0x00105a, model 0x0000, rev. 0 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: bpf attached xl1: Ethernet address: 00:0b:db:21:b7:c6 xl1: [MPSAFE] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xbfa0 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ata1: [MPSAFE] pcm0: port 0xd800-0xd8ff,0xdc40-0xdc7f irq 9 at device 31.5 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xd800 pcm0: Reserved 0x40 bytes for rid 0x14 type 4 at 0xdc40 pcm0: [GIANT-LOCKED] pcm0: pcm0: Codec features mic channel, tone, simulated stereo, bass boost, 20 bit DAC, 18 bit ADC, 5 bit master volume, SRS 3D Stereo Enhancement pcm0: Primary codec extended features variable rate PCM, variable rate mic, AMAP pcm0: sndbuf_setmap 3e9eb000, 4000; 0xe90fc000 -> 3e9eb000 pcm0: sndbuf_setmap 3e9e6000, 4000; 0xe9100000 -> 3e9e6000 pcm0: sndbuf_setmap 3e9da000, 4000; 0xe9104000 -> 3e9da000 pci0: at device 31.6 (no driver attached) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) acpi_tz0: port 0x530-0x537 on acpi0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) psmcpnp0: irq 12 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: current command byte:0065 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000008, packet size:3 psm0: syncmask:c0, syncbits:00 fdc0: port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 fdc0: [MPSAFE] fdc0: [FAST] sio0: irq maps: 0x1 0x11 0x1 0x1 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 port 0x2f8-0x2ff,0x280-0x287 irq 3 drq 3 on acpi0 sio1: type 16550A ppc0: using extended I/O port range ppc0: ECP SPP ECP+EPP SPP ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 1 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_probe: no address given, try 0x530 mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) mss_detect, busy still set (0xff) ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it fdc: fdc0 already exists; skipping it ppc: ppc0 already exists; skipping it sio: sio0 already exists; skipping it sio: sio1 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcefff,0xcf000-0xcf7ff,0xcf800-0xcffff on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fe0: not probed (disabled) ie0: not probed (disabled) lnc0: not probed (disabled) sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 vt0: not probed (disabled) isa_probe_children: probing PnP devices uhub3: vendor 0x0451 General Purpose USB Hub, class 9/0, rev 1.10/1.01, addr 2 uhub3: 2 ports with 0 removable, bus powered ukbd0: Logitech USB Receiver, rev 1.10/24.04, addr 3, iclass 3/1 kbd: new array size 4 kbd1 at ukbd0 kbd1: ukbd0, generic (0), config:0x0, flags:0x1d0000 ums0: Logitech USB Receiver, rev 1.10/24.04, addr 3, iclass 3/1 ums0: 7 buttons and Z dir. uhub4: vendor 0x050d product 0x0237, class 9/0, rev 2.00/1.00, addr 2 uhub4: 7 ports with 7 removable, self powered ugen0: LEGO Group LEGO USB Tower, rev 1.10/1.00, addr 3 umass0: LEXR PLUG DRIVE LEXR PLUG DRIVE, rev 1.10/0.01, addr 4 umass0:0:0:-1: Attached to scbus0 umass1: Generic Mass Storage Device, rev 1.10/1.00, addr 5 umass1: Get Max Lun not supported (STALLED) umass1:1:1:-1: Attached to scbus1 Device configuration finished. procfs registered Timecounter "TSC" frequency 1794712884 Hz quality 800 Timecounters tick every 1.000 msec lo0: bpf attached acpi_acad0: acline initialization start acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times acpi_cmbat0: battery initialization start acpi_cmbat1: battery initialization start fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout fdc0: output ready timeout ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire ad0: setting PIO4 on Intel ICH3 chip ad0: setting UDMA100 on Intel ICH3 chip ad0: 38154MB at ata0-master UDMA100 ad0: 78140160 sectors [77520C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad0 pcib2: pccard2 requested memory range 0xf4000000-0xfbffffff: good pccard2: CIS version PC Card Standard 5.0 pccard2: CIS info: Dell, TrueMobile 1150 Series PC Card, Version 01.01, pccard2: Manufacturer code 0x156, product 0x2 pccard2: function 0: network adapter, ccr addr 3e0 mask 1 pccard2: function 0, config table entry 1: I/O card; irq mask ffff; iomask 6, iospace 0-3f; io16 irqpulse irqlevel pcib2: pccard2 requested I/O range 0xe000-0xffff: in range pcib2: pccard2 requested memory range 0xf4000000-0xfbffffff: good wi0: at port 0xe000-0xe03f irq 9 function 0 config 1 on pccard2 wi0: [MPSAFE] wi0: using Lucent Embedded WaveLAN/IEEE wi0: Lucent Firmware: Station (8.10.1) wi0: bpf attached wi0: Ethernet address: 00:02:2d:7b:df:c4 wi0: bpf attached wi0: bpf attached wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout fdc0: output ready timeout fdc0: input ready timeout fdc0: input ready timeout ad0: Intel check1 failed ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed ad0: FreeBSD check1 failed ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting PIO4 on Intel ICH3 chip acd0: setting UDMA33 on Intel ICH3 chip acd0: CDRW drive at ata1 as master acd0: 2048KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: CDR, CDRW, test write, burnproof acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc pcm0: measured ac97 link rate at 48001 Hz, will use 48000 Hz pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Removable Direct Access SCSI-2 device pass0: Serial Number [ pass0: 1.000MB/s transfers pass1 at umass-sim1 bus 1 target 0 lun 0 pass1: Removable Direct Access SCSI-2 device pass1: Serial Number \^_ pass1: 1.000MB/s transfers ATA PseudoRAID loaded da1 at umass-sim1 bus 1 target 0 lun 0 da1: Removable Direct Access SCSI-2 device da1: Serial Number \^_ da1: 1.000MB/s transfers da1: 125MB (256000 512 byte sectors: 64H 32S/T 125C) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: Serial Number [ da0: 1.000MB/s transfers da0: 61MB (125952 512 byte sectors: 64H 32S/T 61C) GEOM: new disk da0 GEOM: new disk da1 acpi_cmbat0: battery initialization done, tried 1 times Trying to mount root from ufs:/dev/ad0s1a start_init: trying /sbin/init Linux ELF exec handler installed linprocfs registered splash: image decoder found: daemon_saver acpi_cmbat1: battery initialization failed, giving up pci0: driver added found-> vendor=0x8086, dev=0x2486, revid=0x02 bus=0, slot=31, func=6 class=07-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=9 pci0:31:6: reprobing on driver added pci1: driver added found-> vendor=0x1002, dev=0x4c57, revid=0x00 bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x01a7, statreg=0x02b0, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 pci1:0:0: reprobing on driver added drm0: port 0xc000-0xc0ff mem 0xe0000000-0xe7ffffff,0xfcff0000-0xfcffffff irq 11 at device 0.0 on pci1 drm0: Reserved 0x10000 bytes for rid 0x18 type 3 at 0xfcff0000 pcib1: drm0 requested memory range 0xfcff0000-0xfcffffff: good pcib1: drm0 requested memory range 0xfcff0000-0xfcffffff: good drm0: Reserved 0x8000000 bytes for rid 0x10 type 3 at 0xe0000000 pcib1: drm0 requested memory range 0xe0000000-0xe7ffffff: good pcib1: drm0 requested memory range 0xe0000000-0xe7ffffff: good info: [drm] AGP at 0xe8000000 64MB info: [drm] Initialized radeon 1.16.0 20050311 on minor 0 pci2: driver added agp0: Setting AGP v2 mode 1 drm0: [MPSAFE] --Boundary-00=_tKuoCrLaLn4cyIl Content-Type: text/plain; charset="us-ascii"; name="dmidecode.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmidecode.txt" # dmidecode 2.6 SMBIOS 2.3 present. 61 structures occupying 2338 bytes. Table at 0x000F76A0. Handle 0xDA00 DMI type 218, 203 bytes. OEM-specific Type Header and Data: DA CB 00 DA B2 00 0D 1F 0F 17 40 6F 00 00 00 01 00 70 00 00 00 00 00 71 00 02 00 01 00 72 00 02 00 00 00 7B 00 04 00 00 00 7C 00 06 00 00 00 79 00 08 00 00 00 7D 00 0A 00 00 00 7E 00 0C 00 00 00 78 00 0E 00 01 00 77 00 0E 00 00 00 73 00 10 00 01 00 74 00 10 00 00 00 7A 00 11 00 00 00 7F 00 12 00 00 00 40 00 13 00 01 00 41 00 13 00 00 00 1E 00 14 00 00 00 1F 00 14 00 01 00 20 00 14 00 02 00 21 00 14 00 03 00 75 00 15 00 01 00 76 00 15 00 00 00 00 80 00 80 00 00 00 A0 00 A0 01 00 05 80 05 80 01 00 01 F0 01 F0 00 00 02 F0 02 F0 00 00 03 F0 03 F0 00 00 04 F0 04 F0 00 00 05 F0 05 F0 00 00 FF FF 00 00 00 00 Handle 0x0000 DMI type 0, 20 bytes. BIOS Information Vendor: Dell Computer Corporation Version: A10 Release Date: 01/12/2004 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 512 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported PNP is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported Boot from PC Card (PCMCIA) is supported 3.5"/720 KB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported AGP is supported LS-120 boot is supported ATAPI Zip drive boot is supported Smart battery is supported BIOS boot specification is supported Handle 0x0100 DMI type 1, 25 bytes. System Information Manufacturer: Dell Computer Corporation Product Name: Latitude C640 Version: Not Specified Serial Number: 3V54Q0J UUID: 44454C4C-5600-1035-8034-B3C04F51304A Wake-up Type: Power Switch Handle 0x0200 DMI type 2, 9 bytes. Base Board Information Manufacturer: Dell Computer Corporation Product Name: Version: Serial Number: .3V54Q0J. . Handle 0x0300 DMI type 3, 13 bytes. Chassis Information Manufacturer: Dell Computer Corporation Type: Portable Lock: Not Present Version: Not Specified Serial Number: 3V54Q0J Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None Handle 0x0301 DMI type 3, 13 bytes. Chassis Information Manufacturer: Dell Computer Corporation Type: Docking Station Lock: Not Present Version: Not Specified Serial Number: 00C0ADADADAD Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None Handle 0x0400 DMI type 4, 32 bytes. Processor Information Socket Designation: Microprocessor Type: Central Processor Family: Pentium 4 Manufacturer: Intel ID: 27 0F 00 00 FF F9 EB BF Signature: Type 0, Family 15, Model 2, Stepping 7 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Hyper-threading technology) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Not Specified Voltage: 3.3 V External Clock: 133 MHz Max Speed: 2400 MHz Current Speed: 1800 MHz Status: Populated, Enabled Upgrade: None L1 Cache Handle: 0x0700 L2 Cache Handle: 0x0701 L3 Cache Handle: Not Provided Handle 0x0700 DMI type 7, 19 bytes. Cache Information Socket Designation: Not Specified Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 8 KB Maximum Size: 8 KB Supported SRAM Types: Unknown Installed SRAM Type: Unknown Speed: Unknown Error Correction Type: None System Type: Data Associativity: 4-way Set-associative Handle 0x0701 DMI type 7, 19 bytes. Cache Information Socket Designation: Not Specified Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Varies With Memory Address Location: Internal Installed Size: 512 KB Maximum Size: 512 KB Supported SRAM Types: Pipeline Burst Installed SRAM Type: Pipeline Burst Speed: 15 ns Error Correction Type: None System Type: Unified Associativity: Other Handle 0x0800 DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: PARALLEL Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: DB-25 female Port Type: Parallel Port PS/2 Handle 0x0801 DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: SERIAL1 Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: DB-9 male Port Type: Serial Port 16550A Compatible Handle 0x0802 DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: PS/2 Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: Mini DIN Port Type: Mouse Port Handle 0x0803 DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: PS/2 Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: Mini DIN Port Type: Mouse Port Handle 0x0804 DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: USB Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0805 DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: USB Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: Access Bus (USB) Port Type: USB Handle 0x0806 DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: MONITOR Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: DB-15 female Port Type: Video Port Handle 0x0807 DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: ENET Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: RJ-45 Port Type: Network Port Handle 0x0808 DMI type 126, 9 bytes. Inactive Handle 0x0809 DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: IrDA Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: Infrared Port Type: Other Handle 0x080A DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: S-Video Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: Mini DIN Port Type: Video Port Handle 0x080C DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: Modem Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: RJ-11 Port Type: Modem Port Handle 0x080D DMI type 8, 9 bytes. Port Connector Information Internal Reference Designator: Ethernet Internal Connector Type: None External Reference Designator: Not Specified External Connector Type: RJ-45 Port Type: Network Port Handle 0x0900 DMI type 9, 13 bytes. System Slot Information Designation: PCMCIA 0 Type: 32-bit PC Card (PCMCIA) Current Usage: Available Length: Other ID: Adapter 0, Socket 0 Characteristics: 5.0 V is provided 3.3 V is provided PC Card-16 is supported Cardbus is supported Zoom Video is supported Modem ring resume is supported Handle 0x0901 DMI type 9, 13 bytes. System Slot Information Designation: PCMCIA 1 Type: 32-bit PC Card (PCMCIA) Current Usage: Available Length: Other ID: Adapter 10, Socket 0 Characteristics: 5.0 V is provided 3.3 V is provided PC Card-16 is supported Cardbus is supported Modem ring resume is supported Handle 0x0902 DMI type 126, 13 bytes. Inactive Handle 0x0903 DMI type 126, 13 bytes. Inactive Handle 0x0904 DMI type 9, 13 bytes. System Slot Information Designation: MiniPCI Type: 32-bit Other Current Usage: Available Length: Other Characteristics: 5.0 V is provided 3.3 V is provided PME signal is supported Handle 0x0A00 DMI type 10, 6 bytes. On Board Device Information Type: Video Status: Enabled Description: ATI Mobility M7 Handle 0x0A01 DMI type 10, 6 bytes. On Board Device Information Type: Sound Status: Enabled Description: Crystal 4205 Handle 0x0A02 DMI type 10, 6 bytes. On Board Device Information Type: Ethernet Status: Enabled Description: Handle 0x0A03 DMI type 126, 6 bytes. Inactive Handle 0x0B00 DMI type 11, 5 bytes. OEM Strings String 1: Dell System String 2: 5[0593] Handle 0x0D00 DMI type 13, 22 bytes. BIOS Language Information Installable Languages: 1 en|US|iso8859-1 Currently Installed Language: en|US|iso8859-1 Handle 0x1000 DMI type 16, 15 bytes. Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 1 GB Error Information Handle: Not Provided Number Of Devices: 2 Handle 0x1100 DMI type 17, 27 bytes. Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 512 MB Form Factor: DIMM Set: None Locator: DIMM_A Bank Locator: Not Specified Type: DDR Type Detail: Synchronous Speed: 266 MHz (3.8 ns) Manufacturer: Not Specified Serial Number: Not Specified Asset Tag: Not Specified Part Number: Handle 0x1101 DMI type 17, 27 bytes. Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: 64 bits Data Width: 64 bits Size: 512 MB Form Factor: DIMM Set: None Locator: DIMM_B Bank Locator: Not Specified Type: DDR Type Detail: Synchronous Speed: 266 MHz (3.8 ns) Manufacturer: Not Specified Serial Number: Not Specified Asset Tag: Not Specified Part Number: Handle 0x1300 DMI type 19, 15 bytes. Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x0000009FFFF Range Size: 640 kB Physical Array Handle: 0x1000 Partition Width: 0 Handle 0x1301 DMI type 19, 15 bytes. Memory Array Mapped Address Starting Address: 0x00000100000 Ending Address: 0x0003FFFFFFF Range Size: 1023 MB Physical Array Handle: 0x1000 Partition Width: 0 Handle 0x1400 DMI type 20, 19 bytes. Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x0000009FFFF Range Size: 640 kB Physical Device Handle: 0x1100 Memory Array Mapped Address Handle: 0x1300 Partition Row Position: 1 Handle 0x1401 DMI type 20, 19 bytes. Memory Device Mapped Address Starting Address: 0x00000100000 Ending Address: 0x0001FFFFFFF Range Size: 511 MB Physical Device Handle: 0x1100 Memory Array Mapped Address Handle: 0x1301 Partition Row Position: 1 Handle 0x1402 DMI type 20, 19 bytes. Memory Device Mapped Address Starting Address: 0x00020000000 Ending Address: 0x0003FFFFFFF Range Size: 512 MB Physical Device Handle: 0x1101 Memory Array Mapped Address Handle: 0x1301 Partition Row Position: 1 Handle 0x1500 DMI type 21, 7 bytes. Built-in Pointing Device Type: Touch Pad Interface: Bus Mouse Buttons: 2 Handle 0x1600 DMI type 22, 26 bytes. Portable Battery Location: Left Module Bay Manufacturer: Sony Corp. Name: LIP8120DLP Design Capacity: 65120 mWh Design Voltage: 14800 mV SBDS Version: 1.0 Maximum Error: 30% SBDS Serial Number: AAC1 SBDS Manufacture Date: 2003-04-03 SBDS Chemistry: LION OEM-specific Information: 0x00000001 Handle 0x1601 DMI type 126, 26 bytes. Inactive Handle 0x1B00 DMI type 27, 12 bytes. Cooling Device Type: Fan Status: OK OEM-specific Information: 0x0000DD00 Handle 0x1C00 DMI type 28, 20 bytes. Temperature Probe Description: CPU Internal Temperature Location: Processor Status: OK Maximum Value: 127.0 deg C Minimum Value 0.0 deg C Resolution: 1.000 deg C Tolerance: 0.5 deg C Accuracy: Unknown OEM-specific Information: 0x0000DC00 Handle 0x2000 DMI type 32, 11 bytes. System Boot Information Status: No errors detected Handle 0xD000 DMI type 208, 10 bytes. OEM-specific Type Header and Data: D0 0A 00 D0 01 04 FE 00 2A 01 Handle 0xD100 DMI type 209, 12 bytes. OEM-specific Type Header and Data: D1 0C 00 D1 00 00 00 03 04 07 80 05 Handle 0xD200 DMI type 210, 12 bytes. OEM-specific Type Header and Data: D2 0C 00 D2 F8 03 04 03 06 80 04 05 Handle 0xD300 DMI type 211, 13 bytes. OEM-specific Type Header and Data: D3 0D 00 D3 01 03 02 01 00 00 00 00 02 Strings: Back of System Handle 0xD800 DMI type 216, 9 bytes. OEM-specific Type Header and Data: D8 09 00 D8 01 03 01 F0 03 Strings: ATI Technologies Inc. .0 VR006.006.006.00 Handle 0xD900 DMI type 217, 8 bytes. OEM-specific Type Header and Data: D9 08 00 D9 01 02 01 03 Strings: US-101 Proprietary Handle 0xDB00 DMI type 219, 8 bytes. OEM-specific Type Header and Data: DB 08 00 DB 03 01 02 03 Strings: System Device Bay Floppy, Battery, CD-ROM, CD-RW, Hard Disk, LS-120, DVD, ZIP CDRW+DVD Handle 0xDB01 DMI type 126, 8 bytes. Inactive Handle 0xDC00 DMI type 220, 22 bytes. OEM-specific Type Header and Data: DC 16 00 DC 01 F0 00 00 02 F0 00 00 00 00 03 F0 04 F0 00 00 00 00 Handle 0xDD00 DMI type 221, 19 bytes. OEM-specific Type Header and Data: DD 13 00 DD 00 00 00 00 00 05 F0 00 00 00 00 00 00 00 00 Handle 0xD400 DMI type 212, 192 bytes. OEM-specific Type Header and Data: D4 C0 00 D4 70 00 71 00 00 10 2D 2E 5C 00 78 BF 40 5D 00 78 BF 00 5E 00 23 FE 01 5F 00 23 FE 00 60 00 1D EF 10 61 00 1D EF 00 65 00 21 F7 00 66 00 21 F7 08 67 00 25 DF 20 68 00 25 DF 00 1D 00 21 FE 00 1C 00 21 FE 01 0F 00 26 F8 00 11 00 26 F8 01 05 00 26 F8 02 12 00 26 F8 03 06 00 26 F8 04 31 00 26 8F 00 32 00 26 8F 10 33 00 26 8F 20 34 00 26 8F 30 35 00 26 8F 40 07 00 25 F8 00 0B 00 25 F8 01 0C 00 25 F8 02 0D 00 25 F8 04 28 00 23 F3 00 29 00 23 F3 04 2A 00 23 F3 08 2B 00 58 00 00 2C 00 59 00 00 88 00 23 FD 02 89 00 23 FD 00 08 00 1D DF 00 03 00 1D DF 00 FF FF 00 00 00 Handle 0xD401 DMI type 212, 37 bytes. OEM-specific Type Header and Data: D4 25 01 D4 70 00 71 00 03 40 49 4A 42 00 48 7F 80 43 00 48 7F 00 55 00 47 BF 00 6D 00 47 BF 40 FF FF 00 00 00 Handle 0xDE00 DMI type 222, 13 bytes. OEM-specific Type Header and Data: DE 0D 00 DE 01 02 FF FF 00 00 00 00 00 Handle 0x7F00 DMI type 127, 4 bytes. End Of Table --Boundary-00=_tKuoCrLaLn4cyIl Content-Type: text/plain; charset="us-ascii"; name="biosdecode.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="biosdecode.txt" # biosdecode 2.6 SYSID present. Revision: 0 Structure Table Address: 0x000F7661 Number Of Structures: 1 SMBIOS 2.3 present. Structure Table Length: 2338 bytes Structure Table Address: 0x000F76A0 Number Of Structures: 61 Maximum Structure Size: 205 bytes PCI Interrupt Routing 1.0 present. Router ID: 00:1f.0 Exclusive IRQs: None Compatible Router: 8086:1234 Slot Entry 1: ID 00:1d, on-board Slot Entry 2: ID 00:1e, on-board Slot Entry 3: ID 00:1f, on-board Slot Entry 4: ID 01:00, on-board Slot Entry 5: ID 02:00, on-board Slot Entry 6: ID 02:01, on-board Slot Entry 7: ID 02:03, on-board Slot Entry 8: ID 02:08, on-board Slot Entry 9: ID 02:0c, on-board Slot Entry 10: ID 08:00, on-board Slot Entry 11: ID 08:01, on-board ACPI 1.0 present. OEM Identifier: DELL RSD Table 32-bit Address: 0x000FDE64 PNP BIOS 1.0 present. Event Notification: Polling Event Notification Flag Address: 0x000004B4 Real Mode 16-bit Code Address: F000:E2F1 Real Mode 16-bit Data Address: 0040:0000 16-bit Protected Mode Code Address: 0x000FE2F4 16-bit Protected Mode Data Address: 0x00000040 BIOS32 Service Directory present. Revision: 0 Calling Interface Address: 0x000FFE90 --Boundary-00=_tKuoCrLaLn4cyIl Content-Type: text/plain; charset="us-ascii"; name="pciconf-lv.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="pciconf-lv.txt" agp0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x1a308086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82845/E/MP/MZ Brookdale CPU to I/O Bridge' class = bridge subclass = HOST-PCI pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x1a318086 rev=0x04 hdr=0x01 vendor = 'Intel Corporation' device = '82845/E/MP/MZ Brookdale CPU to AGP Bridge' class = bridge subclass = PCI-PCI uhci0@pci0:29:0: class=0x0c0300 card=0x45418086 chip=0x24828086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801CA/CAM (ICH3-S/ICH3-M) USB Controller #1' class = serial bus subclass = USB uhci1@pci0:29:1: class=0x0c0300 card=0x45418086 chip=0x24848086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801CA/CAM (ICH3-S/ICH3-M) USB Controller #2' class = serial bus subclass = USB uhci2@pci0:29:2: class=0x0c0300 card=0x45418086 chip=0x24878086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801CA/CAM (ICH3-S/ICH3-M) USB Controller #3' class = serial bus subclass = USB pcib2@pci0:30:0: class=0x060400 card=0x00000000 chip=0x24488086 rev=0x42 hdr=0x01 vendor = 'Intel Corporation' device = '82801BAM/CAM/DBM (ICH2-M/3-M/4-M) Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:31:0: class=0x060100 card=0x00000000 chip=0x248c8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801CAM LPC Interface or ISA bridge: see Notes' class = bridge subclass = PCI-ISA atapci0@pci0:31:1: class=0x01018a card=0x45418086 chip=0x248a8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801CAM (ICH3-M) UltraATA/100 EIDE Controller' class = mass storage subclass = ATA pcm0@pci0:31:5: class=0x040100 card=0x59591013 chip=0x24858086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801CA/CAM (ICH3-S/ICH3-M) AC'97 Audio Controller' class = multimedia subclass = audio none0@pci0:31:6: class=0x070300 card=0x4c21134d chip=0x24868086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801CA/CAM (ICH3-S/ICH3-M) AC'97 Modem Controller' class = simple comms subclass = generic modem drm0@pci1:0:0: class=0x030000 card=0x012a1028 chip=0x4c571002 rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'fdds Radeon Mobility M7 LW' class = display subclass = VGA xl0@pci2:0:0: class=0x020000 card=0x012a1028 chip=0x920010b7 rev=0x78 hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905C-TX Fast EtherLink for PC Management NIC' class = network subclass = ethernet cbb0@pci2:1:0: class=0x060700 card=0x012a1028 chip=0xac51104c rev=0x00 hdr=0x02 vendor = 'Texas Instruments (TI)' device = 'PCI1420 PC card CardBus Controller' class = bridge subclass = PCI-CardBus cbb1@pci2:1:1: class=0x060700 card=0x012a1028 chip=0xac51104c rev=0x00 hdr=0x02 vendor = 'Texas Instruments (TI)' device = 'PCI1420 PC card CardBus Controller' class = bridge subclass = PCI-CardBus cbb2@pci2:3:0: class=0x060700 card=0xab0112a3 chip=0xac50104c rev=0x01 hdr=0x02 vendor = 'Texas Instruments (TI)' device = 'PCI1410 PC card cardBus Controller' class = bridge subclass = PCI-CardBus xl1@pci2:8:0: class=0x020000 card=0x00a71028 chip=0x920010b7 rev=0x78 hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905C-TX Fast EtherLink for PC Management NIC' class = network subclass = ethernet --Boundary-00=_tKuoCrLaLn4cyIl Content-Type: text/plain; charset="us-ascii"; name="usbdevs.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="usbdevs.txt" Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 addr 2: full speed, power 100 mA, config 1, General Purpose USB Hub(0x2036), vendor 0x0451(0x0451), rev 1.01 port 1 addr 3: low speed, power 98 mA, config 1, USB Receiver(0xc704), Logitech(0x046d), rev 24.04 port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 addr 2: full speed, self powered, config 1, product 0x0237(0x0237), vendor 0x050d(0x050d), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 addr 3: low speed, power 100 mA, config 1, LEGO USB Tower(0x0001), LEGO Group(0x0694), rev 1.00 port 6 addr 4: full speed, power 90 mA, config 1, LEXR PLUG DRIVE(0x0080), LEXR PLUG DRIVE(0x05dc), rev 0.01 port 7 addr 5: full speed, power 100 mA, config 1, Mass Storage Device(0x9385), Generic(0x058f), rev 1.00 --Boundary-00=_tKuoCrLaLn4cyIl Content-Type: text/plain; charset="us-ascii"; name="plugins.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="plugins.txt" Setup your /etc/libmap.conf. - - - - - - - - - - - - - - - - - - - - - - - - - - - - # /etc/libmap.conf for FreeBSD 5.x # $Id: libmap.conf-FreeBSD5.x,v 1.9 2004/08/23 16:26:44 nork Exp $ # Flash6 with Opera is not avilable. # Flash6 with Konqueror # KDE on FreeBSD requires plugins to be placed in /opt/mozilla/plugins/. # (unlike many other www browsers on X11, it does not support # /usr/X11R6/lib/browser_plugins/ for a plugin directory) # So please copy libflashplayer.so and flashplayer.xpt to # /opt/mozilla/plugins like following lines. # mkdir -p /opt/mozilla/plugins # cd /usr/local/lib/linux-flashplugin6 # cp flashplayer.xpt libflashplayer.so /opt/mozilla/plugins/ [/opt/mozilla/plugins/libflashplayer.so] libpthread.so.0 pluginwrapper/flash6.so libdl.so.2 pluginwrapper/flash6.so libz.so.1 libz.so.2 libstdc++-libc6.2-2.so.3 libstdc++.so.4 libm.so.6 libm.so.2 libc.so.6 pluginwrapper/flash6.so # Flash6 with Mozilla/Firebird/Galeon/Epiphany [/usr/local/lib/linux-flashplugin6/libflashplayer.so] libpthread.so.0 pluginwrapper/flash6.so libdl.so.2 pluginwrapper/flash6.so libz.so.1 libz.so.2 libstdc++-libc6.2-2.so.3 libstdc++.so.4 libm.so.6 libm.so.2 libc.so.6 pluginwrapper/flash6.so # Acrobat with Opera [/usr/X11R6/lib/browser_plugins/nppdf.so] libc.so.6 pluginwrapper/acrobat.so # Acrobat with Konqueror # KDE on FreeBSD requires plugins to be placed in /opt/mozilla/plugins/. # (unlike many other www browsers on X11, it does not support # /usr/X11R6/lib/browser_plugins/ for a plugin directory) # So please copy nppdf.so to /opt/mozilla/plugins/ like following lines. # mkdir -p /opt/mozilla/plugins # cd /usr/local/Acrobat5/Browsers/intellinux # cp nppdf.so /opt/mozilla/plugins/ [/opt/mozilla/plugins/nppdf.so] libc.so.6 pluginwrapper/acrobat.so # Acrobat with Mozilla/Firebird/Galeon/Epiphany [/usr/local/Acrobat5/Browsers/intellinux/nppdf.so] libc.so.6 pluginwrapper/acrobat.so # Java3D # NOTE: THESE ARE SAMPLES. PLEASE SEE ALSO INSTALL MESSAGES # OF java/java3d PORT. [/usr/local/jdk1.4.2/jre/lib/i386/libJ3D.so] libdl.so.2 pluginwrapper/java3d.so libm.so.6 libm.so.2 libnsl.so.1 pluginwrapper/java3d.so libpthread.so.0 pluginwrapper/java3d.so libc.so.6 pluginwrapper/java3d.so [/usr/local/jdk1.4.2/jre/lib/i386/libj3daudio.so] libm.so.6 libm.so.2 libnsl.so.1 pluginwrapper/java3d_snd.so libpthread.so.0 pluginwrapper/java3d_snd.so libc.so.6 pluginwrapper/java3d_snd.so [/usr/local/jdk1.4.2/jre/lib/i386/libJ3DUtils.so] libpthread.so.0 pluginwrapper/java3d.so libc.so.6 pluginwrapper/java3d.so # Java Advanced Imaging (JAI) API # NOTE: THIS IS A SAMPLE. PLEASE SEE ALSO INSTALL MESSAGES # OF java/jai PORT. [/usr/local/jdk1.4.2/jre/lib/i386/libmlib_jai/libmlib_jai.so] libm.so.6 libm.so.2 libc.so.6 pluginwrapper/jai.so # JAI Image I/O Tools # NOTE: THIS IS A SAMPLE. PLEASE SEE ALSO INSTALL MESSAGES # OF java/jai-imageio PORT. [/usr/local/jdk1.4.2/jre/lib/i386/libclib_jiio.so] libm.so.6 libm.so.2 libc.so.6 pluginwrapper/jai.so # Photo Image Print System (for EPSON bubble jet printers driver) #[/usr/local/lib/pips/] #libc.so.6 pluginwrapper/pips.so #libdl.so.2 pluginwrapper/pips.so - - - - - - - - - - - - - - - - - - - - - - - - - - - - Now start browser and go to 'about:plugins' and the new plugins are enabled! ===> Registering installation for linuxpluginwrapper-20040831 ===> Cleaning for linuxpluginwrapper-20040831 --Boundary-00=_tKuoCrLaLn4cyIl-- From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 4 22:56:56 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 294DA16A41F for ; Sat, 4 Jun 2005 22:56:56 +0000 (GMT) (envelope-from johnjawed@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EE2243D53 for ; Sat, 4 Jun 2005 22:56:55 +0000 (GMT) (envelope-from johnjawed@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so1357221wri for ; Sat, 04 Jun 2005 15:56:54 -0700 (PDT) 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:references; b=ZXQznbM7DDtLzUTlLT/6/p8PXjBtaaGVYpcE0LG76lrB/NPaoZypJQS3QP7RI5BBtCeAqWL7imUrSq7UAtaQQHab2vCNhCWxw2cd/s9bsEtHcDW49lB0td639E+q9zKjHGFe/597QCgUZnzLJxQAv65XtF1VVdfpIu5qBDcOkoo= Received: by 10.54.150.2 with SMTP id x2mr2233888wrd; Sat, 04 Jun 2005 15:56:54 -0700 (PDT) Received: by 10.54.132.10 with HTTP; Sat, 4 Jun 2005 15:56:54 -0700 (PDT) Message-ID: Date: Sat, 4 Jun 2005 15:56:54 -0700 From: John Jawed To: Scott Long In-Reply-To: <42A11C92.5050505@samsco.org> Mime-Version: 1.0 References: <42A11C92.5050505@samsco.org> X-Mailman-Approved-At: Sun, 05 Jun 2005 12:05:15 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: hackers@freebsd.org, FreeBSD Current Subject: Re: HEADS UP! 6.0 Schedule, 6.0-CURRENT Snapshot X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John Jawed List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2005 22:56:56 -0000 Yes, oh lordie yes. I guess we aren't going to have a new logo in time for= =20 FreeBSD6-RELEASE in August, are we? On 6/3/05, Scott Long wrote: >=20 > All, >=20 > The long anticipated and much feared 6.0 code freeze is about to begin! > I'll cut to the chase: >=20 > June 10 - Feature freeze + code slush > ^^^^^^^ >=20 > July 10 - RELENG_6 branch > August 1 - RELENG_6_0 branch > August 15 - 6.0-RELEASE >=20 > From June 10 until the release, the number one priority is fixing bugs. > All of the dates after June 10 are somewhat fluid and subject to change > depending on where we are with stability. We won't release 6.0 until > it is ready, but I'm pretty confident that we'll have it ready by > August. >=20 > Since SMPVFS is on by default on i386 and amd64, we need as much testing > and bug fixing there as is possible. Jeff has been doing a fantastic > job on this, but I'm sure that more help would be appreciated. Also, > now is the time to start tracking down whatever strange panics or poor > performance anyone might be seeing; the system is pretty stable at the > 80% level, but there are a lot of edge cases that we need to work on > to make it a good release. A stroll through the mailing lists and PR > database would be a good place to start for anyone that wants to help. >=20 > Again, the plan is for 6.0 to be a modest replacement for 5.x. We do > plan on a 5.5 release in September to tie up the branch and help people > move to 6.0/6.1, but 6.x is truly just a much improved 5.x at this > point. For those with bosses who are fainting at the thought of there > being a 7-CURRENT around the corner and 5-STABLE coming to a close, > please keep in mind that migrating from 5.x to 6.x is trivial and is > worthwhile. However, we need to do the branch now so that we can keep > things like SMPVFS under control and produce a high-quality series of > releases with it. For those who have already adopted 5.x and cannot > spend the time/money to migrate again, RELENG_5 will still have secteam > support into at least 2007 (going by their normal formula), and I expect > there to be normal feature and bug-fix commits to it for at least > another year from now. >=20 > To jump-start the testing, I've posted a new set of 6.0-CURRENT > snapshots to ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/Jun_2005. > Once the freeze starts, I expect a new snapshot to be posted every 1-2 > weeks until we get close to the release. So, please help test, report, > and fix bugs! >=20 > Thanks, >=20 > 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= " >=20 --=20 John Jawed From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 06:41:05 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 232F916A41C; Sun, 5 Jun 2005 06:41:05 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from lexi.siliconlandmark.com (lexi.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF13843D48; Sun, 5 Jun 2005 06:41:04 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from lexi.siliconlandmark.com (localhost [127.0.0.1]) by lexi.siliconlandmark.com (8.13.3/8.13.3) with ESMTP id j556exbg065895; Sun, 5 Jun 2005 02:40:59 -0400 (EDT) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost) by lexi.siliconlandmark.com (8.13.3/8.13.3/Submit) with ESMTP id j556evmS065892; Sun, 5 Jun 2005 02:40:57 -0400 (EDT) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: lexi.siliconlandmark.com: andy owned process doing -bs Date: Sun, 5 Jun 2005 02:40:57 -0400 (EDT) From: Andre Guibert de Bruet To: John Jawed In-Reply-To: Message-ID: <20050605023739.J42933@lexi.siliconlandmark.com> References: <42A11C92.5050505@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Information: Please contact the ISP for more information X-SL-MailScanner: Found to be clean X-SL-SpamCheck: not spam, SpamAssassin (score=-2.536, required 6, autolearn=not spam, AWL 0.06, BAYES_00 -2.60) X-MailScanner-From: andy@siliconlandmark.com X-Mailman-Approved-At: Sun, 05 Jun 2005 12:05:15 +0000 Cc: Scott Long , hackers@freebsd.org, FreeBSD Current Subject: Re: HEADS UP! 6.0 Schedule, 6.0-CURRENT Snapshot X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 06:41:05 -0000 On Sat, 4 Jun 2005, John Jawed wrote: > On 6/3/05, Scott Long wrote: >> >> The long anticipated and much feared 6.0 code freeze is about to begin! >> I'll cut to the chase: >> >> June 10 - Feature freeze + code slush >> ^^^^^^^ >> July 10 - RELENG_6 branch >> August 1 - RELENG_6_0 branch >> August 15 - 6.0-RELEASE > > Yes, oh lordie yes. I guess we aren't going to have a new logo in time for > FreeBSD6-RELEASE in August, are we? Coordinating the release with the new logo would be really nifty! My $0.02, Andy /* Andre Guibert de Bruet * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */ /* Code poet / Sysadmin * 636f 656b 2e79 5320 7379 6461 696d 2e6e */ /* GSM: +1 734 846 8758 * 5520 494e 2058 6c73 7565 6874 002e 0000 */ /* WWW: siliconlandmark.com * Tormenting bytes since 1980. */ From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 12:15:16 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42C4816A41C; Sun, 5 Jun 2005 12:15:16 +0000 (GMT) (envelope-from root@Neo-Vortex.net) Received: from Neo-Vortex.net (203-173-58-65.dyn.iinet.net.au [203.173.58.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F6A343D49; Sun, 5 Jun 2005 12:15:14 +0000 (GMT) (envelope-from root@Neo-Vortex.net) Received: from localhost.Neo-Vortex.net (Neo-Vortex@localhost.Neo-Vortex.net [127.0.0.1]) by Neo-Vortex.net (8.13.1/8.12.10) with ESMTP id j55CFCp6044935; Sun, 5 Jun 2005 22:15:12 +1000 (EST) (envelope-from root@Neo-Vortex.net) Date: Sun, 5 Jun 2005 22:15:12 +1000 (EST) From: Neo-Vortex To: Andre Guibert de Bruet In-Reply-To: <20050605023739.J42933@lexi.siliconlandmark.com> Message-ID: <20050605221438.L43170@Neo-Vortex.net> References: <42A11C92.5050505@samsco.org> <20050605023739.J42933@lexi.siliconlandmark.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Scott Long , hackers@freebsd.org, John Jawed , FreeBSD Current Subject: Re: HEADS UP! 6.0 Schedule, 6.0-CURRENT Snapshot X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 12:15:16 -0000 On Sun, 5 Jun 2005, Andre Guibert de Bruet wrote: > > Yes, oh lordie yes. I guess we aren't going to have a new logo in time for > > FreeBSD6-RELEASE in August, are we? > > Coordinating the release with the new logo would be really nifty! Mabe im living under a rock... but what new logo? ~NVX From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 12:17:35 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B8B716A41C for ; Sun, 5 Jun 2005 12:17:35 +0000 (GMT) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp802.mail.ukl.yahoo.com (smtp802.mail.ukl.yahoo.com [217.12.12.139]) by mx1.FreeBSD.org (Postfix) with SMTP id 0427443D1F for ; Sun, 5 Jun 2005 12:17:34 +0000 (GMT) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 46314 invoked from network); 5 Jun 2005 12:17:33 -0000 Received: from unknown (HELO w2fzz0vc01.aah-go-on.com) (thomas.sparrevohn@hg1.btinternet.com@81.157.123.116 with plain) by smtp802.mail.ukl.yahoo.com with SMTP; 5 Jun 2005 12:17:33 -0000 From: Thomas Sparrevohn To: freebsd-hackers@freebsd.org Date: Sun, 5 Jun 2005 13:17:21 +0100 User-Agent: KMail/1.8 References: <200506051231.57725.Thomas.Sparrevohn@btinternet.com> In-Reply-To: <200506051231.57725.Thomas.Sparrevohn@btinternet.com> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_R1uoCNfhOhFTK8s" Message-Id: <200506051317.21527.Thomas.Sparrevohn@btinternet.com> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Debugging UMA allocation X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Thomas.Sparrevohn@btinternet.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 12:17:35 -0000 --Boundary-00=_R1uoCNfhOhFTK8s Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Sunday 05 June 2005 12:31, Thomas Sparrevohn wrote: Ups - two useless files included - please ignore the plugins.txt and the dmesg - it should have been > Hi > > One of the changes introduced after the 27/05 causes a panic in the initial > boot phases in the > > The panic occurs on my Dell Lattitude C640 when using both my own kernel > and the GENERIC kernel. > > The panic is > _mtx_lock_sleep: Recursed on non-recursive mutex in system map > > I have traced the trigger panic to the first call to uma_zcreate in > procinit called from proc0_init - I have just cvs-supped again but the > error is still there > > Unfortunately because it happend before anything is up and running I have > no way of producing a kernel dump and as the problem does not seem to be > widely reported I assume it is specific to this Dell Laptop type > > The dmesg included are provided as reference only for the last good > compilation of the that I know off e.g. the kernel I know that boots - I > have been trying for about 2-3 days which should narrow down the time > > Can anybody give any advise on how to progress? --Boundary-00=_R1uoCNfhOhFTK8s-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 12:58:19 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C055116A41C for ; Sun, 5 Jun 2005 12:58:19 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (244.Red-217-126-240.pooles.rima-tde.net [217.126.240.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id E351743D48 for ; Sun, 5 Jun 2005 12:58:18 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (pato.euesrg02.net [192.168.0.3]) by alf.dyndns.ws (8.13.1/8.13.1) with ESMTP id j55CwH6q022193 for ; Sun, 5 Jun 2005 14:58:17 +0200 (CEST) (envelope-from victor@bsdes.net) Date: Sun, 5 Jun 2005 14:57:46 +0200 From: Victor Balada Diaz To: freebsd-hackers@freebsd.org Message-ID: <20050605125746.GB691@pato.euesrg02.net> Mail-Followup-To: Victor Balada Diaz , freebsd-hackers@freebsd.org References: <20050604181730.GB49520@pato.euesrg02.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Subject: Re: help me with C languaje please, re: files. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 12:58:19 -0000 On Sun, Jun 05, 2005 at 01:35:21AM -0400, Pablo Mora wrote: > #include > #include > > int main(void) { > > FILE *p_to_f; > char buf[1024]; > int i, j = 0; > > p_to_f = fopen("test","r"); > > if(p_to_f == NULL) { > perror("fopen"); > exit(EXIT_FAILURE); > } > > for(i = 0; i < 4 && !feof(p_to_f); i++) { > fgets(buf,1024,p_to_f); > printf("%s", buf); > } > > fclose(p_to_f); > > return 0; > > } > > I expect that be well what I did. Thanks Victor. > > PD Corrigeme Si hay algo malo. :D You don't use j, in the for should be || instead of && and you don't check for errors in fgets. Btw, i think that this is not the best place for ask this questions, you should ask in a c programming list. -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 13:45:04 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF00B16A41C for ; Sun, 5 Jun 2005 13:45:04 +0000 (GMT) (envelope-from cmello@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71DF943D1D for ; Sun, 5 Jun 2005 13:45:04 +0000 (GMT) (envelope-from cmello@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so904227wra for ; Sun, 05 Jun 2005 06:45:03 -0700 (PDT) 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:content-disposition; b=ffQU5UgRJNnwP2O1Xq431BQUrV4gcW7P2Xpe/ydWoqVmcBZIJaqWptzuD/iWsLyDqc1mvsQ0AK7TmP84IZiveTads6L/bcVL4BP3H/9C6w94dIKtjNO+J0pIRXLo848srUYKGgFObFu2uF0do8IN7r7nidWfA9q0eE7di5EypxM= Received: by 10.54.115.3 with SMTP id n3mr2580233wrc; Sun, 05 Jun 2005 06:45:03 -0700 (PDT) Received: by 10.54.102.20 with HTTP; Sun, 5 Jun 2005 06:45:02 -0700 (PDT) Message-ID: Date: Sun, 5 Jun 2005 10:45:02 -0300 From: Cesar Mello To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Vesa X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Cesar Mello List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 13:45:04 -0000 Hello, =20 I'd like to do some research on framebuffer GUIs (without Xorg) in FreeBSD. My background is C/C++ programming, Win32 and a bit of xlib. I've read the developer handbook but it didn't seem to have enough information= =20 for me. Can you please point me to more information about framebuffer development for FreeBSD (if any exists), or about how I can start doing a video driver for example? I have no idea if this should be done in kernel o= r=20 userland, and if in userland, what must I do to have access to video hardware. =20 Thank you very much for the attention. Cesar From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 13:49:31 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D252416A41C for ; Sun, 5 Jun 2005 13:49:31 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D8C143D4C for ; Sun, 5 Jun 2005 13:49:31 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (port-212-202-135-63.static.qsc.de [212.202.135.63]) by hydra.bec.de (Postfix) with ESMTP id 5411735707 for ; Sun, 5 Jun 2005 15:49:29 +0200 (CEST) Received: by britannica.bec.de (Postfix, from userid 1001) id 22AD57D19; Sun, 5 Jun 2005 15:49:14 +0200 (CEST) Date: Sun, 5 Jun 2005 15:49:14 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org Message-ID: <20050605134914.GA40957@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Subject: Re: Vesa X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 13:49:31 -0000 On Sun, Jun 05, 2005 at 10:45:02AM -0300, Cesar Mello wrote: > I'd like to do some research on framebuffer GUIs (without Xorg) in > FreeBSD. My background is C/C++ programming, Win32 and a bit of xlib. I've > read the developer handbook but it didn't seem to have enough information > for me. Can you please point me to more information about framebuffer > development for FreeBSD (if any exists), or about how I can start doing a > video driver for example? I have no idea if this should be done in kernel or > userland, and if in userland, what must I do to have access to video > hardware. The framebuffer support in FreeBSD is pretty weak, look at the VESA part of syscons. You might want to have a look at KGI too, but I'm not sure if that is still actively supported. If you want to do more work in that area, you might want to talk with Sascha Wildner from DragonFly, he's been improving syscons lately. Joerg From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 15:31:19 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5F4616A41C for ; Sun, 5 Jun 2005 15:31:19 +0000 (GMT) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp801.mail.ukl.yahoo.com (smtp801.mail.ukl.yahoo.com [217.12.12.138]) by mx1.FreeBSD.org (Postfix) with SMTP id 40E1E43D49 for ; Sun, 5 Jun 2005 15:31:19 +0000 (GMT) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 96503 invoked from network); 5 Jun 2005 15:31:17 -0000 Received: from unknown (HELO w2fzz0vc01.aah-go-on.com) (thomas.sparrevohn@hg1.btinternet.com@81.129.54.230 with plain) by smtp801.mail.ukl.yahoo.com with SMTP; 5 Jun 2005 15:31:17 -0000 From: Thomas Sparrevohn To: freebsd-hackers@freebsd.org, Poul-Henning Kamp Date: Sun, 5 Jun 2005 16:31:03 +0100 User-Agent: KMail/1.8 References: <200506051231.57725.Thomas.Sparrevohn@btinternet.com> <200506051317.21527.Thomas.Sparrevohn@btinternet.com> In-Reply-To: <200506051317.21527.Thomas.Sparrevohn@btinternet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506051631.04750.Thomas.Sparrevohn@btinternet.com> Cc: Subject: Re: Debugging UMA allocation X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Thomas.Sparrevohn@btinternet.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 15:31:19 -0000 On Sunday 05 June 2005 13:17, Thomas Sparrevohn wrote: Ok - After a hand held trace - here are what happens In the call to uma_zcreate for the "PROC" object the slab_zalloc ends up being called twice - it in turn calls vm_map_lock and establishes the first time a exclusive sleep mutex on the region 0xc1059144 through a call to vm_map_lock in the startup_alloc - however that lock are nover released so when the second call to slab_zalloc is executed it in turns again calls startup_alloc which in turn again calls page_alloc->kmem_malloc->vm_map_lock with the same region which by now holds an exclusive lock that the first call established and the kernel panics Could it be because the "booted" vairable holds the value 1 or it that a long shot? > On Sunday 05 June 2005 12:31, Thomas Sparrevohn wrote: > > Ups - two useless files included - please ignore the plugins.txt and the > dmesg - it should have been > > > Hi > > > > One of the changes introduced after the 27/05 causes a panic in the > > initial boot phases in the > > > > The panic occurs on my Dell Lattitude C640 when using both my own kernel > > and the GENERIC kernel. > > > > The panic is > > _mtx_lock_sleep: Recursed on non-recursive mutex in system map > > > > I have traced the trigger panic to the first call to uma_zcreate in > > procinit called from proc0_init - I have just cvs-supped again but the > > error is still there > > > > Unfortunately because it happend before anything is up and running I have > > no way of producing a kernel dump and as the problem does not seem to be > > widely reported I assume it is specific to this Dell Laptop type > > > > The dmesg included are provided as reference only for the last good > > compilation of the that I know off e.g. the kernel I know that boots - I > > have been trying for about 2-3 days which should narrow down the time > > > > Can anybody give any advise on how to progress? From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 22:59:10 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B93016A41C for ; Sun, 5 Jun 2005 22:59:10 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from postfix4-1.free.fr (postfix4-1.free.fr [213.228.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 845BE43D1F for ; Sun, 5 Jun 2005 22:59:09 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix4-1.free.fr (Postfix) with ESMTP id 0D4D4317ADD for ; Mon, 6 Jun 2005 00:59:08 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 1F49D407E; Mon, 6 Jun 2005 00:58:56 +0200 (CEST) Date: Mon, 6 Jun 2005 00:58:56 +0200 From: Jeremie Le Hen To: freebsd-hackers@freebsd.org Message-ID: <20050605225855.GD41050@obiwan.tataz.chchile.org> References: <20050525175419.GA87847@dan.emsphone.com> <20050526081738.GI850@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline In-Reply-To: <20050526081738.GI850@obiwan.tataz.chchile.org> User-Agent: Mutt/1.5.9i Subject: Re: Opening raw disk while mounted in 5.x? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 22:59:10 -0000 --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi list, > I don't want to start the bikeshed again, but would this be ok to create > a kern.geom.allow_foot_shooting sysctl wrapper for this and reference > it in geom(4) manual page (and anywhere else it is relevant), at least > temporaly until a decision is made ? > > I can't find where this is documented and this question goes back > regularly. I made the small attached patch which creates the kern.geom.allow_foot_shooting sysctl. It's no more than an explicit representation of the fifth bit of debugflags (remember the famous value 16). If needed, I would be pleased to make a modification to the geom(4) manual page and also to drop a note about this in fdisk(8) and boot0cfg(8). Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="geom.kern.allow_foot_shooting.patch" --- geom_kern.c.orig Sun Jun 5 19:12:22 2005 +++ geom_kern.c Sun Jun 5 19:21:17 2005 @@ -213,6 +213,31 @@ return error; } +static int +sysctl_kern_geom_allow_foot_shooting(SYSCTL_HANDLER_ARGS) +{ + int error; + int val; + + if (g_debugflags & 16) + val = 1; + else + val = 0; + + error = sysctl_handle_int(oidp, &val, sizeof(int), req); + if (error || req->newptr == NULL) + return error; + + if (val < 0 || val > 1) + return EINVAL; + + if (val) + g_debugflags |= 16; + else + g_debugflags &= ~16; + return 0; +} + SYSCTL_NODE(_kern, OID_AUTO, geom, CTLFLAG_RW, 0, "GEOMetry management"); SYSCTL_PROC(_kern_geom, OID_AUTO, confxml, CTLTYPE_STRING|CTLFLAG_RD, @@ -230,6 +255,10 @@ TUNABLE_INT("kern.geom.debugflags", &g_debugflags); SYSCTL_INT(_kern_geom, OID_AUTO, debugflags, CTLFLAG_RW, &g_debugflags, 0, ""); + +SYSCTL_PROC(_kern_geom, OID_AUTO, allow_foot_shooting, CTLTYPE_INT|CTLFLAG_RW, + 0, sizeof(int), sysctl_kern_geom_allow_foot_shooting, "I", + "Allow foot-shooting"); SYSCTL_INT(_kern_geom, OID_AUTO, collectstats, CTLFLAG_RW, &g_collectstats, 0, ""); --VS++wcV0S1rZb1Fb-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 6 02:20:02 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A761D16A41C for ; Mon, 6 Jun 2005 02:20:02 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [69.17.104.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A97F43D4C for ; Mon, 6 Jun 2005 02:20:02 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [69.17.104.113]) by sasami.jurai.net (8.13.1/8.13.1) with ESMTP id j562JwR4030729; Sun, 5 Jun 2005 22:20:01 -0400 (EDT) (envelope-from mdodd@FreeBSD.ORG) Date: Sun, 5 Jun 2005 22:19:58 -0400 (EDT) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: Jeremie Le Hen In-Reply-To: <20050605225855.GD41050@obiwan.tataz.chchile.org> Message-ID: <20050605221841.W61059@sasami.jurai.net> References: <20050525175419.GA87847@dan.emsphone.com> <20050526081738.GI850@obiwan.tataz.chchile.org> <20050605225855.GD41050@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (sasami.jurai.net [69.17.104.113]); Sun, 05 Jun 2005 22:20:01 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Opening raw disk while mounted in 5.x? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 02:20:02 -0000 On Mon, 6 Jun 2005, Jeremie Le Hen wrote: > I made the small attached patch which creates the > kern.geom.allow_foot_shooting This was proposed in ftp://ftp.jurai.net/users/winter/geom.foot.patch before debug flag 16 existed. The longer name doesn't really do anything to inform the user about the behavior of GEOM that may run counter to their expectations. -- 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00 From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 6 06:36:41 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DDCE16A41C for ; Mon, 6 Jun 2005 06:36:41 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from server.absolute-media.de (server.absolute-media.de [213.239.231.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFA2243D49 for ; Mon, 6 Jun 2005 06:36:40 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from localhost (unknown [127.0.0.1]) by server.absolute-media.de (Postfix) with ESMTP id 1C83D7F3DC; Mon, 6 Jun 2005 08:36:38 +0200 (CEST) Received: from server.absolute-media.de ([127.0.0.1]) by localhost (server [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03897-05; Mon, 6 Jun 2005 08:36:33 +0200 (CEST) Received: from firewall.demig (p50839338.dip0.t-ipconnect.de [80.131.147.56]) by server.absolute-media.de (Postfix) with ESMTP id 25BCB7F350; Mon, 6 Jun 2005 08:36:33 +0200 (CEST) Received: from ws-ew-3 (ws-ew-3.w2kdemig [192.168.1.72]) by firewall.demig (8.13.4/8.13.1) with SMTP id j566YUBB018102; Mon, 6 Jun 2005 08:34:37 +0200 (CEST) (envelope-from NKoch@demig.de) From: "Norbert Koch" To: "Maksim Yevmenkin" Date: Mon, 6 Jun 2005 08:34:37 +0200 Message-ID: <008001c56a61$cf92bf00$4801a8c0@ws-ew-3.W2KDEMIG> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 In-Reply-To: <42A090DE.8060002@savvis.net> X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at absolute-media.de Cc: "Freebsd-Hackers@Freebsd. Org" Subject: RE: synchronization question about /sys/dev/vkbd/vkbd.c X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 06:36:41 -0000 > > My question is: > > Is it not possible, that vkbd_dev_intr() could be > > interrupted at any position before the VKBD_LOCK() > > and then vkbd_dev_write() called? > > in theory it is possible. > > > If yes, how should vkbd_dev_write() know, that it should > > call task_enqueue(), as TASK is still set? > > well, i guess it is possible to miss interrupt in this case. also, the > scancodes are not lost, they will be processed on next write. > I agree, that it is hardly possible to miss an interrupt, as keys come in so slowly. But that also means if it happens, you will notice it, because you have to press an additional key. > i suspect that the vkbd_dev_intr() should be interrupted exactly > in between > > (*kbdsw[kbd->kb_index]->intr)(kbd, NULL); > > and > > VKBD_LOCK(state); > Yes, precisely. > yes, that could be done. it is also possible to have a callout going few > times a second to check if there is a scancodes in the queue and > schedule vkbd_dev_intr(). funny that atkbd(4) and ukbd(4) have just this. Thank you for your comments, Norbert From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 20:02:37 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A51616A41C; Sun, 5 Jun 2005 20:02:37 +0000 (GMT) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [194.58.105.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8D9A43D48; Sun, 5 Jun 2005 20:02:36 +0000 (GMT) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.44 (FreeBSD)) id 1Df1KM-000A5P-Oo; Mon, 06 Jun 2005 00:02:35 +0400 Date: Mon, 6 Jun 2005 00:02:33 +0400 From: Slawa Olhovchenkov To: Scott Long Message-ID: <20050605200233.GA38531@zxy.spb.ru> References: <42A11C92.5050505@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42A11C92.5050505@samsco.org> User-Agent: Mutt/1.5.7i X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-Mailman-Approved-At: Mon, 06 Jun 2005 11:56:48 +0000 Cc: hackers@freebsd.org, 'FreeBSD Current' Subject: Re: HEADS UP! 6.0 Schedule, 6.0-CURRENT Snapshot X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 20:02:37 -0000 On Fri, Jun 03, 2005 at 09:14:26PM -0600, Scott Long wrote: > All, > > The long anticipated and much feared 6.0 code freeze is about to begin! > I'll cut to the chase: > > June 10 - Feature freeze + code slush > ^^^^^^^ > > July 10 - RELENG_6 branch > August 1 - RELENG_6_0 branch > August 15 - 6.0-RELEASE Nice time for compat5x? From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 5 21:25:55 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60ED616A41C for ; Sun, 5 Jun 2005 21:25:55 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from cobalt.antimatter.net (cobalt.antimatter.net [69.55.224.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBC0E43D1F for ; Sun, 5 Jun 2005 21:25:54 +0000 (GMT) (envelope-from glenn@antimatter.net) Received: from glenn-mobile.antimatter.net (cpe-66-27-86-22.san.res.rr.com [66.27.86.22]) (authenticated bits=0) by cobalt.antimatter.net (8.13.4/8.13.4) with ESMTP id j55LPqSG016901 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO); Sun, 5 Jun 2005 14:25:53 -0700 Message-Id: <6.1.0.6.2.20050605142135.040c89a0@cobalt.antimatter.net> X-Sender: glenn@cobalt.antimatter.net X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6 Date: Sun, 05 Jun 2005 14:24:19 -0700 To: freebsd-hackers@freebsd.org From: Glenn Dawson Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Mailman-Approved-At: Mon, 06 Jun 2005 11:56:48 +0000 Subject: vn(4) performance on 4.11 versus md(4) on 5.4 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Jun 2005 21:25:55 -0000 (I sent this to freebsd-performance yesterday, but that list seems kind of dead, so I'm trying this one. If there's a better place for me to send this, let me know.) I have a number of systems running 4.11 that have file backed virtual disks, each of which contains a jail. I need to start using 5.4 for new servers. The catch is, file backed virtual disks using md(4) seem to be much slower than similar virtual disks on 4.11 using vn(4). vn(4) on 4.11 is about 2.24 times faster than the equivalent setup using md(4) on 5.4. I've posted the results of some tests that I ran at http://www.antimatter.net/md-versus-vn.txt Is this decrease in performance known? Is there something I can do in order to come close to the performance that 4.11 has? I've tried changing some of the parameters of the filesystem on the virtual disk, but the performance didn't change. I can supply more info than what the link above has, if needed. -Glenn From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 6 14:41:08 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5238A16A41C for ; Mon, 6 Jun 2005 14:41:08 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id B473643D49 for ; Mon, 6 Jun 2005 14:41:07 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [212.42.16.7]) (MDaemon.PRO.v8.0.2.R) with ESMTP id md50001462791.msg for ; Mon, 06 Jun 2005 15:35:22 +0100 Message-ID: <008201c56aa5$9d2ac0a0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: Date: Mon, 6 Jun 2005 15:39:54 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Spam-Processed: multiplay.co.uk, Mon, 06 Jun 2005 15:35:22 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org X-MDAV-Processed: multiplay.co.uk, Mon, 06 Jun 2005 15:35:24 +0100 Subject: using beastie.4th to alternate boot i386 / amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 14:41:08 -0000 I'm trying to get beastie.4th to allow me to select either amd64 or i386 as my running system. I can get this to happen from the boot loader using: set currdev=disk1s1d set rootdev=disk1s1d unload load /boot/kernel/kernel load /boot/kernel/acpi.ko load /boot/kernel/hptmv.ko boot But Im at a loss when it comes to altering beastie.4th to replicate these steps I've currently added a menu option with the following code: ... dup booti386key @ = if s" disk1s1d" s " currdev" setenv s" disk1s1d" s " rootdev" setenv 0 boot then .... So all I need to do is replicate the unload / load steps I though this would be just like: dup booti386key @ = if s" disk1s1d" s " currdev" setenv s" disk1s1d" s " rootdev" setenv unload load /boot/kernel/kernel load /boot/kernel/acpi.ko load /boot/kernel/hptmv.ko 0 boot then When I that it wasn't pretty, rescue disk.. as I didn't even get the menu. I've had a look at some forth guides but have been unable to come up with the correct way of making this work. Can someone point me in the right direction ? Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 6 15:48:58 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E388F16A41C for ; Mon, 6 Jun 2005 15:48:58 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81CE443D1D for ; Mon, 6 Jun 2005 15:48:58 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so1993001rne for ; Mon, 06 Jun 2005 08:48:54 -0700 (PDT) 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:content-disposition:references; b=eeBlEt5zEKm85YvSRJ2AI54o7o4Gulm3NMvI3HmY1grFmpdVDu3a9qowGGQWUhlvzsrxQrwoNNC5Ec0JRk1BYXG2acwh7nnBK0LqxEL0fZok5H+5z6NbJf70Pl5tAUhdO9FfQSpaLvc4rvUSdXPVysYhy4HBSfLVeBgmRYtrTf4= Received: by 10.38.88.3 with SMTP id l3mr2458801rnb; Mon, 06 Jun 2005 08:48:54 -0700 (PDT) Received: by 10.38.209.31 with HTTP; Mon, 6 Jun 2005 08:48:54 -0700 (PDT) Message-ID: <84dead7205060608484edd8d88@mail.gmail.com> Date: Mon, 6 Jun 2005 21:18:54 +0530 From: Joseph Koshy To: Steven Hartland In-Reply-To: <008201c56aa5$9d2ac0a0$b3db87d4@multiplay.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <008201c56aa5$9d2ac0a0$b3db87d4@multiplay.co.uk> Cc: freebsd-hackers@freebsd.org Subject: Re: using beastie.4th to alternate boot i386 / amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joseph Koshy List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 15:48:59 -0000 > I'm trying to get beastie.4th to allow me to select either > amd64 or i386 as my running system. I can get this to happen > from the boot loader using: > set currdev=3Ddisk1s1d > set rootdev=3Ddisk1s1d > unload > load /boot/kernel/kernel > load /boot/kernel/acpi.ko > load /boot/kernel/hptmv.ko > boot If you are looking for a way to manage i386/amd64 dual booting, the you can just interrupt the boot sequence at the=20 boot: prompt and then load /boot/loader itself from the=20 appropriate root partition. You can specify a 'default' in file /boot.config in the disk's 'a' partition. Using FORTH would allow for a nice menu though :). --=20 FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 6 16:12:43 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F59016A41F; Mon, 6 Jun 2005 16:12:43 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A13843D48; Mon, 6 Jun 2005 16:12:42 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id j56GFFpq000812; Mon, 6 Jun 2005 18:15:15 +0200 (MEST) Message-ID: <42A475AB.6020808@fer.hr> Date: Mon, 06 Jun 2005 18:11:23 +0200 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: pjd@freebsd.org Subject: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Jun 2005 16:12:43 -0000 I have an idea that I could implement through Google's "Summer of Code" project, but as I have little experience with stuff it involves (kernel programming / disks / filesystem optimization), so I expect any answer from "It won't work" or "It's useless" to "It can't be done". :) The idea is this: to implement sort of GEOM-layer disk data journaling system. I imagine it to be a GEOM class using two "lower-level" devices: one for data and one for the "journal" (this way, the journal device can be on a fast and small disk). Such journaled device could be used to host any filesystem, probably mounted with synchronoues-access, and it will result in faster write access by keeping the writes sequential in the "journal" device. Journal information will be commited to the data disk periodically by a separate log-writer thread, or when it gets full. The "data disk" will be consistent so it can be used without it's "journal" part (after a clean disconnect/rebuild) if needed. At the worst case, I think this will help performance in cases when there's a burst of write activity followed by a period of IO idleness. I've made the above idea more-or-less from my head in one afternoon, so it's perfectly possible that I'm missing some vital point or that it's complete nonsense :) Does it make sense to do it this way? Is it worth applying for the SoC? From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 7 09:57:20 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03C1A16A41C for ; Tue, 7 Jun 2005 09:57:20 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (www1.multiplay.co.uk [212.42.16.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78AF543D1F for ; Tue, 7 Jun 2005 09:57:19 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [212.42.16.7]) (MDaemon.PRO.v8.0.2.R) with ESMTP id md50001465267.msg for ; Tue, 07 Jun 2005 10:51:58 +0100 Message-ID: <019d01c56b47$2fe27ef0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Joseph Koshy" References: <008201c56aa5$9d2ac0a0$b3db87d4@multiplay.co.uk> <84dead7205060608484edd8d88@mail.gmail.com> Date: Tue, 7 Jun 2005 10:56:29 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Spam-Processed: multiplay.co.uk, Tue, 07 Jun 2005 10:51:58 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org X-MDAV-Processed: multiplay.co.uk, Tue, 07 Jun 2005 10:51:59 +0100 Cc: freebsd-hackers@freebsd.org Subject: Re: using beastie.4th to alternate boot i386 / amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2005 09:57:20 -0000 Thanks for that Joseph, its a quicker option than what I have atm but would still like to get the menu based option to work so if anyone has any ideas please do shout. Steve / K ----- Original Message ----- From: "Joseph Koshy" X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17B7216A41C for ; Tue, 7 Jun 2005 18:34:51 +0000 (GMT) (envelope-from khall@stbernard.com) Received: from mail04.stbernard.com (mail02.stbernard.com [64.154.93.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id C789C43D48 for ; Tue, 7 Jun 2005 18:34:50 +0000 (GMT) (envelope-from khall@stbernard.com) Received: from mail01.stbernard.com (mail01.stbernard.com [192.168.32.92]) by mail04.stbernard.com (8.12.11/8.12.11) with ESMTP id j57IYoGe052834 for ; Tue, 7 Jun 2005 11:34:50 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 7 Jun 2005 11:30:33 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: using beastie.4th to alternate boot i386 / amd64 Thread-Index: AcVrWNg52Ue2zBs6S/uKT0V0JFhl1wANd0Gg From: "Kelly Hall" To: X-Scanned-By: ePrism email filtering appliance Subject: RE: using beastie.4th to alternate boot i386 / amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2005 18:34:51 -0000 > Date: Mon, 6 Jun 2005 15:39:54 +0100 > From: "Steven Hartland" > Subject: using beastie.4th to alternate boot i386 / amd64 > > load /boot/kernel/kernel > load /boot/kernel/acpi.ko > load /boot/kernel/hptmv.ko Try s" load /boot/kernel/kernel" evaluate s" load /boot/kernel/acpi.ko" evaluate s" load /boot/kernel/hptmv.ko" evaluate Kelly From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 7 19:07:22 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FF5416A41C for ; Tue, 7 Jun 2005 19:07:22 +0000 (GMT) (envelope-from samuel.pierson@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id B011843D4C for ; Tue, 7 Jun 2005 19:07:21 +0000 (GMT) (envelope-from samuel.pierson@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so51991wra for ; Tue, 07 Jun 2005 12:07:21 -0700 (PDT) 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:content-disposition; b=cC5+Kp5OSpaYYhDRw8nHxh9Lrtns6gsgd6v86LdjnOhR96GYHxS2R0wWa2rSGakS9SU+4zatBCOc1xjDyCce6wWJG5kyaideA5qRWAypg94EXRZs66P+WSk5LfIxALPd26poYKuvCcXeHqlExgSFW3m7FfNaTyzLee7iV+XJGJs= Received: by 10.54.16.63 with SMTP id 63mr1967612wrp; Tue, 07 Jun 2005 12:07:21 -0700 (PDT) Received: by 10.54.144.1 with HTTP; Tue, 7 Jun 2005 12:07:20 -0700 (PDT) Message-ID: Date: Tue, 7 Jun 2005 14:07:20 -0500 From: Sam Pierson To: FreeBSD Hackers Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Use if_ath.c for on the fly transmission power change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sam Pierson List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2005 19:07:22 -0000 I was curious if there was a way to use the if_ath.c file in order to chang= e transmission power on the fly in the middle of a program. This is in if_a= th: ath_hal_setuptxdesc(ah, ds , pktlen /* packet length */ , hdrlen /* header length */ , atype /* Atheros packet type */ , 0x60 /* txpower XXX */ , txrate, 1+10 /* series 0 rate/tries */ , iswep ? sc->sc_ic.ic_wep_txkey : HAL_TXKEYIX_INVALID , antenna /* antenna mode */ , flags /* flags */ , ctsrate /* rts/cts rate */ , ctsduration /* rts/cts duration */ ); So I would assume there is a way to do it, although I seem stuck. Do I hav= e to construct each packet by hand (is this even feasible)? I saw back in=20 September that Sam Leffler said "per-packet TPC is not working right now",= =20 so I assume that it may have been worked on or at least checked out since= =20 then. Thanks From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 7 19:40:12 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D889416A41C; Tue, 7 Jun 2005 19:40:12 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6290C43D53; Tue, 7 Jun 2005 19:40:12 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 9D8A6ACC56; Tue, 7 Jun 2005 21:40:05 +0200 (CEST) Date: Tue, 7 Jun 2005 21:40:05 +0200 From: Pawel Jakub Dawidek To: Ivan Voras Message-ID: <20050607194005.GG837@darkness.comp.waw.pl> References: <42A475AB.6020808@fer.hr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AG6PiNxwwkUqaz46" Content-Disposition: inline In-Reply-To: <42A475AB.6020808@fer.hr> 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: hackers@freebsd.org, scottl@FreeBSD.org, phk@FreeBSD.org Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2005 19:40:13 -0000 --AG6PiNxwwkUqaz46 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 06, 2005 at 06:11:23PM +0200, Ivan Voras wrote: +> I have an idea that I could implement through Google's "Summer of Code"= =20 +> project, but as I have little experience with stuff it involves (kernel= =20 +> programming / disks / filesystem optimization), so I expect any answer= =20 +> from "It won't work" or "It's useless" to "It can't be done". :) +>=20 +> The idea is this: to implement sort of GEOM-layer disk data journaling= =20 +> system. I imagine it to be a GEOM class using two "lower-level" devices:= =20 +> one for data and one for the "journal" (this way, the journal device can= =20 +> be on a fast and small disk). Such journaled device could be used to=20 +> host any filesystem, probably mounted with synchronoues-access, and it= =20 +> will result in faster write access by keeping the writes sequential in= =20 +> the "journal" device. Journal information will be commited to the data= =20 +> disk periodically by a separate log-writer thread, or when it gets full.= =20 +> The "data disk" will be consistent so it can be used without it's=20 +> "journal" part (after a clean disconnect/rebuild) if needed. At the=20 +> worst case, I think this will help performance in cases when there's a= =20 +> burst of write activity followed by a period of IO idleness. +>=20 +> I've made the above idea more-or-less from my head in one afternoon, so= =20 +> it's perfectly possible that I'm missing some vital point or that it's= =20 +> complete nonsense :) +>=20 +> Does it make sense to do it this way? Is it worth applying for the SoC? Not sure. Basically this is simlar what softupdate does, I think. =46rom another point of view softupdates are only available for UFS. You probably wants to hear scottl and phk opinions (CCed). --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --AG6PiNxwwkUqaz46 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFCpfgVForvXbEpPzQRAulyAKDRdFAB5RebkoghErbCJRqidowyCgCg6j/V Inrlfvv6F5+Hwq+VvjImM4Y= =wc9J -----END PGP SIGNATURE----- --AG6PiNxwwkUqaz46-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 7 20:16:54 2005 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13C9216A41C; Tue, 7 Jun 2005 20:16:54 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id D644543D53; Tue, 7 Jun 2005 20:16:52 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 7 Jun 2005 21:16:43 +0100 (BST) Date: Tue, 7 Jun 2005 21:16:42 +0100 From: David Malone To: Pawel Jakub Dawidek Message-ID: <20050607201642.GA58346@walton.maths.tcd.ie> References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050607194005.GG837@darkness.comp.waw.pl> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: hackers@FreeBSD.org, scottl@FreeBSD.org, phk@FreeBSD.org, Ivan Voras Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2005 20:16:54 -0000 On Tue, Jun 07, 2005 at 09:40:05PM +0200, Pawel Jakub Dawidek wrote: > +> Does it make sense to do it this way? Is it worth applying for the SoC? > > Not sure. Basically this is simlar what softupdate does, I think. > From another point of view softupdates are only available for UFS. > You probably wants to hear scottl and phk opinions (CCed). I think that Ivan's idea is kind of different from softupdates. His idea is pretty clever, in that it could provide synchronus random writes at sequential write speeds for any filesystem, providing you repaly the journal at startup. However, our main problem these days is the fact that we do an fsck after every unclean reboot, not the speed of writes. I guess that you could skip the fsck (or run it very slowly in the background) if you knew the filesystem was clean 'cos of jounral replay. David. From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 7 20:53:18 2005 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3D9716A41C; Tue, 7 Jun 2005 20:53:18 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A10B43D1D; Tue, 7 Jun 2005 20:53:16 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.2.252.34] ([206.13.39.65]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j57Kwies062158; Tue, 7 Jun 2005 14:58:47 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42A6091C.40409@samsco.org> Date: Tue, 07 Jun 2005 14:52:44 -0600 From: Scott Long User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Malone References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> In-Reply-To: <20050607201642.GA58346@walton.maths.tcd.ie> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: scottl@FreeBSD.org, hackers@FreeBSD.org, Pawel Jakub Dawidek , phk@FreeBSD.org, Ivan Voras Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2005 20:53:19 -0000 David Malone wrote: > On Tue, Jun 07, 2005 at 09:40:05PM +0200, Pawel Jakub Dawidek wrote: > >>+> Does it make sense to do it this way? Is it worth applying for the SoC? >> >>Not sure. Basically this is simlar what softupdate does, I think. >>From another point of view softupdates are only available for UFS. >>You probably wants to hear scottl and phk opinions (CCed). > > > I think that Ivan's idea is kind of different from softupdates. His > idea is pretty clever, in that it could provide synchronus random > writes at sequential write speeds for any filesystem, providing you > repaly the journal at startup. > > However, our main problem these days is the fact that we do an fsck > after every unclean reboot, not the speed of writes. I guess that > you could skip the fsck (or run it very slowly in the background) > if you knew the filesystem was clean 'cos of jounral replay. > > David. /me jumps up and down and waves his hands The problem with journalling at the block layer is that you pretty much become forced to journal metadata and data, since the block layer really doesn't know the distinction, and definitely not in a filesystem-independent way (yes, UFS does evil things to the buffer cache by representing metadata with negative block numbers, but that is just UFS). Full journalling has many drawbacks from the viewpoint of speed and complexity, of course. So you really want to be able to do just metadata journalling. Another hard part of distinguishing between metadata and data is that filesystems have a habit of migrating disk blocks from holding metadata to holding data, and vice versa (think indirect pointer blocks, not inode blocks). If you are only replaying metadata, you want to make sure that you don't smash data blocks with old metadata. Coming up with a filesystem independent way to represent all of this for the block layer is not easy. Filesystems would have to be able to be modified to provide proper metadata vs. data hints to the block layer. And if you're going to do that, then why not just make it a library in VFS, like what Darwin does? The UFS Journalling work is already well underway, and I expect it to follow the path of being a VFS library. Note that I'm saying 'library' here, not 'layer'. There really is no way to make journalling work with an arbitrary filesystem 'for free', whether as a VFS layer or a GEOM transform, since journalling is 100% dependent on the filesystem working with the buffer-cache to do sane operations in a defined in order. An alternate SoC project that would be very useful is block-level snapshots. I'm not sure if I'll be able to retain the filesystem snapshot functionality in UFS with journalling enabled, so moving to doing the snapshots in the block layer would be a good way to make up for this. Beware that while the GEOM transform would be pretty straight-forward to write, the real trick comes from being able to make the consumer of a block device (a filesystem, maybe) flush itself to a consistent state while the snapshot is being taken. The infrastructure for this is the part that is very interesting, but also the most work. Scott From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 7 21:26:00 2005 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC78716A41C; Tue, 7 Jun 2005 21:26:00 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id BC54343D48; Tue, 7 Jun 2005 21:25:59 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 7 Jun 2005 22:25:58 +0100 (BST) To: Scott Long In-reply-to: Your message of "Tue, 07 Jun 2005 14:52:44 MDT." <42A6091C.40409@samsco.org> X-Request-Do: Date: Tue, 07 Jun 2005 22:25:58 +0100 From: David Malone Message-ID: <200506072225.aa16681@salmon.maths.tcd.ie> Cc: scottl@FreeBSD.org, hackers@FreeBSD.org, Pawel Jakub Dawidek , phk@FreeBSD.org, Ivan Voras Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2005 21:26:01 -0000 > The problem with journalling at the block layer is that you pretty much > become forced to journal metadata and data, since the block layer really > doesn't know the distinction, Definitely - I guess I should have stated that explicitly. > Full journalling has many drawbacks from the viewpoint of > speed and complexity, of course. So you really want to be able to do > just metadata journalling. The complexity of full journaling (for filesystems that offer a consistent version of themselves to the disk layer) would not seem to be that high: a scheme like Ivan's seems to achieve it. Maybe I've missed something? For us, journaling the metadata is of interest because we're interested in avoiding fscks. I suppose full journaling may be of interest to people with other applications, despite the unfortunate performance in many situations. > An alternate SoC project that would be very useful is block-level > snapshots. I'm not sure if I'll be able to retain the filesystem > snapshot functionality in UFS with journalling enabled, so moving to > doing the snapshots in the block layer would be a good way to make up > for this. Beware that while the GEOM transform would be pretty > straight-forward to write, the real trick comes from being able to make > the consumer of a block device (a filesystem, maybe) flush itself to a > consistent state while the snapshot is being taken. The infrastructure > for this is the part that is very interesting, but also the most work. Definitely another interesting project, though maybe a bit too much work to ask someone to do for $4500 over a summer... David. From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 01:18:37 2005 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BBB216A41C; Wed, 8 Jun 2005 01:18:37 +0000 (GMT) (envelope-from rcoleman@criticalmagic.com) Received: from saturn.criticalmagic.com (saturn.criticalmagic.com [69.61.68.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB9C343D53; Wed, 8 Jun 2005 01:18:36 +0000 (GMT) (envelope-from rcoleman@criticalmagic.com) Received: from [172.16.0.200] (adsl-34-200-245.asm.bellsouth.net [67.34.200.245]) by saturn.criticalmagic.com (Postfix) with ESMTP id 99FE13BD10; Tue, 7 Jun 2005 21:18:33 -0400 (EDT) Message-ID: <42A647B8.30709@criticalmagic.com> Date: Tue, 07 Jun 2005 21:19:52 -0400 From: Richard Coleman User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> <42A6091C.40409@samsco.org> In-Reply-To: <42A6091C.40409@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Pawel Jakub Dawidek , scottl@FreeBSD.org, Ivan Voras , David Malone , hackers@FreeBSD.org, phk@FreeBSD.org Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 01:18:37 -0000 Scott Long wrote: > /me jumps up and down and waves his hands > > The problem with journalling at the block layer is that you pretty much > become forced to journal metadata and data, since the block layer really > doesn't know the distinction, and definitely not in a > filesystem-independent way (yes, UFS does evil things to the buffer > cache by representing metadata with negative block numbers, but that is > just UFS). Full journalling has many drawbacks from the viewpoint of > speed and complexity, of course. So you really want to be able to do > just metadata journalling. > > Another hard part of distinguishing between metadata and data is that > filesystems have a habit of migrating disk blocks from holding metadata > to holding data, and vice versa (think indirect pointer blocks, not > inode blocks). If you are only replaying metadata, you want to make > sure that you don't smash data blocks with old metadata. > > Coming up with a filesystem independent way to represent all of this for > the block layer is not easy. Filesystems would have to be able to be > modified to provide proper metadata vs. data hints to the block layer. > And if you're going to do that, then why not just make it a library in > VFS, like what Darwin does? > > The UFS Journalling work is already well underway, and I expect it to > follow the path of being a VFS library. Note that I'm saying 'library' > here, not 'layer'. There really is no way to make journalling work with > an arbitrary filesystem 'for free', whether as a VFS layer or a GEOM > transform, since journalling is 100% dependent on the filesystem working > with the buffer-cache to do sane operations in a defined in order. > > An alternate SoC project that would be very useful is block-level > snapshots. I'm not sure if I'll be able to retain the filesystem > snapshot functionality in UFS with journalling enabled, so moving to > doing the snapshots in the block layer would be a good way to make up > for this. Beware that while the GEOM transform would be pretty > straight-forward to write, the real trick comes from being able to make > the consumer of a block device (a filesystem, maybe) flush itself to a > consistent state while the snapshot is being taken. The infrastructure > for this is the part that is very interesting, but also the most work. > > Scott Scott, Have you looked at the journaling layer that Matt has been adding to DragonflyBSD? What you are talking about appears very similar. Or am I misunderstanding something? Richard Coleman rcoleman@criticalmagic.com From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 03:07:25 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EAA716A41C for ; Wed, 8 Jun 2005 03:07:25 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4EA843D1D for ; Wed, 8 Jun 2005 03:07:24 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.94] ([66.127.85.94]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j5837Nms053560 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Jun 2005 20:07:24 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <42A660F9.3000302@errno.com> Date: Tue, 07 Jun 2005 20:07:37 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Pierson References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers Subject: Re: Use if_ath.c for on the fly transmission power change? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 03:07:25 -0000 Sam Pierson wrote: > I was curious if there was a way to use the if_ath.c file in order to change > transmission power on the fly in the middle of a program. This is in if_ath: > > ath_hal_setuptxdesc(ah, ds > , pktlen /* packet length */ > , hdrlen /* header length */ > , atype /* Atheros packet type */ > , 0x60 /* txpower XXX */ > , txrate, 1+10 /* series 0 rate/tries */ > , iswep ? sc->sc_ic.ic_wep_txkey : HAL_TXKEYIX_INVALID > , antenna /* antenna mode */ > , flags /* flags */ > , ctsrate /* rts/cts rate */ > , ctsduration /* rts/cts duration */ > ); > > So I would assume there is a way to do it, although I seem stuck. Do I have > to construct each packet by hand (is this even feasible)? I saw back in > September that Sam Leffler said "per-packet TPC is not working right now", > so I assume that it may have been worked on or at least checked out since > then. Still no support for TPC. There's a sysctl knob for a global power setting but nothing per-packet. Sam From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 07:14:09 2005 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B123116A41C for ; Wed, 8 Jun 2005 07:14:09 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ABEA43D1D for ; Wed, 8 Jun 2005 07:14:08 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.0.2.2] ([12.174.84.3]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j587JZ5i064988; Wed, 8 Jun 2005 01:19:44 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42A69A69.2040005@samsco.org> Date: Wed, 08 Jun 2005 01:12:41 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Richard Coleman References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> <42A6091C.40409@samsco.org> <42A647B8.30709@criticalmagic.com> In-Reply-To: <42A647B8.30709@criticalmagic.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: Pawel Jakub Dawidek , scottl@FreeBSD.org, Ivan Voras , David Malone , hackers@FreeBSD.org, phk@FreeBSD.org Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 07:14:09 -0000 Richard Coleman wrote: > Scott Long wrote: > >> /me jumps up and down and waves his hands >> >> The problem with journalling at the block layer is that you pretty >> much become forced to journal metadata and data, since the block layer >> really doesn't know the distinction, and definitely not in a >> filesystem-independent way (yes, UFS does evil things to the buffer >> cache by representing metadata with negative block numbers, but that >> is just UFS). Full journalling has many drawbacks from the viewpoint >> of speed and complexity, of course. So you really want to be able to >> do just metadata journalling. >> >> Another hard part of distinguishing between metadata and data is that >> filesystems have a habit of migrating disk blocks from holding >> metadata to holding data, and vice versa (think indirect pointer >> blocks, not inode blocks). If you are only replaying metadata, you >> want to make sure that you don't smash data blocks with old metadata. >> >> Coming up with a filesystem independent way to represent all of this >> for the block layer is not easy. Filesystems would have to be able to >> be modified to provide proper metadata vs. data hints to the block >> layer. And if you're going to do that, then why not just make it a >> library in VFS, like what Darwin does? >> >> The UFS Journalling work is already well underway, and I expect it to >> follow the path of being a VFS library. Note that I'm saying >> 'library' here, not 'layer'. There really is no way to make >> journalling work with an arbitrary filesystem 'for free', whether as a >> VFS layer or a GEOM transform, since journalling is 100% dependent on >> the filesystem working with the buffer-cache to do sane operations in >> a defined in order. >> >> An alternate SoC project that would be very useful is block-level >> snapshots. I'm not sure if I'll be able to retain the filesystem >> snapshot functionality in UFS with journalling enabled, so moving to >> doing the snapshots in the block layer would be a good way to make up >> for this. Beware that while the GEOM transform would be pretty >> straight-forward to write, the real trick comes from being able to >> make the consumer of a block device (a filesystem, maybe) flush itself >> to a consistent state while the snapshot is being taken. The >> infrastructure for this is the part that is very interesting, but also >> the most work. >> >> Scott > > > Scott, > > Have you looked at the journaling layer that Matt has been adding to > DragonflyBSD? What you are talking about appears very similar. Or am I > misunderstanding something? > > Richard Coleman > rcoleman@criticalmagic.com Ah, you might have misunderstood my use of the term 'VFS library'. This is distinctly different from a 'VFS layer', which is what Matt did. I've looked extensively at his work, but unfortunately it doesn't solve the kinds of problems that I'm looking to solve. After discussing journalling this evening with the author of BeFS and HFS+J, I'm pretty happy that I'm taking the approach that I am. Scott From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 10:07:26 2005 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3575A16A41C; Wed, 8 Jun 2005 10:07:26 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7A9143D1F; Wed, 8 Jun 2005 10:07:25 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id j58A9mpq022551; Wed, 8 Jun 2005 12:09:58 +0200 (MEST) Message-ID: <42A6C311.5090400@fer.hr> Date: Wed, 08 Jun 2005 12:06:09 +0200 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> <42A6091C.40409@samsco.org> In-Reply-To: <42A6091C.40409@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: David Malone , scottl@FreeBSD.org, hackers@FreeBSD.org, Pawel Jakub Dawidek , phk@FreeBSD.org Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 10:07:26 -0000 Scott Long wrote: > An alternate SoC project that would be very useful is block-level > snapshots. I'm not sure if I'll be able to retain the filesystem > snapshot functionality in UFS with journalling enabled, so moving to > doing the snapshots in the block layer would be a good way to make up > for this. Beware that while the GEOM transform would be pretty One addenum that was introduced after I made the post to hackers@, but before sending a proposal to Google (PHK's idea, actually) is to implement a delayed-commit mode, in which journaled data will not be commited until requested. This would allow something like block-level snapshots, but one-shot only (or at least one per journal). From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 11:47:31 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2FE316A41C; Wed, 8 Jun 2005 11:47:31 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4338243D4C; Wed, 8 Jun 2005 11:47:31 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j58BlLsX097276; Wed, 8 Jun 2005 06:47:22 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42A6DAB3.4080105@centtech.com> Date: Wed, 08 Jun 2005 06:46:59 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> <42A6091C.40409@samsco.org> <42A647B8.30709@criticalmagic.com> <42A69A69.2040005@samsco.org> In-Reply-To: <42A69A69.2040005@samsco.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Pawel Jakub Dawidek , scottl@freebsd.org, Ivan Voras , David Malone , hackers@freebsd.org, phk@freebsd.org, Richard Coleman Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 11:47:32 -0000 Scott Long wrote: > Richard Coleman wrote: > >> Scott Long wrote: >> >>> /me jumps up and down and waves his hands >>> >>> The problem with journalling at the block layer is that you pretty >>> much become forced to journal metadata and data, since the block >>> layer really doesn't know the distinction, and definitely not in a >>> filesystem-independent way (yes, UFS does evil things to the buffer >>> cache by representing metadata with negative block numbers, but that >>> is just UFS). Full journalling has many drawbacks from the viewpoint >>> of speed and complexity, of course. So you really want to be able to >>> do just metadata journalling. >>> >>> Another hard part of distinguishing between metadata and data is that >>> filesystems have a habit of migrating disk blocks from holding >>> metadata to holding data, and vice versa (think indirect pointer >>> blocks, not inode blocks). If you are only replaying metadata, you >>> want to make sure that you don't smash data blocks with old metadata. >>> >>> Coming up with a filesystem independent way to represent all of this >>> for the block layer is not easy. Filesystems would have to be able >>> to be modified to provide proper metadata vs. data hints to the block >>> layer. And if you're going to do that, then why not just make it a >>> library in VFS, like what Darwin does? >>> >>> The UFS Journalling work is already well underway, and I expect it to >>> follow the path of being a VFS library. Note that I'm saying >>> 'library' here, not 'layer'. There really is no way to make >>> journalling work with an arbitrary filesystem 'for free', whether as >>> a VFS layer or a GEOM transform, since journalling is 100% dependent >>> on the filesystem working with the buffer-cache to do sane operations >>> in a defined in order. >>> >>> An alternate SoC project that would be very useful is block-level >>> snapshots. I'm not sure if I'll be able to retain the filesystem >>> snapshot functionality in UFS with journalling enabled, so moving to >>> doing the snapshots in the block layer would be a good way to make up >>> for this. Beware that while the GEOM transform would be pretty >>> straight-forward to write, the real trick comes from being able to >>> make the consumer of a block device (a filesystem, maybe) flush >>> itself to a consistent state while the snapshot is being taken. The >>> infrastructure for this is the part that is very interesting, but >>> also the most work. >>> >>> Scott >> >> >> >> Scott, >> >> Have you looked at the journaling layer that Matt has been adding to >> DragonflyBSD? What you are talking about appears very similar. Or am >> I misunderstanding something? >> >> Richard Coleman >> rcoleman@criticalmagic.com > > > Ah, you might have misunderstood my use of the term 'VFS library'. This > is distinctly different from a 'VFS layer', which is what Matt did. > I've looked extensively at his work, but unfortunately it doesn't solve > the kinds of problems that I'm looking to solve. After discussing > journalling this evening with the author of BeFS and HFS+J, I'm pretty > happy that I'm taking the approach that I am. Maybe a good SoC project (but maybe too much work) would be getting the clustering UFS stuff going.. :) Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 03:51:20 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDB7A16A41C for ; Wed, 8 Jun 2005 03:51:20 +0000 (GMT) (envelope-from sydoh@fidalgo.net) Received: from proxy1.mtvwa.fidalgo.net (proxy2.mtvwa.fidalgo.net [66.218.206.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id B712D43D48 for ; Wed, 8 Jun 2005 03:51:20 +0000 (GMT) (envelope-from sydoh@fidalgo.net) Received: from [66.52.206.36] (port=3238 helo=huffakerw0m4f2) by proxy1.mtvwa.fidalgo.net with asmtp (Exim Citadel) id 1Dfrb5-0002vE-JW for hackers@freebsd.org; Tue, 07 Jun 2005 20:51:20 -0700 From: "Sydney Hole & Owen Huffaker" To: Date: Tue, 7 Jun 2005 20:50:50 -0700 Message-ID: <000001c56bdd$58f5b7d0$24ce3442@huffakerw0m4f2> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Authenticated-Sender: sydoh X-Mailman-Approved-At: Wed, 08 Jun 2005 12:06:31 +0000 Cc: Subject: Version 4.4 sick and dying X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sydoh@fidalgo.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 03:51:21 -0000 Hello, Wonder if you can give me a little advise. I don't have a background in freebsd. I maintained a Unix V5 system years ago and I have been called in to look at an installation that is ailing. This system is a 4.4 version that is acting as a web server. It has some web functionality on it which was refreshing unusually slow. They called me and I came in to look at it. I noticed that the logon was slow either directly on the console or through telnet. I suspected a hard drive issue. Since the system had been running for some time, I shut it down and I ran a hard drive test (Fujitsu drive and ran the proprietary fujitsu program) and it failed. No backup and no tape drive. They happen to have a few BSD books around so I figured out how to add a disk in place of the cdrom and I partition it with sysinstall. Then I used TAR and I copied all of the file systems to this new hard drive with exception of swap. Also I used the sysinstall and looked at the labels of the main (failing) drive and copied down all the sizes of the slices. I used a bsd 4.5 version on a separate machine I had lying around and was able to partition and slice/label a brand new drive with the same sizes as the old drive. My intentions were to copy the files to the new drive and then plug it in somehow. I thought I had some time. This all happened on Monday. Today the drive crashed. I am wondering what the best way to proceed. If I am thinking (but really sort of guessing) about this correct, the new machine has a 4.5 install on it and a drive that is sliced and labeled as per the original. I know this because during the install it let me do the partition and label and I took advantage of the opportunity. Does it make sense that I could put the backup drive in the new machine, and then mount it, copy all the files to the drive I partition and then maybe put the drive that I copied all the stuff to back in the original machine? But I don't know if I am going to run into trouble with existing files from the 4.5 install if they get overlayed or its going to be a big mess. I also noticed in one of the books about a fixit program on the cd. Would it be best to use that, mount both drives (newly partitioned and the backup) and copy stuff that way. The books don't go into the fixit much, just summary info. I am going to try this tomorrow morning and wondered if you might have some good advise. I do have a copy of BSD 4.5 and 5.o from a FreeBSD Unleashed book by Michael Urban and Brian Tieman. I also have the absolute BSD by Michael Lucas. Regards, Owen From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 12:13:24 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 196FF16A420 for ; Wed, 8 Jun 2005 12:13:24 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: from salvador.pacific.net.sg (salvador.pacific.net.sg [203.120.90.219]) by mx1.FreeBSD.org (Postfix) with SMTP id 2796543D49 for ; Wed, 8 Jun 2005 12:13:22 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 15168 invoked from network); 8 Jun 2005 12:13:21 -0000 Received: from unknown (HELO maxwell2.pacific.net.sg) (203.120.90.192) by salvador with SMTP; 8 Jun 2005 12:13:21 -0000 Received: from [192.168.0.107] ([210.24.246.101]) by maxwell2.pacific.net.sg with ESMTP id <20050608121321.JQPH1130.maxwell2.pacific.net.sg@[192.168.0.107]>; Wed, 8 Jun 2005 20:13:21 +0800 Message-ID: <42A6E0CD.90704@pacific.net.sg> Date: Wed, 08 Jun 2005 20:13:01 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050514) X-Accept-Language: en-us, en MIME-Version: 1.0 To: sydoh@fidalgo.net References: <000001c56bdd$58f5b7d0$24ce3442@huffakerw0m4f2> In-Reply-To: <000001c56bdd$58f5b7d0$24ce3442@huffakerw0m4f2> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Version 4.4 sick and dying X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 12:13:24 -0000 Hi, Sydney Hole & Owen Huffaker wrote: > Wonder if you can give me a little advise. > But not much more. > > I do have a copy of BSD 4.5 and 5.o from a FreeBSD Unleashed book by Michael > Urban and Brian Tieman. I also have the absolute BSD by Michael Lucas. > I would not touch them as they are really old. Can you download either 4.11 or 5.4, burn a CD and start from scratch? It would save you a lot of time as the original disk is dead anyway. All you could do is a copying the rescuded data over after the systems works again. I expect that it would be hard to find help here for older versions of FreeBSD. It should not be a problem to run the new versions on old hardware. Friends of mine do this all the time without any serious problems. Erich From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 12:21:27 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AF2A16A41F for ; Wed, 8 Jun 2005 12:21:27 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4068943D55 for ; Wed, 8 Jun 2005 12:21:25 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j58CLNLW020984; Wed, 8 Jun 2005 07:21:23 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42A6E2AC.9080300@centtech.com> Date: Wed, 08 Jun 2005 07:21:00 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: sydoh@fidalgo.net References: <000001c56bdd$58f5b7d0$24ce3442@huffakerw0m4f2> In-Reply-To: <000001c56bdd$58f5b7d0$24ce3442@huffakerw0m4f2> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/921/Wed Jun 8 03:51:44 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: hackers@freebsd.org Subject: Re: Version 4.4 sick and dying X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 12:21:27 -0000 Sydney Hole & Owen Huffaker wrote: > Hello, > Wonder if you can give me a little advise. [..snip..] > I am going to try this tomorrow morning and wondered if you might have some > good advise. > > I do have a copy of BSD 4.5 and 5.o from a FreeBSD Unleashed book by Michael > Urban and Brian Tieman. I also have the absolute BSD by Michael Lucas. Well, it's hard to say what the right path would be for you. I think if it were me, and I had tarred up all the files, I would install the most recent FreeBSD version I can (5.4 in this case), install all the necessary ports (/usr/ports/*), and then copy the data back from the 'backup' drive (you created when you did all the tars) onto the newly installed system in the right places. If you are totally new to FreeBSD, the Handbook is your best friend: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 14:16:50 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CED6116A41C; Wed, 8 Jun 2005 14:16:50 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71CD743D1F; Wed, 8 Jun 2005 14:16:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.0.2.2] ([12.174.84.3]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j58EMBrP067476; Wed, 8 Jun 2005 08:22:14 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42A6FD59.7060501@samsco.org> Date: Wed, 08 Jun 2005 08:14:49 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> <42A6091C.40409@samsco.org> <42A647B8.30709@criticalmagic.com> <42A69A69.2040005@samsco.org> <42A6DAB3.4080105@centtech.com> In-Reply-To: <42A6DAB3.4080105@centtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: Pawel Jakub Dawidek , scottl@freebsd.org, Ivan Voras , David Malone , hackers@freebsd.org, phk@freebsd.org, Richard Coleman Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 14:16:51 -0000 Eric Anderson wrote: > Scott Long wrote: > >> Richard Coleman wrote: >> >>> Scott Long wrote: >>> >>>> /me jumps up and down and waves his hands >>>> >>>> The problem with journalling at the block layer is that you pretty >>>> much become forced to journal metadata and data, since the block >>>> layer really doesn't know the distinction, and definitely not in a >>>> filesystem-independent way (yes, UFS does evil things to the buffer >>>> cache by representing metadata with negative block numbers, but that >>>> is just UFS). Full journalling has many drawbacks from the >>>> viewpoint of speed and complexity, of course. So you really want to >>>> be able to do just metadata journalling. >>>> >>>> Another hard part of distinguishing between metadata and data is >>>> that filesystems have a habit of migrating disk blocks from holding >>>> metadata to holding data, and vice versa (think indirect pointer >>>> blocks, not inode blocks). If you are only replaying metadata, you >>>> want to make sure that you don't smash data blocks with old metadata. >>>> >>>> Coming up with a filesystem independent way to represent all of this >>>> for the block layer is not easy. Filesystems would have to be able >>>> to be modified to provide proper metadata vs. data hints to the >>>> block layer. And if you're going to do that, then why not just make >>>> it a library in VFS, like what Darwin does? >>>> >>>> The UFS Journalling work is already well underway, and I expect it >>>> to follow the path of being a VFS library. Note that I'm saying >>>> 'library' here, not 'layer'. There really is no way to make >>>> journalling work with an arbitrary filesystem 'for free', whether as >>>> a VFS layer or a GEOM transform, since journalling is 100% dependent >>>> on the filesystem working with the buffer-cache to do sane >>>> operations in a defined in order. >>>> >>>> An alternate SoC project that would be very useful is block-level >>>> snapshots. I'm not sure if I'll be able to retain the filesystem >>>> snapshot functionality in UFS with journalling enabled, so moving to >>>> doing the snapshots in the block layer would be a good way to make >>>> up for this. Beware that while the GEOM transform would be pretty >>>> straight-forward to write, the real trick comes from being able to >>>> make the consumer of a block device (a filesystem, maybe) flush >>>> itself to a consistent state while the snapshot is being taken. The >>>> infrastructure for this is the part that is very interesting, but >>>> also the most work. >>>> >>>> Scott >>> >>> >>> >>> >>> Scott, >>> >>> Have you looked at the journaling layer that Matt has been adding to >>> DragonflyBSD? What you are talking about appears very similar. Or >>> am I misunderstanding something? >>> >>> Richard Coleman >>> rcoleman@criticalmagic.com >> >> >> >> Ah, you might have misunderstood my use of the term 'VFS library'. This >> is distinctly different from a 'VFS layer', which is what Matt did. >> I've looked extensively at his work, but unfortunately it doesn't solve >> the kinds of problems that I'm looking to solve. After discussing >> journalling this evening with the author of BeFS and HFS+J, I'm pretty >> happy that I'm taking the approach that I am. > > > Maybe a good SoC project (but maybe too much work) would be getting the > clustering UFS stuff going.. :) > > Eric > > > THat is more along the lines of a good master's of PhD topic. Scott From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 14:23:15 2005 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0310416A41C; Wed, 8 Jun 2005 14:23:15 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8613543D49; Wed, 8 Jun 2005 14:23:14 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.0.2.2] ([12.174.84.3]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j58ESm2c067534; Wed, 8 Jun 2005 08:28:52 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42A6FF04.706@samsco.org> Date: Wed, 08 Jun 2005 08:21:56 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ivan Voras References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> <42A6091C.40409@samsco.org> <42A6C311.5090400@fer.hr> In-Reply-To: <42A6C311.5090400@fer.hr> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: David Malone , scottl@FreeBSD.org, hackers@FreeBSD.org, Pawel Jakub Dawidek , phk@FreeBSD.org Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 14:23:15 -0000 Ivan Voras wrote: > Scott Long wrote: > >> An alternate SoC project that would be very useful is block-level >> snapshots. I'm not sure if I'll be able to retain the filesystem >> snapshot functionality in UFS with journalling enabled, so moving to >> doing the snapshots in the block layer would be a good way to make up >> for this. Beware that while the GEOM transform would be pretty > > > One addenum that was introduced after I made the post to hackers@, but > before sending a proposal to Google (PHK's idea, actually) is to > implement a delayed-commit mode, in which journaled data will not be > commited until requested. > > This would allow something like block-level snapshots, but one-shot only > (or at least one per journal). Again, I'm not exactly sure how a generic mechanism can handle the distinction of data vs. metadata vs. journal data. Also, what you need to delay is not the journal writes, but the metdata writes. In order for journal replay to work, the on-disk journal must always be ahead of the on-disk metadata, and the proper bookkeeping must be kept to track what sectors have been committed to the drive and what sectors haven't. Again, you simply don't get this 'for free'. Scott From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 16:11:21 2005 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DC6A16A41C; Wed, 8 Jun 2005 16:11:21 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE53A43D49; Wed, 8 Jun 2005 16:11:20 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id j58GDqpq009357; Wed, 8 Jun 2005 18:13:53 +0200 (MEST) Message-ID: <42A71865.4020906@fer.hr> Date: Wed, 08 Jun 2005 18:10:13 +0200 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> <42A6091C.40409@samsco.org> <42A6C311.5090400@fer.hr> <42A6FF04.706@samsco.org> In-Reply-To: <42A6FF04.706@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@FreeBSD.org, scottl@FreeBSD.org, phk@FreeBSD.org Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 16:11:21 -0000 Scott Long wrote: > Again, I'm not exactly sure how a generic mechanism can handle the > distinction of data vs. metadata vs. journal data. Also, what you I don't care about the distinction at this level - all data is treated equal :) From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 16:13:49 2005 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B422116A41F; Wed, 8 Jun 2005 16:13:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F54D43D1D; Wed, 8 Jun 2005 16:13:46 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.4.248.35] ([206.13.39.129]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j58GJO4p068165; Wed, 8 Jun 2005 10:19:25 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <42A718EF.30803@samsco.org> Date: Wed, 08 Jun 2005 10:12:31 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ivan Voras References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> <42A6091C.40409@samsco.org> <42A6C311.5090400@fer.hr> <42A6FF04.706@samsco.org> <42A71464.8070705@fer.hr> In-Reply-To: <42A71464.8070705@fer.hr> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: hackers@FreeBSD.org, scottl@FreeBSD.org, phk@FreeBSD.org Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 16:13:49 -0000 Ivan Voras wrote: > Scott Long wrote: > >> Again, I'm not exactly sure how a generic mechanism can handle the >> distinction of data vs. metadata vs. journal data. Also, what you > > > I don't care about the distinction at this level - all data is treated > equal. > But for journalling to work, you must care about the distinction. Scott From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 17:17:10 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A48EE16A41C for ; Wed, 8 Jun 2005 17:17:10 +0000 (GMT) (envelope-from brucem@mail.cruzio.com) Received: from cruzio.com (dsl3-63-249-85-132.cruzio.com [63.249.85.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F83743D48 for ; Wed, 8 Jun 2005 17:17:10 +0000 (GMT) (envelope-from brucem@mail.cruzio.com) Received: from mail.cruzio.com (localhost [127.0.0.1]) by cruzio.com (8.12.10/8.12.10) with ESMTP id j58GJL2P000349; Wed, 8 Jun 2005 09:19:21 -0700 (PDT) (envelope-from brucem@mail.cruzio.com) Received: (from brucem@localhost) by mail.cruzio.com (8.12.10/8.12.10/Submit) id j58GJIob000348; Wed, 8 Jun 2005 09:19:18 -0700 (PDT) (envelope-from brucem) Date: Wed, 8 Jun 2005 09:19:18 -0700 (PDT) From: "Bruce R. Montague" Message-Id: <200506081619.j58GJIob000348@mail.cruzio.com> To: hackers@freebsd.org Cc: scottl@samsco.org, ivoras@fer.hr Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 17:17:10 -0000 Scott Long wrote: >Again, I'm not exactly sure how a generic mechanism can handle the >distinction of data vs. metadata vs. journal data. Also, what you Ivan Voras wrote: >I don't care about the distinction at this level - all data is treated >equal. Scott Long wrote: >But for journalling to work, you must care about the distinction. Ivan, some recent PhD dissertations probably discuss some of the dragons lurking in this area. For instance, see the "thesis research" discussion and papers in: http://www.cs.wisc.edu/~muthian/ His paper "Life or Death at Block-Level" might be of interest... - bruce From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 17:39:20 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FB5216A42A for ; Wed, 8 Jun 2005 17:39:20 +0000 (GMT) (envelope-from shmukler@mail.ru) Received: from f29.mail.ru (f29.mail.ru [194.67.57.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F18943D49 for ; Wed, 8 Jun 2005 17:39:20 +0000 (GMT) (envelope-from shmukler@mail.ru) Received: from mail by f29.mail.ru with local id 1Dg4WM-0009UX-00; Wed, 08 Jun 2005 21:39:18 +0400 Received: from [24.185.244.192] by win.mail.ru with HTTP; Wed, 08 Jun 2005 21:39:18 +0400 From: Igor Shmukler To: qemu-devel@nongnu.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [24.185.244.192] Date: Wed, 08 Jun 2005 21:39:18 +0400 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Cc: hackers@freebsd.org Subject: debugging with Qemu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Igor Shmukler List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 17:39:20 -0000 Hello, We have tried to use qemu for debugging of kernel-level code the same way we used bochs in past. The qemu whether with or without kqemu is quite fast for our needs. The gdb connects to guest just fine, however breakpoints break things and qemu stops working. Our guest OS is FreeBSD 5.3. We would not need to use qemu if not for the problems 5.3 has with gdb. Any ideas what could we do besides using painfully slow bochs? Thank you in advance, Igor From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 18:05:50 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C541716A420 for ; Wed, 8 Jun 2005 18:05:50 +0000 (GMT) (envelope-from ups@tree.com) Received: from smtp.speedfactory.net (talon.speedfactory.net [66.23.216.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06BC043D55 for ; Wed, 8 Jun 2005 18:05:49 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 14116 invoked from network); 8 Jun 2005 19:01:45 +0000 Received: from 66-23-216-49.clients.speedfactory.net (HELO palm.tree.com) (66.23.216.49) by smtp.speedfactory.net with AES256-SHA encrypted SMTP; 8 Jun 2005 19:01:45 +0000 Received: from [127.0.0.1] (ups@localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id j58I5ipP086686; Wed, 8 Jun 2005 14:05:46 -0400 (EDT) (envelope-from ups@tree.com) From: Stephan Uphoff To: Scott Long In-Reply-To: <42A6091C.40409@samsco.org> References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> <42A6091C.40409@samsco.org> Content-Type: text/plain Message-Id: <1118253944.27369.35584.camel@palm> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 08 Jun 2005 14:05:44 -0400 Content-Transfer-Encoding: 7bit Cc: Pawel Jakub Dawidek , Scott Long , Ivan Voras , David Malone , hackers@freebsd.org, phk@freebsd.org Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 18:05:50 -0000 On Tue, 2005-06-07 at 16:52, Scott Long wrote: > David Malone wrote: > > On Tue, Jun 07, 2005 at 09:40:05PM +0200, Pawel Jakub Dawidek wrote: > > > >>+> Does it make sense to do it this way? Is it worth applying for the SoC? > >> > >>Not sure. Basically this is simlar what softupdate does, I think. > >>From another point of view softupdates are only available for UFS. > >>You probably wants to hear scottl and phk opinions (CCed). > > > > > > I think that Ivan's idea is kind of different from softupdates. His > > idea is pretty clever, in that it could provide synchronus random > > writes at sequential write speeds for any filesystem, providing you > > repaly the journal at startup. > > > > However, our main problem these days is the fact that we do an fsck > > after every unclean reboot, not the speed of writes. I guess that > > you could skip the fsck (or run it very slowly in the background) > > if you knew the filesystem was clean 'cos of jounral replay. > > > > David. > > /me jumps up and down and waves his hands > > The problem with journalling at the block layer is that you pretty much > become forced to journal metadata and data, since the block layer really > doesn't know the distinction, and definitely not in a > [ ... SNIP ...] In my opinion the original proposal described a non volatile write cache using dedicated cache disks. The proposed write cache implementation uses journaling. This does not offer additional guarantees to a file system and should not be confused with file system journaling / soft updates. Something like this has been on my wish list for a long time. A disk based write cache could easily accept short write bursts and reorder them later for more efficient writing (clustering?) to the final destination. ( Mirrored 15K SCSI write cache for big, fat slow RAID 5/6 SATA disk system) Support for nvram (micromemory comes to mind) cards would also be nice. Stephan From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 18:23:19 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D2BF16A41C for ; Wed, 8 Jun 2005 18:23:19 +0000 (GMT) (envelope-from valenok@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7FF843D53 for ; Wed, 8 Jun 2005 18:23:18 +0000 (GMT) (envelope-from valenok@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so361700wra for ; Wed, 08 Jun 2005 11:23:18 -0700 (PDT) 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:content-disposition; b=oCDRMcSYOHZZkYyj93SNQDCj44sgI/JwNBllpp5rJwS1zznsPwhyftixWfykdP0D7dfdDSSJyiRcvXF4gZYYC+9Y6RvZnV8R19ePtgvDdFLvaFpH/TThwkeU6Mx4Bn3qwvBcj9tN+Y1N+Onff8Csuu3U41Py7/AvLh7AbTWe92k= Received: by 10.54.50.12 with SMTP id x12mr4702988wrx; Wed, 08 Jun 2005 11:23:18 -0700 (PDT) Received: by 10.54.116.3 with HTTP; Wed, 8 Jun 2005 11:23:18 -0700 (PDT) Message-ID: <72c3a957050608112348e2f6ca@mail.gmail.com> Date: Wed, 8 Jun 2005 19:23:18 +0100 From: Sergey Lyubka To: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: freebsd 5.4 on HP DL 385 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sergey Lyubka List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 18:23:19 -0000 Hi hackers, I have got an HP DL 385 dual opteron system, with 2 on-board broadcom network cards. If I use more NICs, I have to have ACPI turned on. But if the ACPI is turned on, kernel does not boot, this is an error message: panic: npx: can't get ports Does anybody knows a solution for that ? Another strange problem I saw with DL 385 is when I boot a huge kernel (with embedded MFS), it panics. DDB shows that that happens to be in function nexus_get_resource(). Any ideas how to fight that ? sources are -stable 5.4 from 8 Jun 2005. system built for x86, so DL385 runs in x86 emulation mode. kernel config: silversoft.net/~devnull/MANAGER thanks, sergey From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 18:30:00 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 725DD16A41C for ; Wed, 8 Jun 2005 18:30:00 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2AE643D1F for ; Wed, 8 Jun 2005 18:29:59 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id j58IWWpq015710; Wed, 8 Jun 2005 20:32:32 +0200 (MEST) Message-ID: <42A738E4.5040506@fer.hr> Date: Wed, 08 Jun 2005 20:28:52 +0200 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0 (X11/20041213) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stephan Uphoff References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> <42A6091C.40409@samsco.org> <1118253944.27369.35584.camel@palm> In-Reply-To: <1118253944.27369.35584.camel@palm> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 18:30:00 -0000 Stephan Uphoff wrote: > In my opinion the original proposal described a non volatile write cache > using dedicated cache disks. Yes, I think that best describes what I have in mind. Here's the proposal that went to Google yesterday: http://geri.cc.fer.hr/~ivoras/proposal.pdf From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 18:38:45 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B91D16A41C for ; Wed, 8 Jun 2005 18:38:45 +0000 (GMT) (envelope-from julian@elischer.org) Received: from bigwoop.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCF9E43D49 for ; Wed, 8 Jun 2005 18:38:44 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [208.206.78.97] (julian.vicor-nb.com [208.206.78.97]) by bigwoop.vicor-nb.com (Postfix) with ESMTP id 9922B7A403; Wed, 8 Jun 2005 11:38:44 -0700 (PDT) Message-ID: <42A73B34.2050205@elischer.org> Date: Wed, 08 Jun 2005 11:38:44 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050423 X-Accept-Language: en, hu MIME-Version: 1.0 To: sydoh@fidalgo.net References: <000001c56bdd$58f5b7d0$24ce3442@huffakerw0m4f2> In-Reply-To: <000001c56bdd$58f5b7d0$24ce3442@huffakerw0m4f2> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Version 4.4 sick and dying X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 18:38:45 -0000 where (physically) are you? It is possible there is someone nearby that can help you.. Sydney Hole & Owen Huffaker wrote: >Hello, >Wonder if you can give me a little advise. > > > > [...] >Regards, >Owen > > > > From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 18:55:12 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 131D916A44F for ; Wed, 8 Jun 2005 18:55:12 +0000 (GMT) (envelope-from bakul@bitblocks.com) Received: from gate.bitblocks.com (bitblocks.com [209.204.185.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56F3F43D58 for ; Wed, 8 Jun 2005 18:55:08 +0000 (GMT) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost [127.0.0.1]) by gate.bitblocks.com (8.13.3/8.13.1) with ESMTP id j58It7m2087868; Wed, 8 Jun 2005 11:55:07 -0700 (PDT) (envelope-from bakul@bitblocks.com) Message-Id: <200506081855.j58It7m2087868@gate.bitblocks.com> To: Igor Shmukler In-reply-to: Your message of "Wed, 08 Jun 2005 21:39:18 +0400." Date: Wed, 08 Jun 2005 11:55:07 -0700 From: Bakul Shah Cc: hackers@freebsd.org, qemu-devel@nongnu.org Subject: Re: debugging with Qemu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 18:55:12 -0000 Hmm... I've used qemu a bit to debug the kernel. Even used it to debug a loadable module. Here is what I did: # qemu -s img # cd # gdb kernel.debug (gdb) target remote localhost:1234 ... (gdb) l kldload 739 /* 740 * MPSAFE 741 */ 742 int 743 kldload(struct thread *td, struct kldload_args *uap) 744 { 745 char *kldname, *modname; 746 char *pathname = NULL; 747 linker_file_t lf; 748 int error = 0; (gdb) b 743 (gdb) c Continuing. Breakpoint 3, kldload (td=0xc1419c00, uap=0xc8105d14) at /usr/src/sys/kern/kern_linker.c:744 744 { (gdb) c Continuing. ... ^C Program received signal 0, Signal 0. cpu_idle_default () at /usr/src/sys/i386/i386/machdep.c:1113 1113 } (gdb) detach Ending remote debugging. (gdb) q I am using kqemu and qemu built from May 2 snapshot if that matters. This was a stock 5.4-RELEASE complied locallly with makeoptions DEBUG=-g added the kernel config file. The host was also running 5.4 but that should not matter. May be if you describe the exact symptoms.... From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 19:45:01 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DF0C16A41C for ; Wed, 8 Jun 2005 19:45:01 +0000 (GMT) (envelope-from bakul@bitblocks.com) Received: from gate.bitblocks.com (bitblocks.com [209.204.185.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57F8743D1F for ; Wed, 8 Jun 2005 19:45:01 +0000 (GMT) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost [127.0.0.1]) by gate.bitblocks.com (8.13.3/8.13.1) with ESMTP id j58Jj0J3088231; Wed, 8 Jun 2005 12:45:00 -0700 (PDT) (envelope-from bakul@bitblocks.com) Message-Id: <200506081945.j58Jj0J3088231@gate.bitblocks.com> To: qemu-devel@nongnu.org In-reply-to: Your message of "Wed, 08 Jun 2005 11:55:07 PDT." <200506081855.j58It7m2087868@gate.bitblocks.com> Date: Wed, 08 Jun 2005 12:45:00 -0700 From: Bakul Shah Cc: hackers@freebsd.org Subject: Re: [Qemu-devel] Re: debugging with Qemu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 19:45:01 -0000 > I am using kqemu and qemu built from May 2 snapshot if that > matters. This was a stock 5.4-RELEASE complied locallly > with > > makeoptions DEBUG=-g > > added the kernel config file. The host was also running 5.4 > but that should not matter. Ugh... Should've done a diff with GENERIC since the options are needed for debugging: --- /sys/i386/conf/GENERIC Tue Apr 12 12:50:23 2005 +++ /sys/i386/conf/DUMBLEDORE Mon May 9 17:51:10 2005 @@ -58,6 +58,12 @@ # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. +options KDB +options DDB +options GDB +makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols + + device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 8 23:26:30 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E53916A41C for ; Wed, 8 Jun 2005 23:26:30 +0000 (GMT) (envelope-from davidc@acns.ab.ca) Received: from mail.acns.ab.ca (mail.acns.ab.ca [142.179.151.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13EA843D58 for ; Wed, 8 Jun 2005 23:26:29 +0000 (GMT) (envelope-from davidc@acns.ab.ca) Received: from ranger.acns.ab.ca (localhost [127.0.0.1]) by mail.acns.ab.ca (8.13.1/8.12.2) with ESMTP id j58NqLhV071631 for ; Wed, 8 Jun 2005 17:52:21 -0600 (MDT) (envelope-from davidc@ranger.acns.ab.ca) Received: (from davidc@localhost) by ranger.acns.ab.ca (8.13.1/8.12.9/Submit) id j58NqLJV071630 for freebsd-hackers@freebsd.org; Wed, 8 Jun 2005 17:52:21 -0600 (MDT) (envelope-from davidc) Date: Wed, 8 Jun 2005 17:52:21 -0600 From: Chad David To: freebsd-hackers@freebsd.org Message-ID: <20050608235221.GA71575@ranger.acns.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Bootable CDROM creation system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 23:26:30 -0000 My company built a tool a few years back for creating a bootable cdrom based on a running host FreeBSD 3/4 system, which promptly got shelved and forgotten.I recently had to update it for FreeBSD 5 and thought that perhaps the community at large could make use it before it gets forgotten again. The system is named 'shimmer', and basically all you need to do is type 'make shimmer' and it will create a bootable cd with everything you need to have a useless system that runs from single cdrom (usefulness is left as an exercise for the user). We are not at all interested in competing with groups like FreeSBIE, but are willing to support and help enhance some of the basic utilities and structure etc. if anybody is interested in using this stuff. http://www.issci.ca/chad/shimmer.tgz Comments and questions are welcome. -- Chad David From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 03:16:39 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDC5616A41C for ; Thu, 9 Jun 2005 03:16:39 +0000 (GMT) (envelope-from john@essenz.com) Received: from beck.quonix.net (beck.quonix.net [146.145.66.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 752C643D4C for ; Thu, 9 Jun 2005 03:16:39 +0000 (GMT) (envelope-from john@essenz.com) Received: from [192.168.1.100] (pool-71-242-16-137.phil.east.verizon.net [71.242.16.137]) by beck.quonix.net (8.13.4/8.13.4) with ESMTP id j593GMOS046492; Wed, 8 Jun 2005 23:16:22 -0400 (EDT) In-Reply-To: <000001c56bdd$58f5b7d0$24ce3442@huffakerw0m4f2> References: <000001c56bdd$58f5b7d0$24ce3442@huffakerw0m4f2> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: John Von Essen Date: Wed, 8 Jun 2005 23:14:10 -0400 To: " " X-Mailer: Apple Mail (2.622) X-SpamAssassin-3.0.3-Score: -2.82/5.8 ALL_TRUSTED X-MimeDefang-2.51: beck.quonix.net X-Scanned-By: MIMEDefang 2.51 on 146.145.66.90 Cc: Sydney Hole & Owen Huffaker Subject: Re: Version 4.4 sick and dying X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 03:16:39 -0000 If I understand your email correctly, you were able to get all the files tar'd up from the original system. And you put those tar's on a second hard drive that you mounted in the dying system, then a day later, the primary boot drive died. So right now you have a non-bootable drive formated with ufs containing tars of original system. If you want to salvage the old system, you could replace the boot drive, then re-install version 4.4. Then grab the tar files off the second drive. If you cant get 4.4 ISO off the FBSD ftp servers, I can send you the ISO's (I have all the CD's going back to 3.0). However, as others have mentioned, you dont need to go that route, especially if all this box did was run apache. As long as you can get the apache data (just htdocs or the whole apache install), you can just do a fresh install of 4.11, then dump your 4.4 apache files. (if your lucky, the entire apache install might be under /usr/local/apache - so you just have to copy one directory) Start apache binaries and your done. Or install 5.4, install and build a new apache from source or ports, then just copy over the htdocs and conf directories. As you mention in your email.... I would NOT recommend untarring your 4.4 files into a active 4.5 system. It only takes a few things to create a mess. Much easier just starting from scratch and restore apache, or install 4.4. -john von essen On Jun 7, 2005, at 11:50 PM, Sydney Hole & Owen Huffaker wrote: > Hello, > Wonder if you can give me a little advise. > > I don't have a background in freebsd. I maintained a Unix V5 system > years > ago and I have been called in to look at an installation that is > ailing. > This system is a 4.4 version that is acting as a web server. It has > some > web functionality on it which was refreshing unusually slow. They > called me > and I came in to look at it. I noticed that the logon was slow either > directly on the console or through telnet. I suspected a hard drive > issue. > Since the system had been running for some time, I shut it down and I > ran a > hard drive test (Fujitsu drive and ran the proprietary fujitsu > program) and > it failed. No backup and no tape drive. They happen to have a few BSD > books around so I figured out how to add a disk in place of the cdrom > and I > partition it with sysinstall. Then I used TAR and I copied all of the > file > systems to this new hard drive with exception of swap. Also I used the > sysinstall and looked at the labels of the main (failing) drive and > copied > down all the sizes of the slices. I used a bsd 4.5 version on a > separate > machine I had lying around and was able to partition and slice/label a > brand > new drive with the same sizes as the old drive. My intentions were to > copy > the files to the new drive and then plug it in somehow. I thought I > had > some time. This all happened on Monday. > > Today the drive crashed. I am wondering what the best way to proceed. > If I > am thinking (but really sort of guessing) about this correct, the new > machine has a 4.5 install on it and a drive that is sliced and labeled > as > per the original. I know this because during the install it let me do > the > partition and label and I took advantage of the opportunity. Does it > make > sense that I could put the backup drive in the new machine, and then > mount > it, copy all the files to the drive I partition and then maybe put the > drive > that I copied all the stuff to back in the original machine? But I > don't > know if I am going to run into trouble with existing files from the 4.5 > install if they get overlayed or its going to be a big mess. > > I also noticed in one of the books about a fixit program on the cd. > Would > it be best to use that, mount both drives (newly partitioned and the > backup) > and copy stuff that way. The books don't go into the fixit much, just > summary info. > > I am going to try this tomorrow morning and wondered if you might have > some > good advise. > > I do have a copy of BSD 4.5 and 5.o from a FreeBSD Unleashed book by > Michael > Urban and Brian Tieman. I also have the absolute BSD by Michael Lucas. > > Regards, > Owen > > > _______________________________________________ > 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-hackers@FreeBSD.ORG Thu Jun 9 06:36:07 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE96516A41C for ; Thu, 9 Jun 2005 06:36:07 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DF7043D1D for ; Thu, 9 Jun 2005 06:36:07 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id BD4ED60F3; Thu, 9 Jun 2005 08:35:59 +0200 (CEST) Received: from xps.des.no (des.no [80.203.228.37]) by tim.des.no (Postfix) with ESMTP id A1EEE60F2; Thu, 9 Jun 2005 08:35:59 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 87E5333C3B; Thu, 9 Jun 2005 08:35:59 +0200 (CEST) To: Chad David References: <20050608235221.GA71575@ranger.acns.ab.ca> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Thu, 09 Jun 2005 08:35:59 +0200 In-Reply-To: <20050608235221.GA71575@ranger.acns.ab.ca> (Chad David's message of "Wed, 8 Jun 2005 17:52:21 -0600") Message-ID: <86ll5kdokw.fsf@xps.des.no> 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 3.0.2 (2004-11-16) on tim.des.no X-Spam-Level: X-Spam-Status: No, score=-5.1 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.2 Cc: freebsd-hackers@freebsd.org Subject: Re: Bootable CDROM creation system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 06:36:07 -0000 Chad David writes: > My company built a tool a few years back for creating a bootable cdrom > based on a running host FreeBSD 3/4 system, which promptly got shelved and > forgotten.I recently had to update it for FreeBSD 5 and thought that > perhaps the community at large could make use it before it gets forgotten > again. # cd /usr/src # make buildworld buildkernel # mkdir /tmp/cdrom # make installworld installkernel DESTDIR=3D/tmp/cdrom # cd /usr/src/etc # make distribution DESTDIR=3D/tmp/cdrom # mkisofs -o /tmp/cdrom.iso -r -no-emul-boot -b /tmp/cdrom/boot/cdboot /tmp= /cdrom # burncd -s max data /tmp/cdrom.iso fixate eject did I leave anything out? DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 07:46:35 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E38AC16A41C for ; Thu, 9 Jun 2005 07:46:35 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CC5443D1D for ; Thu, 9 Jun 2005 07:46: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 j597kO0e057057; Thu, 9 Jun 2005 10:46:24 +0300 (EEST) (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 84093-16; Thu, 9 Jun 2005 10:46:24 +0300 (EEST) 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 j597kOVg057054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Jun 2005 10:46:24 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.3/8.13.3) id j597kpOT029071; Thu, 9 Jun 2005 10:46:51 +0300 (EEST) (envelope-from ru) Date: Thu, 9 Jun 2005 10:46:51 +0300 From: Ruslan Ermilov To: Dag-Erling Sm?rgrav Message-ID: <20050609074651.GC25346@ip.net.ua> References: <20050608235221.GA71575@ranger.acns.ab.ca> <86ll5kdokw.fsf@xps.des.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TYecfFk8j8mZq+dy" Content-Disposition: inline In-Reply-To: <86ll5kdokw.fsf@xps.des.no> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: freebsd-hackers@freebsd.org Subject: Re: Bootable CDROM creation system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 07:46:36 -0000 --TYecfFk8j8mZq+dy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 09, 2005 at 08:35:59AM +0200, Dag-Erling Sm?rgrav wrote: > Chad David writes: > > My company built a tool a few years back for creating a bootable cdrom > > based on a running host FreeBSD 3/4 system, which promptly got shelved = and > > forgotten.I recently had to update it for FreeBSD 5 and thought that > > perhaps the community at large could make use it before it gets forgott= en > > again. >=20 > # cd /usr/src > # make buildworld buildkernel > # mkdir /tmp/cdrom > # make installworld installkernel DESTDIR=3D/tmp/cdrom > # cd /usr/src/etc > # make distribution DESTDIR=3D/tmp/cdrom > # mkisofs -o /tmp/cdrom.iso -r -no-emul-boot -b /tmp/cdrom/boot/cdboot /t= mp/cdrom > # burncd -s max data /tmp/cdrom.iso fixate eject >=20 > did I leave anything out? >=20 :-) --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --TYecfFk8j8mZq+dy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCp/PrqRfpzJluFF4RAs9eAJ9qjcWF5FJEfVQkKDQ/TeYiq117YACfQsSp cXnIKz/PKbA+WGmB6iJDo+k= =AjDN -----END PGP SIGNATURE----- --TYecfFk8j8mZq+dy-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 13:32:25 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE03716A41C for ; Thu, 9 Jun 2005 13:32:25 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from s-utl01-sjpop.stsn.net (s-utl01-sjpop.stsn.net [72.254.0.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 846EE43D1F for ; Thu, 9 Jun 2005 13:32:25 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from s-utl01-sjpop.stsn.net ([127.0.0.1]) by s-utl01-sjpop.stsn.net (SMSSMTP 4.0.0.59) with SMTP id M2005060906322524175 ; Thu, 09 Jun 2005 06:32:25 -0700 Received: from [10.0.1.5] ([10.1.191.21]) by s-utl01-sjpop.stsn.net; Thu, 9 Jun 2005 06:32:22 -0700 In-Reply-To: <20050520224928.GI2129@cirb503493.alcatel.com.au> References: <200505201340.36176.hselasky@c2i.net> <428E12B0.9020208@samsco.org> <20050520173236.GG1201@green.homeunix.org> <200505202151.35831.hselasky@c2i.net> <20050520224928.GI2129@cirb503493.alcatel.com.au> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1bc2efb62d58b3be72efe326781aee70@FreeBSD.org> Content-Transfer-Encoding: 7bit From: John Baldwin Date: Thu, 9 Jun 2005 06:31:13 -0700 To: Peter Jeremy X-Mailer: Apple Mail (2.622) Cc: hackers@freebsd.org, Hans Petter Selasky Subject: Re: problems with new the "contigmalloc" routine X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 13:32:25 -0000 On May 20, 2005, at 3:49 PM, Peter Jeremy wrote: > On Fri, 2005-May-20 21:51:34 +0200, Hans Petter Selasky wrote: >> Can anyone explain why "uiomove()" has to sleep, and why there is no >> non-blocking "uiomove()"? > > As far as I can see, uiomove() only sleeps if it is asked to do a > kernel<->userland move that takes more than twice a scheduler quantum. > As long as you don't uiomove() ridiculous amounts of data, it should > never sleep. It can also sleep if it is reading from or writing to user memory if any of that memory needs to be faulted in. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 13:43:33 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D16B316A41C for ; Thu, 9 Jun 2005 13:43:33 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from server.absolute-media.de (server.absolute-media.de [213.239.231.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75C0043D48 for ; Thu, 9 Jun 2005 13:43:32 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from localhost (unknown [127.0.0.1]) by server.absolute-media.de (Postfix) with ESMTP id 671C680C68 for ; Thu, 9 Jun 2005 15:43:30 +0200 (CEST) Received: from server.absolute-media.de ([127.0.0.1]) by localhost (server [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31445-07 for ; Thu, 9 Jun 2005 15:43:25 +0200 (CEST) Received: from firewall.demig (p50839768.dip0.t-ipconnect.de [80.131.151.104]) by server.absolute-media.de (Postfix) with ESMTP id 9C51480A01 for ; Thu, 9 Jun 2005 15:43:25 +0200 (CEST) Received: from ws-ew-3 (ws-ew-3.w2kdemig [192.168.1.72]) by firewall.demig (8.13.4/8.13.1) with SMTP id j59DftiT046625 for ; Thu, 9 Jun 2005 15:41:55 +0200 (CEST) (envelope-from NKoch@demig.de) From: "Norbert Koch" To: "Freebsd-Hackers@Freebsd. Org" Date: Thu, 9 Jun 2005 15:41:55 +0200 Message-ID: <000001c56cf8$fffeb920$4801a8c0@ws-ew-3.W2KDEMIG> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at absolute-media.de Subject: usbd.conf: detach ukbd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 13:43:33 -0000 Hello, when running usbd (under FreeBSD 4.11) with -dv switches I can see that a usb keyboard correctly attaches as ukbd0, but detaches as fall-through "USB device". Do I just have to live with that fact or can I change that anyhow? Is that a device/device-class specific problem? Thank you, Norbert From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 14:29:50 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0BD516A41C for ; Thu, 9 Jun 2005 14:29:50 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FE1643D53 for ; Thu, 9 Jun 2005 14:29:49 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-205-88.daxnet.no ([193.217.205.88] verified) by mailfe05.swip.net (CommuniGate Pro SMTP 4.3.2) with ESMTP id 193480527; Thu, 09 Jun 2005 16:29:48 +0200 From: Hans Petter Selasky To: "Norbert Koch" , "Freebsd-Hackers@Freebsd.Org" Date: Thu, 9 Jun 2005 16:30:36 +0200 User-Agent: KMail/1.7 References: <000001c56cf8$fffeb920$4801a8c0@ws-ew-3.W2KDEMIG> In-Reply-To: <000001c56cf8$fffeb920$4801a8c0@ws-ew-3.W2KDEMIG> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200506091630.39439.hselasky@c2i.net> Cc: Subject: Re: usbd.conf: detach ukbd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 14:29:50 -0000 On Thursday 09 June 2005 15:41, Norbert Koch wrote: > Hello, > > when running usbd (under FreeBSD 4.11) with > -dv switches I can see that a usb keyboard > correctly attaches as ukbd0, > but detaches as fall-through "USB device". "usbd" is going to be replaced by "devd". "devd" will catch when the keyboard device detaches. --HPS From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 15:08:33 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BEB316A41C for ; Thu, 9 Jun 2005 15:08:33 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from server.absolute-media.de (server.absolute-media.de [213.239.231.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id C161E43D55 for ; Thu, 9 Jun 2005 15:08:32 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from localhost (unknown [127.0.0.1]) by server.absolute-media.de (Postfix) with ESMTP id 1C42C80E77 for ; Thu, 9 Jun 2005 17:08:30 +0200 (CEST) Received: from server.absolute-media.de ([127.0.0.1]) by localhost (server [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07135-07 for ; Thu, 9 Jun 2005 17:08:25 +0200 (CEST) Received: from firewall.demig (p50839768.dip0.t-ipconnect.de [80.131.151.104]) by server.absolute-media.de (Postfix) with ESMTP id 5832780DF7 for ; Thu, 9 Jun 2005 17:08:25 +0200 (CEST) Received: from ws-ew-3 (ws-ew-3.w2kdemig [192.168.1.72]) by firewall.demig (8.13.4/8.13.1) with SMTP id j59F3gLo050579 for ; Thu, 9 Jun 2005 17:03:42 +0200 (CEST) (envelope-from NKoch@demig.de) From: "Norbert Koch" To: "Freebsd-Hackers@Freebsd.Org" Date: Thu, 9 Jun 2005 17:03:42 +0200 Message-ID: <000101c56d04$6ce3eaa0$4801a8c0@ws-ew-3.W2KDEMIG> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 In-Reply-To: <200506091630.39439.hselasky@c2i.net> Importance: Normal X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at absolute-media.de Subject: RE: usbd.conf: detach ukbd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 15:08:33 -0000 > -----Original Message----- > From: Hans Petter Selasky [mailto:hselasky@c2i.net] > Sent: Thursday, June 09, 2005 4:31 PM > To: Norbert Koch; Freebsd-Hackers@Freebsd.Org > Subject: Re: usbd.conf: detach ukbd > > > On Thursday 09 June 2005 15:41, Norbert Koch wrote: > > Hello, > > > > when running usbd (under FreeBSD 4.11) with > > -dv switches I can see that a usb keyboard > > correctly attaches as ukbd0, > > but detaches as fall-through "USB device". > > "usbd" is going to be replaced by "devd". "devd" will catch when > the keyboard > device detaches. > > --HPS > I know, but I need to solve that problem for FreeBSD 4.X. From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 15:44:28 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8CAC16A41C for ; Thu, 9 Jun 2005 15:44:28 +0000 (GMT) (envelope-from davidc@acns.ab.ca) Received: from mail.acns.ab.ca (mail.acns.ab.ca [142.179.151.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6838F43D1F for ; Thu, 9 Jun 2005 15:44:28 +0000 (GMT) (envelope-from davidc@acns.ab.ca) Received: from ranger.acns.ab.ca (localhost [127.0.0.1]) by mail.acns.ab.ca (8.13.1/8.12.2) with ESMTP id j59GAFkF079011; Thu, 9 Jun 2005 10:10:15 -0600 (MDT) (envelope-from davidc@ranger.acns.ab.ca) Received: (from davidc@localhost) by ranger.acns.ab.ca (8.13.1/8.12.9/Submit) id j59GAFrh079010; Thu, 9 Jun 2005 10:10:15 -0600 (MDT) (envelope-from davidc) Date: Thu, 9 Jun 2005 10:10:15 -0600 From: Chad David To: Dag-Erling Sm?rgrav Message-ID: <20050609161015.GA78763@ranger.acns.ab.ca> References: <20050608235221.GA71575@ranger.acns.ab.ca> <86ll5kdokw.fsf@xps.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86ll5kdokw.fsf@xps.des.no> User-Agent: Mutt/1.4.1i Cc: freebsd-hackers@freebsd.org Subject: Re: Bootable CDROM creation system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 15:44:28 -0000 On Thu, Jun 09, 2005 at 08:35:59AM +0200, Dag-Erling Sm?rgrav wrote: > Chad David writes: > > My company built a tool a few years back for creating a bootable cdrom > > based on a running host FreeBSD 3/4 system, which promptly got shelved and > > forgotten.I recently had to update it for FreeBSD 5 and thought that > > perhaps the community at large could make use it before it gets forgotten > > again. > > # cd /usr/src > # make buildworld buildkernel > # mkdir /tmp/cdrom > # make installworld installkernel DESTDIR=/tmp/cdrom > # cd /usr/src/etc > # make distribution DESTDIR=/tmp/cdrom > # mkisofs -o /tmp/cdrom.iso -r -no-emul-boot -b /tmp/cdrom/boot/cdboot /tmp/cdrom > # burncd -s max data /tmp/cdrom.iso fixate eject > > did I leave anything out? No, not if the intention is to build a FreeBSD distribution; however, the point of shimmer is to build something a little more custom. What I posted begins to break the various parts of the system down into packages, and only installs what is required to boot and be minimally useful. mktree allow us to package things into more complex groupings to build different custom 'distributions' from a single shimmer tree. I didn't clame it was going to change the world, only that I would like to see someone benefit from my work. Did you actually look at what was there? -- Chad David davidc@acns.ab.ca ACNS Inc. Calgary, Alberta Canada From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 15:49:50 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 481C016A41C for ; Thu, 9 Jun 2005 15:49:50 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (berlin-qwest.village.org [168.103.84.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85D7043D48 for ; Thu, 9 Jun 2005 15:49:49 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j59Flj1e034936; Thu, 9 Jun 2005 09:47:46 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 09 Jun 2005 09:48:40 -0600 (MDT) Message-Id: <20050609.094840.90705479.imp@bsdimp.com> To: hselasky@c2i.net From: "M. Warner Losh" In-Reply-To: <200506091630.39439.hselasky@c2i.net> References: <000001c56cf8$fffeb920$4801a8c0@ws-ew-3.W2KDEMIG> <200506091630.39439.hselasky@c2i.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: NKoch@demig.de, freebsd-hackers@freebsd.org Subject: Re: usbd.conf: detach ukbd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 15:49:50 -0000 In message: <200506091630.39439.hselasky@c2i.net> Hans Petter Selasky writes: : On Thursday 09 June 2005 15:41, Norbert Koch wrote: : > Hello, : > : > when running usbd (under FreeBSD 4.11) with : > -dv switches I can see that a usb keyboard : > correctly attaches as ukbd0, : > but detaches as fall-through "USB device". : : "usbd" is going to be replaced by "devd". "devd" will catch when the keyboard : device detaches. devd doesn't exist on 4.x. Warner From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 15:50:20 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13BE916A41F for ; Thu, 9 Jun 2005 15:50:20 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B5A943D48 for ; Thu, 9 Jun 2005 15:50:19 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 91FAC3BF89; Thu, 9 Jun 2005 10:50:18 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 26360-01-39; Thu, 9 Jun 2005 10:50:18 -0500 (CDT) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45]) by mailgate1b.savvis.net (Postfix) with ESMTP id 67AA53BE82; Thu, 9 Jun 2005 10:50:18 -0500 (CDT) Received: from s228130hz1ew171.apptix-01.savvis.net ([10.146.4.29]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 9 Jun 2005 10:50:16 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew171.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 9 Jun 2005 10:50:02 -0500 Message-ID: <42A86529.5020103@savvis.net> Date: Thu, 09 Jun 2005 08:50:01 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Norbert Koch References: <000001c56cf8$fffeb920$4801a8c0@ws-ew-3.W2KDEMIG> In-Reply-To: <000001c56cf8$fffeb920$4801a8c0@ws-ew-3.W2KDEMIG> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 09 Jun 2005 15:50:02.0807 (UTC) FILETIME=[E622D470:01C56D0A] X-Virus-Scanned: amavisd-new at savvis.net Cc: "Freebsd-Hackers@Freebsd. Org" Subject: Re: usbd.conf: detach ukbd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 15:50:20 -0000 Norbert, > when running usbd (under FreeBSD 4.11) with > -dv switches I can see that a usb keyboard > correctly attaches as ukbd0, > but detaches as fall-through "USB device". can you please tell what is in your /etc/usbd.conf? > Do I just have to live with that fact or can > I change that anyhow? Is that a device/device-class > specific problem? does something like device "USB keyboard" devname "ukbd[0-9]+" attach "foo" detach "bar" work? note: please replace "foo" and "bar" with actual commands you want to be executed. thanks, max From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 16:00:01 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E874916A41C for ; Thu, 9 Jun 2005 16:00:01 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AEBA43D48 for ; Thu, 9 Jun 2005 16:00:00 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id j59FxiqU026912; Thu, 9 Jun 2005 18:59:45 +0300 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) by orion.daedalusnetworks.priv (8.13.4/8.13.4) with ESMTP id j59FxgN7070651; Thu, 9 Jun 2005 18:59:42 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by orion.daedalusnetworks.priv (8.13.4/8.13.4/Submit) id j59FxghA070650; Thu, 9 Jun 2005 18:59:42 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Thu, 9 Jun 2005 18:59:42 +0300 From: Giorgos Keramidas To: Dag-Erling Sm?rgrav Message-ID: <20050609155941.GA70079@orion.daedalusnetworks.priv> References: <20050608235221.GA71575@ranger.acns.ab.ca> <86ll5kdokw.fsf@xps.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86ll5kdokw.fsf@xps.des.no> Cc: freebsd-hackers@freebsd.org Subject: Re: Bootable CDROM creation system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 16:00:02 -0000 On 2005-06-09 08:35, Dag-Erling Sm?rgrav wrote: > Chad David writes: > > My company built a tool a few years back for creating a bootable cdrom > > based on a running host FreeBSD 3/4 system, which promptly got shelved and > > forgotten.I recently had to update it for FreeBSD 5 and thought that > > perhaps the community at large could make use it before it gets forgotten > > again. > > # cd /usr/src > # make buildworld buildkernel > # mkdir /tmp/cdrom > # make installworld installkernel DESTDIR=/tmp/cdrom > # cd /usr/src/etc > # make distribution DESTDIR=/tmp/cdrom > # mkisofs -o /tmp/cdrom.iso -r -no-emul-boot -b /tmp/cdrom/boot/cdboot /tmp/cdrom > # burncd -s max data /tmp/cdrom.iso fixate eject > > did I leave anything out? For completion's shake, before installkernel one may have to run: # cp /usr/src/sys//conf/GENERIC.hints /tmp/cdrom/boot/device.hints and then a minor nit. The -b /tmp/cdrom/boot/cdboot option should be relative to the CD-ROM root directory. Otherwise mkisofs complains and aborts. But yeah, this is a great mini-guide for making a bootable CD :) From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 16:25:21 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9203216A41C; Thu, 9 Jun 2005 16:25:21 +0000 (GMT) (envelope-from davidc@acns.ab.ca) Received: from mail.acns.ab.ca (mail.acns.ab.ca [142.179.151.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CE5743D48; Thu, 9 Jun 2005 16:25:21 +0000 (GMT) (envelope-from davidc@acns.ab.ca) Received: from ranger.acns.ab.ca (localhost [127.0.0.1]) by mail.acns.ab.ca (8.13.1/8.12.2) with ESMTP id j59GpBoT079558; Thu, 9 Jun 2005 10:51:11 -0600 (MDT) (envelope-from davidc@ranger.acns.ab.ca) Received: (from davidc@localhost) by ranger.acns.ab.ca (8.13.1/8.12.9/Submit) id j59GpBhj079557; Thu, 9 Jun 2005 10:51:11 -0600 (MDT) (envelope-from davidc) Date: Thu, 9 Jun 2005 10:51:11 -0600 From: Chad David To: Giorgos Keramidas Message-ID: <20050609165111.GB79470@ranger.acns.ab.ca> References: <20050608235221.GA71575@ranger.acns.ab.ca> <86ll5kdokw.fsf@xps.des.no> <20050609155941.GA70079@orion.daedalusnetworks.priv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050609155941.GA70079@orion.daedalusnetworks.priv> User-Agent: Mutt/1.4.1i Cc: Dag-Erling Sm?rgrav , freebsd-hackers@freebsd.org Subject: Re: Bootable CDROM creation system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 16:25:21 -0000 On Thu, Jun 09, 2005 at 06:59:42PM +0300, Giorgos Keramidas wrote: > On 2005-06-09 08:35, Dag-Erling Sm?rgrav wrote: > > Chad David writes: > > > My company built a tool a few years back for creating a bootable cdrom > > > based on a running host FreeBSD 3/4 system, which promptly got shelved and > > > forgotten.I recently had to update it for FreeBSD 5 and thought that > > > perhaps the community at large could make use it before it gets forgotten > > > again. > > > > # cd /usr/src > > # make buildworld buildkernel > > # mkdir /tmp/cdrom > > # make installworld installkernel DESTDIR=/tmp/cdrom > > # cd /usr/src/etc > > # make distribution DESTDIR=/tmp/cdrom > > # mkisofs -o /tmp/cdrom.iso -r -no-emul-boot -b /tmp/cdrom/boot/cdboot /tmp/cdrom > > # burncd -s max data /tmp/cdrom.iso fixate eject > > > > did I leave anything out? > > For completion's shake, before installkernel one may have to run: > > # cp /usr/src/sys//conf/GENERIC.hints /tmp/cdrom/boot/device.hints > > and then a minor nit. The -b /tmp/cdrom/boot/cdboot option should be > relative to the CD-ROM root directory. Otherwise mkisofs complains and > aborts. > > But yeah, this is a great mini-guide for making a bootable CD :) At least my post was a catalyst for something positive, however unintended ;). -- Chad David davidc@acns.ab.ca ACNS Inc. Calgary, Alberta Canada From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 20:24:01 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4313F16A41C for ; Thu, 9 Jun 2005 20:24:01 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id C862543D1D for ; Thu, 9 Jun 2005 20:24:00 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-206-17.daxnet.no ([193.217.206.17] verified) by mailfe07.swip.net (CommuniGate Pro SMTP 4.3.2) with ESMTP id 193820501; Thu, 09 Jun 2005 22:23:58 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Thu, 9 Jun 2005 22:24:46 +0200 User-Agent: KMail/1.7 References: <000001c56cf8$fffeb920$4801a8c0@ws-ew-3.W2KDEMIG> <42A86529.5020103@savvis.net> In-Reply-To: <42A86529.5020103@savvis.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200506092224.50203.hselasky@c2i.net> Cc: Norbert Koch Subject: Re: usbd.conf: detach ukbd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 20:24:01 -0000 On Thursday 09 June 2005 17:50, Maksim Yevmenkin wrote: > Norbert, > > > when running usbd (under FreeBSD 4.11) with > > -dv switches I can see that a usb keyboard > > correctly attaches as ukbd0, > > but detaches as fall-through "USB device". > > does something like > > device "USB keyboard" > devname "ukbd[0-9]+" > attach "foo" > detach "bar" > I'm not sure if detach is supported like that, because the "ukbd" device name will not be passed to "usbd" during detach. Then one needs to match against the class/subclass of the USB-keyboard: device "USB keyboard" class 3 subclass 1 detach "xxxx ukbd0" Else if devd is not available on 4.11 you will have to change some code and compile a new kernel, from what I can see. To the file /sys/dev/usb/ukbd.c add this: static void usbd_add_device_detach_event(device_t self) { struct usb_event ue; bzero(&ue, sizeof(ue)); strlcpy(ue.u.ue_device.udi_devnames[0], device_get_nameunit(self), USB_MAX_DEVNAMELEN) ; usb_add_event(USB_EVENT_DEVICE_DETACH, &ue); return; } ukbd_detach() { ... usbd_add_device_detach_event(self); return (0); } This will make the suggestion from Maksim work. A generic solution would be to call "usbd_add_device_detach_event()" from the "bus_child_detached" method of uhub, which must be added. Also one can change "usb_disconnect_port()" to generate the event before the sub-devices are detached, but that might not work in all cases. --HPS From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 9 21:42:17 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9574716A41C for ; Thu, 9 Jun 2005 21:42:17 +0000 (GMT) (envelope-from french.linuxian@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id C88E143D55 for ; Thu, 9 Jun 2005 21:42:16 +0000 (GMT) (envelope-from french.linuxian@gmail.com) Received: by zproxy.gmail.com with SMTP id 12so123369nzp for ; Thu, 09 Jun 2005 14:42:16 -0700 (PDT) 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:content-disposition; b=PILJNZ1v3iTIK9b8juHQNbIrv7yqkcWaSCLBq2MrIm1uBFZLhQMIIYf9FNtTHAFNqD3X+VOaHsO89e4GxtfPxUNnc7M8Jdpb6cRGQjLdjU0rXiihWYOihbRNeTCi9VbcnSgI+dR0ZuOjON8CnydZW9aW18Ur00Gs0V9IrkIFr6w= Received: by 10.36.222.42 with SMTP id u42mr773775nzg; Thu, 09 Jun 2005 14:42:16 -0700 (PDT) Received: by 10.36.58.12 with HTTP; Thu, 9 Jun 2005 14:42:16 -0700 (PDT) Message-ID: <37273927050609144244862086@mail.gmail.com> Date: Thu, 9 Jun 2005 17:42:16 -0400 From: Aziz Kezzou To: freebsd-hackers , freebsd-net Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: How to do a routing lookup inside the kernel in FreeBSD ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Aziz Kezzou List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 21:42:17 -0000 Hi all, I am trying to figure out from the kernel source code (FreeBSD 5.3) how can I perform a routing lookup in a KLD module. Since I am short in time, if anyone knows how do to do this I would appreciate. Any pointers to the right portion of the code are also apperciated. Thanks, -aziz From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 01:58:53 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE46416A41F for ; Fri, 10 Jun 2005 01:58:53 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70D5443D1D for ; Fri, 10 Jun 2005 01:58:53 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from SMILEY (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 552A319F3B for ; Thu, 9 Jun 2005 19:00:12 -0700 (PDT) From: "Darren Pilgrim" To: Date: Thu, 9 Jun 2005 18:58:44 -0700 Message-ID: <000001c56d5f$efe5c260$0a2a15ac@SMILEY> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Subject: Determining disk device and kicking GEOM when doing automatic mounting of umass devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 01:58:53 -0000 I want to have a devd entry that automatically mounts umass devices when they get attached. The problem is figuring out which device to mount = and then getting the correct devices created. For example, the entry for my thumbdrive: attach 1000 { device-name "umass[0-9]+"; match "vendor" "0x08ec"; match "product" "0x0015"; match "sernum" "0C50935151F0EA20"; action "$scripts/mount_umass.sh $device-name msdosfs /stickdrive"; }; The mount_umass.sh script is as follows: ---BEGIN FILE--- sleep 10 scsidev=3D"`echo ${1} | sed s/umass/umass-sim/g`" diskdev=3D"`camcontrol devlist -v | grep -A 1 ${scsidev} | tail -n 1 | \ awk -F "(" '{ print $2 }' | awk -F "," '{ print $1 }'`" fstype=3D"${2}" mountpoint=3D"${3}" mount -t ${fstype} /dev/${diskdev} ${mountpoint} 2>/dev/null mount -t ${fstype} /dev/${diskdev}s1 ${mountpoint} 2>/dev/null ----END FILE---- First, the script has to sleep because the device doesn't immediately = show up in the CAM device list. After waiting long enough to be safe, the = script takes the device name passed by devd and uses it to parse the device = name from the output of `camcontrol devlist`. GEOM doesn't automatically = read the partition table and create the slice device, so the script forces it = to do so by trying to mount the base device before mounting the actual partition. These tricks are ridiculous, IMO. There has to be a more intelligent = means of going about this. How do I get the scsi disk device name created for = a umass device as soon as it's created? How do I inform GEOM that it = needs to add a new MBR to it's configuration and create the appropriate = /dev/da?s* devices? From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 05:34:53 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E842C16A41C for ; Fri, 10 Jun 2005 05:34:53 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (berlin-qwest.village.org [168.103.84.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1345543D49 for ; Fri, 10 Jun 2005 05:34:52 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j5A5XRwu043151; Thu, 9 Jun 2005 23:33:27 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 09 Jun 2005 23:34:24 -0600 (MDT) Message-Id: <20050609.233424.42500001.imp@bsdimp.com> To: dmp@bitfreak.org From: "M. Warner Losh" In-Reply-To: <000001c56d5f$efe5c260$0a2a15ac@SMILEY> References: <000001c56d5f$efe5c260$0a2a15ac@SMILEY> 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: freebsd-hackers@freebsd.org Subject: Re: Determining disk device and kicking GEOM when doing automatic mounting of umass devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 05:34:54 -0000 In message: <000001c56d5f$efe5c260$0a2a15ac@SMILEY> "Darren Pilgrim" writes: : These tricks are ridiculous, IMO. There has to be a more intelligent means : of going about this. How do I get the scsi disk device name created for a : umass device as soon as it's created? How do I inform GEOM that it needs to : add a new MBR to it's configuration and create the appropriate /dev/da?s* : devices? One way is to make devd grok devices arriving and leaving from /dev. One could kludge it to send out geom events, but I think that's insufficiently general since it reports too many things that aren't of interest. Of course, you have no way of knowing what entries in /dev really are, apart from pattern matching. As to your second question, GEOM and/or da (it depends on who you ask) need to react to certain events and re-taste the device. This isn't done automatically, especially when da0 changes from a 32MB to a 64MB part, for reasons I've never known. Warner From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 06:03:02 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB4F916A41C for ; Fri, 10 Jun 2005 06:03:02 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4655C43D4C for ; Fri, 10 Jun 2005 06:03:02 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id EA79460F7; Fri, 10 Jun 2005 08:02:55 +0200 (CEST) Received: from xps.des.no (des.no [80.203.228.37]) by tim.des.no (Postfix) with ESMTP id D968D60F5; Fri, 10 Jun 2005 08:02:55 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id B6D3433C3B; Fri, 10 Jun 2005 08:02:55 +0200 (CEST) To: "Darren Pilgrim" References: <000001c56d5f$efe5c260$0a2a15ac@SMILEY> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Fri, 10 Jun 2005 08:02:55 +0200 In-Reply-To: <000001c56d5f$efe5c260$0a2a15ac@SMILEY> (Darren Pilgrim's message of "Thu, 9 Jun 2005 18:58:44 -0700") Message-ID: <86ekba4uls.fsf@xps.des.no> 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-Learn: ham X-Spam-Score: -5.1/5.0 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on tim.des.no Cc: freebsd-hackers@freebsd.org Subject: Re: Determining disk device and kicking GEOM when doing automatic mounting of umass devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 06:03:02 -0000 "Darren Pilgrim" writes: > GEOM doesn't automatically read the partition table and create the > slice device [...] Yes, it does. When the umassX provider shows up, GEOM immediately tastes it and creates geoms for the individual slices. If it really doesn't on your system, try the following: # /etc/rc.d/devd stop # logger START # sysctl debug.bootverbose=3D1 # sysctl -b kern.geom.conftxt >geom-before [insert umass device, wait 10 secs] # sysctl -b kern.geom.conftxt >geom-after # sysctl debug.bootverbose=3D0 # logger STOP # /etc/rc.d/devd start # awk '/START/{s=3D1}{if(s)print}/STOP/{s=3D0}' /var/log/messages >geom-logs then post the contents of geom-{before,after,logs}. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 06:18:34 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71D2016A41C for ; Fri, 10 Jun 2005 06:18:34 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from server.absolute-media.de (server.absolute-media.de [213.239.231.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 033FD43D53 for ; Fri, 10 Jun 2005 06:18:33 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from localhost (unknown [127.0.0.1]) by server.absolute-media.de (Postfix) with ESMTP id E384A84796; Fri, 10 Jun 2005 08:18:31 +0200 (CEST) Received: from server.absolute-media.de ([127.0.0.1]) by localhost (server [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18664-02; Fri, 10 Jun 2005 08:18:27 +0200 (CEST) Received: from firewall.demig (p50839768.dip0.t-ipconnect.de [80.131.151.104]) by server.absolute-media.de (Postfix) with ESMTP id 2572084510; Fri, 10 Jun 2005 08:18:27 +0200 (CEST) Received: from ws-ew-3 (ws-ew-3.w2kdemig [192.168.1.72]) by firewall.demig (8.13.4/8.13.1) with SMTP id j5A6EPXm091548; Fri, 10 Jun 2005 08:14:25 +0200 (CEST) (envelope-from NKoch@demig.de) From: "Norbert Koch" To: "Maksim Yevmenkin" Date: Fri, 10 Jun 2005 08:14:25 +0200 Message-ID: <001601c56d83$a6a06500$4801a8c0@ws-ew-3.W2KDEMIG> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <42A86529.5020103@savvis.net> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Importance: Normal X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at absolute-media.de Cc: "Freebsd-Hackers@Freebsd. Org" Subject: RE: usbd.conf: detach ukbd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 06:18:34 -0000 > -----Original Message----- > From: Maksim Yevmenkin [mailto:maksim.yevmenkin@savvis.net] > Sent: Thursday, June 09, 2005 5:50 PM > To: Norbert Koch > Cc: Freebsd-Hackers@Freebsd. Org > Subject: Re: usbd.conf: detach ukbd > > > Norbert, > > > when running usbd (under FreeBSD 4.11) with > > -dv switches I can see that a usb keyboard > > correctly attaches as ukbd0, > > but detaches as fall-through "USB device". > > can you please tell what is in your /etc/usbd.conf? > > > Do I just have to live with that fact or can > > I change that anyhow? Is that a device/device-class > > specific problem? > > does something like > > device "USB keyboard" > devname "ukbd[0-9]+" > attach "foo" > detach "bar" > > work? note: please replace "foo" and "bar" with actual commands you want > to be executed. No it does not, which is exactly my problem. Actually, I don't have the wildcard in my devname, just "ukbd0", but that doesn't make the difference, I think. From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 06:18:35 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E79916A41C for ; Fri, 10 Jun 2005 06:18:35 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from server.absolute-media.de (server.absolute-media.de [213.239.231.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id F19D943D49 for ; Fri, 10 Jun 2005 06:18:34 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from localhost (unknown [127.0.0.1]) by server.absolute-media.de (Postfix) with ESMTP id 26B4184510; Fri, 10 Jun 2005 08:18:34 +0200 (CEST) Received: from server.absolute-media.de ([127.0.0.1]) by localhost (server [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18577-08; Fri, 10 Jun 2005 08:18:29 +0200 (CEST) Received: from firewall.demig (p50839768.dip0.t-ipconnect.de [80.131.151.104]) by server.absolute-media.de (Postfix) with ESMTP id 78DC7847A4; Fri, 10 Jun 2005 08:18:27 +0200 (CEST) Received: from ws-ew-3 (ws-ew-3.w2kdemig [192.168.1.72]) by firewall.demig (8.13.4/8.13.1) with SMTP id j5A6EPXo091548; Fri, 10 Jun 2005 08:14:32 +0200 (CEST) (envelope-from NKoch@demig.de) From: "Norbert Koch" To: , Date: Fri, 10 Jun 2005 08:14:32 +0200 Message-ID: <001701c56d83$aada3e20$4801a8c0@ws-ew-3.W2KDEMIG> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <200506092224.50203.hselasky@c2i.net> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Importance: Normal X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at absolute-media.de Cc: Subject: RE: usbd.conf: detach ukbd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 06:18:35 -0000 > I'm not sure if detach is supported like that, because the "ukbd" > device name > will not be passed to "usbd" during detach. Then one needs to > match against > the class/subclass of the USB-keyboard: > > device "USB keyboard" > class 3 > subclass 1 > detach "xxxx ukbd0" > But from what I see, when running usbd, the class and subclass keys of the cherry keyboard, I am testing with, are both zero at attach and detach. So, one idea would be to rewrite usbd.conf in the attach script. Usbd - as it is now - does only setenv ("DEVNAME"), but it would be trivial to add e.g. setenv ("VENDOR") and setenv ("PRODUCTID"). > Else if devd is not available on 4.11 you will have to change > some code and > compile a new kernel, from what I can see. > > To the file /sys/dev/usb/ukbd.c add this: > > static void > usbd_add_device_detach_event(device_t self) > { > struct usb_event ue; > > bzero(&ue, sizeof(ue)); > > strlcpy(ue.u.ue_device.udi_devnames[0], > device_get_nameunit(self), USB_MAX_DEVNAMELEN) ; > > usb_add_event(USB_EVENT_DEVICE_DETACH, &ue); > return; > } > > ukbd_detach() > { > ... > usbd_add_device_detach_event(self); > return (0); > } > > This will make the suggestion from Maksim work. > > A generic solution would be to call > "usbd_add_device_detach_event()" from the > "bus_child_detached" method of uhub, which must be added. > > Also one can change "usb_disconnect_port()" to generate the event > before the > sub-devices are detached, but that might not work in all cases. > > --HPS > Hmm, may be I'll try this. Thank you very much. Norbert From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 06:23:33 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FF5B16A41C for ; Fri, 10 Jun 2005 06:23:33 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from server.absolute-media.de (server.absolute-media.de [213.239.231.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EA2843D4C for ; Fri, 10 Jun 2005 06:23:32 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from localhost (unknown [127.0.0.1]) by server.absolute-media.de (Postfix) with ESMTP id B8C2284757; Fri, 10 Jun 2005 08:23:31 +0200 (CEST) Received: from server.absolute-media.de ([127.0.0.1]) by localhost (server [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19116-05; Fri, 10 Jun 2005 08:23:27 +0200 (CEST) Received: from firewall.demig (p50839768.dip0.t-ipconnect.de [80.131.151.104]) by server.absolute-media.de (Postfix) with ESMTP id D9510847A0; Fri, 10 Jun 2005 08:23:26 +0200 (CEST) Received: from ws-ew-3 (ws-ew-3.w2kdemig [192.168.1.72]) by firewall.demig (8.13.4/8.13.1) with SMTP id j5A6Mijr091980; Fri, 10 Jun 2005 08:22:44 +0200 (CEST) (envelope-from NKoch@demig.de) From: "Norbert Koch" To: "=?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" , "Darren Pilgrim" Date: Fri, 10 Jun 2005 08:22:45 +0200 Message-ID: <001a01c56d84$d09d2f40$4801a8c0@ws-ew-3.W2KDEMIG> 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 8.5, Build 4.71.2173.0 In-Reply-To: <86ekba4uls.fsf@xps.des.no> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Importance: Normal X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at absolute-media.de Cc: freebsd-hackers@freebsd.org Subject: RE: Determining disk device and kicking GEOM when doing automaticmounting of umass devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 06:23:33 -0000 > -----Original Message----- > From: owner-freebsd-hackers@freebsd.org > [mailto:owner-freebsd-hackers@freebsd.org]On Behalf Of Dag-Erling > Smørgrav > Sent: Friday, June 10, 2005 8:03 AM > To: Darren Pilgrim > Cc: freebsd-hackers@freebsd.org > Subject: Re: Determining disk device and kicking GEOM when doing > automaticmounting of umass devices > > > "Darren Pilgrim" writes: > > GEOM doesn't automatically read the partition table and create the > > slice device [...] > > Yes, it does. When the umassX provider shows up, GEOM immediately > tastes it and creates geoms for the individual slices. > >From what I've seen, it doesn't. After attaching a memory stick I only see "da0". I then call mount_msdosfs on "da0", which fails expectedly. Only then I see "da0s1", which I can mount. But I didn't test this against the very latest 5-stable. From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 07:02:40 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D176316A41C for ; Fri, 10 Jun 2005 07:02:40 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5531F43D48 for ; Fri, 10 Jun 2005 07:02:40 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from SMILEY (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 171D419F3B; Fri, 10 Jun 2005 00:03:58 -0700 (PDT) From: "Darren Pilgrim" To: =?iso-8859-1?Q?'=22Dag-Erling_Sm=F8rgrav=22'?= Date: Fri, 10 Jun 2005 00:02:28 -0700 Message-ID: <000001c56d8a$5ec04320$0a2a15ac@SMILEY> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0001_01C56D4F.B2616B20" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <86ekba4uls.fsf@xps.des.no> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Cc: freebsd-hackers@freebsd.org Subject: RE: Determining disk device and kicking GEOM when doing automatic mounting of umass devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 07:02:40 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C56D4F.B2616B20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable From: "Dag-Erling Sm=F8rgrav" [mailto:des@des.no]=20 > "Darren Pilgrim" writes: > > GEOM doesn't automatically read the partition table and create the > > slice device [...] >=20 > Yes, it does. When the umassX provider shows up, GEOM immediately > tastes it and creates geoms for the individual slices. >=20 > If it really doesn't on your system, try the following: >=20 > # /etc/rc.d/devd stop > # logger START > # sysctl debug.bootverbose=3D1 > # sysctl -b kern.geom.conftxt >geom-before > [insert umass device, wait 10 secs] > # sysctl -b kern.geom.conftxt >geom-after > # sysctl debug.bootverbose=3D0 > # logger STOP > # /etc/rc.d/devd start > # awk '/START/{s=3D1}{if(s)print}/STOP/{s=3D0}' /var/log/messages=20 > >geom-logs >=20 > then post the contents of geom-{before,after,logs}. Attached as named above. The logs show the da0 DISK class in the GEOM config, but no MBR class entry. This is on -current as of May 22. ------=_NextPart_000_0001_01C56D4F.B2616B20 Content-Type: application/octet-stream; name="geom-before" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="geom-before" 0 DISK cd0 0 2048 hd 0 sc 0=0A= 0 DISK ad0 80026361856 512 hd 16 sc 63=0A= 1 MBR ad0s4 25761576960 512 i 3 o 54262172160 ty 165=0A= 2 BSD ad0s4h 1073741824 512 i 7 o 9663676416 ty 7=0A= 2 BSD ad0s4g 3221225472 512 i 6 o 6442450944 ty 7=0A= 2 BSD ad0s4f 4831838208 512 i 5 o 1610612736 ty 7=0A= 2 BSD ad0s4e 805306368 512 i 4 o 805306368 ty 7=0A= 2 BSD ad0s4d 805306368 512 i 3 o 0 ty 7=0A= 2 BSD ad0s4c 25761576960 512 i 2 o 0 ty 0=0A= 2 BSD ad0s4b 13950416896 512 i 1 o 11811160064 ty 7=0A= 2 BSD ad0s4a 1073741824 512 i 0 o 10737418240 ty 7=0A= 1 MBR ad0s3 1077511680 512 i 2 o 53184660480 ty 165=0A= 2 BSD ad0s3d 217679360 512 i 3 o 859832320 ty 7=0A= 2 BSD ad0s3c 1077511680 512 i 2 o 0 ty 0=0A= 2 BSD ad0s3b 545259520 512 i 1 o 314572800 ty 1=0A= 2 BSD ad0s3a 314572800 512 i 0 o 0 ty 7=0A= 1 MBR ad0s2 53127083520 512 i 1 o 57576960 ty 7=0A= 1 MBR ad0s1 57544704 512 i 0 o 32256 ty 222=0A= =00 ------=_NextPart_000_0001_01C56D4F.B2616B20 Content-Type: application/octet-stream; name="geom-after" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="geom-after" 0 DISK da0 0 0 hd 0 sc 0=0A= 0 DISK cd0 0 2048 hd 0 sc 0=0A= 0 DISK ad0 80026361856 512 hd 16 sc 63=0A= 1 MBR ad0s4 25761576960 512 i 3 o 54262172160 ty 165=0A= 2 BSD ad0s4h 1073741824 512 i 7 o 9663676416 ty 7=0A= 2 BSD ad0s4g 3221225472 512 i 6 o 6442450944 ty 7=0A= 2 BSD ad0s4f 4831838208 512 i 5 o 1610612736 ty 7=0A= 2 BSD ad0s4e 805306368 512 i 4 o 805306368 ty 7=0A= 2 BSD ad0s4d 805306368 512 i 3 o 0 ty 7=0A= 2 BSD ad0s4c 25761576960 512 i 2 o 0 ty 0=0A= 2 BSD ad0s4b 13950416896 512 i 1 o 11811160064 ty 7=0A= 2 BSD ad0s4a 1073741824 512 i 0 o 10737418240 ty 7=0A= 1 MBR ad0s3 1077511680 512 i 2 o 53184660480 ty 165=0A= 2 BSD ad0s3d 217679360 512 i 3 o 859832320 ty 7=0A= 2 BSD ad0s3c 1077511680 512 i 2 o 0 ty 0=0A= 2 BSD ad0s3b 545259520 512 i 1 o 314572800 ty 1=0A= 2 BSD ad0s3a 314572800 512 i 0 o 0 ty 7=0A= 1 MBR ad0s2 53127083520 512 i 1 o 57576960 ty 7=0A= 1 MBR ad0s1 57544704 512 i 0 o 32256 ty 222=0A= =00 ------=_NextPart_000_0001_01C56D4F.B2616B20 Content-Type: application/octet-stream; name="geom-logs" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="geom-logs" Jun 9 23:44:54 Smiley root: START=0A= Jun 9 23:46:31 Smiley kernel: umass0: M-SysT5 Dell Memory Key, rev = 2.00/2.00, addr 2=0A= Jun 9 23:46:31 Smiley kernel: umass0:3:0:-1: Attached to scbus3=0A= Jun 9 23:46:32 Smiley kernel: pass1 at umass-sim0 bus 0 target 0 lun 0=0A= Jun 9 23:46:32 Smiley kernel: pass1: = Removable Direct Access SCSI-0 device =0A= Jun 9 23:46:32 Smiley kernel: pass1: Serial Number u=0A= Jun 9 23:46:32 Smiley kernel: pass1: 40.000MB/s transfers=0A= Jun 9 23:46:32 Smiley kernel: GEOM: new disk da0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Retrying Command=0A= Jun 9 23:46:32 Smiley last message repeated 3 times=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): error 6=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Unretryable Error=0A= Jun 9 23:46:32 Smiley kernel: da0 at umass-sim0 bus 0 target 0 lun 0=0A= Jun 9 23:46:32 Smiley kernel: da0: = Removable Direct Access SCSI-0 device =0A= Jun 9 23:46:32 Smiley kernel: da0: Serial Number u=0A= Jun 9 23:46:32 Smiley kernel: da0: 40.000MB/s transfers=0A= Jun 9 23:46:32 Smiley kernel: da0: Attempt to query device size failed: = UNIT ATTENTION, Medium not present=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. = CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI = Status Error=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): SCSI Status: = Check Condition=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): = (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: Retrying Command (per Sense Data)=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Retrying Command=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. = CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI = Status Error=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): SCSI Status: = Check Condition=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): = (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: Retrying Command (per Sense Data)=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Retrying Command=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. = CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI = Status Error=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): SCSI Status: = Check Condition=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): = (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: Retrying Command (per Sense Data)=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Retrying Command=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. = CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI = Status Error=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): SCSI Status: = Check Condition=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): = (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: Retrying Command (per Sense Data)=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Retrying Command=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. = CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI = Status Error=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): SCSI Status: = Check Condition=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): = (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: Retries Exhausted=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): error 6=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Unretryable Error=0A= Jun 9 23:46:32 Smiley kernel: Opened disk da0 -> 6=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. = CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI = Status Error=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): SCSI Status: = Check Condition=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): = (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: Retrying Command (per Sense Data)=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Retrying Command=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. = CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI = Status Error=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): SCSI Status: = Check Condition=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): = (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: Retrying Command (per Sense Data)=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Retrying Command=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. = CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI = Status Error=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): SCSI Status: = Check Condition=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): = (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: Retrying Command (per Sense Data)=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Retrying Command=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. = CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI = Status Error=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): SCSI Status: = Check Condition=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): = (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: Retrying Command (per Sense Data)=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Retrying Command=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. = CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI = Status Error=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): SCSI Status: = Check Condition=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): = (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 =0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION = asc:3a,0=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Medium not present=0A= Jun 9 23:46:32 Smiley kernel: Retries Exhausted=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): error 6=0A= Jun 9 23:46:32 Smiley kernel: (da0:umass-sim0:0:0:0): Unretryable Error=0A= Jun 9 23:46:32 Smiley kernel: Opened disk da0 -> 6=0A= Jun 9 23:47:05 Smiley root: STOP=0A= ------=_NextPart_000_0001_01C56D4F.B2616B20-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 07:16:06 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 053BC16A41C for ; Fri, 10 Jun 2005 07:16:06 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96E1943D1F for ; Fri, 10 Jun 2005 07:16:05 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 718B760F7; Fri, 10 Jun 2005 09:16:00 +0200 (CEST) Received: from xps.des.no (des.no [80.203.228.37]) by tim.des.no (Postfix) with ESMTP id 5E14360F5; Fri, 10 Jun 2005 09:16:00 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 42E2733C3B; Fri, 10 Jun 2005 09:16:00 +0200 (CEST) To: "Darren Pilgrim" References: <000001c56d8a$5ec04320$0a2a15ac@SMILEY> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Fri, 10 Jun 2005 09:16:00 +0200 In-Reply-To: <000001c56d8a$5ec04320$0a2a15ac@SMILEY> (Darren Pilgrim's message of "Fri, 10 Jun 2005 00:02:28 -0700") Message-ID: <86k6l23cnj.fsf@xps.des.no> 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-Learn: ham X-Spam-Score: -5.2/5.0 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on tim.des.no Cc: freebsd-hackers@freebsd.org Subject: Re: Determining disk device and kicking GEOM when doing automatic mounting of umass devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 07:16:06 -0000 "Darren Pilgrim" writes: > Attached as named above. The logs show the da0 DISK class in the GEOM > config, but no MBR class entry. Take a closer look at geom-logs. It shows a slew of CAM errors. There's something wrong with your fob, or possibly (but not likely) with the USB stack. Here's what I get in a similar scenario: Jun 10 09:14:02 xps des: START Jun 10 09:14:06 xps kernel: umass0: vendor 0x0d7d USB DISK, rev 1.10/1.00, = addr 5 Jun 10 09:14:06 xps kernel: umass0:0:0:-1: Attached to scbus0 Jun 10 09:14:07 xps kernel: pass0 at umass-sim0 bus 0 target 0 lun 0 Jun 10 09:14:07 xps kernel: pass0: < USB DISK 1.20> Removable Direct Access= SCSI-0 device Jun 10 09:14:07 xps kernel: pass0: Serial Number Jun 10 09:14:07 xps kernel: pass0: 1.000MB/s transfers Jun 10 09:14:07 xps kernel: GEOM: new disk da0 Jun 10 09:14:07 xps kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Jun 10 09:14:07 xps kernel: da0: < USB DISK 1.20> Removable Direct Access S= CSI-0 device Jun 10 09:14:07 xps kernel: da0: Serial Number Jun 10 09:14:07 xps kernel: da0: 1.000MB/s transfers Jun 10 09:14:07 xps kernel: da0: 31MB (64000 512 byte sectors: 64H 32S/T 31= C) Jun 10 09:14:13 xps des: STOP except my fob is unpartitioned (like a floppy), which is why I only get da0. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 07:41:11 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5A2E16A484; Fri, 10 Jun 2005 07:41:11 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 079BC43D48; Fri, 10 Jun 2005 07:41:10 +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 j5A7f9b8039040; Fri, 10 Jun 2005 10:41:09 +0300 (EEST) (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 38127-09; Fri, 10 Jun 2005 10:41:08 +0300 (EEST) 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 j5A7f89i039037 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Jun 2005 10:41:08 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.3/8.13.3) id j5A7fake078777; Fri, 10 Jun 2005 10:41:36 +0300 (EEST) (envelope-from ru) Date: Fri, 10 Jun 2005 10:41:26 +0300 From: Ruslan Ermilov To: Aziz Kezzou Message-ID: <20050610074126.GD78035@ip.net.ua> References: <37273927050609144244862086@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nYySOmuH/HDX6pKp" Content-Disposition: inline In-Reply-To: <37273927050609144244862086@mail.gmail.com> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: freebsd-hackers , freebsd-net Subject: Re: How to do a routing lookup inside the kernel in FreeBSD ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 07:41:12 -0000 --nYySOmuH/HDX6pKp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 09, 2005 at 05:42:16PM -0400, Aziz Kezzou wrote: > Hi all, > I am trying to figure out from the kernel source code (FreeBSD 5.3) > how can I perform a routing lookup in a KLD module. > Since I am short in time, if anyone knows how do to do this I would > appreciate. Any pointers to the right portion of the code are also > apperciated. >=20 man 9 rtalloc Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --nYySOmuH/HDX6pKp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCqUQmqRfpzJluFF4RAugrAJ9Nblt1pnzg8l3oprv+yhX4lg3xnwCgjp+e baQpYwlk9OI9cIpofqzWim0= =Mry1 -----END PGP SIGNATURE----- --nYySOmuH/HDX6pKp-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 08:08:29 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9DD316A41C for ; Fri, 10 Jun 2005 08:08:29 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8ACD243D1F for ; Fri, 10 Jun 2005 08:08:29 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from SMILEY (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 036AA19F3B; Fri, 10 Jun 2005 01:09:48 -0700 (PDT) From: "Darren Pilgrim" To: =?iso-8859-1?Q?'=22Dag-Erling_Sm=F8rgrav=22'?= Date: Fri, 10 Jun 2005 01:08:10 -0700 Message-ID: <000001c56d93$8b65c590$0a2a15ac@SMILEY> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: <86k6l23cnj.fsf@xps.des.no> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Cc: freebsd-hackers@freebsd.org Subject: RE: Determining disk device and kicking GEOM when doing automatic mounting of umass devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 08:08:29 -0000 > -----Original Message----- > From: "Dag-Erling Sm=F8rgrav" [mailto:des@des.no]=20 > Sent: Friday, June 10, 2005 12:16 AM > To: Darren Pilgrim > Cc: freebsd-hackers@freebsd.org > Subject: Re: Determining disk device and kicking GEOM when=20 > doing automatic mounting of umass devices >=20 >=20 > "Darren Pilgrim" writes: > > Attached as named above. The logs show the da0 DISK class=20 > in the GEOM > > config, but no MBR class entry. >=20 > Take a closer look at geom-logs. It shows a slew of CAM errors. > There's something wrong with your fob, or possibly (but not likely) > with the USB stack. Except that after all those errors, it still mounts and "works fine". = Also, trying to mount /dev/da0 does produce the MBR entry in the GEOM config: 1 MBR da0s1 255849984 512 i 0 o 2048 ty 11 It also produces a single "READ CAPACITY" CAM error like those produced = when the device attaches. I also tested with a known-good USB zip drive = plugged into the same USB port. It attached flawlessly: the console showed the normal attach messages, GEOM config shows the appropriate MBR entry and /dev/da0s4 is created. So yeah I gueuss my fob is busted or funky. The CAM errors are "just" = the drive saying there's no media present, so maybe the device doesn't = support the commands necessary to report disk capacity? Is there a way to = educate CAM about this so the attach procedure doesn't break? Why would the CAM errors prevent GEOM from creating the MBR geom during attach but not when trying to mount /dev/da0? From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 09:01:27 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7575D16A41C for ; Fri, 10 Jun 2005 09:01:27 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1775943D48 for ; Fri, 10 Jun 2005 09:01:26 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 6605860F5; Fri, 10 Jun 2005 11:01:20 +0200 (CEST) Received: from xps.des.no (des.no [80.203.228.37]) by tim.des.no (Postfix) with ESMTP id 53A1F60F2; Fri, 10 Jun 2005 11:01:20 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 2DA0B33C3B; Fri, 10 Jun 2005 11:01:20 +0200 (CEST) To: "Darren Pilgrim" References: <000001c56d93$8b65c590$0a2a15ac@SMILEY> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Fri, 10 Jun 2005 11:01:20 +0200 In-Reply-To: <000001c56d93$8b65c590$0a2a15ac@SMILEY> (Darren Pilgrim's message of "Fri, 10 Jun 2005 01:08:10 -0700") Message-ID: <86k6l2y49r.fsf@xps.des.no> 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-Learn: ham X-Spam-Score: -5.1/5.0 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on tim.des.no Cc: freebsd-hackers@freebsd.org Subject: Re: Determining disk device and kicking GEOM when doing automatic mounting of umass devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 09:01:27 -0000 "Darren Pilgrim" writes: > So yeah I gueuss my fob is busted or funky. The CAM errors are "just" the > drive saying there's no media present, so maybe the device doesn't support > the commands necessary to report disk capacity? Is there a way to educate > CAM about this so the attach procedure doesn't break? It's a direct-access storage device. It *can't* not support the READ CAPACITY command. > Why would the CAM errors prevent GEOM from creating the MBR geom during > attach but not when trying to mount /dev/da0? My guess is that the fob is marginal and takes a while to stabilize after being plugged in. GEOM first tastes it when it is plugged in, it is still funky, and GEOM fails to read the partition table. Then you try to mount /dev/da0, it is opened r/w, which causes GEOM to retaste it once it is closed; by that time, it has settled and the second tasting succeeds. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 09:55:55 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01BCF16A41C for ; Fri, 10 Jun 2005 09:55:55 +0000 (GMT) (envelope-from crown@xnet.nnov.ru) Received: from mail.mts-nn.ru (mail.mts-nn.ru [213.177.96.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E47543D4C for ; Fri, 10 Jun 2005 09:55:53 +0000 (GMT) (envelope-from crown@xnet.nnov.ru) Received: from xnet.nnov.ru (pppoe-adsl-ats41-81.adsl.mts-nn.ru [82.208.80.81] (may be forged)) by mail.mts-nn.ru (8.12.11/8.12.11) with ESMTP id j5A9toNu027484 for ; Fri, 10 Jun 2005 13:55:50 +0400 Received: from xnet.nnov.ru (localhost [127.0.0.1]) by xnet.nnov.ru (8.13.4/8.13.3) with ESMTP id j5A9teDT015121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Jun 2005 13:55:49 +0400 (MSD) (envelope-from crown@xnet.nnov.ru) Received: (from crown@localhost) by xnet.nnov.ru (8.13.4/8.13.3/Submit) id j5A9tewe015120 for freebsd-hackers@freebsd.org; Fri, 10 Jun 2005 13:55:40 +0400 (MSD) (envelope-from crown) Date: Fri, 10 Jun 2005 13:55:40 +0400 From: sb To: freebsd-hackers@freebsd.org Message-ID: <20050610095540.GA936@cololo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline X-key-fingerprint: 821C 4172 7F17 D0A7 F8A6 0C6C 91DD AFD3 3DD4 FB12 User-Agent: Mutt/1.5.6i Subject: test X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 09:55:55 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable test --=20 place ur advertise here --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iQCVAwUBQqljnJHdr9M91PsSAQKViwP/e1FoWnl8tb3BQ7sgCFLGdMLb7mu6DheP dQb1JS2YYoz0H6uBfQoCI6TTF6Ci8WrJlTqCEWz24MsGr0jjQMCz5KVeMd4hsFPx IxnfhPvrvYJj8xO/rXQVmaY7WjjRb1wVaOwTwG0fyfm92Q8oIzJIvSmmp7uuD2mQ WFq18PFbthw= =58SP -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 00:09:29 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BDCE16A41C for ; Fri, 10 Jun 2005 00:09:29 +0000 (GMT) (envelope-from sdrhodus@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA2E043D49 for ; Fri, 10 Jun 2005 00:09:28 +0000 (GMT) (envelope-from sdrhodus@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so294814wri for ; Thu, 09 Jun 2005 17:09:28 -0700 (PDT) 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:content-disposition:references; b=HjWb4/CGGJNDRc9zm7vznkfUzJBU1bPlxxkrqT3+nDfy7SxVvmuhmqIhU2brn2EJPCF+Ym7xIKzehzwW+fnn4TljPCCJ68TZ/A2m+hgGBn4mSnJAPQdcx6AFXSfA7EEKQLMsrTciUYuLFpD0q/vbd3D2PgRjcr+9Fg7FExAsHkM= Received: by 10.54.118.7 with SMTP id q7mr709973wrc; Thu, 09 Jun 2005 17:09:28 -0700 (PDT) Received: by 10.54.25.9 with HTTP; Thu, 9 Jun 2005 17:09:28 -0700 (PDT) Message-ID: Date: Fri, 10 Jun 2005 00:09:28 +0000 From: David Rhodus To: Scott Long In-Reply-To: <42A718EF.30803@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42A475AB.6020808@fer.hr> <20050607194005.GG837@darkness.comp.waw.pl> <20050607201642.GA58346@walton.maths.tcd.ie> <42A6091C.40409@samsco.org> <42A6C311.5090400@fer.hr> <42A6FF04.706@samsco.org> <42A71464.8070705@fer.hr> <42A718EF.30803@samsco.org> X-Mailman-Approved-At: Fri, 10 Jun 2005 11:47:56 +0000 Cc: hackers@freebsd.org, scottl@freebsd.org, phk@freebsd.org, Ivan Voras Subject: Re: Google SoC idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: drhodus@machdep.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 00:09:29 -0000 On 6/8/05, Scott Long wrote: > Ivan Voras wrote: > > Scott Long wrote: > > > >> Again, I'm not exactly sure how a generic mechanism can handle the > >> distinction of data vs. metadata vs. journal data. Also, what you > > > > > > I don't care about the distinction at this level - all data is treated > > equal. > > >=20 > But for journalling to work, you must care about the distinction. No, one does not have to concern oneself if the data block they are currently processing is data or metadata. That issue is completely dependent on the type of journaling implementation one is trying to achieve. --=20 -David Steven David Rhodus X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6806716A41C for ; Fri, 10 Jun 2005 14:01:29 +0000 (GMT) (envelope-from reko.turja@liukuma.net) Received: from tarjoilu.luukku.com (tarjoilu.luukku.com [194.215.205.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0972343D4C for ; Fri, 10 Jun 2005 14:01:29 +0000 (GMT) (envelope-from reko.turja@liukuma.net) Received: from localhost (mta1-o.i.luukku.com [10.0.1.112]) by mta1-o.i.luukku.com (Postfix) with ESMTP id 35494150116 for ; Fri, 10 Jun 2005 17:01:28 +0300 (EEST) Received: from rekon (92a7.dsl.mtv3.fi [82.203.167.146]) by tarjoilu.luukku.com (Postfix) with SMTP id 0C3FA150013 for ; Fri, 10 Jun 2005 17:01:28 +0300 (EEST) Message-ID: <00aa01c56dc4$e93fb050$92a7cb52@rekon> From: "Reko Turja" To: Date: Fri, 10 Jun 2005 17:01:34 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Subject: X86 machine code enter and FreeBSD kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 14:01:29 -0000 I received no reply on this question at questions mailing list, so I try asking this here. Hope I'm not asking this in completely wrong list. In recent discussion in OpenWatcom lists it was noticed that at least certain addressing modes of assembler ENTER instruction causes a crash when used in Linux. GCC circumnavigates this by not emitting ENTER instructions in machine code. Linus's comment on the above issue can be found on: http://groups.google.co.nz/groups?selm=7i86ni%24b7n%241%40palladium.transmeta.com What's the status of the above "feature" in FreeBSD, does the kernel support the whole x86 instruction set without similar cut corners? -Reko From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 15:04:42 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D441716A41C for ; Fri, 10 Jun 2005 15:04:42 +0000 (GMT) (envelope-from gerarra@tin.it) Received: from vsmtp2.tin.it (vsmtp2.tin.it [212.216.176.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CE3C43D49 for ; Fri, 10 Jun 2005 15:04:39 +0000 (GMT) (envelope-from gerarra@tin.it) Received: from ims3a.cp.tin.it (192.168.70.103) by vsmtp2.tin.it (7.0.027) id 42A8BA670005734F; Fri, 10 Jun 2005 17:04:38 +0200 Received: from [192.168.70.227] by ims3a.cp.tin.it with HTTP; Fri, 10 Jun 2005 17:04:37 +0200 Date: Fri, 10 Jun 2005 17:04:37 +0200 Message-ID: <429C8E8F00012B5F@ims3a.cp.tin.it> In-Reply-To: <00aa01c56dc4$e93fb050$92a7cb52@rekon> From: gerarra@tin.it To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable X-Originating-IP: 213.140.22.70 Cc: reko.turja@liukuma.net Subject: RE: X86 machine code enter and FreeBSD kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 15:04:43 -0000 >I received no reply on this question at questions mailing list, so I try= > >asking this here. Hope I'm not asking this in completely wrong list. > >In recent discussion in OpenWatcom lists it was noticed that at least >certain addressing modes of assembler ENTER instruction causes a crash >when used in Linux. GCC circumnavigates this by not emitting ENTER >instructions in machine code. Linus's comment on the above issue can be >found on: > >http://groups.google.co.nz/groups?selm=3D7i86ni%24b7n%241%40palladium.tr= ansmeta.com > >What's the status of the above "feature" in FreeBSD, does the kernel >support the >whole x86 instruction set without similar cut corners? > >-Reko Mainly, I think gcc sets stack by hands beacause ENTER does a lot of dirt= y work. If you see x86 pseudocode, it perform a lot of wasting work... howe= ver, what you proposed is not a bug, just a way of ruling stack frames. rookie From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 15:13:49 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4319A16A41C for ; Fri, 10 Jun 2005 15:13:49 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: from sarajevo.pacific.net.sg (sarajevo.pacific.net.sg [203.120.90.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 663E143D1D for ; Fri, 10 Jun 2005 15:13:47 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 6705 invoked from network); 10 Jun 2005 15:13:46 -0000 Received: from unknown (HELO maxwell2.pacific.net.sg) (203.120.90.192) by sarajevo with SMTP; 10 Jun 2005 15:13:46 -0000 Received: from [192.168.0.107] ([210.24.246.101]) by maxwell2.pacific.net.sg with ESMTP id <20050610151346.WKCR1130.maxwell2.pacific.net.sg@[192.168.0.107]>; Fri, 10 Jun 2005 23:13:46 +0800 Message-ID: <42A9AE12.8060702@pacific.net.sg> Date: Fri, 10 Jun 2005 23:13:22 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050514) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Reko Turja References: <00aa01c56dc4$e93fb050$92a7cb52@rekon> In-Reply-To: <00aa01c56dc4$e93fb050$92a7cb52@rekon> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: X86 machine code enter and FreeBSD kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 15:13:49 -0000 Hi, Reko Turja wrote: > I received no reply on this question at questions mailing list, so I try > asking this here. Hope I'm not asking this in completely wrong list. > > In recent discussion in OpenWatcom lists it was noticed that at least > certain addressing modes of assembler ENTER instruction causes a crash > when used in Linux. GCC circumnavigates this by not emitting ENTER > instructions in machine code. Linus's comment on the above issue can be > found on: > > http://groups.google.co.nz/groups?selm=7i86ni%24b7n%241%40palladium.transmeta.com > > > What's the status of the above "feature" in FreeBSD, does the kernel > support the > whole x86 instruction set without similar cut corners? > This here is out of my memory from the days when 'enter' was a new instruction. So, do not kill me if I am wrong. 'enter' allows to specify a nesting level. Languages like Pascal can use this for functions which are local to other functions to enable the inner function to access the stack of the outer function. C does not support this at all. So, if you use this instruction, it must be used with a nesting level of zero. This will not cause any problems but will be a plain waste of CPU time. Erich From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 16:11:07 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 489AB16A422 for ; Fri, 10 Jun 2005 16:11:07 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mail27.sea5.speakeasy.net (mail27.sea5.speakeasy.net [69.17.117.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0279443D49 for ; Fri, 10 Jun 2005 16:11:06 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 10943 invoked from network); 10 Jun 2005 16:11:06 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender ) by mail27.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 10 Jun 2005 16:11:06 -0000 Received: from [10.4.255.72] ([206.13.39.129]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j5AGAicv073579; Fri, 10 Jun 2005 12:10:56 -0400 (EDT) (envelope-from jhb@FreeBSD.org) In-Reply-To: <86ll5kdokw.fsf@xps.des.no> References: <20050608235221.GA71575@ranger.acns.ab.ca> <86ll5kdokw.fsf@xps.des.no> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <5aa5b3269b31db56aea70fcd38ccbd1a@FreeBSD.org> Content-Transfer-Encoding: quoted-printable From: John Baldwin Date: Fri, 10 Jun 2005 07:48:40 -0700 To: des@des.no (=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=) X-Mailer: Apple Mail (2.622) X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Cc: freebsd-hackers@FreeBSD.org Subject: Re: Bootable CDROM creation system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 16:11:07 -0000 On Jun 8, 2005, at 11:35 PM, Dag-Erling Sm=F8rgrav wrote: > Chad David writes: >> My company built a tool a few years back for creating a bootable = cdrom >> based on a running host FreeBSD 3/4 system, which promptly got=20 >> shelved and >> forgotten.I recently had to update it for FreeBSD 5 and thought that >> perhaps the community at large could make use it before it gets=20 >> forgotten >> again. > > # cd /usr/src > # make buildworld buildkernel > # mkdir /tmp/cdrom > # make installworld installkernel DESTDIR=3D/tmp/cdrom > # cd /usr/src/etc > # make distribution DESTDIR=3D/tmp/cdrom > # mkisofs -o /tmp/cdrom.iso -r -no-emul-boot -b /tmp/cdrom/boot/cdboot=20= > /tmp/cdrom > # burncd -s max data /tmp/cdrom.iso fixate eject > > did I leave anything out? I think you need to use -b boot/cdboot (i.e. I think it's a relative=20 path to the root of the image) or it won't work and it's --no-emul-boot=20= I believe. -J can be handy for Windoze systems as well. :-P --=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org= From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 16:11:18 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECE4B16A431 for ; Fri, 10 Jun 2005 16:11:18 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from mail21.sea5.speakeasy.net (mail21.sea5.speakeasy.net [69.17.117.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B58943D48 for ; Fri, 10 Jun 2005 16:11:18 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 1587 invoked from network); 10 Jun 2005 16:11:17 -0000 Received: from server.baldwin.cx ([216.27.160.63]) (envelope-sender ) by mail21.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 10 Jun 2005 16:11:16 -0000 Received: from [10.4.255.72] ([206.13.39.129]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j5AGAicw073579; Fri, 10 Jun 2005 12:11:05 -0400 (EDT) (envelope-from jhb@FreeBSD.org) In-Reply-To: <429AB5D2.7090102@pacific.net.sg> References: <42A44827271EB64C83E2B38A6E75787C03DCA3B4@exhkmb04.apac.nsroot.n et> <429AB314.6030908@atempo.com> <429AB5D2.7090102@pacific.net.sg> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <4064e2471eeab41d1413c7612fb979ad@FreeBSD.org> Content-Transfer-Encoding: quoted-printable From: John Baldwin Date: Fri, 10 Jun 2005 06:57:42 -0700 To: Erich Dollansky X-Mailer: Apple Mail (2.622) X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx Cc: freebsd-hackers@FreeBSD.org, =?ISO-8859-1?Q?Herv=E9_Kergourlay?= , "Que, Wei-Feng" , Max Laier , Maslan Subject: Re: Screen Resolution X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 16:11:19 -0000 On May 29, 2005, at 11:42 PM, Erich Dollansky wrote: > Hi, > > Herv=E9 Kergourlay wrote: >> xorgconfig >> I launch this tools but I 'm not sure of the screen resolution=20 >> details, vertical refresh rate, horizontal sync rate, ... >> I fill the answers with standard values > Do not do this. You must have the details for you monitor. Especially=20= > if it is a CRT, it could even kill it if the details are wrong. > >> but at the end, no xorg.conf file is written on the disk in /etc/X11 = ? >> > It has to be there. No it doesn't. xorgcfg actually defaults to writing xorg.conf to some=20= subdirectory of /usr/X11R6/lib/X11 or some such nowadays rather than=20 /etc/X11. You can see that path when you ask it to save the=20 configuration. Probably the docs need to be updated to include the=20 other more cryptic path as another place to look besides /etc/X11. --=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org= From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 22:40:59 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17CCA16A41C for ; Fri, 10 Jun 2005 22:40:59 +0000 (GMT) (envelope-from mhunter@malcolm.berkeley.edu) Received: from malcolm.berkeley.edu (malcolm.Berkeley.EDU [128.32.206.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB28443D1F for ; Fri, 10 Jun 2005 22:40:58 +0000 (GMT) (envelope-from mhunter@malcolm.berkeley.edu) Received: from malcolm.berkeley.edu (localhost [127.0.0.1]) by malcolm.berkeley.edu (8.13.3/8.13.3) with ESMTP id j5AMewbp012085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Jun 2005 15:40:58 -0700 (PDT) (envelope-from mhunter@malcolm.berkeley.edu) Received: (from mhunter@localhost) by malcolm.berkeley.edu (8.13.3/8.13.3/Submit) id j5AMewhX012084 for freebsd-hackers@freebsd.org; Fri, 10 Jun 2005 15:40:58 -0700 (PDT) (envelope-from mhunter) Date: Fri, 10 Jun 2005 15:40:58 -0700 From: Mike Hunter To: freebsd-hackers@freebsd.org Message-ID: <20050610224058.GA11336@malcolm.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (malcolm.berkeley.edu [127.0.0.1]); Fri, 10 Jun 2005 15:40:58 -0700 (PDT) Subject: unitialized memory is all zeros...why not garbage instead? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 22:40:59 -0000 Hey everybody, I have a feeling that I'm missing something really obvious, but I'm having trouble understanding why the following program: #include #include int main (int argc, char * argv[]) { void * ptr = malloc(65536); size_t i; for (i = 0; i < 65536; i++) { printf ("%x", *((unsigned char *)ptr + i)); if ((i % 16) == 0) { puts("\n"); } } return 0; } Never prints anything but "0"'s. I ran less up to my hw.physmem by feeding it /dev/random and watching top, and then ran the program, so I "know" there was tons of non-zero bits in memory. I'm curious because I am worried about information leaks between processes on the same machine...did somebody decide to solve this problem while I wasn't paying attention? :) %gcc -v Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.4.2 [FreeBSD] 20040728 %uname -a FreeBSD mylabtop.berkeley.edu 5.4-STABLE FreeBSD 5.4-STABLE #1: Wed May 11 12:05:39 PDT 2005 From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 22:43:12 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16A0716A41C for ; Fri, 10 Jun 2005 22:43:12 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id A98B943D1F for ; Fri, 10 Jun 2005 22:43:11 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j5AMgv9p045556; Fri, 10 Jun 2005 17:42:57 -0500 (CDT) (envelope-from dan) Date: Fri, 10 Jun 2005 17:42:57 -0500 From: Dan Nelson To: Mike Hunter Message-ID: <20050610224256.GG4116@dan.emsphone.com> References: <20050610224058.GA11336@malcolm.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050610224058.GA11336@malcolm.berkeley.edu> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.9i Cc: freebsd-hackers@freebsd.org Subject: Re: unitialized memory is all zeros...why not garbage instead? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 22:43:12 -0000 In the last episode (Jun 10), Mike Hunter said: > I have a feeling that I'm missing something really obvious, but I'm > having trouble understanding why the following program: > > int main (int argc, char * argv[]) > { > void * ptr = malloc(65536); > > Never prints anything but "0"'s. The kernel zeros out memory before handing it to processes. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 22:44:15 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E96A16A41C for ; Fri, 10 Jun 2005 22:44:15 +0000 (GMT) (envelope-from mhunter@malcolm.berkeley.edu) Received: from malcolm.berkeley.edu (malcolm.Berkeley.EDU [128.32.206.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FDCC43D1F for ; Fri, 10 Jun 2005 22:44:15 +0000 (GMT) (envelope-from mhunter@malcolm.berkeley.edu) Received: from malcolm.berkeley.edu (localhost [127.0.0.1]) by malcolm.berkeley.edu (8.13.3/8.13.3) with ESMTP id j5AMiF5s012293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 10 Jun 2005 15:44:15 -0700 (PDT) (envelope-from mhunter@malcolm.berkeley.edu) Received: (from mhunter@localhost) by malcolm.berkeley.edu (8.13.3/8.13.3/Submit) id j5AMiFTO012292 for freebsd-hackers@freebsd.org; Fri, 10 Jun 2005 15:44:15 -0700 (PDT) (envelope-from mhunter) Date: Fri, 10 Jun 2005 15:44:15 -0700 From: Mike Hunter To: freebsd-hackers@freebsd.org Message-ID: <20050610224415.GB11336@malcolm.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (malcolm.berkeley.edu [127.0.0.1]); Fri, 10 Jun 2005 15:44:15 -0700 (PDT) Subject: Slowing down an old program to run on a fast CPU? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 22:44:15 -0000 Hey everybody, I was playing around in ports and came across xroach. Cool program :) The only problem is that it runs too fast; you can't see the roaches because they scurry under your windows too quickly. Is there a general-purpose approach to this kind of problem in the FBSD world? I can see myself writing a C program called `slow` that would take argv[1] as the factor ( > 1) by which argv[2] should be slowed down by. Anybody else ever come up against this? Thanks and happy Friday! Mike From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 22:59:45 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BE7F16A41C for ; Fri, 10 Jun 2005 22:59:45 +0000 (GMT) (envelope-from root@Neo-Vortex.net) Received: from Neo-Vortex.net (203-173-58-65.dyn.iinet.net.au [203.173.58.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id E358C43D53 for ; Fri, 10 Jun 2005 22:59:44 +0000 (GMT) (envelope-from root@Neo-Vortex.net) Received: from localhost.Neo-Vortex.net (Neo-Vortex@localhost.Neo-Vortex.net [127.0.0.1]) by Neo-Vortex.net (8.13.1/8.12.10) with ESMTP id j5AMxWgP099243; Sat, 11 Jun 2005 08:59:32 +1000 (EST) (envelope-from root@Neo-Vortex.net) Date: Sat, 11 Jun 2005 08:59:32 +1000 (EST) From: Neo-Vortex To: Mike Hunter In-Reply-To: <20050610224415.GB11336@malcolm.berkeley.edu> Message-ID: <20050611085830.N98712@Neo-Vortex.net> References: <20050610224415.GB11336@malcolm.berkeley.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-hackers@freebsd.org Subject: Re: Slowing down an old program to run on a fast CPU? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 22:59:45 -0000 On Fri, 10 Jun 2005, Mike Hunter wrote: > Hey everybody, > > I was playing around in ports and came across xroach. Cool program :) > The only problem is that it runs too fast; you can't see the roaches > because they scurry under your windows too quickly. > > Is there a general-purpose approach to this kind of problem in the FBSD > world? I can see myself writing a C program called `slow` that would take > argv[1] as the factor ( > 1) by which argv[2] should be slowed down by. > > Anybody else ever come up against this? > > Thanks and happy Friday! You could try installing vmware and running however many copies of windows it takes to make the game playable... (i would say some other form of *BSD, but it probobly wouldn't hog as much cpu :P) ~NVX From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 23:24:38 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D11216A41C for ; Fri, 10 Jun 2005 23:24:38 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF01343D53 for ; Fri, 10 Jun 2005 23:24:37 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j5ANOYRQ023397; Fri, 10 Jun 2005 19:24:35 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <20050610224058.GA11336@malcolm.berkeley.edu> References: <20050610224058.GA11336@malcolm.berkeley.edu> Date: Fri, 10 Jun 2005 19:24:33 -0400 To: Mike Hunter , freebsd-hackers@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) on 128.113.2.3 Cc: Subject: Re: unitialized memory is all zeros...why not garbage instead? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 23:24:38 -0000 At 3:40 PM -0700 6/10/05, Mike Hunter wrote: >Hey everybody, > >I have a feeling that I'm missing something really obvious, but >I'm having trouble understanding why the following program: >Never prints anything but "0"'s. Kernel generally clears out memory in the background. See also the man page for 'malloc', which will describe some options that you can set by creating an appropriate symlink at /etc/malloc.conf. In particular, the -J flag. -- 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-hackers@FreeBSD.ORG Fri Jun 10 23:57:51 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA09916A41C for ; Fri, 10 Jun 2005 23:57:51 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9958843D48 for ; Fri, 10 Jun 2005 23:57:51 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.9p2/8.12.9) with ESMTP id j5ANvoYk010518; Fri, 10 Jun 2005 16:57:50 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id j5ANvoUD010517; Fri, 10 Jun 2005 16:57:50 -0700 (PDT) (envelope-from dillon) Date: Fri, 10 Jun 2005 16:57:50 -0700 (PDT) From: Matthew Dillon Message-Id: <200506102357.j5ANvoUD010517@apollo.backplane.com> To: Neo-Vortex References: <20050610224415.GB11336@malcolm.berkeley.edu> <20050611085830.N98712@Neo-Vortex.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Slowing down an old program to run on a fast CPU? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 23:57:52 -0000 You think that is bad, try running 'rain' on an xterm! -Matt Matthew Dillon From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 11 00:06:30 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65F5D16A41C for ; Sat, 11 Jun 2005 00:06:30 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from nic.ach.sch.gr (nic.sch.gr [194.63.238.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8369C43D53 for ; Sat, 11 Jun 2005 00:06:29 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: (qmail 21390 invoked by uid 207); 11 Jun 2005 00:06:28 -0000 Received: from keramida@freebsd.org by nic by uid 201 with qmail-scanner-1.21 (sophie: 3.04/2.19/3.81. Clear:RC:1(81.186.70.242):. Processed in 9.674322 secs); 11 Jun 2005 00:06:28 -0000 Received: from dialup242.ach.sch.gr (HELO gothmog.gr) ([81.186.70.242]) (envelope-sender ) by nic.sch.gr (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Jun 2005 00:06:17 -0000 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.4/8.13.4) with ESMTP id j5B05tgh001405; Sat, 11 Jun 2005 03:05:56 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.gr (8.13.4/8.13.4/Submit) id j5B05trS001404; Sat, 11 Jun 2005 03:05:55 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Sat, 11 Jun 2005 03:05:55 +0300 From: Giorgos Keramidas To: Mike Hunter Message-ID: <20050611000555.GE787@gothmog.gr> References: <20050610224415.GB11336@malcolm.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050610224415.GB11336@malcolm.berkeley.edu> Cc: freebsd-hackers@freebsd.org Subject: Re: Slowing down an old program to run on a fast CPU? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2005 00:06:30 -0000 On 2005-06-10 15:44, Mike Hunter wrote: > Hey everybody, > I was playing around in ports and came across xroach. Cool program :) > The only problem is that it runs too fast; you can't see the roaches > because they scurry under your windows too quickly. A port patch would fix this nicely, I guess :-) But it's not a general solution that would work by something like: % slowdown -f 0.025 ./a.out From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 11 00:16:07 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BD2616A425 for ; Sat, 11 Jun 2005 00:16:07 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-222-102-125.jan.bellsouth.net [68.222.102.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id C029143D1D for ; Sat, 11 Jun 2005 00:16:06 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: by mortis.over-yonder.net (Postfix, from userid 100) id 2FD7020F6C; Fri, 10 Jun 2005 19:16:05 -0500 (CDT) Date: Fri, 10 Jun 2005 19:16:04 -0500 From: "Matthew D. Fuller" To: Mike Hunter Message-ID: <20050611001604.GB93862@over-yonder.net> References: <20050610224415.GB11336@malcolm.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050610224415.GB11336@malcolm.berkeley.edu> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 Cc: freebsd-hackers@freebsd.org Subject: Re: Slowing down an old program to run on a fast CPU? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2005 00:16:07 -0000 On Fri, Jun 10, 2005 at 03:44:15PM -0700 I heard the voice of Mike Hunter, and lo! it spake thus: > > Is there a general-purpose approach to this kind of problem in the > FBSD world? I can see myself writing a C program called `slow` that > would take argv[1] as the factor ( > 1) by which argv[2] should be > slowed down by. It'd be tough. One way might be a wrapper program that SIGSTOP'd and SIGCONT'd the program with some pauses, but that would be incredibly nasty and probably not too pretty. A better way could would be to wrap the program with a library implementing sleep() and friends differently, so they pause for N times as long. But even that doesn't help when the programs don't slow themselves down. I guess the only general solution would be an API into the scheduler saying "Don't give this program more than N% of the CPU", but I'm pretty sure we don't have one. It'd be neat, though... /usr/bin/too-nice-for-its-own-good 8-} -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 11 00:48:32 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D6A016A41F for ; Sat, 11 Jun 2005 00:48:32 +0000 (GMT) (envelope-from braulio@solsoft.co.cr) Received: from wbm1.pair.net (wbm1.pair.net [209.68.3.41]) by mx1.FreeBSD.org (Postfix) with SMTP id 1198F43D48 for ; Sat, 11 Jun 2005 00:48:31 +0000 (GMT) (envelope-from braulio@solsoft.co.cr) Received: (qmail 85168 invoked by uid 65534); 11 Jun 2005 00:48:31 -0000 Received: from 163.178.104.130 ([163.178.104.130]) (SquirrelMail authenticated user braulio@solsoft.co.cr) by webmail1.pair.com with HTTP; Fri, 10 Jun 2005 18:48:31 -0600 (CST) Message-ID: <51351.163.178.104.130.1118450911.squirrel@webmail1.pair.com> Date: Fri, 10 Jun 2005 18:48:31 -0600 (CST) From: Braulio =?iso-8859-1?Q?Jos=E9_Solano_Rojas?= To: hackers@freebsd.org User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: Subject: NDIS driver Intel(R) PRO/Wireless 2200BG reaches kernel panic X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2005 00:48:32 -0000 Hello. I have installed FreeBSD 5.4 on a ASUS S5200N. Runs very nice! However I still need to install Wifi. I saw that Intel(R) PRO/Wireless 2200BG is not supported by wlan FreeBSD driver (reading through the man pages). Then I found that I could use the NDIS driver added on FreeBSD 5.3 to achieve Wireless Networking. So, I copied the Windows driver to /sys/modules/if_ndis. Then I run the command: ndiscvt -i w29n51.INF -s w29n51.sys -o ndis_driver_data.h After that: make make install Everything goes fine, but when I do: kldload ndis.ko kldload if_ndis.ko I get this: no match for MmMapIoSpace no match for MmUnmapIoSpace no match for WmiTraceMessage no match for IoWMIRegistrationControl no match for WmiQueryTraceInformation ntoskrnl dummy called... ndis0: mem 0xfe8fe000-0xfe8fefff irq 18 at device 5.0 on pci1 ndis0: NDIS API version: 5.1 ndis0: Ethernet address: 00:0e:35:40:56:24 ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ntoskrnl dummy called... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x80000002 fault code = supervisor read, page not present instruction pointer = 0x8:0x80000002 stack pointer = 0x10:0xd4c71adc frame pointer = 0x10:0xc24b57b0 code segment = base 0x0, limit 0xffffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 556 (kldload) trap number = 12 panic: page fault Uptime: 2m13s Cannot dump. No dump device defined. What does this mean (I know what means page fault)? Does this mean that there is a bug in the NDIS driver? Or is the page fault a problem in the Windows driver? And, what about all those no match for *? The example I found on the internet used NDIS API version: 5.0. Does the NDIS driver for FreeBSD support the 5.1 API? I tried to find more reading man pages but without success... Am I just plain stupid wrong with something? By the way, FreeBSD runs a lot faster that Windows XP on my laptop, even with KDE. ;-) I will appreciate any hints you can provide... Best regards, Braulio Solano From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 11 06:24:49 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBFD616A41C for ; Sat, 11 Jun 2005 06:24:49 +0000 (GMT) (envelope-from kamalpr@yahoo.com) Received: from web52708.mail.yahoo.com (web52708.mail.yahoo.com [206.190.39.159]) by mx1.FreeBSD.org (Postfix) with SMTP id 4ED5543D48 for ; Sat, 11 Jun 2005 06:24:49 +0000 (GMT) (envelope-from kamalpr@yahoo.com) Received: (qmail 57147 invoked by uid 60001); 11 Jun 2005 06:24:48 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=QsWgqAc6vSXsIL9cwnvmBoXGrtcwKyoiaoa59kCANLzqcny/Ynhrxarw3pKd6uoCoP+lRg4QTzSxnSsCeu0I3X5spNVLoL8CMp2W+bNn0sfXGuOG1F9zoP+4vSfnG7SpCPb71GlQlB1X4e/biWg0edJ8wITb+PvvZnNxomKWl8M= ; Message-ID: <20050611062448.57145.qmail@web52708.mail.yahoo.com> Received: from [64.186.168.226] by web52708.mail.yahoo.com via HTTP; Fri, 10 Jun 2005 23:24:48 PDT Date: Fri, 10 Jun 2005 23:24:48 -0700 (PDT) From: "Kamal R. Prasad" To: Neo-Vortex , Mike Hunter In-Reply-To: <20050611085830.N98712@Neo-Vortex.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@freebsd.org Subject: Re: Slowing down an old program to run on a fast CPU? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kamalp@acm.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2005 06:24:49 -0000 --- Neo-Vortex wrote: > > > On Fri, 10 Jun 2005, Mike Hunter wrote: > > > Hey everybody, > > > > I was playing around in ports and came across > xroach. Cool program :) > > The only problem is that it runs too fast; you > can't see the roaches > > because they scurry under your windows too > quickly. > > > > Is there a general-purpose approach to this kind > of problem in the FBSD > > world? I can see myself writing a C program > called `slow` that would take > > argv[1] as the factor ( > 1) by which argv[2] > should be slowed down by. > > > > Anybody else ever come up against this? > > > > Thanks and happy Friday! > Try lowering the priority of the target using nice and see if you can raise the priority of all other processes. In that case, the process with a lower priority will be automatically starved of cpu time. (p.s It has happned inadverently to me many times during debugging that I starved my shell of resources). regards -kamal > You could try installing vmware and running however > many copies of windows > it takes to make the game playable... (i would say > some other form of > *BSD, but it probobly wouldn't hog as much cpu :P) > > ~NVX > _______________________________________________ > 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" > ------------------------------------------------------------ Kamal R. Prasad UNIX systems consultant kamalp@acm.org In theory, there is no difference between theory and practice. In practice, there is:-). ------------------------------------------------------------ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 11 11:12:22 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 887FB16A41C for ; Sat, 11 Jun 2005 11:12:22 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B61C43D48 for ; Sat, 11 Jun 2005 11:12:21 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 2798E60F3; Sat, 11 Jun 2005 13:12:12 +0200 (CEST) Received: from xps.des.no (des.no [80.203.228.37]) by tim.des.no (Postfix) with ESMTP id 091FD60F2; Sat, 11 Jun 2005 13:12:12 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id E30C733C3B; Sat, 11 Jun 2005 13:12:11 +0200 (CEST) To: Mike Hunter References: <20050610224058.GA11336@malcolm.berkeley.edu> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Sat, 11 Jun 2005 13:12:11 +0200 In-Reply-To: <20050610224058.GA11336@malcolm.berkeley.edu> (Mike Hunter's message of "Fri, 10 Jun 2005 15:40:58 -0700") Message-ID: <86vf4lb110.fsf@xps.des.no> 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-Learn: ham X-Spam-Score: -5.1/5.0 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on tim.des.no Cc: freebsd-hackers@freebsd.org Subject: Re: unitialized memory is all zeros...why not garbage instead? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2005 11:12:22 -0000 Mike Hunter writes: > I have a feeling that I'm missing something really obvious, but I'm having > trouble understanding why the following program: > [...] > Never prints anything but "0"'s. Because the kernel always hands processes pre-zeroed pages. > I ran less up to my hw.physmem by feeding it /dev/random and watching > top, and then ran the program, so I "know" there was tons of non-zero > bits in memory. If your program had been able to see leftovers from less in its own address space, we'd have a huge security hole on our hands. > I'm curious because I am worried about information leaks between processes > on the same machine...did somebody decide to solve this problem while I > wasn't paying attention? :) It's always been this way. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 11 12:36:41 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6B0816A41C for ; Sat, 11 Jun 2005 12:36:41 +0000 (GMT) (envelope-from o@go.local.sib-ecometall.ru) Received: from mail.sib-ecometall.ru (sibekometall.ranetka.ru [80.255.129.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3160643D1F for ; Sat, 11 Jun 2005 12:36:40 +0000 (GMT) (envelope-from o@go.local.sib-ecometall.ru) Received: from go.local.sib-ecometall.ru (unknown [192.168.2.252]) by mail.sib-ecometall.ru (Postfix) with ESMTP id AE7DA39837 for ; Sat, 11 Jun 2005 20:36:38 +0800 (KRAST) Received: by go.local.sib-ecometall.ru (Postfix, from userid 6301) id BA3F94505E; Sat, 11 Jun 2005 20:36:46 +0800 (KRAST) Date: Sat, 11 Jun 2005 20:36:46 +0800 From: Oleg Gritsak To: freebsd-hackers@freebsd.org Message-ID: <20050611123646.GA92781@go.local.sib-ecometall.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.1i Subject: mio_connect specificity X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2005 12:36:41 -0000 Greetings! Would you, please, help to understand, what's specific FreeBSD has in a syscall mio_connect? The problem, I've ran into is - the shutting jabber server. In linux this code: out->fd = mio_connect(s2s->mio, pkt->port, pkt->ip, _out_mio_callback, (void *) out); doesn't lead to problems, but on my servers (FreeBSD 4.11/5.4) the daemon dies instantly. It doesn't even write to log, that it is exiting. The author of Jabber (2.0.8, from latest ports) is probably a linux-user and therefor doesn't believe the problem (on FreeBSD) exists. 8-( p.s. Of course, this problem occures only when peer is unreachable (return code 1, Operation not permitted). p.p.s. "Operation not permitted" because of isakmpd. -- ÓÉÓÔÅÍÎÙÊ ÁÄÍÉÎÉÓÔÒÁÔÏÒ ïïï "óÉÂ-üËÏíÅÔÁÌÌ" Ô. (3912) 60-99-42 (144) From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 11 22:24:46 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 743FB16A41F for ; Sat, 11 Jun 2005 22:24:46 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from smtp.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0D9D43D1F for ; Sat, 11 Jun 2005 22:24:45 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by smtp.xbsd.org (Postfix) with ESMTP id E240A11B8A; Sun, 12 Jun 2005 00:29:53 +0200 (CEST) Received: from smtp.xbsd.org ([127.0.0.1]) by localhost (srv1.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16552-05; Sun, 12 Jun 2005 00:29:47 +0200 (CEST) Received: from cream.xbsd.org (cream.xbsd.org [192.168.42.6]) by smtp.xbsd.org (Postfix) with ESMTP id AFA3411B89; Sun, 12 Jun 2005 00:29:46 +0200 (CEST) From: Florent Thoumie To: Braulio =?ISO-8859-1?Q?Jos=E9?= Solano Rojas In-Reply-To: <51351.163.178.104.130.1118450911.squirrel@webmail1.pair.com> References: <51351.163.178.104.130.1118450911.squirrel@webmail1.pair.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-ywcM+ZVA36II8igN4GIs" Date: Sun, 12 Jun 2005 00:24:43 +0200 Message-Id: <1118528683.11644.5.camel@cream.xbsd.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port X-Virus-Scanned: amavisd-new at xbsd.org Cc: hackers@freebsd.org Subject: Re: NDIS driver Intel(R) PRO/Wireless 2200BG reaches kernel panic X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2005 22:24:46 -0000 --=-ywcM+ZVA36II8igN4GIs Content-Type: text/plain; charset=iso8859-15 Content-Transfer-Encoding: quoted-printable Le Vendredi 10 juin 2005 =E0 18:48 -0600, Braulio Jos=E9 Solano Rojas a =E9crit : > Hello. >=20 > I have installed FreeBSD 5.4 on a ASUS S5200N. Runs very nice! >=20 > However I still need to install Wifi. I saw that Intel(R) PRO/Wireless > 2200BG is not supported by wlan FreeBSD driver (reading through the man > pages). Then I found that I could use the NDIS driver added on FreeBSD > 5.3 to achieve Wireless Networking. This chipset is supported by iwi(4) driver, but it hasn't been=20 MFC'ed to RELENG_5. Here [1] is a port I'm planning to commit that installs the=20 needed firmware and optionally (you seem to need it though) a=20 kernel module to support your card. I can't test it by myself, so I'd be glad you test it for me. It has a rcNG script, if you just put iwi_enable=3D"YES" it will try to set iwi0 in bss mode. Just put if_iwi_enable=3D"YES" in /boot/loader.conf so that it works at boot time. See pkg-message for more information. Note: It needs latest modifications I just committed to=20 net/ipw-firmware.=20 Note2: Sorry, it has nothing to do with ndis(4). [1] http://www.xbsd.org/~flz/ports/iwi-firmware.shar --=20 Florent Thoumie flz@xbsd.org --=-ywcM+ZVA36II8igN4GIs Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBCq2SrMxEkbVFH3PQRAh6nAKCCYLIqXObVdQGojt2SxJHX4FHd/ACcDCok hW0nyhAjMLzz1fMr94pcOyc= =d3zN -----END PGP SIGNATURE----- --=-ywcM+ZVA36II8igN4GIs-- From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 11 22:54:20 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1EAA16A41C; Sat, 11 Jun 2005 22:54:20 +0000 (GMT) (envelope-from nock@email.arizona.edu) Received: from smtpgate.email.arizona.edu (deagol.email.Arizona.EDU [128.196.133.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F57943D49; Sat, 11 Jun 2005 22:54:20 +0000 (GMT) (envelope-from nock@email.arizona.edu) Received: from localhost (boromir.email.arizona.edu [10.0.0.217]) by smtpgate.email.arizona.edu (Postfix) with ESMTP id 40779ADB37D; Sat, 11 Jun 2005 15:54:20 -0700 (MST) Received: from [10.10.10.201] (ip68-231-138-22.tc.ph.cox.net [68.231.138.22]) by smtpgate.email.arizona.edu (Postfix) with ESMTP id 93E2FADADF9; Sat, 11 Jun 2005 15:54:19 -0700 (MST) From: Shawn Nock To: hackers@freebsd.org In-Reply-To: <1118528683.11644.5.camel@cream.xbsd.org> References: <51351.163.178.104.130.1118450911.squirrel@webmail1.pair.com> <1118528683.11644.5.camel@cream.xbsd.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-fBpkJ/PnH/vCo/Ibgs0Q" Organization: University of Arizona Date: Sat, 11 Jun 2005 15:54:11 -0700 Message-Id: <1118530451.912.7.camel@rainbow> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port X-Virus-Scanned: amavisd-new at email.arizona.edu Cc: mobile@freebsd.org Subject: Re: NDIS driver Intel(R) PRO/Wireless 2200BG reaches kernel panic X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2005 22:54:21 -0000 --=-fBpkJ/PnH/vCo/Ibgs0Q Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Coincidently, I tried to revert to the ndis wrapper for my 2200bg after several months using if_iwi... (iwi has some problems: won't associate with hidden ssid host & the g speed negociation leaves something to be desired) I am experiencing the same panic on a very recent current: FreeBSD rainbow.kuatcom.local 6.0-CURRENT FreeBSD 6.0-CURRENT #5: Sat Jun 11 03:15:34 MST 2005 4 months ago if_ndis worked fine with this card... Can't tell you when it broke (just tried today...).=20 Supplimentary information can be provided if anyone is interested in working on the problem. FYI (Probably unrelated): The only thing that changed in my config is the addition of ULE+PREEMPTION. On Sun, 2005-06-12 at 00:24 +0200, Florent Thoumie wrote: > Le Vendredi 10 juin 2005 =E0 18:48 -0600, Braulio Jos=E9 Solano Rojas a > =E9crit : > > Hello. > >=20 > > I have installed FreeBSD 5.4 on a ASUS S5200N. Runs very nice! > >=20 > > However I still need to install Wifi. I saw that Intel(R) PRO/Wireless > > 2200BG is not supported by wlan FreeBSD driver (reading through the man > > pages). Then I found that I could use the NDIS driver added on FreeBSD > > 5.3 to achieve Wireless Networking. >=20 > This chipset is supported by iwi(4) driver, but it hasn't been=20 > MFC'ed to RELENG_5. >=20 > Here [1] is a port I'm planning to commit that installs the=20 > needed firmware and optionally (you seem to need it though) a=20 > kernel module to support your card. >=20 > I can't test it by myself, so I'd be glad you test it for me. >=20 > It has a rcNG script, if you just put iwi_enable=3D"YES" it will > try to set iwi0 in bss mode. Just put if_iwi_enable=3D"YES" in > /boot/loader.conf so that it works at boot time. See pkg-message > for more information. >=20 > Note: It needs latest modifications I just committed to=20 > net/ipw-firmware.=20 >=20 > Note2: Sorry, it has nothing to do with ndis(4). >=20 > [1] http://www.xbsd.org/~flz/ports/iwi-firmware.shar >=20 --=20 Shawn Nock (OpenPGP: 0x8ED6EE9A) Broadcast Engineer; KUAT-TV 6, Tucson, AZ University of Arizona nock@email.arizona.edu desk: 520.621.3280 cell: 520.820.0687 --=-fBpkJ/PnH/vCo/Ibgs0Q Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBCq2uTXOm+F47W7poRAlAEAJ9MWCPTpmm/PCbvoSJFv8WLlc9evACfQJNB T0R5x1K0r2sRYEy+Wk3GsO0= =JAn6 -----END PGP SIGNATURE----- --=-fBpkJ/PnH/vCo/Ibgs0Q-- From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 11 23:29:48 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7396916A41C for ; Sat, 11 Jun 2005 23:29:48 +0000 (GMT) (envelope-from braulio@solsoft.co.cr) Received: from wbm3.pair.net (wbm3.pair.net [209.68.3.66]) by mx1.FreeBSD.org (Postfix) with SMTP id DD42643D49 for ; Sat, 11 Jun 2005 23:29:47 +0000 (GMT) (envelope-from braulio@solsoft.co.cr) Received: (qmail 99632 invoked by uid 65534); 11 Jun 2005 23:29:47 -0000 Received: from 163.178.104.130 ([163.178.104.130]) (SquirrelMail authenticated user braulio@solsoft.co.cr) by webmail3.pair.com with HTTP; Sat, 11 Jun 2005 17:29:47 -0600 (CST) Message-ID: <63049.163.178.104.130.1118532587.squirrel@webmail3.pair.com> In-Reply-To: <1118530451.912.7.camel@rainbow> References: <51351.163.178.104.130.1118450911.squirrel@webmail1.pair.com> <1118528683.11644.5.camel@cream.xbsd.org> <1118530451.912.7.camel@rainbow> Date: Sat, 11 Jun 2005 17:29:47 -0600 (CST) From: Braulio =?iso-8859-1?Q?Jos=E9_Solano_Rojas?= To: "Shawn Nock" User-Agent: SquirrelMail/1.4.4 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, mobile@freebsd.org Subject: Re: NDIS driver Intel(R) PRO/Wireless 2200BG reaches kernel panic X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2005 23:29:48 -0000 I have tried using the w29n50.sys file instead of w29n51.sys. It seems that the NDIS wrapper has some trouble with NDIS 5.1 drivers. However it works sometimes. When I kldload the driver I get this: no match for MmMapIoSpace no match for MmUnmapIoSpace no match for InterlockedExchange ndis0: mem 0xfe8fe000-0xfe8fefff irq 18 at device 5.0 on pci1 ndis0: NDIS API version: 5.0 ndis0: Ethernet address: 00:0e:35:40:56:24 ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps (And everything works fine... however...) But sometimes I get this: no match for MmMapIoSpace no match for MmUnmapIoSpace no match for InterlockedExchange ndis0: mem 0xfe8fe000-0xfe8fefff irq 18 at device 5.0 on pci1 ndis0: NDIS API version: 5.0 ndis0: NDIS ERROR: c000138d (unknown error) ndis0: NDIS NUMERRORS: 0 ndis0: init handler failed device_attach: ndis0 attach returned 6 And sometimes I get kernel panic. If I add the driver to loader.conf I always get ndis0 attach returned 6. Just FYI... Shawn Nock dijo: > Coincidently, I tried to revert to the ndis wrapper for my 2200bg after > several months using if_iwi... (iwi has some problems: won't associate > with hidden ssid host & the g speed negociation leaves something to be > desired) > > I am experiencing the same panic on a very recent current: > > FreeBSD rainbow.kuatcom.local 6.0-CURRENT FreeBSD 6.0-CURRENT #5: Sat > Jun 11 03:15:34 MST 2005 > > 4 months ago if_ndis worked fine with this card... Can't tell you when > it broke (just tried today...). > > Supplimentary information can be provided if anyone is interested in > working on the problem. > > FYI (Probably unrelated): The only thing that changed in my config is > the addition of ULE+PREEMPTION. > > > > On Sun, 2005-06-12 at 00:24 +0200, Florent Thoumie wrote: >> Le Vendredi 10 juin 2005 à 18:48 -0600, Braulio José Solano Rojas a >> écrit : >> > Hello. >> > >> > I have installed FreeBSD 5.4 on a ASUS S5200N. Runs very nice! >> > >> > However I still need to install Wifi. I saw that Intel(R) >> PRO/Wireless >> > 2200BG is not supported by wlan FreeBSD driver (reading through the >> man >> > pages). Then I found that I could use the NDIS driver added on >> FreeBSD >> > 5.3 to achieve Wireless Networking. >> >> This chipset is supported by iwi(4) driver, but it hasn't been >> MFC'ed to RELENG_5. >> >> Here [1] is a port I'm planning to commit that installs the >> needed firmware and optionally (you seem to need it though) a >> kernel module to support your card. >> >> I can't test it by myself, so I'd be glad you test it for me. >> >> It has a rcNG script, if you just put iwi_enable="YES" it will >> try to set iwi0 in bss mode. Just put if_iwi_enable="YES" in >> /boot/loader.conf so that it works at boot time. See pkg-message >> for more information. >> >> Note: It needs latest modifications I just committed to >> net/ipw-firmware. >> >> Note2: Sorry, it has nothing to do with ndis(4). >> >> [1] http://www.xbsd.org/~flz/ports/iwi-firmware.shar