SunFire X4100 MPT Issues 6.2 RC1
We have a new SunFire X4100 box and so I figured I would try 6.2 RC1 on it. Everything seems to work with the exception of the following messages when the disk has some medium to heavy use. mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 65 mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x03 Depth 65 So are these something to be concerned about? Secondly, are there any issues I should be concerned about running 6.2 on this hardware? dmesg of i386 verbose boot can be found here: http://wiki.nostrum.com/~daved/sunfire-4100.dmesg.txt I get the same messages when running amd64 port as well. Thanks, -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SunFire X4100 MPT Issues 6.2 RC1
On Nov 23, 2006, at 2:16 PM, Matthew Jacob wrote: [i'm on vacation now] Hmm- I thought I put in code so you should only see one of those. I'll check this out when I get back next week. Thanks for your help. One thing to note is that the firmware and BIOS of the unit was upgraded to try and fix another problem and because of this, the unit will not boot directly from the controller. I don't think this is your problem so if anybody has any thoughts on what path I should take on trying to get this fixed, I would be much appreciated. Here is the output from the console: BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 612kB/4060704kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Thu Nov 16 01:32:15 UTC 2006) int=000d err=001a efl=00030287 eip=290f eax=140a ebx=0b40 ecx= edx=cf00 esi=0d1c edi=0001 ebp=0206 esp=0200 cs=cf00 ds=9a00 es=9a00fs= gs= ss=9a00 cs:eip=cc 68 32 06 ff 34 e8 db-fc 83 c4 04 89 46 fe 5f 5e c9 c3 55 8b ec 1e 33-c0 8e d8 a0 75 04 3c 00 ss:esp=1c 0d 02 00 00 00 34 02-32 46 1c 0d 00 00 00 14 00 00 00 00 01 00 00 00-1c 0d 02 00 00 00 00 00 BTX halted The unit boots find from the network. I guess I get to see if I can downgrade the firmware but I am not having much luck finding previous images. -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SunFire X4100 MPT Issues 6.2 RC1
On Nov 25, 2006, at 10:06 PM, Jeremy Chadwick wrote: On Sat, Nov 25, 2006 at 09:49:13PM -0600, Dave wrote: The unit boots find from the network. I guess I get to see if I can downgrade the firmware but I am not having much luck finding previous images. Have you tried talking to Sun about this? The problem really does sound like it's with the BIOS not supporting the ability to boot off of an external controller. This would be something Sun would have to address, would it not? We have talked to Sun about it and have not heard back on a fix for the latest BIOS. We have been given an older version of the BIOS that does not have this issue. Also, for what it's worth, I have a couple Intel boards which also exhibit the same issue (re: can't boot off of an external controller). The solution I went with was to use the onboard SATA controller instead of my Promise controller. :-) This is an internal on the motherboard controller that drives the built-in disks. -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SunFire X4100 MPT Issues 6.2 RC1
On Dec 1, 2006, at 12:47 PM, Vivek Khera wrote: On Dec 1, 2006, at 11:29 AM, Dave wrote: We have talked to Sun about it and have not heard back on a fix for the latest BIOS. We have been given an older version of the BIOS that does not have this issue. Which version of bios is the latest that works for you? I have two of these X4100's and they both came with bios 1.0.0 (even though purchased 10 months apart). I'm now afraid to update the bios since we boot from an external RAID array. We are running the 1.2.1 package from Sun on the ILOM card and the system BIOS. The LSI card is running: LSI Logic Corp. MPT SAS BIOS MPTBIOS-6.04.07.00 (2005.11.03) Copyright 2000-2005 LSI Logic Corp. The upgrade to the ILOM card, and consequently the system BIOS, will not upgrade the LSI card and cause the boot problem that has been reported by me and others. As far as I know, the problem is only caused by upgrading the LSI MPT card to version 6.06.06.00. -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Hardware Security Modules
Anybody have a list of hardware security modules that work with FreeBSD? Mostly looking for units that certificate authority functions (signing, secure key storage). Any help that you can provide would be greatly appreciated. Thanks for your time, -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
internal compiler error: segmentation fault: 11
Hello, I'm trying to compile 6.0-stable on a release box, prior to upgrade. I've tried several times and all end with an internal compiler error: segmentation fault: 11. And then i'm told to submit a bug report. My problem is when this occurs it's not always at the same spot or the same file. One time it even core dumped, though only once. At this point i would appreciate any suggestions, i'm hoping this is not the indicator of a problem. Thanks. Dave. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sysinstall on boot.flp enters boot loop with md device
Hello, Trying to install 5.4 on a box that had previously run 5.3 just fine and before that 5.2. I wanted to do a fresh install vs. an upgrade and unfortunately this box can not boot from CD, the install is also headless. I created the floppies, then mounted boot.flp and put a boot.config file on it with "-h" contained within. I then booted the install, got through the point where i had to reinsert the boot.flp disk, after the two kern*.flp disks, and the system went in to a loop. Here's the repeating error: spec_getpages:(md0) I/O read failure: (error=5) bp 0xc94fb9ec vp 0xc1d42d68 size: 36864, resid: 36864, a_count: 36864, valid: 0x0 nread: 0, reqpage: 0, pindex: 459, pcount: 9 vm_fault: pager read error, pid 1 (sysinstall) At first i thought it was a media issue or a download issue, but i've verified the md5 signature of the image, which came off a 5.4-RELEASE cd-rom, and have recreated four boot.flp floppies with the same result. My dmesg is below. Any input welcome. Thanks. Dave. dmesg: Uncompressing ... done Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS 638kB/392192kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Sun May 8 05:59:07 UTC 2005) Loading /boot/defaults/loader.conf /kernel text=0x444168 \ Insert disk labelled "Kernel floppy 1" and press any key... | Insert disk labelled "Kernel floppy 2" and press any key... data=0x7d5c8+0x4fc78 syms=[0x4+0x5b390+0x4+0x706c9] Insert boot floppy and press Enter /acpi.ko text=0x414fc data=0x1dc4+0x112c syms=[0x4+0x7670+0x4+0x9d05] zf_read: fill error Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (397.33-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 402653184 (384 MB) avail memory = 380243968 (362 MB) ACPI-0159: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES ACPI: table load failed: AE_NO_ACPI_TABLES npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xfcd0-0xfcdf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0xfce0-0xfcff irq 11 at device 4.2 on pci0 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 pci0: at device 4.3 (no driver attached) ed0: port 0xf8e0-0xf8ff irq 3 at device 13.0 on pci0 ed0: Ethernet address: 00:20:78:1a:5d:ab ed0: if_start running deferred for Giant ed0: type NE2000 (16 bit) rl0: port 0xf400-0xf4ff mem 0xfedffc00-0xfedffcff irq 10 at device 14.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:e0:7d:d9:a1:58 orm0: at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) uhid0: American Power Conversion Back-UPS RS 1500 FW:8.g8 .D USB FW:g8, rev 1.10/1.06, addr 2, iclass 3/0 Timecounter "TSC" frequency 397331331 Hz quality 800 Timecounters tick every 10.000 msec md0: Preloaded image 3719168 bytes at 0xc0a34270 ad0: 4104MB [8895/15/63] at ata0-master UDMA33 ad2: 4028MB [8184/16/63] at ata1-master UDMA33 Mounting root from ufs:/dev/md0 spec_getpages:(md0) I/O read failure: (error=5) bp 0xc94fb9ec vp 0xc1d42d68
trouble booting 5.4 installation media (repost)
Hello, Didn't get a response so i'm going to try this again. I'm trying to do a fresh install of 5.4 on a test machine, which previously ran 5.3 just fine. I'm doing the install via a serial terminal as this box is headless and off of an nfs server which i've also prepared identically to 5.3. I have made the three floppies, boot.flp and the two kern*.flp disks, then mounted boot.flp and created a boot.config file on it with "-h" so i get output on serial port1. All this works fine, i am prompted to switch disks to the two kern* disks, again no problems. When i put in boot.flp after being prompted after kern2.flp i get a repeating error, which is below from sysinstall and the process goes no further. At first i thought it was a problem with the downloaded iso image, so i checked the md5 signatures, they matched, then i rewrote the floppy in question, on 4 different disks with the same result. Any help appreciated. Thanks. Dave. error: Uncompressing ... done Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS 638kB/392192kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Sun May 8 05:59:07 UTC 2005) Loading /boot/defaults/loader.conf /kernel text=0x444168 \ Insert disk labelled "Kernel floppy 1" and press any key... | Insert disk labelled "Kernel floppy 2" and press any key... data=0x7d5c8+0x4fc78 syms=[0x4+0x5b390+0x4+0x706c9] Insert boot floppy and press Enter /acpi.ko text=0x414fc data=0x1dc4+0x112c syms=[0x4+0x7670+0x4+0x9d05] zf_read: fill error Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (397.33-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 402653184 (384 MB) avail memory = 380243968 (362 MB) ACPI-0159: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES ACPI: table load failed: AE_NO_ACPI_TABLES npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xfcd0-0xfcdf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0xfce0-0xfcff irq 11 at device 4.2 on pci0 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 pci0: at device 4.3 (no driver attached) ed0: port 0xf8e0-0xf8ff irq 3 at device 13.0 on pci0 ed0: Ethernet address: 00:20:78:1a:5d:ab ed0: if_start running deferred for Giant ed0: type NE2000 (16 bit) rl0: port 0xf400-0xf4ff mem 0xfedffc00-0xfedffcff irq 10 at device 14.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:e0:7d:d9:a1:58 orm0: at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) uhid0: American Power Conversion Back-UPS RS 1500 FW:8.g8 .D USB FW:g8, rev 1.10/1.06, addr 2, iclass 3/0 Timecounter "TSC" frequency 397331331 Hz quality 800 Timecounters tick every 10.000 msec md0: Preloaded image 3719168 bytes at 0xc0a34270 ad0: 4104MB [8895/15/63] at ata0-master UDMA33 ad2: 4028MB [8184/16/63] at ata1-master UDMA33 Mounting root from ufs:/dev/md0 spec_getpages:(md0) I/O read failure: (error=5) bp 0xc94fb9ec vp 0xc1d42d68 size: 36864, resid: 36864, a_count: 36864, valid: 0x0
trouble booting 5.4 installation media (repost)
Hello, Didn't get a response so i'm going to try this again. I'm trying to do a fresh install of 5.4 on a test machine, which previously ran 5.3 just fine. I'm doing the install via a serial terminal as this box is headless and off of an nfs server which i've also prepared identically to 5.3. I have made the three floppies, boot.flp and the two kern*.flp disks, then mounted boot.flp and created a boot.config file on it with "-h" so i get output on serial port1. All this works fine, i am prompted to switch disks to the two kern* disks, again no problems. When i put in boot.flp after being prompted after kern2.flp i get a repeating error, which is below from sysinstall and the process goes no further. At first i thought it was a problem with the downloaded iso image, so i checked the md5 signatures, they matched, then i rewrote the floppy in question, on 4 different disks with the same result. Any help appreciated. Thanks. Dave. error: Uncompressing ... done Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS drive D: is disk2 BIOS 638kB/392192kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Sun May 8 05:59:07 UTC 2005) Loading /boot/defaults/loader.conf /kernel text=0x444168 \ Insert disk labelled "Kernel floppy 1" and press any key... | Insert disk labelled "Kernel floppy 2" and press any key... data=0x7d5c8+0x4fc78 syms=[0x4+0x5b390+0x4+0x706c9] Insert boot floppy and press Enter /acpi.ko text=0x414fc data=0x1dc4+0x112c syms=[0x4+0x7670+0x4+0x9d05] zf_read: fill error Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (397.33-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 402653184 (384 MB) avail memory = 380243968 (362 MB) ACPI-0159: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES ACPI: table load failed: AE_NO_ACPI_TABLES npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xfcd0-0xfcdf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: port 0xfce0-0xfcff irq 11 at device 4.2 on pci0 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 pci0: at device 4.3 (no driver attached) ed0: port 0xf8e0-0xf8ff irq 3 at device 13.0 on pci0 ed0: Ethernet address: 00:20:78:1a:5d:ab ed0: if_start running deferred for Giant ed0: type NE2000 (16 bit) rl0: port 0xf400-0xf4ff mem 0xfedffc00-0xfedffcff irq 10 at device 14.0 on pci0 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:e0:7d:d9:a1:58 orm0: at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) uhid0: American Power Conversion Back-UPS RS 1500 FW:8.g8 .D USB FW:g8, rev 1.10/1.06, addr 2, iclass 3/0 Timecounter "TSC" frequency 397331331 Hz quality 800 Timecounters tick every 10.000 msec md0: Preloaded image 3719168 bytes at 0xc0a34270 ad0: 4104MB [8895/15/63] at ata0-master UDMA33 ad2: 4028MB [8184/16/63] at ata1-master UDMA33 Mounting root from ufs:/dev/md0 spec_getpages:(md0) I/O read failure: (error=5) bp 0xc94fb9ec vp 0xc1d42d68 size: 36864, resid: 36864, a_count: 36864, valid: 0x0
gmirror unable to boot kernel from second disk
Hello, I posted this to -questions but haven't got a response. I'm following procedure2 of the gmirror for system disks howto at: http://people.freebsd.org/~rse/mirror/ and i get to the first reboot stage. The box never comes back up. I have to plug in a monitor to it as i do everything via ssh and it says that it can't find the kernel. This is using the stage2 boot loader on the first disk to boot stage3 off the second disk in preparation for sync-ing the two disks and bringing up the raid. This is on a 5.4-stable box cvsupped as of last week. This is my third atempt at raid1 on this box, on another box this procedure went fine, it's also running -stable. Before i rebooted the box i checked /mnt/boot/kernel and there was indeed a kernel file in that location. Up until the first reboot i didn't get any errors, or warnings, and the procedure went fine. Any help appreciated. Thanks. Dave. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kernel Update / IPFW not working
Hi all An IPFW problem when going from release to stable on 8.2 An help gladly accepted LOG ON Flushed all rules. 00010 allow ip from 127.0.0.1 to 127.0.0.1 via lo0 00030 divert 8668 ip from any to any via bge0 ipfw: getsockopt(IP_FW_ADD): Invalid argument 5 allow ip from any to any Firewall rules loaded. Starting natd. rc.conf defaultrouter="192.168.0.1" gateway_enable="YES" hostname="xxx.xxx.xxx" ifconfig_bge0="inet 192.168.0.11 netmask 255.255.255.0" ifconfig_em0="inet 192.168.1.2 netmask 255.255.255.0" keymap="us.iso" moused_enable="YES" sshd_enable="YES" firewall_enable="YES" firewall_script="/etc/rc.firewall" natd_program="/sbin/natd" natd_enable="YES" natd_interface="bge0" natd_flags="-f /etc/natd.conf" dhcpd_enable="NO" dhcpd_flags="-q" dhcpd_conf="/usr/local/etc/dhcpd.conf" dhcpd_ifaces="em0" dhcpd_withumask="022" natd.conf interface bge0 use_sockets yes same_ports yes log #redirect_port tcp 192.168.1.189:3389 3389 #redirect_port tcp 192.168.1.53:5500 5500 #!/bin/sh /sbin/ipfw -f flush /sbin/ipfw -f pipe flush #Nat Rules /sbin/ipfw add 10 allow ip from 127.0.0.1 to 127.0.0.1 via lo0 /sbin/ipfw add 30 divert natd all from any to any via bge0 #Forward to Transparent Proxy Server #/sbin/ipfw add 10001 fwd 127.0.0.1,3128 tcp from any to any 80 #/sbin/ipfw add 10010 fwd 127.0.0.1,3128 tcp from 10.0.21.2 to any 80 /sbin/ipfw add 10001 fwd 127.0.0.1,3128 tcp from any to any 80 /sbin/ipfw add 5 allow ip from any to any KERNEL options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=5 options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT options DUMMYNET Regards ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Port 80 closed?
Hi all An IPFW problem? An help gladly accepted It would appear Port 80 closed Ports 21 25 443 587 998 work well rc.conf defaultrouter="192.168.0.1" gateway_enable="YES" hostname="xxx.xxx.xxx" ifconfig_re0="inet 192.168.0.11 netmask 255.255.255.0" ifconfig_re1="inet 192.168.1.2 netmask 255.255.255.0" keymap="us.iso" moused_enable="YES" sshd_enable="YES" firewall_enable="YES" firewall_script="/etc/rc.firewall" natd_program="/sbin/natd" natd_enable="YES" natd_interface="re0" natd_flags="-f /etc/natd.conf" dhcpd_enable="NO" dhcpd_flags="-q" dhcpd_conf="/usr/local/etc/dhcpd.conf" dhcpd_ifaces="re1" dhcpd_withumask="022" natd.conf interface re0 use_sockets yes same_ports yes log #redirect_port tcp 192.168.1.189:3389 3389 #redirect_port tcp 192.168.1.53:5500 5500 #!/bin/sh /sbin/ipfw -f flush /sbin/ipfw -f pipe flush #Nat Rules /sbin/ipfw add 10 allow ip from 127.0.0.1 to 127.0.0.1 via lo0 /sbin/ipfw add 30 divert natd all from any to any via re0 #Forward to Transparent Proxy Server #/sbin/ipfw add 10001 fwd 127.0.0.1,3128 tcp from any to any 80 #/sbin/ipfw add 10010 fwd 127.0.0.1,3128 tcp from 10.0.21.2 to any 80 /sbin/ipfw add 10001 fwd 127.0.0.1,3128 tcp from any to any 80 /sbin/ipfw add 5 allow ip from any to any Regards ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ZFS V28 on 8.2-RELEASE write behavior
Hello,
I'm running ZFS V28 with 8.2-RELEASE. Its a stock system patched with
the following
http://people.freebsd.org/~mm/patches/zfs/v28/releng-8.2-zfsv28-20110616.patch.xz
https://www.illumos.org/attachments/292/txg.c.patch
The zfsv28 patch did have a failed hunk in
/usr/src/sys/cddl/compat/opensolaris/sys/sysmacros.h but it appeared
that was because the file already existed identically in my src tree.
I have not upgraded the zpool, it remains at v15 in case I need to
drop back to the old kernel. I've removed all zfs related
loader/sysctl options I had in from v15.
What I'm seeing is strange write behavior. When I first set it up I'd
see writes in small bursts of 100 megs or so every 5 seconds. Now I'm
seeing small writes and reads are stalling.
This is what it looks like when IO is horrible:
capacity operationsbandwidth
poolalloc free read write read write
-- - - - - - -
san 3.97T 8.66T269228 6.54M 21.9M
san 3.97T 8.66T 2142 131K 1.18M
san 3.97T 8.66T952 0 52.7M 0
san 3.97T 8.66T527149 24.7M 1.22M
san 3.97T 8.66T 2181 192K 1.35M
san 3.97T 8.66T 1.17K 0 47.9M 0
san 3.97T 8.66T452247 23.6M 3.40M
san 3.97T 8.66T702268 23.8M 3.38M
san 3.97T 8.66T 0 0 0 0
san 3.97T 8.66T686255 30.7M 3.39M
san 3.97T 8.66T379229 19.3M 2.82M
san 3.97T 8.66T 94 0 5.59M 0
san 3.97T 8.66T 1004243 52.4M 3.32M
san 3.97T 8.66T 3270 195K 3.48M
san 3.97T 8.66T250 0 14.6M 0
san 3.97T 8.66T439250 15.5M 3.42M
san 3.97T 8.66T 1257 128K 3.65M
It gets better for short periods and looks like this
san 3.95T 8.68T 1004 55 53.1M 360K
san 3.95T 8.68T341533 10.6M 42.4M
san 3.95T 8.68T783 0 43.5M 0
san 3.95T 8.68T409374 17.1M 35.5M
san 3.95T 8.68T423117 18.4M 3.83M
san 3.95T 8.68T 1.01K136 43.2M 2.26M
san 3.95T 8.68T447454 16.8M 35.4M
san 3.95T 8.68T991 0 46.3M 0
san 3.95T 8.68T420394 21.8M 32.9M
san 3.95T 8.68T 1.16K241 54.4M 6.00M
san 3.95T 8.68T575 0 20.4M 0
san 3.95T 8.68T284328 9.77M 30.3M
san 3.95T 8.68T663203 33.6M 5.15M
san 3.95T 8.68T319 0 10.0M 0
san 3.95T 8.68T318453 10.0M 24.0M
san 3.95T 8.68T 1.06K299 30.9M 25.0M
I also see very high CPU usage on a few ZFS related threads
38 root -8- 0K 7536K zio->i 3 64:23 25.20% {txg_thread_enter}
0 root -160 0K 2704K sm->sm 0 66:48 21.39% {zio_write_issue_}
0 root -160 0K 2704K sm->sm 1 66:36 18.16% {zio_write_issue_}
0 root -160 0K 2704K sm->sm 1 67:50 13.77% {zio_write_issue_}
0 root -160 0K 2704K CPU33 67:28 12.16% {zio_write_issue_}
These would be a 1-2% each prior. Any help tracking this down would be
greatly appreciated.
Thanks,
--
Dave Cundiff
System Administrator
A2Hosting, Inc
http://www.a2hosting.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS V28 on 8.2-RELEASE write behavior
> >> Any help tracking this down would be greatly appreciated. >> > > There have been numerous changes to v28 in -STABLE since June. > Can you reproduce the behavior with a recent build of -STABLE instead of > -RELEASE? Perhaps even on -CURRENT? > I can sure give that a try. I'm 95% sure my ZFS code is pretty up to date compared to stable. I dug through svn-src-stable-8 for anything ZFS related and only caught 1 patch that, though severe, is not a feature I'm currently using. The rest are either minor functionality that I don't use, memory saving of which I have tons, or cosmetic. Granted any patches to the OS that didn't involve a directory/file with ZFS or CDDL in it I would definitely have missed. -- Dave Cundiff System Administrator A2Hosting, Inc http://www.a2hosting.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Attempting to boot into ramdisk on 8.3
I have a build process (which worked at release 7.3) that makes a bootable ISO using a ramdisk image as the boot volume. At release 8 it panics right after reporting the real memory size with: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode ... [thread pid 0 tid 0 ] Stopped at pmap_enter+0x19a:moveq (%rcx),%r14 (I have the text frozen on another screen if more data is needed, I've literally spent weeks trying to get this panic to appear on the screen so it's not going anywhere.) I build the world with this system without cross compiling. # uname -mrs FreeBSD 8.3-RC1 amd64 The system that paniced is very similar: a 64-bit amd4 system. What am I doing wrong, if anything? How can I do a successful large ramdisk boot? My process is to copy the entire OS to a ramdisk and boot off of that. I use the following ideas for this: /boot/loader.conf: mfsroot_type="mfs_root" mfsroot_name="/mfsboot" vfs.root.mountfrom="ufs:md0" vfs.root.mountfrom.options="rw" ## Tunables kern.ipc.nmbclusters=32768 net.inet.tcp.tcbhashsize=16384 vm.pmap.pg_ps_enabled=1 accf_http_load="YES" net.inet.tcp.syncache.hashsize=1024 net.inet.tcp.syncache.bucketlimit=100 The size of mfsboot is 600M. The diff between GENERIC and my kernel config, comments left in so people can see what I was doing 7.3ish: 28.43d26 < ### FBCD64 SPECIFIC < #options MD_ROOT_SIZE="524288" < options GEOM_UZIP < #options INCLUDE_CONFIG_FILE < #options ZERO_COPY_SOCKETS < #options HZ=1000 < #options DEVICE_POLLING < #options NKPT=600# not set up on amd64 < # < # Debugging < options KDB < options DDB < options BREAK_TO_DEBUGGER < options ALT_BREAK_TO_DEBUGGER Thanks in advance for any assistance! -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< One of the most common defenses against really learning something is to believe that one knows it already. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Attempting to boot into ramdisk on 8.3
Replying to myself here for the edification of those interested. A value of 320 for NKPT eliminated this crash, set in the kernel config file: options NKPT=320 For those of you with large ramdisk booting requirements, this one option will likely save you hours of trial and error. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< None should say "I can trust" or "I cannot trust" until they are the master of the option of trusting or not trusting. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why Are You Using FreeBSD?
Flemming Jacobsen writes: > Damien Fleuriot wrote: >> You missed the bit about 3 reboots, while these don't take 15 mins each, >> they're still time consuming and disruptive. >> 1/ reboot after installing new kernel >> 2/ reboot after installing new world >> 3/ reboot after rebuilding ports > Or ... use sysbuild (/usr/src/tools/tools/sysbuild) and just boot > once. I respectfully disagree here. Sysbuild makes some assumptions about the partition layout which you'd need to factor in before you created your server. For the average layout (single disk, single partition), sysbuild won't be easy to make work. More generally, it's best not to clutter this interesting thread with delusions of rapidity. Given ports/packages/rpms/etc ... I claim it does not matter what system you use: There's just too much software out there that all has to work together to expect a simple upgrade to take 5 minutes on a well managed production server. I believe the more cogent solution is along these lines: Kevin Oberman writes: > Make your own freebsd-update server and build whatever custom system > you need. It does not need to be a GENERIC kernel. It does not need to > be RELEASE.Then use freebsd-update to update all of your production > systems with a single reboot and about 15 minutes (depending on system > and disk speed and I have not actually timed it).and it can be done > without console access or a single-user boot. If you take some time and plan your deployment and server layout, a single (even virtualized) server dedicated to building world and ports can help homogenize and streamline upgrades of large numbers of FreeBSD servers. I'd imagine that anything over 10 servers would almost demand this kind of attention to detail, but that's me. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< People complain about time being short, going fast. But when it seems to go slowly they complain that it drags. Let us consider the people, not the supposed movements of time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why Are You NOT Using FreeBSD ?
Mehmet Erol Sanliturk writes: > If you are NOT using FreeBSD for any area or some areas , would you please > list those areas with most important first to least important last ? 1) I don't use FreeBSD for virtualization as the host OS. I really want to, becaus I want to be able to somewhat trust the kernel hosting my virtual machines. FreeBSD technology, support, and documentation for this idea appears unavailable. 2) I don't use FreeBSD for a 'modern' desktop. By 'modern' I mean areas which most rank and file users would need: day-to-day non technical browsing with flash, applications like skype, syncing to mobile devices, etc. I'd imagine this is important for rank and file users. However, I'm an old schooler who likes text based applications and command lines, and I personally feel that a lot of the desktop technologies out there (Gnome, KDE, Aqua, Windows) are inherently unsafe (security wise) for a desktop I do software development on. One glance at my X-mailer should tell many people where I'm at. ;) As an example (please don't think I'm singling KDE out here, I can likely find examples for each desktop technology out there) I was given to understand that the KDE file browser allowed the execution of javascript. This single rumor has kept me from trying out KDE for years. Again, nothing against KDE in particular, all of the 'user friendly' desktop technologies likely have something just as egregious. Thus, in many ways I feel it's a *feature* of FreeBSD that the desktop software lags behind everyone else. I don't want flash in my Firefox. I don't want hal, bonjour, or dbus as an extra attack surface. I don't want gnome to auto discover all the fileshares on my network(s). 3) I don't use FreeBSD for games, sadly. This is the only place where I will tolerate having a Windoze box, for my love of games exceeds my hatred of windows (yes I -really- do love games) and it's hard to find a better platform for games. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Freedom is free of the need to be free.-George Clinton ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why Are You NOT Using FreeBSD ?
Lars Engels writes: > I guess he made his experiences with that some years ago when support > for amd64 in the ports was not very mature. But this has changed since > then, apart from a few ports almost all of them should work on amd64 > without problems. I can vouch for this. I have several production and two development amd64 machines. I've yet to have a problem with a port because of the architecture. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Man does not have a capacity of instant comprehension. So rare is the knowledge of how to train this, that most people and institutions have compromised by playing upon man's proneness to conditioning and indoctrination instead. The end of *that* road is the ant-heap. Or, at best, the beehive. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why Are You NOT Using FreeBSD ?
Gary Palmer writes: > Have you looked at VirtualBox? /usr/ports/emulators/virtualbox-ose > Its not a fully featured replacement for vSphere (e.g. no equivalent > of vMotion) but it is a perfectly workable virtualisation solution > for a number of situations. I don't necessarily need vMotion. Thanks greatly for the tip, which is very valuable and the reason I like discussions like these. As I am trying to try this, of course I ran into a snag. This snag is very relevant to the current discussion(s) about ports and "ease of use". # cd /usr/ports/emulators/virtualbox-ose # make config I'm now presented with a number of options, but no real documentation for what these options actually mean (to say nothing of the -fine points- which can be drastically important). I can pretty much guess Qt4 is for a GUI frontend, but pulseaudio? Eh? Why do I need sound, especially pulseaudio, in a virtualbox hypervisor? What is VDE? Do I really need that to do intra-virtual-box networking at all or are there other solutions? I know. Google is a resource. Still, would it kill us to have some sort of extra file of textual documentation lying around for each port that explained each option in a bit more depth, what ports it will try to include, and why you'd want it or not want it? Ok so continuing... # make install ...way later... In file included from socket/qabstractsocket.cpp:2927: .moc/release-shared/moc_qabstractsocket.cpp:14:2: error: #error "This file was generated using the moc from 4.7.4. It" .moc/release-shared/moc_qabstractsocket.cpp:15:2: error: #error "cannot be used with the include files from this version of Qt." .moc/release-shared/moc_qabstractsocket.cpp:16:2: error: #error "(The moc has changed too much.)" Here you "just have to know" that this kind of an error likely means that the qt4-moc port is out of date. At this point, a "normal" user gives up. (A smarter "normal" user gave up when they couldn't figure out what the port options really meant.) When I talk about documentation and support being unavailable, this is a decent example of what I mean. I see features and pkgng and things being offered up as solutions...these are all well and good, but in my opinion more comprehensive documentation and support in these areas would do more good than pkgng. Even for us seasoned experts, installing something new out of ports is sometimes met with at least an hour of googling, re-compiling, re-installing, and struggling. It goes smoothly often enough, but IMO not often enough for prime time. All these ideas presume that the FreeBSD community wants more users. I have a vague impression that a percentage of the community really doesn't. I'm not commenting on this other than to say I understand both sides and that my comments really only make sense if FreeBSD as a community really does want more users. :) Anyway, given my workload, it will probably take me a man week to get two virtualized test servers. Someone I know with a vmware gui and windows is doing this in 15 minutes (and that's being careful). Just my $0.02. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< There's only one corner of the universe you can be certain of improving and that's your own self. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why Are You NOT Using FreeBSD ?
Mark Linimon writes: > On Sun, Jun 03, 2012 at 07:24:11PM -0700, Dave Hayes wrote: >> I see features and pkgng and things being offered up as solutions... >> these are all well and good, but in my opinion more comprehensive >> documentation and support in these areas would do more good than pkgng. > IMHO pkgng and optionsng are necessary, but not sufficient, to solve > our current problems. Optionsng is nice, but lacking in documentation. Is it too much to ask port maintainers to write a bit more documentation on the options they are providing? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Sunshine proves it's own existence. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why Are You NOT Using FreeBSD ?
Chris Rees writes: > On Jun 4, 2012 9:50 AM, "Dave Hayes" wrote: >> Mark Linimon writes: >> > On Sun, Jun 03, 2012 at 07:24:11PM -0700, Dave Hayes wrote: >> >> I see features and pkgng and things being offered up as solutions... >> >> these are all well and good, but in my opinion more comprehensive >> >> documentation and support in these areas would do more good than pkgng. >> > IMHO pkgng and optionsng are necessary, but not sufficient, to solve >> > our current problems. >> Optionsng is nice, but lacking in documentation. Is it too much to ask >> port maintainers to write a bit more documentation on the options they >> are providing? > Where are you looking? I updated the Porter's Handbook- is there something > missing? Yes there is...my point. :) Perhaps I was unclear. Optionsng is likely a fine project. However, it does not include the idea of extra documentation on the user selectable options provided to a port. Often when building a port I am presented with a list of build options. For example, virtualbox has this: OPTIONS= QT4 "Build with QT4 Frontend" on \ DEBUG "Build with debugging symbols" off \ GUESTADDITIONS "Build with Guest Additions" off \ DBUS "Build with D-Bus and HAL support" on \ PULSEAUDIO "Build with PulseAudio" off \ X11 "Build with X11 support" on \ UDPTUNNEL "Build with UDP tunnel support" on \ VDE "Build with VDE support" off \ VNC "Build with VNC support" off \ WEBSERVICE "Build Webservice" off \ NLS "Native language support" on What I feel is missing from ports is the information that would allow me to make intelligent decisions about each option. To see what's missing, consider the following questions: - Why would I want pulseaudio in a hypervisor? - What, exactly, are guestadditions and why would I want them? - Why does this need dbus and hal? - What is VDE? - What webservice? etc. The porter's handbook is fine if you are writing ports. It's using them that can get opaque. There's meta topics also, these would be great to know about without having to read 200 mail messages: - Some people do not like pulseaudio for good technical reasons. What are those? What are the non-technical opinion based reasons? - What are the common objections to HAL and DBUS? It's this kind of attention to communication that I think FreeBSD, in any attempt to reach more users, needs to strongly consider. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Treat people as if they are what they ought to be, and you help them to become what they are capable of being. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why Are You NOT Using FreeBSD ?
Chris Nehren writes: > The descriptions of the options assume the admin is familiar with the > software they're installing. I do not think it is the FreeBSD Project's > purview to document every option for every port. At the very least it'd > take quite a lot of time and effort to document all of that. That's a fair position. Perhaps it would not be too much trouble to add this one idea to optionsng: a "more info" field on each option knob which may be filled in by a port maintainer. > Beyond this, such explanations would duplicate each port's own > documentation. Not necessarily. I don't have an example offhand, but I suspect there are a number of FreeBSD specific option knobs applied to ports. > If you're not familiar with something, you very probably shouldn't be > installing it. Basing my argument here on assumptions that FreeBSD wants more users, I would argue that the better policy is to be liberal in who you help and conservative in who you call unfamiliar. In this spirit, I can guarantee you that there are plenty of people who will install despite your requirement above, set some option that they shouldn't (or fail to set one that they should), and then come away with a bad experience. Instead, if the person familiar with the software (who is ostensibly writing the port) could spend just 5 more minutes writing a simple "this option is documented at url://..." or "dont set this if you have port foo installed" that would help a lot of people. > Show me one other similar packaging system that does this level of > handholding. The only comparable ones I can think of are portage and > macports, and they certainly don't, either. The absence of such a system isn't really relevant to the idea of improving the current one is it? :) -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< "Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why Are You NOT Using FreeBSD ?
Daniel Kalchev writes: > On 04.06.12 22:32, Dave Hayes wrote: >> That's a fair position. Perhaps it would not be too much trouble to add >> this one idea to optionsng: a "more info" field on each option knob >> which may be filled in by a port maintainer. > The pkg-descr file in the port already contains link to the software's > origin. The various options the software has are or should be described > there. We definitely don't want the ports cluttered with extraneous and > sometimes out of date (and thus misleading) information. I'm describing more of a use case here, not attempting to specify an implementation. If a user invokes 'make', a window is presented to them with various options. It's probably very common that this is met with an initial reaction of "what the hell do these do?", even from the most seasoned of admins (presuming they are unfamiliar with the software they have been asked to install). I claim it would be an improvement to have that information at the fingertips of the make invoker. I believe this is the first time I've seen more documentation labeled as "extraneous". :) I had thought to suggest an implementation by having a simple pkg-option-desr file which describes the options and implications in each port. Are you suggesting that such a file would be unwelcome? I have built many ports for many years. IIRC I've seen the option descriptions you mention in pkg-descr maybe 0.1% of the time. (That's my sense, not a measured objective number.) Usually I have to go digging through the Makefile, then the source to find these answers. > In all case, compiling from source is not for those having no clue > what they do. ... you need to make informed decisions on options > yourself. If this is beyond you (and not you personally), ... > Since it is very likely that you interpret this as yet another elitist > comment, Actually, I hadn't thought of this conceptual linkage until you suggested it here. :) Still, you are quite correct. The likelihood of anyone interpreting your position as 'elitist' from these comments is high. I will, of course, not interpret them that way. > If this is beyond you (and not you personally), then by all means use > pre-packaged software in binary form. Heh. Even this idea is beyond most normal users, who should likely use PC-BSD or Ubuntu. In responding in this thread, I was thinking of the reasonably clued system admin level users when I said "users". As an SA, in many situations, you aren't able to have fun digging for information. It's much easier to have the answers right here in front of you. I know if I ever committed a port, I would quite likely spend the extra five minutes to put option documentation in a number of places, even if this angered some of the more anal of the community. > elsewhere" or "apparently, you don't want the number of FreeBSD users to > grow". Then you waste everyone's time -- that could be spent on > answering other people's "stupid" questions. I see. Personally, I believe this way: It is the responsibility of the responder to determine whether their response is a waste of time or not. Blaming anyone else other than you (the generic 'you', not you personally) for the inappropriate use of your time should only really happen in an employment or indentured servitude relationship; certainly not on a mailing list. :) Given that the "FreeBSD wants more users" idea is repeatedly brought up on lists (at least this is my impression), I would presume that the subject of 'more users' is somewhat relevant to some people; one look at the subject of this thread should be enough to demonstrate relevance. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Implementation: (n.) The fruitless struggle by the talented and underpaid to fulfill promises made by the rich and ignorant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Documenting 'make config' options
Doug Barton writes: > On 06/06/2012 11:59, Dave Hayes wrote: >> I'm describing more of a use case here, not attempting to specify an >> implementation. If a user invokes 'make', a window is presented to them >> with various options. It's probably very common that this is met with an >> initial reaction of "what the hell do these do?", even from the most >> seasoned of admins (presuming they are unfamiliar with the software they >> have been asked to install). I claim it would be an improvement to have >> that information at the fingertips of the make invoker. > What manner of providing this information would meet your needs? Personally, a 'pkg-options-descr' text file would suit me just fine. I don't claim this is a good or bad idea from the general perspective of FreeBSD users as a group. ;) From that perspective, the menu example suggested by Warren Block is decent; perhaps with an added button to "reset to defaults". From a quick persual of dialog(1), I'm sure something similar in functionality could be used without having to modify dialog itself. My loose attempt at requirements is that "enough" information about each option be in one place in the port skeleton to make an informed decision about whether to turn that option on or off. There should be a clear paragraph explaining what the option does, what consequences it might have if you enable/disable it, and why the default was chosen. BTW, thank you for changing the subject line. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Never promise, even by implication, without fulfilling your promise. The only acceptable alternative to completing an undertaking is to over-fulfil it. To betray any promise, explicit or otherwise, will harm you more than it can harm anyone else. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Documenting ports options (was Re: Why Are You NOT Using FreeBSD ?)
[ This probably should be redirected to freebsd-ports but I am not subscribed so the anal mailer will likely reject such a submission ] Rainer Duffner writes: > Am 06.06.2012 um 20:59 schrieb Dave Hayes: >> I believe this is the first time I've seen more documentation labeled as >> "extraneous". :) I had thought to suggest an implementation by having a >> simple pkg-option-desr file which describes the options and implications >> in each port. Are you suggesting that such a file would be unwelcome? >> > No, but take a look at the nginx port, which (I'm too lazy to count) > has gained a couple of dozens of options over the years. This is a port I use often, and yes...it's a lot of work to document it. It is good to read the nginx wiki to learn what these are and perhaps any initial foray into documenting these options should merely be a set of links, each one telling us where this option is discussed on the nginx wiki. I had to go read the wiki too, and it's required reading if you do advanced nginx work like I do. Still, it takes 5 minutes to add links to a text file in the port eh? > Asking him to do even more work - I wouldn't dare to do that ;-) So don't ask, just write some links. ;) > Sometimes, options only make sense in context of the selection of > options of other ports and it thus may no be easily explainable in one > line. I don't understand Are you saying this is a reason not to document what these options do? > Personally, I don't need more frequent FreeBSD-releases but two or > maybe three ports-tree freezes per year would be good. While I have learned a bit more about ports by reading this and other threads, I rarely worry about ports freezes. Production software in ports is a moving target (security fixes, bug fixes, etc). I use portsnap a lot. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Exaggeration is a standard peculiarity of man. To deprecate is often a form of exaggeration which people do not notice because it appears to be its opposite. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why Are You NOT Using FreeBSD ?
Adam Strohl writes: > There in lies the question -- why do you need to compile a port which > was just released? Is it a security thing or is it "I want the latest" > ? I'm just curious (and totally uninterested in how this ranks in your > "worse question" list). If I weren't honorable, I'd consider this question a troll. It's so far afield from my daily reality...well I'm going to take this at face value, because maybe -I've- got something wrong. ;) Let's just consider Firefox, which has a rather aggressive release schedule (once a month). $ pkg_info -r firefox-10.0.3,1 | grep Dependency | wc -l 175 Look at some of these dependencies: $ pkg_info -r firefox-10.0.3,1 | grep Dependency | sort ... Dependency: cairo-1.10.2_3,1 ... Dependency: gtk-2.24.6 ... Dependency: libgnome-2.32.0 ... Dependency: perl-threaded-5.14.2_2 ... Dependency: python27-2.7.2_4 Basically, everytime you want to upgrade firefox to 'stay current', you are upgrading a fair number of heavyweight packages. The chances that these will change month to month are high. (In the interests of brevity I will leave the verification of this to interested parties). Any of the ports listed above can have dependencies and consequences that reach very far into your workflow. If you do not upgrade them, you risk that firefox breaks in unknown ways. This is a rock and a hard place...do you upgrade everything from scratch (safest, but the 48 hour downtime is not unreasonable) or do you try to just replace that one port (risky, but you'll likely be up in an hour)? For firefox, it might very well be a security thing that causes the upgrade. Note well that I am not running 12 (is it at 12 now? 13? urgh.) because I'm in development and I do not want to touch certain other ports. Do I have this wrong? Anyone see a problem with this picture? What can we do to "just upgrade" in a safe fashion when we want to? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< The treasure house within you contains everything, and you are free to use it. You don't need to seek outside. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Locking a file backed mdconfig into memory
On FreeBSD 7.3-STABLE I'm mounting a DVD and doing something like this: mdconfig -a -t vnode -o reserve -o readonly -f /dvd/file so that /dvd/file becomes the backing storage for my memory disk. Now if the system is under severe memory pressure, will this memory get swapped out, causing a read from the DVD? How would I tell the system to never swap this file out of ram, even under severe memory pressure? The idea is to load this backing storage once and only once from the DVD into memory and leave it there. Thanks in advance. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Have you noticed how economical the human race is with it's idols? It sets them up, enjoys them, then falls upon them and devours them until nothing is left. Even the complete consumption of the idol, if it is another human being, is not the end. There are then hundreds of years worth of argument and analysis to be worked through... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locking a file backed mdconfig into memory
Clifton Royston writes: > It sounds like what you really want is to load the contents of the > specified file as a memory system? That's not part of mdconfig's > repertoire, to the best of my recollection. So if, in /etc/loader.conf, I do this: rootfs_load="YES" rootfs_type="mfs_root" rootfs_name="/mfsboot" vfs.root.mountfrom="ufs:md0" and /mfsboot comes from a bootable DVD, am I to assume that this mount is under the same constraint? Specifically, this constraint is that the /mfsboot file (and hence the DVD) will be read repeatedly if the system is under memory pressure. > If that's what you want, you need to use a different tool; the purpose > of mdconfig is to provide scratch disk. The backing store is to > specify a region its contents can be swapped out to if the system is > under memory pressure (which certainly won't work with a DVD) Heh. Certainly I am using tools for purposes which may not match the original intention. If I wanted to run the rootfs on a memory device which did -not- swap to the backing store of /mfsboot, how would I go about doing that? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Faith (n): The quality by which we believe what we would otherwise think was false. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locking a file backed mdconfig into memory
Jeremy Chadwick writes: > On Fri, May 28, 2010 at 10:57:29AM -0700, Dave Hayes wrote: >> Clifton Royston writes: >> > It sounds like what you really want is to load the contents of the >> > specified file as a memory system? That's not part of mdconfig's >> > repertoire, to the best of my recollection. >> >> So if, in /etc/loader.conf, I do this: >> >> rootfs_load="YES" >> rootfs_type="mfs_root" >> rootfs_name="/mfsboot" >> vfs.root.mountfrom="ufs:md0" > > I think you mean /boot/loader.conf? Yes, you are correct. > And I think you meant this for variable names, in addition to what > vfs.root.mountfrom should be (specific to RELENG_8): > mfsroot_load="YES" > mfsroot_type="mfs_root" > mfsroot_name="/some/path/mfsroot" I'm using RELENG_7, but it seems rootfs_* works just like mfsroot_* ... is the former deprecated? > vfs.root.mountfrom="ufs:/dev/md0" Hm, 'ufs:md0' currently works. What trouble can be had from using the abbreviated device name? > If using RELENG_7 and the mfsroot was made on RELENG_7, replace > "/dev/md0" with "/dev/md0c". Is there a reason for doing this? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< If you want to strengthen an enemy -- hate them. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locking a file backed mdconfig into memory
Garrett Cooper writes: > This is how I do it in my quickie loader.rc: > include /boot/loader.4th > set vfs.root.mountfrom="ufs:/dev/md0" > load /kernel > load -t mfs_root /mfsroot > start I used to do exactly this back at FreeBSD 4.11 to boot off a cdrom. Nice to know it still works this way. Jeremy Chadwick writes: > However, what I'm having trouble understanding is what exactly > preload_search_info() looks for and how all this actually connects > and works. It appears to me that there are specific drivers located in > src/sys/dev that are KLD-supported and others which are expected to be > included in the kernel statically. Maybe this confusion explains why /dev/md0c is giving me random crashes at the moment? Of course, another theory might be the size of my initial ramdisk (300Mb). Would there any known bug where booting off a large ramdisk causes unreadable panics to flash past the console too rapidly to view? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< By and large, language is a tool for concealing the truth. -George Carlin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locking a file backed mdconfig into memory
Jeremy Chadwick writes: > Is the mfsroot file compressed (.gz extension)? Reason I ask is that > the OP states he's using RELENG_7... Yes it is compressed. > http://jdc.parodius.com/freebsd/pxeboot_serial_install_7.html#step7 Thanks much for this. I did a simple test, I rebuilt a DVD that wasn't booting to use a lower level of compression (gzip -9 to gzip -6) on mfsroot without changing anything else. This caused it to boot normally. I'm not sure it's conclusive evidence, but it certainly looks like a weak datapoint supporting this kernel bug being the source of my problem. Is this problem fixed in 8.0 or by a patch? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Suggested definition of "sin": Trading aliveness for survival. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locking a file backed mdconfig into memory
Jeremy Chadwick writes: > CC'ing jhb@ since he last updated PR kern/120127 (which I would say is > still a problem on RELENG_7 :-) ). John, are you aware of any gzip > decompression / mfsroot changes which might explain the problem on > RELENG_7? I haven't done a "thorough" series of tests, but on my > testbed boxes RELENG_8 works fine with a gzip'd mfsroot. I can get you an iso that crashes when you try to boot it, if that will help? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Your ego is a failed API for a system that doesn't need your input. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locking a file backed mdconfig into memory
Dave Hayes writes: > Jeremy Chadwick writes: >> CC'ing jhb@ since he last updated PR kern/120127 (which I would say is >> still a problem on RELENG_7 :-) ). John, are you aware of any gzip >> decompression / mfsroot changes which might explain the problem on >> RELENG_7? I haven't done a "thorough" series of tests, but on my >> testbed boxes RELENG_8 works fine with a gzip'd mfsroot. > I can get you an iso that crashes when you try to boot it, if that > will help? Well this doesn't seem to be the compression issue, since I just tried a test without compressing the ramdisk image. It still crashes. I'm back to thinking it's the size of the ramdisk image itself, but really I've no clue. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< "In theory, there is no difference between theory and practice. In practice, there is." -- Jan L. A. Van De Snepscheut ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locking a file backed mdconfig into memory
John Baldwin writes: > Ok, if you are using a stock mfsroot from a release build, that should > work fine. If you have built a custom mfsroot that is larger, then > you may need to increase NKPT on i386. In very recent 7 and later you > can do this by setting it to a new value in your kernel config. In > older versions you can do this by manually adding a #define to set a > new value of NKPT in opt_global.h or hacking on the source directly. Is this also true for amd64 (which is my particular target)? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< "Be who you are and say what you feel, because those who mind don't matter, and those who matter don't mind." - Dr. Seuss ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locking a file backed mdconfig into memory
John Baldwin writes: > On Wednesday 02 June 2010 6:37:59 pm Dave Hayes wrote: >> John Baldwin writes: >> > Ok, if you are using a stock mfsroot from a release build, that should >> > work fine. If you have built a custom mfsroot that is larger, then >> > you may need to increase NKPT on i386. In very recent 7 and later you >> > can do this by setting it to a new value in your kernel config. In >> > older versions you can do this by manually adding a #define to set a >> > new value of NKPT in opt_global.h or hacking on the source directly. >> >> Is this also true for amd64 (which is my particular target)? > > It might be. What is the panic you are seeing? I can't see the panic as it repeatedly scrolls across the console screen faster than I can read it. In this case the mfsroot is around 275MB. I have noticed that sometimes I can build an mfsroot that does not crash of this size. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< People usually oppose things because they are ignorant of them. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 7.3p1 repeatable crash when running on ramdisk
I work with a small number of FreeBSD 7.3p1 amd64 systems which are running off of an MFS root partition loaded via a DVD, and there have been a couple of problems with the mfsroot. I'd like to focus on one in particular and see if the assembled minds here have any insight as to what this might be. Basically if I do this: # yes >/crashme the system doesn't panic, there's no warning (except for some random 'k' characters being output to the console) and the machine simply resets. I have some configuration details on the following URL: http://www.jetcafe.org/dave/freebsd/dvdconfig.html for perusal. The df for said machine looks like so: Filesystem SizeUsed Avail Capacity Mounted on /dev/md0c 270M231M 39M85%/ devfs 1.0K1.0K 0B 100%/dev /dev/acd0 606M606M 0B 100%/cd0 /dev/md1.uzip 254M225M 29M89%/usr /dev/md231M 30K 30M 0%/usr_rw :/usr_rw284M254M 30M89%/usr /dev/da1s1d653G1.0G600G 0%/rw procfs 4.0K4.0K 0B 100%/proc I would expect that a system running off of MFS would inform one via log files or console messages when I fill up the root partition. I'd say it's definately a bug but I'm not sure if it's mine or not. :) Thanks in advance for any answers you all can provide. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< A poor man shames us all. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Panic: attempted pmap_enter on 2MB page
What does the above mentioned panic mean? I'm booting from an mfsroot off of a DVD with a loader.conf like this: autoboot_delay="5" mfsroot_load="YES" mfsroot_type="mfs_root" mfsroot_name="/mfsboot" vfs.root.mountfrom="ufs:md0" vfs.root.mountfrom.options="rw" kern.ipc.nmbclusters=32768 net.inet.tcp.tcbhashsize=16384 vm.pmap.pg_ps_enabled=1 vm.kmem_size="2G" accf_http_load="YES" net.inet.tcp.syncache.hashsize=1024 net.inet.tcp.syncache.bucketlimit=100 This is FreeBSD 8.1-RELEASE amd64 running with the debugger installed into the kernel. Thanks in advance for any insight provided. :) -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< No one is lazy except in the pursuit of another one's goal. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic: attempted pmap_enter on 2MB page
Alan Cox writes: > I'm afraid that I can't offer much insight without a stack trace. At > initialization time, we map the kernel with 2MB pages. I suspect that > something within the kernel is later trying to change one those mappings. > If I had to guess, it's related to the mfs root. Here is the stack trace. The machine is sitting here in KDB if you need me to extract any information from it. I db> bt Tracing pid 0 tid 0 td 0x80c67140 kdb_enter() at kdbenter+0x3d panic() at panic+0x17b pmap_enter() at pmap_enter+0x641 kmem_malloc() at kmem_malloc+0x1b5 uma_large_malloc() at uma_large_malloc+0x4a malloc() at malloc+0xd7 acpi_alloc_wakeup_handler() at acpi_alloc_wakeup_handler+0x82 mi_startup() at mi_startup+0x59 btext() at btext+0x2c db> -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< Only one who is seeking certainty can be uncertain. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic: attempted pmap_enter on 2MB page
Alan Cox writes: > There are two pieces of information that might be helpful: the value of > the global variable "kernel_vm_end" and the virtual address that was > passed to pmap_enter(). I'm afraid I don't have enough experience with this debugger to get these values with offhand commands. I could trial and error my way through figuring it out, but I'd rather get the data you expect. :) If you could give me the commands to do this, I'd be happy to type them in and get a response to you. > Is this problem reproducible? I don't recall if you mentioned that > earlier. Sort of. It seems that everytime I generate a bootable FreeBSD ISO, a die is rolled. If it comes up a certain number then it crashes, otherwise it's fine. ;) My ISO generation process might be relevant; I create a 600MB ramdisk (it used to be 512 on FreeBSD 7.3) which loads from the ISO on boot. This winds up being the root partition. As a datapoint the same die roll happens on FreeBSD 7.3 although the chance of working seems to be greater. If you'd like a copy of the ISO to see this for yourself I can make it available. I'm guessing it will also crash for you in this way modulo hardware issues. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< The treasure house within you contains everything, and you are free to use it. You don't need to seek outside. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic: attempted pmap_enter on 2MB page
Alan Cox writes: > When you build your kernel for this ISO are you increasing the value of > NKPT? No. I was under the impression that this value auto-tunes on amd64, is that correct? -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>> The opinions expressed above are entirely my own <<< >From your first day at school you are cut off from life to make theories. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
+rtfree: 0xffffff0003635780 has 1 refs
I am new to the AMD64 stable branch, so forgive me if this has been beat to death, but I can't find why this message keeps occurring over and over all day. FreeBSD 7.0 Stable on AMD x2. It works (or seems to) fine. +rtfree: 0xff0003635780 has 1 refs its a kernel "bold" on the terminal, and would scare me to death if I just knew what it meant... Should I be worried about something? I hate bold white text Dave Overton, Owner SYIX.COM [EMAIL PROTECTED] (530) 755-1751 x101 Fax (530) 751-8871 800-988-SYIX ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
BSD 6 or 7 + Intel 3200 MCH chipset
Just put together a nice 1U box, Tyan Tank GT20, plugged in its 8gb ECC RAM, its 4 shiney new HDs and fired it up. Bios looks normal, reset the clock to something resembling today, and throw in the Fbsd7 disk! No joy. I get just a hint of a "booting" line, then an instant reboot, or with a 6 disk, I get a scrolling mess that I have no idea what it says. My question, has anyone got fbsd running on one of these chipsets? If so, how did you do it? Tried 7 release in i386 and amd64 version, and v6 i386. They all do the same thing. (it will run the misc test CDs I have here just fine, even let it do most of a WinXP install with no issues, so I don't really believe it to be a hardware issue) Tyan Tank GT20 model B5211 Tyan Toledo i3200R m/b Intel 3200 MCH chipset. Help? Dave Overton, Owner SYIX.COM [EMAIL PROTECTED] (530) 755-1751 x101 Fax (530) 751-8871 800-988-SYIX ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: BSD 6 or 7 + Intel 3200 MCH chipset
> > On Tuesday 25 March 2008 09:19:00 pm Dave Overton wrote: > > Just put together a nice 1U box, Tyan Tank GT20, plugged in its 8gb > > ECC RAM, its 4 shiney new HDs and fired it up. Bios looks normal, > > reset the clock to something resembling today, and throw in > the Fbsd7 disk! > > > > No joy. > > > > I get just a hint of a "booting" line, then an instant > reboot, or with > > a 6 disk, I get a scrolling mess that I have no idea what it says. > > Partly guessing, but this sounds like the real-mode BTX > bootloader issue. > It's become increasingly common on newer hardware, and it's > not limited to USB devices like it used to be. Fortunately, > there is a good chance that jhb's recent BTX overhaul will > fix it. Unfortunately, it was only committed to -CURRENT two > weeks ago and MFC'ed to RELENG_6 and RELENG_7 one week ago so > I doubt there's a ready-to-use snapshot CD you can download > that includes it. > > If it were me I'd create a bootable USB stick (on another > machine) to verify that you can boot the server with the > latest boot blocks, then use it to do a manual install (or at > least bootstrap the process). But that's just me--I like that > sort of thing. It's also possible to roll your own > installation CD but I've never done.it. I do recall someone > posting an link to an image to one of the mailing lists, but > IIRC that was with a BTX patch older than the one that > actually got committed. Probably someone else on this list > has a better suggestion. > > JN > > > Tyan Tank GT20 model B5211 > > Tyan Toledo i3200R m/b > > Intel 3200 MCH chipset. Fixed with ISO built on March 25,2008 Fbsd7-Stable, in case anyone else find they have this problem. Probably fixed before that, but thats the one I used, and things are working great today. Thanks for the help guys. smime.p7s Description: S/MIME cryptographic signature
Rockbox on a USB device causes kernel panic on 7.0
Hi all, I'm running FreeBSD 7.0 on a home file server that holds, among a bunch of other stuff, my music collection. I occasionally hook up my iPod Video (5.5) to charge and to synchronize files using rsync; I've got Rockbox (http://www.rockbox.org/) running on the iPod. For as long as I've had 7 running on the server (about a year), everything has been fine. However, after a recent Rockbox update, the server reports a kernel panic when I plug in the iPod. I think that this is related to some changes on the rsync end, specifically their "New USB stack with limited capability". It would be great to get this combination working again, and I'm wondering what information would be most useful if anyone wanted to take a crack at the problem. I'm working on getting a scratch box together for testing purposes so that I can avoid taking down my server. Thanks for any help or suggestions, Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Buildworld Fails RELENG_7
Sources checked out yesterday, updated this morning using cvsup and repository at cvsup12.freebsd.org. The build fails in /usr/src/lib/libc /usr/bin/gcc -O2 -fno-strict-aliasing -pipe -m32 -march=athlon-mp -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /usr/src/lib/libc/sys/fcntl.c /usr/src/lib/libc/sys/fcntl.c: In function 'fcntl': /usr/src/lib/libc/sys/fcntl.c:42: error: storage size of 'ofl' isn't known /usr/src/lib/libc/sys/fcntl.c:67: error: 'F_OGETLK' undeclared (first use in this function) /usr/src/lib/libc/sys/fcntl.c:67: error: (Each undeclared identifier is reported only once /usr/src/lib/libc/sys/fcntl.c:67: error: for each function it appears in.) /usr/src/lib/libc/sys/fcntl.c:74: error: 'struct flock' has no member named 'l_sysid' /usr/src/lib/libc/sys/fcntl.c:79: error: 'F_OSETLK' undeclared (first use in this function) /usr/src/lib/libc/sys/fcntl.c:82: error: 'F_OSETLKW' undeclared (first use in this function) /usr/src/lib/libc/sys/fcntl.c:42: warning: unused variable 'ofl' *** Error code 1 Stop in /usr/src/lib/libc. *** Error code 1 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 05:07:08PM +0100, Doug Rabson wrote: > This symbol has been added to fcntl.h recently. It appears as if your build > is picking up the installed header rather than the one from the source > tree. Are you using 'make buildworld'? Yes, although at this point is it 'make -DNO_CLEAN buildworld' until I get a clean build. The header files in /usr/include/sys are those from 7.0 RELEASE, however, and I have had to copy 3 files (so far) from /usr/src/sys/sys to get the build to continue. [EMAIL PROTECTED] /usr/include/sys]# ls *.orig fcntl.h.orig tree.h.orig umtx.h.orig Just got another stoppage in /usr/src/gnu/lib/libstdc++. /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/libsupc++/unwind-cxx.h:41:20: error: unwind.h: No such file or directory The #include declaration has that header file in the local directory. It exists in /usr/obj, however. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 05:42:56PM +0100, Doug Rabson wrote: > > On 19 May 2008, at 17:38, Dave Uhring wrote: > >> On Mon, May 19, 2008 at 05:07:08PM +0100, Doug Rabson wrote: >>> This symbol has been added to fcntl.h recently. It appears as if your >>> build >>> is picking up the installed header rather than the one from the source >>> tree. Are you using 'make buildworld'? >> >> Yes, although at this point is it 'make -DNO_CLEAN buildworld' until I get >> a clean >> build. >> >> The header files in /usr/include/sys are those from 7.0 RELEASE, however, >> and I >> have had to copy 3 files (so far) from /usr/src/sys/sys to get the build >> to >> continue. > > You should never have to copy any header files to /usr/include to get a > buildworld to work. Try without the -DNO_CLEAN and if that still fails, > clean your /usr/obj (e.g. with rm -rf /usr/obj/*). The build is going nowhere without the correct header files in /usr/include/sys. I have repeatedly cleaned /usr/obj to no avail, but I have a better method for doing that: umount /usr/obj newfs /dev/da4s2f mount /usr/obj ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 09:42:21AM -0700, Jeremy Chadwick wrote: > > Is there some reason you're using -DNO_CLEAN, and haven't just nuked > /usr/obj/* and done buildworld normally? I can't reproduce any of this > behaviour on any of our RELENG_7 systems. I have repeately nuked /usr/obj. That is not going to put updated header files where they need to be. I'm using -DNO_CLEAN in order to get the system to a point where a build just might succeed without -DNO_CLEAN and I'm not getting there without some header files being in the right place. Remember I'm starting from a RELEASE userland. This is just about as bad as jumping from one full release to the next :( ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 09:59:25AM -0700, Jeremy Chadwick wrote: > > Is there breakage of some sort being caused by your make.conf or (less > probable) your src.conf? Any filesystem corruption (boot single user > and force fsck on all the filesystems)? [EMAIL PROTECTED] /etc]$ grep -v ^# make.conf CPUTYPE?=athlon64 CFLAGS= -O2 -fno-strict-aliasing -pipe -m32 CXXFLAGS+= -fconserve-space MAKE_SHELL?=sh COPTFLAGS= -O -pipe INSTALL=install -C MTREE_FOLLOWS_SYMLINKS= -L ENABLE_SUID_SSH= NO_SENDMAIL= NO_PROFILE= DOC_LANG= en_US.ISO8859-1 src.conf is untouched. > In all the years I've used FreeBSD, I've never had to copy include files > from parts of /usr/src to get buildworld to work, so this is very odd > behaviour. Start with a clean RELEASE userland and try to build RELENG_7 today :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 10:06:19AM -0700, Jeremy Chadwick wrote: > On Mon, May 19, 2008 at 12:03:34PM -0500, Dave Uhring wrote: > > > > [EMAIL PROTECTED] /etc]$ grep -v ^# make.conf > > CPUTYPE?=athlon64 > > CFLAGS= -O2 -fno-strict-aliasing -pipe -m32 > > CXXFLAGS+= -fconserve-space > > MAKE_SHELL?=sh > > COPTFLAGS= -O -pipe > > INSTALL=install -C > > MTREE_FOLLOWS_SYMLINKS= -L > > ENABLE_SUID_SSH= > > NO_SENDMAIL= > > NO_PROFILE= > > DOC_LANG= en_US.ISO8859-1 > > Can you please comment out all of the above and see if the problem > persists? Sure, but that is not going to put the correct headers where the sources are looking for them. Nor is it going to put groff headers into a directory where the #include "driver.h" is declared within a source file and the directory contains *no* headers. In particular, /usr/src/contrib/groff/src/libs/libdriver has no header files at all, yet input.cpp in that directory has these declarations: #include "driver.h" #include "device.h" > > Start with a clean RELEASE userland and try to build RELENG_7 today :) > > Give me a few hours (installing VMware + 7.0-RELEASE + csup). My money > is on that I won't be able to reproduce the problem. VMware? Give me a break! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 10:02:23AM -0700, David Wolfskill wrote: > On Mon, May 19, 2008 at 11:54:21AM -0500, Dave Uhring wrote: > > > > The build is going nowhere without the correct header files in > > /usr/include/sys. > > That appears to indicate that your build environment is fundamentally > broken.. > > You might consider doing the build within script(1), then making the > resulting script file available for folks to examine. I posted the relevant output from "make buildworld". Copying the 3 new header files from /usr/src/sys/sys to /usr/include/sys solved my original problem. I'm sure that after a successful buildworld and installworld that the original problem will go away. The problem now is in the build of groff: [EMAIL PROTECTED] /usr/src/contrib/groff/src/devices/grodvi]# ls *.h ls: *.h: No such file or directory However, dvi.cpp in that directory has this: #include "driver.h" #include "nonposix.h" #include "paper.h" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 10:04:28AM -0700, Jeremy Chadwick wrote: > On Mon, May 19, 2008 at 11:58:07AM -0500, Dave Uhring wrote: > > > > I have repeately nuked /usr/obj. That is not going to put updated header > > files > > where they need to be. > > It's apparent you don't quite understand. The "updated header files" > reside in /usr/src, and ***remain there*** until installworld is done. That is as it should be. > The buildworld process will include the "updated header files", trumping > most of those which are in /usr/include. Does not happen. The header files included were those from /usr/include/sys, not /usr/src/sys/sys. The errors would not have occurred if the header files in /usr/src/sys/sys were being referenced by In any case, that problem has been solved by putting the updated header files in /usr/include/sys and will be properly fixed when I can finally make installworld. > > Remember I'm starting from a RELEASE userland. This is just about as bad as > > jumping from one full release to the next :( > > Okay, so you installed 7.0-RELEASE on a machine. Did you choose to > install src from the CD/DVD when installing? (If so, you will need to > "adopt" the version you installed to the current version, see the cvsup > FAQ here: http://www.cvsup.org/faq.html#caniadopt -- and you'll need to > do this for ports if you installed the ports tree off the CD/DVD as > well) > > If you csup'd, what tag did you use? RELENG_7? I'm assuming so. Did > you use src-all, or are you using a custom supfile? We use > /usr/share/examples/cvsup/stable-supfile. Whatever tag was in /usr/share/examples/cvsup/stable-supfile. In fact it is: *default release=cvs tag=RELENG_7 > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 06:00:39PM +0100, Doug Rabson wrote: > > The thing is that a working buildworld doesn't depend on headers from > /usr/include. One of the first thing it does is install a set of new > headers in somewhere like /usr/obj/usr/src/tmp. At this point, it might be > useful to see a log of a failed buildworld attempt to see what is going > wrong. Putting the updated header files in /usr/include/sys solved that problem. Whether is was the correct solution or not is moot since the build continued from the previous stoppage in libc. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 11:00:28AM -0700, Jeremy Chadwick wrote: > > Something I thought of while doing the above: there's been reports in > the past of problems with buildworld (or building software in general) > bombing out or behaving oddly due to clock issues on the local machine. > If you don't use ntpd, consider doing so. Otherwise, at least use > ntpdate once to set your clock to something sane. I hadn't yet started ntpd but [EMAIL PROTECTED] /etc]# ntpdate newton 19 May 13:29:22 ntpdate[55524]: step time server 192.168.0.8 offset -1.044724 sec I doubt that a second off would make any difference. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 11:02:01AM -0700, David Wolfskill wrote: > On Mon, May 19, 2008 at 12:53:58PM -0500, Dave Uhring wrote: > > > > I posted the relevant output from "make buildworld". Copying the 3 new > > header > > files from /usr/src/sys/sys to /usr/include/sys solved my original problem. > > s/solved/circumvented/ :) Whatever, libc does build now. > freebeast(8.0-C)[52] ls -l usr/src/contrib/groff/src/devices/grodvi/*.h > ls: No match. > freebeast(8.0-C)[53] grep '#include "' > usr/src/contrib/groff/src/devices/grodvi/dvi.cpp > #include "driver.h" > #include "nonposix.h" > #include "paper.h" > freebeast(8.0-C)[54] > > The compilation of dvi.cpp uses > "-I/usr/src/gnu/usr.bin/groff/src/devices/grodvi/../../../../../../contrib/groff/src/include > -I/usr/src/gnu/usr.bin/groff/src/devices/grodvi/../../../src/include" > (among other things); I expect you will find the needed header files > in those directories. If a -I/some/directory is used as a CFLAG then the *include directive must read #include , *not* #include "driver.h". The latter demands that the header file be in the same directory as the source file. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 12:16:46PM -0700, Jeremy Chadwick wrote: > On Mon, May 19, 2008 at 11:00:28AM -0700, Jeremy Chadwick wrote: > > This picked up src-all using the RELENG_7 tag. I then attempted a > > buildworld (cd /usr/src && time make -j2 buildworld). It's just begun > > stage 2.3, but so far no issues. I'll report back in about 30 minutes > > or so, when it has a chance to finish. That is what I did after the first build using the original RELEASE sources and updated using csup. I blew away /usr/src and cvsupped a fresh RELENG_7 source tree. > The compile has finished successfully. Took 1 hour 15 minutes. Another > user also mailed me (privately) adding that he too cannot reproduce this > problem. Last time I succeeded in building world on another box it took 47 minutes :-) That's still a long way from years back when RELENG_4 built in 30 minutes on a machine with an Athlon Tbird 1.2GHz processor. Double the processor speed and quadruple the memory and the build takes 50% longer. > I will attempt the same with your make.conf to see if it's any > different. But at this point, it appears the issue is with your system > or system configuration. I just wish I knew what was doing it. Any odd > filesystem mount flags (output of "mount")? [EMAIL PROTECTED] /usr/src/contrib/groff]# mount /dev/ad4s2a on / (ufs, local, soft-updates) devfs on /dev (devfs, local) /dev/ad4s2h on /home (ufs, local, soft-updates) /dev/ad4s2e on /usr (ufs, local, soft-updates) /dev/ad4s2g on /usr/local (ufs, local, soft-updates) /dev/ad4s2d on /var (ufs, local, soft-updates) /dev/md0 on /tmp (ufs, local, soft-updates) /dev/ad4s2f on /usr/obj (ufs, asynchronous, local, noatime) [EMAIL PROTECTED] /usr/src/contrib/groff]# Not even an NFS mount. I'm trying to update to FreeBSD-STABLE to use on my home file server. At present it has OpenSolaris installed but that OS does not have the Ethernet driver I need and I want to be able to use 2 Adaptec 29160N HBAs in the system. But I only have 2 PCI slots and I would like to remove the Intel NIC and use the system's on-board nfe NIC. I'll blow away /usr/src and /usr/obj, cvsup the entire RELENG_7 source tree again and once more attempt to buildworld. If that fails, Solaris stays on the server. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 02:54:31PM -0400, Lowell Gilbert wrote: > Dave Uhring <[EMAIL PROTECTED]> writes: > > > > If a -I/some/directory is used as a CFLAG then the *include directive must > > read > > > > #include , *not* #include "driver.h". The latter demands that the > > header file be in the same directory as the source file. > > Not that it necessarily affects what you're going through, but that > last statement is incorrect. The double quotes are (according to the > C standard) implementation defined, and gcc (like many other > compilers) will prefer the local directory for the double quotes, but > will search the entire search path if it doesn't find the file there. The problem is that gcc is *not* finding the file in the directory referenced by the -I cflag. If I copy the header files to the directory where the error occurs the header file is found and used to compile the source file. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 06:46:41PM -0500, Jeffrey Goldberg wrote: > On May 19, 2008, at 1:21 PM, Dave Uhring wrote: > >> In any case, that problem has been solved by putting the updated header >> files >> in /usr/include/sys and will be properly fixed when I can finally make >> installworld. > > I did not have to manually move or copy any header files. > >> *default release=cvs tag=RELENG_7 > > My build on that, csupped just after seeing your first message in this > thread, has just completed. make buildworld worked just fine without > error. I'm also on athlon64. All the headers that I needed were in the > right places in /usr/src Did you start from a RELEASE source tree and userland? > So all I can say is that things worked for me. I really suspect that you > got /usr/src and /usr/obj into some sort of inconsistent state. I completely removed both, cvsupped a new RELENG_7 source tree, removed /etc/make.conf and got this: /usr/bin/gcc -fpic -DPIC -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_THREADS -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_IDEA -DL_ENDIAN -DNO_IDEA -std=gnu89 -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine/eng_openssl.c -o eng_openssl.So /usr/bin/gcc -fpic -DPIC -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/libcrypto -DOPENSSL_THREADS -DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_IDEA -DL_ENDIAN -DNO_IDEA -std=gnu89 -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine/eng_padlock.c -o eng_padlock.So /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine/eng_padlock.c: In function 'padlock_xcrypt_ecb': /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine/eng_padlock.c:445: error: can't find a register in class 'GENERAL_REGS' while reloading 'asm' /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine/eng_padlock.c:445: error: 'asm' operand has impossible constraints *** Error code 1 Stop in /usr/src/secure/lib/libcrypto. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. real8m58.524s user7m18.995s sys 1m22.150s Solaris Nevada b_87 is installing on the server this minute instead of FreeBSD. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 02:01:48PM -1000, Clifton Royston wrote: > On Mon, May 19, 2008 at 03:14:08PM -0500, Dave Uhring wrote: > > > > The problem is that gcc is *not* finding the file in the directory > > referenced by the -I cflag. If I copy the header files to the directory > > where the error occurs the header file is found and used to compile the > > source file. > > This starts to narrow down the problem you're having a bit, I think. > > Given that this is different from the expected behavior and the > behavior others are seeing, this sounds to me like either 1) the wrong > compiler or version of the compiler is being found and used in place of > the desired gcc instance, or 2) something in your shell or environment > is somehow getting into the buildworld environment and causing make or > the inner shell to misparse the commandline to gcc. The c compiler is the one shipped with 7.0 RELEASE. Except for the 3 new header files that I placed from cvsupped sources into /usr/include/sys the entire system is 7.0 RELEASE. Prior to beginning the build I deliberately set # export CFLAGS="" Nothing else in my environment would have affected the compiler. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Tue, May 20, 2008 at 11:58:03AM +1000, Mark Andrews wrote: > > > # export CFLAGS="" > > This does NOT remove CFLAGS from the environment. It does when you shell is bash. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 10:08:22PM -0400, Josh Carroll wrote: > > The c compiler is the one shipped with 7.0 RELEASE. Except for the 3 > > new header files that I placed from cvsupped sources into /usr/include/sys > > the entire system is 7.0 RELEASE. > > > > Prior to beginning the build I deliberately set > > > > # export CFLAGS="" > > > > Nothing else in my environment would have affected the compiler. > > You're not using make -j when building world are you? If so, remove > that and see if it then builds properly. No, even though it is a dual-core system. I did not want to chance a race condition. I simply executed 'make buildworld' initially, then 'make -DNO_CLEAN buildworld' when I encountered problems in the build. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 10:59:18PM -0400, Josh Carroll wrote: > > On Tue, May 20, 2008 at 11:58:03AM +1000, Mark Andrews wrote: > >> > >> > # export CFLAGS="" > >> > >> This does NOT remove CFLAGS from the environment. > > > > It does when you shell is bash. > > I think what Mark was getting at is that simply setting CFLAGS to "" > prior to make does not trump the setting of CFLAGS in > make.conf/src.conf. So if you haven't removed/commented that from > your make.conf, the export command above will do nothing for the > actual build environment. Before that last build I had removed /etc/make.conf and had never touched src.conf. CFLAGS was empty. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Mon, May 19, 2008 at 11:10:32PM -0400, Josh Carroll wrote: > > No, even though it is a dual-core system. I did not want to chance a > > race condition. I simply executed 'make buildworld' initially, then > > 'make -DNO_CLEAN buildworld' when I encountered problems in the build. > > Ok, it was worth asking, just to rule out the obvious. > > I'm still not sure where your logic in using -DNOCLEAN comes in, for a > failed build. I would expect that to continue to fail in most > circumstances if it were already failing. If you fix what caused the build to break and want to find any other failure points there is little point in restarting the build from zero. > So I think in one of your other mails you said you're installing > something else now? Solaris? If so, this thread is moot, since you > aren't running FreeBSD on the box anymore, and no one has been able to > reproduce your problem. I think the most likely culprits have already > been mentioned in the thread so far anyway. I would still like to get FreeBSD on that server but with the latest improvements to ZFS. The release version is not going to do that for me and the only way that I can get up-to-date binaries is to build a new world and kernel. I'll give it another days' try and if that still fails Solaris will stay on the server. This BTW is not my first time building world on FreeBSD. I followed STABLE from 3.4 through the end of RELENG_4 and I never had such problems with a simple compile. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Tue, May 20, 2008 at 01:33:15PM +1000, Mark Andrews wrote:
>
> And when tested does behave the way you describe.
>
> Mark
>
> drugs:9.5.x 13:30 {4371} % bash
> [EMAIL PROTECTED] ~/cvs/9.5.x]$ printenv | grep FOO
> [EMAIL PROTECTED] ~/cvs/9.5.x]$ FOO=ll
> [EMAIL PROTECTED] ~/cvs/9.5.x]$ export FOO
> [EMAIL PROTECTED] ~/cvs/9.5.x]$ printenv | grep FOO
> FOO=ll
> [EMAIL PROTECTED] ~/cvs/9.5.x]$ FOO=""
> [EMAIL PROTECTED] ~/cvs/9.5.x]$ export FOO
> [EMAIL PROTECTED] ~/cvs/9.5.x]$ printenv | grep FOO
> FOO=
> [EMAIL PROTECTED] ~/cvs/9.5.x]$ env -i PATH=$PATH printenv | grep FOO
> [EMAIL PROTECTED] ~/cvs/9.5.x]$
This is Solaris but bash is bash:
[EMAIL PROTECTED] ~]$ printenv | grep CFLAGS
CFLAGS=-xO3 -m32 -xarch=native -mt -I/usr/sfw/include -I/usr/X11/include
-I/opt/sfw/include
You have mail in /var/mail/duhring
[EMAIL PROTECTED] ~]$ export CFLAGS=""
[EMAIL PROTECTED] ~]$ printenv | grep CFLAGS
CFLAGS=
[EMAIL PROTECTED] ~]$ export CFLAGS='-xO3 -m32 -xarch=native'
[EMAIL PROTECTED] ~]$ printenv | grep CFLAGS
CFLAGS=-xO3 -m32 -xarch=native
[EMAIL PROTECTED] ~]$ export CFLAGS=""
[EMAIL PROTECTED] ~]$ printenv | grep CFLAGS
CFLAGS=
[EMAIL PROTECTED] ~]$ env -i PATH=$PATH printenv | grep CFLAGS
[EMAIL PROTECTED] ~]$
When I tell you that CFLAGS="", CFLAGS="", and a cursory
examination of my last compiler output would have shown you exactly
that.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
On Tue, May 20, 2008 at 12:54:59PM +0100, Doug Rabson wrote: > > On 20 May 2008, at 12:25, Dave Uhring wrote: > >> On Tue, May 20, 2008 at 08:50:14AM +0100, Doug Rabson wrote: >>> >>> In this, your build is explicitly using '/usr/bin/gcc' for the build >>> which >>> is not the way buildworld normally works. In normal operation, buildworld >>> first builds a compiler from source and then uses that compiler by adding >>> to $PATH and building with just 'cc'. Are you overriding $CC in your >>> environment? >> >> I did not even have $CC in my environment. My environment had absolutely >> nothing involving the compiler and the compiler was the one shipped with >> FreeBSD-7.0-RELEASE. It is the *only* compiler on the system. >> > > Odd. Could you please send me the complete log of a failed build attempt. I did not maintain such a log. On that last build everything proceeded normally until it broke in an inline assembler piece of code. But I published not only the error but also the previous 4 or 5 compile lines. I'm building again with a virgin clean cvsupped source tree from cvsup4.freebsd.org, a clean /usr/obj, and I have reverted to /bin/csh for my root shell if that can possibly matter. /etc/make.conf sets the build shell as /bin/sh. This time I started the build using script. The entire log will be available. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld Fails RELENG_7
Tried again this morning with a fresh cvsup from cvsup4.freebsd.org and the build went to completion. maxwell# grep -v ^# /etc/make.conf CPUTYPE?=k8 CFLAGS= -O2 -fno-strict-aliasing -pipe -m32 CXXFLAGS+= -fconserve-space MAKE_SHELL?=sh COPTFLAGS= -O -pipe INSTALL=install -C MTREE_FOLLOWS_SYMLINKS= -L ENABLE_SUID_SSH= NO_SENDMAIL= NO_PROFILE= DOC_LANG= en_US.ISO8859-1 maxwell# printenv MACHTYPE=i386 USER=root MAIL=/var/mail/root SHLVL=2 VENDOR=intel HOME=/root PAGER=more GROUP=wheel LOGNAME=root TERM=xterm BLOCKSIZE=K WINDOWPATH=9 PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin REMOTEHOST= DISPLAY=:0.0 XAUTHORITY=/root/.Xauthority HOST=maxwell.uhring.com SHELL=/bin/csh OSTYPE=FreeBSD PWD=/root FTP_PASSIVE_MODE=YES HOSTTYPE=FreeBSD EDITOR=vi WINDOWID=14680077 XTERM_VERSION=XTerm(235) XTERM_LOCALE=C TERMCAP=xterm|xterm-color|X11 terminal emulator:ti@:te@:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:k;=\E[21~:F1=\E[23~:F2=\E[24~:kH=\EOF:@7=\EOF:kI=\E[2~:kh=\EOH:*6=\EOF:kP=\E[5~:kN=\E[6~:ku=\EOA:kd=\EOB:kr=\EOC:kl=\EOD:Km=\E[M:li#24:co#80:am:kn#12:km:mi:ms:xn:AX:bl=^G:is=\E[!p\E[?3;4l\E[4l\E>:rs=\E[!p\E[?3;4l\E[4l\E>:le=^H:AL=\E[%dL:DL=\E[%dM:DC=\E[%dP:al=\E[L:dc=\E[P:dl=\E[M:UP=\E[%dA:DO=\E[%dB:LE=\E[%dD:RI=\E[%dC:ho=\E[H:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:cs=\E[%i%d;%dr:im=\E[4h:ei=\E[4l:ks=\E[?1h\E=:ke=\E[?1l\E>:kD=\E[3~:sf=\n:sr=\EM:st=\EH:ct=\E[3g:sc=\E7:rc=\E8:eA=\E(B\E)0:as=\E(0:ae=\E(B:ml=\El:mu=\Em:up=\E[A:nd=\E[C:md=\E[1m:me=\E[m:mr=\E[7m:so=\E[7m:se=\E[27m:us=\E[4m:ue=\E[24m:vi=\E[?25l:ve=\E[?25h:ut:Co#8:pa#64:op=\E[39;49m:AB=\E[4%dm:AF=\E[3%dm:kb=\010: XTERM_SHELL=/bin/csh Note the last line. Even if /etc/make.conf specifies the build shell, that is apparently ignored in the build process. The CPUTYPE in /etc/make.conf is also ignored and make chooses one from thin air apparently since the cflags used in the build are shown in the last line of the compile: cc -O2 -fno-strict-aliasing -pipe -m32 -march=athlon-mp -DTM_GMTOFF=tm_gmtoff -DTM_ZONE=tm_zone -DSTD_INSPIRED -DPCTS -DHAVE_LONG_DOUBLE -DTZDIR=\"/usr/share/zoneinfo\" -Demkdir=mkdir -I/usr/src/usr.sbin/zic/zdump/.. -I/usr/src/usr.sbin/zic/zdump/../../../lib/libc/stdtime -o zdump zdump.o ialloc.o scheck.o I specified CPUTYPE?=k8 but make chose -march=athlon-mp. Thanks to all who tried to help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Deprecating base system ftpd?
> On 03/04/2021 22:39, Ed Maste wrote: > > I propose deprecating the ftpd currently included in the base system > > before FreeBSD 14, and opened review D26447 > > (https://reviews.freebsd.org/D26447) to add a notice to the man page. > > I had originally planned to try to do this before 13.0, but it dropped > > off my list. FTP is not nearly as relevant now as it once was, and it > > had a security vulnerability that secteam had to address. > > > > I'm happy to make a port for it if anyone needs it. Comments? +1 for port. I suspect I last used an FTPd in anger sometime in late 90s, and I surmise this is the vast majority. We will have a very small # of users who require FTPd at all, to make their systems useful. An even smaller # of those users will be unable to use FreeBSD if FTPd is only available in a pkg. For those objecting, are you *really* in that latter category -- are these boxes running without a single port/package installed? When 13.0 goes EOL, somewhere after 2025, will you *still* need ftpd in 14.0 base? It seems a reasonable delay, even for a large corporate, to accommodate this change, which can be done in less time than reading this email. Ian's point about preserving paths is a reasonable one, but I had to add an ntpd user in last updates, this would be less difficult. Eugene mentioned the convenience of ftpd in the same sentence as ipsec. I'm willing to bet those systems have ports installed too. If speed is an issue, HTTP supports pipelining, compression, chunked encoding, & parallel connections. I'm not sure ftpd is even in the same game anymore. The more code we hang onto in base, the larger the millstone around our necks when moving forwards. Each individual opportunity to slim down base *in itself* is not significant, but cumulatively they represent gridlock. For each removal or deprecation, please consider, is this worth holding the project back for? # /etc/src.conf WITHOUT_CRUFT=yes A+ Dave ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
AHCI Patsburg SATA controller and slow transfer speed
Greetings all. I'm on FreeBSD 9.1-STABLE #0 r251391M. I'm noticing two of my SATA disks are at half speed. Is this normal or is there some configuration I'm forgetting? # dmesg | grep -C 4 ahc ... ahci0: port 0x2070-0x2077,0x2060-0x2063,0x2050-0x2057,0x2040-0x2043,0x2020-0x203f mem 0xd0b0-0xd0b007ff irq 21 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 ... ada0: ATA-8 SATA 3.x device ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ATA-8 SATA 3.x device ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad6 ada2 at ahcich2 bus 0 scbus2 target 0 lun 0 ada2: ATA-8 SATA 3.x device ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ^ ada2: Command Queueing enabled ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) ada2: Previously was known as ad8 ada3 at ahcich3 bus 0 scbus3 target 0 lun 0 ada3: ATA-8 SATA 3.x device ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ^^^ ada3: Command Queueing enabled ada3: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) ada3: Previously was known as ad10 # pciconf -lcvb ahci0@pci0:0:31:2: class=0x010601 card=0x35ae8086 chip=0x1d028086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'Patsburg 6-Port SATA AHCI Controller' class = mass storage subclass = SATA bar [10] = type I/O Port, range 32, base 0x2070, size 8, enabled bar [14] = type I/O Port, range 32, base 0x2060, size 4, enabled bar [18] = type I/O Port, range 32, base 0x2050, size 8, enabled bar [1c] = type I/O Port, range 32, base 0x2040, size 4, enabled bar [20] = type I/O Port, range 32, base 0x2020, size 32, enabled bar [24] = type Memory, range 32, base 0xd0b0, size 2048, enabled cap 05[80] = MSI supports 1 message enabled with 1 message cap 01[70] = powerspec 3 supports D0 D3 current D0 cap 12[a8] = SATA Index-Data Pair cap 13[b0] = PCI Advanced Features: FLR TP Thanks for any insight provided. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< "The ultimate aim of dancing is to be able to move *without* thinking. To *be* danced." -John Blacking ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: AHCI Patsburg SATA controller and slow transfer speed
On 06/27/13 18:38, Jeremy Chadwick wrote: Next, this statement by ahci(4) then confuses the user: ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported Yes, this confuses even a seasoned user. ;) TL;DR -- Your motherboard offers 6 ports, 2 of which are SATA600, 4 of which are SATA300, and despite the line shown above by FreeBSD not matching reality, everything is working as designed. It wasn't too long, I *did* read both messages, and thank you both very much for the insight. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< Nobody wants constructive criticism. It's all we can do to put up with constructive praise. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
unexpected idprio 31 behavior on 9.2-BETA2 and 9.2-RC1
I have an i5-2500 machine 8GB RAM now running 9.2-RC1 amd64 with the GENERIC kernel. Today, while still running 9.2-BETA2, I updated my source tree and started building world with idprio 31 and I looked back a while later and all the CPU cores and disk were essentially idle, and hardly any progress had been made on the build. I stopped and restarted the build without the idle priority setting and it ran fine. Anybody else seen any of this? Anybody know about any fairly recent changes that might account for it? I did a "rm -rf /usr/src /usr/obj" and loaded a new source tree before going to RC1. I still see odd behavior at RC1. Sometimes it works just like it should (i.e. compute bound processes use most/all of the available CPU time), but a lot of the time both the CPU and disk are idle (e.g. CPU 97.8% idle, disk 1% busy per systat). I don't think I ever saw this behavior before while running "make buildworld -j4". Can anyone else confirm/rebut my findings? Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
9-STABLE, clang, and virtualbox
I've been trying to get emulators/virtualbox-ose-kmod to compile from ports on a clang built 9-STABLE: # uname -v FreeBSD 9.1-STABLE #0 r251391M: Tue Jun 4 09:47:42 PDT 2013 r...@fb9build.jetcafe.org:/usr/obj/usr/src.amd64/sys/GENERIC amd64 # cc -v FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 Target: x86_64-unknown-freebsd9.1 Thread model: posix After some work I can get it to compile, but then I get this: # kldload /boot/modules/vboxdrv.ko kldload: can't load /boot/modules/vboxdrv.ko: Exec format error # dmesg | tail -2 KLD vboxdrv.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type # kldxref -d /boot/modules/vboxdrv.ko ... /boot/modules/vboxdrv.ko depends on kernel.901505 (901505,99) module vboxdrv interface vboxdrv.1 # kldxref -d /boot/kernel | grep -C 3 /boot/kernel/kernel depends on kernel.901504 (901504,99) module ppi_ppbus depends on ppbus.1 (1,1) /boot/kernel/kernel depends on kernel.901504 (901504,99) module xpt depends on cam.1 (1,1) What's going on here and how can I debug this one? It seems that the module vboxdrv.ko has the correct versions. Thanks in advance for any assistance anyone can provide. :) -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< Imagination is not a talent of some men, but it is the health of every man. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9-STABLE, clang, and virtualbox
On 08/26/13 13:16, Glen Barber wrote: On Mon, Aug 26, 2013 at 01:01:06PM -0700, Dave Hayes wrote: I've been trying to get emulators/virtualbox-ose-kmod to compile from ports on a clang built 9-STABLE: # uname -v FreeBSD 9.1-STABLE #0 r251391M: Tue Jun 4 09:47:42 PDT 2013 r...@fb9build.jetcafe.org:/usr/obj/usr/src.amd64/sys/GENERIC amd64 # cc -v FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 Target: x86_64-unknown-freebsd9.1 Thread model: posix After some work I can get it to compile, but then I get this: # kldload /boot/modules/vboxdrv.ko kldload: can't load /boot/modules/vboxdrv.ko: Exec format error # dmesg | tail -2 KLD vboxdrv.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type # kldxref -d /boot/modules/vboxdrv.ko ... /boot/modules/vboxdrv.ko depends on kernel.901505 (901505,99) module vboxdrv interface vboxdrv.1 # kldxref -d /boot/kernel | grep -C 3 /boot/kernel/kernel depends on kernel.901504 (901504,99) module ppi_ppbus depends on ppbus.1 (1,1) /boot/kernel/kernel depends on kernel.901504 (901504,99) module xpt depends on cam.1 (1,1) What's going on here and how can I debug this one? It seems that the module vboxdrv.ko has the correct versions. Thanks in advance for any assistance anyone can provide. :) What is the svn revision of your /usr/src/ checkout? 251391. See the uname above. :) -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< A question about the sky -- The answer about a rope. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9-STABLE, clang, and virtualbox
On 08/26/13 14:21, Glen Barber wrote: On Mon, Aug 26, 2013 at 02:16:39PM -0700, Dave Hayes wrote: On 08/26/13 13:16, Glen Barber wrote: On Mon, Aug 26, 2013 at 01:01:06PM -0700, Dave Hayes wrote: I've been trying to get emulators/virtualbox-ose-kmod to compile >from ports on a clang built 9-STABLE: # uname -v FreeBSD 9.1-STABLE #0 r251391M: Tue Jun 4 09:47:42 PDT 2013 r...@fb9build.jetcafe.org:/usr/obj/usr/src.amd64/sys/GENERIC amd64 # cc -v FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 Target: x86_64-unknown-freebsd9.1 Thread model: posix After some work I can get it to compile, but then I get this: # kldload /boot/modules/vboxdrv.ko kldload: can't load /boot/modules/vboxdrv.ko: Exec format error # dmesg | tail -2 KLD vboxdrv.ko: depends on kernel - not available or version mismatch linker_load_file: Unsupported file type # kldxref -d /boot/modules/vboxdrv.ko ... /boot/modules/vboxdrv.ko depends on kernel.901505 (901505,99) module vboxdrv interface vboxdrv.1 # kldxref -d /boot/kernel | grep -C 3 /boot/kernel/kernel depends on kernel.901504 (901504,99) module ppi_ppbus depends on ppbus.1 (1,1) /boot/kernel/kernel depends on kernel.901504 (901504,99) module xpt depends on cam.1 (1,1) What's going on here and how can I debug this one? It seems that the module vboxdrv.ko has the correct versions. Thanks in advance for any assistance anyone can provide. :) What is the svn revision of your /usr/src/ checkout? 251391. See the uname above. :) That does not mean your current checkout matches that revision. In my case it doesI checked with svn info before I sent the mail. -- Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org >>>> *The opinions expressed above are entirely my own* <<<< Only one who is seeking certainty can be uncertain. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On 09/27/2013 15:06, David Demelier wrote: > > Also in the future you can just forgot that crappy ideas as you can see, > nobody liked it. > Glad you aren't my dad, Grinch. -- Dave Robison Sales Solution Architect II FIS Banking Solutions 510/621-2089 (w) 530/518-5194 (c) 510/621-2020 (f) da...@vicor.com david.robi...@fisglobal.com _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Pf, rtable, and rdr...bug?
Hello everyone. I'm having a problem with using rdr in an existing pf that uses
rtable. I'm running 10.1-STABLE #0 r282154 and I believe this is a bug, but it
could also be something I haven't spotted.
I have a firewall with three interfaces. The ip addresses have been changed to
protect the innocent. :)
- a slow net (1.2.3.0/24) interface: em0 @ 1.2.3.10
- a fast net (4.5.6.0/24) interface: em1 @ 4.5.6.10
- an internal net (192.168.4.0/24) interface: em2 @ 192.168.4.10
I route the internal net traffic over the fast cable net, and allow the
internet net to access machines on the slower work net. Both default routes for
the slow and fast net are .1 addresses (e.g. 1.2.3.1 and 4.5.6.1). I use an
alias on both the slow and fast net (.42) to route the traffic from so I can
see what's going on. I have net.fibs="2" in loader.conf and two different
default routes set up for each fib. The default "default route" (fib 0) is
1.2.3.1.
Here's my pf ruleset that works, paraphrased.
$slow_net = "1.2.3.0/24"
$slow_if = "em0"
$slow_nat_ip = "1.2.3.42"
$fast_net = "4.5.6.0/24"
$fast_if = "em1"
$fast_nat_ip = "4.5.6.42"
$int_net = "192.168.4.0/24"
$int_if = "em2"
$int_ip = "192.168.4.10" # I don't alias this side
table const { 10/8, 172.16/12, 192.168/16 }
nat log in $fast_if inet from $int_if:network to ! $slow_net -> $fast_nat_ip
nat log on $slow_if inet from $int_if:network to $slow_net -> $slow_nat_ip
block in log all
antispoof log quick for { $slow_if $fast_if $int_if }
pass in log quick on $int_if inet from $int_net to !$slow_if:network
modulate state rtable 1
pass in log quick on $int_if inet from $int_net to $slow_if:network
modulate state rtable 0
pass log on $slow_if inet from ! to any modulate state
pass out log inet from any to any modulate state
So I tried to use rdr to forward some ports from the to a machine on the
internal net:
$webserver = "192.168.4.22"
rdr on $fast_if inet proto tcp from any to port 80 -> $webserver
This doesn't work. When I turn on tcpdump on all three interfaces, I see the
packets coming in from the fast net to the internal net. The responses are
appearing on the slow net, with the IP addresses of the fast net. So if I see
this from em1:
14:34:11.887357 IP 10.11.12.13:18600 > 4.5.6.42:80 ...
I then see the response...but on em0:
14:34:12.087283 IP 4.5.6.42:80 > 10.11.12.13:18600 ...
Why doesn't this response packet go out the proper interface?
Thanks in advance for any insight. If I don't hear from anyone, I'm going to
assume this is a bug and file a bug report.
--
Dave Hayes - Consultant - Altadena CA, USA - d...@jetcafe.org
>>>> *The opinions expressed above are entirely my own* <<<<
A path and a gateway have no meaning or use once the
objective is in sight.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
freebsd-update upgrading 9.2 -> 9.3
Trying to upgrade a system from 9.2 -> 9.3 with freebsd-update and I get the output below. Search has seen reports but not solutions. I also tried upgrading to 10.1 and seeing similar issue those the "No such file or directory" error only shows up once but is asking for me to manually merge lots of unmodified files in /etc. Anybody have a clue on what is going wrong? -- Dave freebsd-update -r 9.3-RELEASE upgrade Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching public key from update6.freebsd.org... done. Fetching metadata signature for 9.2-RELEASE from update6.freebsd.org... done. Fetching metadata index... done. Fetching 2 metadata files... done. Inspecting system... done. The following components of FreeBSD seem to be installed: kernel/generic world/base world/doc world/lib32 The following components of FreeBSD do not seem to be installed: src/src world/games Does this look reasonable (y/n)? y Fetching metadata signature for 9.3-RELEASE from update6.freebsd.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Fetching files from 9.2-RELEASE for merging... done. Preparing to download files... done. Fetching 1322 patches.102030405060708090100110120130140150160170180190200210220230240250260270280290300310320330340350360370380390400410420430440450460470480490500510520530540550560570580590600610620630640650660670680690700710720730740750760770780790800810820830840850860870880890900910920930940950960970980990100010101020103010401050106010701080109011001110112011301140115011601170118011901200121012201230124012501260127012801290130013101320. done. Applying patches... done. Fetching 199 files... done. /usr/sbin/freebsd-update: cannot open files/.gz: No such file or directory /usr/sbin/freebsd-update: cannot open files/.gz: No such file or directory /usr/sbin/freebsd-update: cannot open files/.gz: No such file or directory [ snip the out the 100 repeats of this error ] /usr/sbin/freebsd-update: cannot open files/.gz: No such file or directory /usr/sbin/freebsd-update: cannot open files/.gz: No such file or directory The following file will be removed, as it no longer exists in FreeBSD 9.3-RELEASE: /boot/device.hints Does this look reasonable (y/n)? n ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: freebsd-update upgrading 9.2 -> 9.3
> On Jun 14, 2015, at 8:59 AM, Rainer Duffner wrote: > > >> Am 14.06.2015 um 15:46 schrieb Dave Duchscher : >> >> Trying to upgrade a system from 9.2 -> 9.3 with freebsd-update and I get the >> output below. Search has seen reports but not solutions. I also tried >> upgrading to 10.1 and seeing similar issue those the "No such file or >> directory" error only shows up once but is asking for me to manually merge >> lots of unmodified files in /etc. >> >> Anybody have a clue on what is going wrong? > > > > Are you on the latest patch-level for 9.2? Looking, I am not at the latest version. Trying to upgrade to the latest version breaks things (ssh is the main thing, missing libssh.so.5 errors). Ignoring the breakage, I get the same errors. Using the freebsd-update script from the latest 9.2 doesn't help. I am guessing a rebuild of the system is necessary. That may have to wait for another day. Thankfully, I can rollback. -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Any suggestions for a layer 3 load ablancer for 12, as relayd doesnt work anymore
On Mon, 14 Jan 2019, at 17:15, Pete French wrote: > So, until the middle of this afternoon I was, doing my load > balancing using> relayd from ports and PF. My own fault for not checking, but > I > upgraded> one of the firewall pair to 12 and then discovered that the > relayd port is> no > Am now puzzling over solutions to this - I dont really want to stay on> 11 > forevere. Moving to OpenBSD to get their PF and relayd is a bit of> an > uncomfortable idea as we gain a lot from having one OS > everywhere that> people know, so does anyone have any suggestions ? > > PF round robin is not good enough for this as I have some dynamic > problems> which indicate when a node is up or down. Relayd will check > these, but the> basic PF wil not as far as I know. > > What do other people do ? haproxy does proper failover and allows custom health checks either via URL or real world traffic of external scripts. Traefik has lots of container oriented features. Dave ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ipfw with if_bridge oddity
I got nothing from questions@ so I'm posting here.
I can't seem to grasp why this is working differently.
FreeBSD 6.2 using ipfw + if_bridge
LAN -- em1(if_bridge + ipfw)em0 -- internet
I am at xx.xx.16.6 and try to ping say www.yahoo.com
in ruleset:
1100 allow icmp from any to xx.xx.16.0/27{1-10,13,14,19,22,23} icmptypes
0,3,11,12,13,14
2100 allow ip from xx.xx.16.0/27 to any in via em1
gets dropped by following rule as shown in logs:
4700 deny log ip from any to any
Log entry: ipfw: 4700 Deny ICMP:8.0 xx.xx.16.6 69.147.114.210 out via em0
If I add this rule all works great:
2101 allow icmp from xx.xx.16.0/27 to any recv em1
Why would the "recv em1" work and the "in via em1" get blocked?
I just changed from using bridge(4) to if_bridge using the same ruleset.
The rest of my ruleset seems to be working fine but this problem is causing me
a little paranoia
about the effectiveness of the firewall.
Also, should I still be seeing "deny (snip) in via bridge0" messages in by logs
if I have this set "net.link.bridge.pfil_bridge: 0"?
Thanks for your help.
dave
Looking for a deal? Find great prices on flights and hotels with Yahoo!
FareChase.
http://farechase.yahoo.com/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfw with if_bridge oddity
On Fri, 6 Jul 2007, Dave McCammon wrote:
> I can't seem to grasp why this is working differently.
> FreeBSD 6.2 using ipfw + if_bridge
>
> LAN -- em1(if_bridge + ipfw)em0 -- internet
>
> I am at xx.xx.16.6 and try to ping say www.yahoo.com
>
> in ruleset:
> 1100 allow icmp from any to xx.xx.16.0/27{1-10,13,14,19,22,23} icmptypes
> 0,3,11,12,13,14
> 2100 allow ip from xx.xx.16.0/27 to any in via em1
>Seeing noone more knowledgeable has had a go, and with the caveat that
Thank you.
>I've never setup an if_bridge(4) but still maintain a bridge(4)+ipfw ..
>Rule 2100 lets your ping in, and 1100 allows the response (in and out)
> gets dropped by following rule as shown in logs:
>
> 4700 deny log ip from any to any
>
> Log entry: ipfw: 4700 Deny ICMP:8.0 xx.xx.16.6 69.147.114.210 out via em0
>Denied because you have no rule letting it go out, it seems.
It's the "out via em0" that I am questioning, which I believe shouldn't be
happening.
It seems that ipfw+if_bridge works differently with ICMP than ipfw_bridge(4).
Rule 2100 should allow the packet through(I read the rule as:"it is ok since it
came in em1").
Other rules just like this(in via em1) work with tcp and udp.
example :
allow tcp from xx.xx.16.0/27 to any in via em1 setup keep-state
if the packet came from xx.xx.16.0/27 network and came "in" the em1
interface,
than pass the packet.
It just seems the ICMP gets dropped,
which, I am assuming, rule 2100 should have allowed through the firewall.
> If I add this rule all works great:
>
> 2101 allow icmp from xx.xx.16.0/27 to any recv em1
>Which allows it both in and out (neither specified)
This should allow the packet because it came through the receiving interface on
interface em1.
This is really my questioning: Why is it that "in via em1" doesn't work on ICMP
but changing or adding
a similar rule with "recv em1" will pass the ICMP.
allow ip from 157.91.16.0/27 to any in via em1 > legit "passing_thru"
ICMP gets dropped with if_bridge but not with bridge(4)
allow ip from 157.91.16.0/27 to any recv em1 > passes the "passing_thru"
ICMP using if_bridge
> Why would the "recv em1" work and the "in via em1" get blocked?
>
> I just changed from using bridge(4) to if_bridge using the same ruleset.
>Only inbound bridged packets are passed to ipfw from bridge(4) .. once
>allowed in, they go out. My reading of if_bridge(4) suggests that ipfw
>(etc) may also be examining outbound bridged packets, depending on the
>sysctls. How have you got the sysctls mentioned in if_bridge(4) set?
my sysctl.conf variables:
net.link.bridge.ipfw=1
net.link.bridge.pfil_member=1
net.link.bridge.pfil_onlyip=1
net.link.bridge.pfil_bridge=0
net.link.bridge.ipfw_arp=1
> The rest of my ruleset seems to be working fine but this problem is causing
> me a little paranoia
> about the effectiveness of the firewall.
>
> Also, should I still be seeing "deny (snip) in via bridge0" messages in by
> logs
> if I have this set "net.link.bridge.pfil_bridge: 0"?
Thanks again,
Dave
Looking for a deal? Find great prices on flights and hotels with Yahoo!
FareChase.
http://farechase.yahoo.com/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portaudit and portsnap acting silly.
Portaudit does this: # portaudit -Fa auditfile.tbz 100% of 46 kB 6001 kBps portaudit: Database too old. Old database restored. portaudit: Download failed. Portsnap does this: # portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found. Fetching snapshot tag from portsnap3.FreeBSD.org... done. Latest snapshot on server is older than what we already have! Cowardly refusing to downgrade from Thu Dec 27 08:10:58 PST 2007 to Mon Dec 3 17:04:28 PST 2007. In case anyone knows anyone who can beat them back into submission. Dave Overton, Owner SYIX.COM [EMAIL PROTECTED] (530) 755-1751 x101 Fax (530) 751-8871 800-988-SYIX ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: portaudit and portsnap acting silly.
Fixed. For reference, it was squid, happily caching the data for me. Makes one wonder why the portsnap and portaudit servers or clients aren't http compliant if they use http protocols... Especially since the author of portsnap suggests a cache server for speed Oh well... Dave Overton, Owner SYIX.COM [EMAIL PROTECTED] (530) 755-1751 x101 Fax (530) 751-8871 800-988-SYIX > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dave Overton > Sent: Thursday, December 27, 2007 11:22 AM > To: freebsd-stable@freebsd.org > Subject: portaudit and portsnap acting silly. > > Portaudit does this: > # portaudit -Fa > auditfile.tbz 100% of 46 kB > 6001 kBps > portaudit: Database too old. > Old database restored. > portaudit: Download failed. > > > Portsnap does this: > # portsnap fetch > Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found. > Fetching snapshot tag from portsnap3.FreeBSD.org... done. > Latest snapshot on server is older than what we already have! > Cowardly refusing to downgrade from Thu Dec 27 08:10:58 PST > 2007 to Mon Dec 3 17:04:28 PST 2007. > > > In case anyone knows anyone who can beat them back into submission. > > Dave Overton, Owner > SYIX.COM > > [EMAIL PROTECTED] > (530) 755-1751 x101 > Fax (530) 751-8871 > 800-988-SYIX > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
8.0-BETA-4: no mouse or keyboard in X.
I upgraded from 7.2 to 8.0-BETA4. Now X will not receive input from either the mouse or keyboard. When this has happened in 7.1 or 7.2 it was fixed by running hal. The keyboard, mouse and hal are all working. I did not configure X, the xorg.conf file was auto generated when X was first started. I have tried a few things; new xorg.conf with Xorg -configure, putting config files, which I found in a mailing list, in /usr/local/etc/hal/fdi/policy. Using a different window manager. Nothing worked. Theres nothing in the log files that I recognise. Xorg.log reported "config/hal Adding input device AT Keyboard." Any suggestions I also noticed the fuse.ko will not load, reporting "Exec format error." d...@loc:/usr/home/dave $ uname -a FreeBSD loc.alh.ost 8.0-BETA4 FreeBSD 8.0-BETA4 #0: Sun Sep 6 04:44:31 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Thanks Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8.0-BETA-4: no mouse or keyboard in X.
On Tue, Sep 15, 2009 at 01:24:37PM +1000, Dave Hardman wrote: > On Sun, Sep 13, 2009 at 12:40:52PM +0200, Patrick Lamaiziere > wrote: > > Le Sun, 13 Sep 2009 15:29:58 +1000, Dave Hardman > > a écrit : > > > > > I upgraded from 7.2 to 8.0-BETA4. Now X will not receive > > > input from either the mouse or keyboard. > >[...] You need to rebuild hal and to remove the old libusb port. > >libusb is now part of the base system in 8.X and you must use > >this version. You should rebuild all that depend on the old port > >libusb (at least). > I rebuilt all the ports (portupgrade -afc), during the upgrade > and there was no indication of any failures. I tried again > (portmanager -u -f -l). hal-0.5.11_26 failed. See below. > > > > I also noticed the fuse.ko will not load, reporting "Exec > > > format error." > > > > Did you rebuild this module too? > It rebuilt when I ran portmanager. > > I also tried to remove the libusb, as another responded > suggested. However pkg_delete refused as it was required by other > packages. Mostly gnome by the look of it eg, gnucash gnumeric. > > Best > Dave > > gmake[5]: Entering directory > `/usr/ports/sysutils/hal/work/hal-0.5.11/hald/freebsd/probing' > cc -DHAVE_CONFIG_H -I. -I../../.. -DPACKAGE_SYSCONF_DIR=\""/usr/local/etc"\" > -DPACKAGE_DATA_DIR=\""/usr/local/share"\" > -DPACKAGE_BIN_DIR=\""/usr/local/bin"\" > -DPACKAGE_LOCALE_DIR=\""/usr/local/share/locale"\" > -DPACKAGE_LOCALSTATEDIR=\""/var"\" -I../../.. -I/usr/local/include/dbus-1.0 > -I/usr/local/include/dbus-1.0/include -I/usr/local/include -DHAVE_CK_0_3 > -O2 -pipe -fno-strict-aliasing -Wall -Wchar-subscripts -Wmissing-declarations > -Wnested-externs -Wpointer-arith -Wcast-align -Wsign-compare -MT > probe-hiddev.o -MD -MP -MF .deps/probe-hiddev.Tpo -c -o probe-hiddev.o > probe-hiddev.c > probe-hiddev.c: In function 'main': > probe-hiddev.c:81: error: 'USB_GET_REPORT_ID' undeclared (first use in this > function) > probe-hiddev.c:81: error: (Each undeclared identifier is reported only once > probe-hiddev.c:81: error: for each function it appears in.) > gmake[5]: *** [probe-hiddev.o] Error 1 > gmake[5]: Leaving directory > `/usr/ports/sysutils/hal/work/hal-0.5.11/hald/freebsd/probing' > gmake[4]: *** [all-recursive] Error 1 > gmake[4]: Leaving directory > `/usr/ports/sysutils/hal/work/hal-0.5.11/hald/freebsd' > gmake[3]: *** [all-recursive] Error 1 > gmake[3]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11/hald' > gmake[2]: *** [all] Error 2 > gmake[2]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11/hald' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/sysutils/hal/work/hal-0.5.11' > gmake: *** [all] Error 2 > *** Error code 1 > > Stop in /usr/ports/sysutils/hal. > *** Error code 1 > > Stop in /usr/ports/sysutils/hal. > ! sysutils/hal (hal-0.5.11_26) (compiler error) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Can't build 11-stable without BPF
When I remove the "device bpf" from the kernel configuration the resulting "make buildkernel KERNCONF=XXX" fails to compile in module lmc, source file if_lmc.c The problem seems to be that DEV_BPF is not defined, but this is not tested for. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Cannot set CPU frequency for 8th gen CPU
I have an 8th gen (i5-8400) processor installed in motherboard using the H370 chipset (Gigabyte H370 HD3) with factory default BIOS configuration running FreeBSD 11.2 amd64. Although the correct number of cores (6) and available frequencies are correctly detected only the lowest frequency is usable: # sysctl dev.cpu.0.freq_levels dev.cpu.0.freq_levels: 2801/65000 2800/65000 2700/61690 2500/55888 2400/52759 2200/47301 2100/44946 1900/39204 1800/37000 1700/34277 1500/29546 1400/27531 1200/22557 1100/20688 900/16549 800/14296 # sysctl dev.cpu.0.freq=2800 dev.cpu.0.freq: 800 -> 800 Accordingly powerd continues to try and raise the frequency in response to high system load but is unable to do so. If I disable 5 of the 6 cores in the BIOS then setting frequency as above is successful. Has this been reproduced and/or what are the next steps I should take to investigate? Attached is the obligatory dmesg which contains some complaints about ACPI firmware of unknown relevance? -- CPU: Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz (2808.23-MHz K8-class CPU) Origin="GenuineIntel" Id=0x906ea Family=0x6 Model=0x9e Stepping=10 Features=0xbfebfbff Features2=0x7ffafbbf AMD Features=0x2c100800 AMD Features2=0x121 Structured Extended Features=0x29c67af Structured Extended Features2=0x4000 Structured Extended Features3=0xc00 XSAVE Features=0xf VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16386461696 (15627 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 6 CPUs FreeBSD/SMP: 1 package(s) x 6 core(s) ioapic0 irqs 0-119 on motherboard SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #4 Launched! Timecounter "TSC-low" frequency 1404113625 Hz quality 1000 random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0x80ff4550, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 cryptosoft0: on motherboard aesni0: on motherboard acpi0: on motherboard ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x33CCD (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x33CD6 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x343C1 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x343CA (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x34AB5 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x34ABE (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x351AA (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x351B3 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x3589F (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x358A8 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x35C52 (20171214/psloop-344) ACPI Warning: Unsupported module-level executable opcode 0x70 at table offset 0x35C5B (20171214/psloop-344) Firmware Error (ACPI): Failure looking up [\134_SB.PCI0.RP04.PXSX._SB.PCI0.RP05.PXSX], AE_NOT_FOUND (20171214/dswload2-312) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20171214/psobject-371) ACPI Error: Method parse/execution failed \134_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20171214/psparse-677) Firmware Error (ACPI): Failure looking up [\134_SB.PCI0.RP08.PXSX._SB.PCI0.RP09.PXSX], AE_NOT_FOUND (20171214/dswload2-312) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20171214/psobject-371) ACPI Error: Method parse/execution failed \134_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20171214/psparse-677) Firmware Error (ACPI): Failure looking up [\134_SB.PCI0.RP12.PXSX._SB.PCI0.RP13.PXSX], AE_NOT_FOUND (20171214/dswload2-312) ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20171214/psobject-371) ACPI Error: Method parse/execution failed \134_SB.PCI0.RP12.PXSX, AE_NOT_FOUND (20171214/psparse-677) Firmware Error (ACPI): Failure looking up [\134_SB.PCI0.RP05.PXSX.WIST], AE_NOT_FOUND (20171214/psargs-503) ACPI Error: Method parse/execution failed \134CNDP, AE_NOT_FOUND (20171214/psparse-677) ACPI Error: Method parse/execution failed \134, AE_NOT_FOUND (20171214/psparse-677) acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 2400 Hz quality 950 Event timer "HPET
Re: Cannot set CPU frequency for 8th gen CPU
On Wed, 18 Jul 2018, at 8:31 PM, Dave Green wrote: > If I disable 5 of the 6 > cores in the BIOS then setting frequency as above is successful. Further, when setting: # sysctl debug.cpufreq.verbose=1 A different 11.1 amd64 system with a 2nd gen 4 core processor reports: cpufreq: setting abs freq 2500 on est0 (cpu 0) cpufreq: setting abs freq 2500 on est1 (cpu 1) cpufreq: setting abs freq 2500 on est2 (cpu 2) cpufreq: setting abs freq 2500 on est3 (cpu 3) Whereas the 11.2 amd64 system with the 8th gen 6 core reports: cpufreq: setting abs freq 2800 on est0 (cpu 1) cpufreq: setting abs freq 2800 on est1 (cpu 2) cpufreq: setting abs freq 2800 on est2 (cpu 3) cpufreq: setting abs freq 2800 on est3 (cpu 4) cpufreq: setting abs freq 2800 on est3 (cpu 5) For the second (faulty) system cpu0 is conspicuously missing and may explain why frequency can only be set on that machine with all but one core disabled? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Failing to retrieve source tarballs for anything.
On Sat, 1 Sep 2018, at 19:25, Alex McKeever wrote: > After compiling PKG, when I go to ports to compile anything (my eMac can > run FreeBSD but not modern Linux due to the version of the Radeon GPU) Is it one these, https://en.wikipedia.org/wiki/EMac ? A dmesg and ifconfig of this "eMac" may be helpful, and a specific model number in case somebody else already bashed their head against it enough to get a working setup. Does it even get an interface up & running in some form? Maybe start off with throwing a USB ethernet wired adapter onto it and hoping a miracle occurs. A+ Dave ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RocketRAID 2224
I am attemping to use a RocketRAID 2224 8 channel card to set up a storage server. The server board is an Intel SE7230NH1-E with a P4-D 2.8GHz, 2GB RAM. FreeBSD doesn't see it at all. I've noticed that the kernel config has options built in for the RocketRAID 182x. Are there options I can add for the newer card? If so, will they work with FreeBSD 6.1 so that I can reconfigure for it rather than 6.0 that's running now? Basically we're trying to set up backups to disk with a RAID of about 4.5TB. Thanks for any help. -- Dave *** There are 10 types of people. Those who understand binrary ... ...and those who don't ### David Kingsley, Systems Administrator Eastern Nazarene College 23 East Elm Avenue Quincy, MA 02170 [EMAIL PROTECTED] 617-745-3806 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RocketRAID 2224
I am attemping to use a RocketRAID 2224 8 channel card to set up a storage server. The server board is an Intel SE7230NH1-E with a P4-D 2.8GHz, 2GB RAM. When I set up a RAID5 with 7 750GB drives I get nothing but wierdness. Using sysinstall -> Configure -> Fdisk I can see the full size: DISK Geometry: 547149 cyls/255 heads/63 sectors = 8789948685 sectors (4291967MB) But Label sees: Disk: da0 Partition name: da0s1 Free: 200014030 blocks (97663MB) What am I doing wrong? All of the drivers seem to installed; at least they say they are. Is this just too big for FreeBSD? I hope not! Help! -- Dave *** There are 10 types of people. Those who understand binrary ... ...and those who don't ### David Kingsley, Systems Administrator Eastern Nazarene College 23 East Elm Avenue Quincy, MA 02170 [EMAIL PROTECTED] 617-745-3806 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Attention Julian Stacey
On Sun, 17 Sep 2006, Julian H. Stacey wrote: > > lol, that's the stupidest thing I've heard all week. > > Inflamatory. Refered to postmaster. That's even funnier. -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
On Mon, 18 Sep 2006, Oliver Fromme wrote: [...] > Then the names match exactly what the branches are: "current" is the > current head of experimental development, "releng" is the release > engineering branch, and "stable" is the stable branch for people who > want to track only security fixes and the most critical stuff. Which is pretty well what OpenLDAP does; over there, HEAD is bleeding edge, RELEASE is the latest version, and STABLE is, well, stable as understood by most humans... See http://www.openldap.org/software/download/ -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Buckets of spam on list?
Has FreeBSD's spam filter opened its legs again? Along with MOBILE, ACPI, and just about every other spammer-friendly open list? -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SCB - timed out on FreeBSD 4.10-p2
[Reposted, no answer from the SCSI list] I'm wondering if this has been seen before exactly? I'm seeing the following on a FreeBSD server: /kernel: (da1:ahd1:0:0:0): SCB 0x12 - timed out /kernel: (da1:ahd1:0:0:0): Other SCB Timeout /kernel: ahd1: Recovery Initiated - Card was not paused Googling around a bit gave me a weak theory that the seagate firmware might be defective, but that diagnosis is several months old. Can anyone shed some light on this? I can provide more data on request. The server has the following relevant devices on it: /kernel: The Regents of the University of California. All rights reserved. /kernel: FreeBSD 4.10-RELEASE-p2 #0: Fri Jul 30 02:50:53 PDT 2004 /kernel: [EMAIL PROTECTED]:/usr/src/sys/compile/DTE /kernel: Timecounter "i8254" frequency 1193182 Hz /kernel: CPU: Intel(R) Xeon(TM) CPU 2.60GHz (2599.72-MHz 686-class CPU) /kernel: Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 /kernel: Features=0xbfebfbff /kernel: Hyperthreading: 2 logical CPUs /kernel: real memory = 1073217536 (1048064K bytes) /kernel: avail memory = 1022291968 (998332K bytes) ... /kernel: ahd0: port 0x4000-0x40ff,0x4400-0x44ff mem 0xfc40-0xfc401fff irq 11 at device 2.0 on pci6 /kernel: aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs /kernel: ahd1: port 0x4800-0x48ff,0x4c00-0x4cff mem 0xfc402000-0xfc403fff irq 11 at device 2.1 on pci6 /kernel: aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs ... /kernel: da0 at ahd0 bus 0 target 0 lun 0 /kernel: da0: Fixed Direct Access SCSI-3 device /kernel: da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled /kernel: da0: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) /kernel: da1 at ahd1 bus 0 target 0 lun 0 /kernel: da1: Fixed Direct Access SCSI-3 device /kernel: da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled /kernel: da1: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) The motherboard specs can be found at: http://www.supermicro.com/products/motherboard/Xeon/E7500/P4DP8-G2.cfm Thanks in advance. -- Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] >>> The opinions expressed above are entirely my own <<< Man is most nearly himself when he achieves the seriousness of a child at play. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bktr_core.c:1261: error: `FNDELAY' undeclared
FreeBSD 5.3-STABLE, last updated 1st Jan 2005. Just did a CVSUP of -STABLE. make buildworld - OK. make buildkernel KERNCONF=STINKY Goes swimmingly, then... cc -O -pipe -D_KERNEL -DKLD_MODULE -nostdinc -I- -include /usr/obj/usr/src/sys/STINKY/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/usr/obj/usr/src/sys/STINKY -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c /usr/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c: In function `vbi_read': /usr/src/sys/modules/bktr/bktr/../../../dev/bktr/bktr_core.c:1261: error: `FNDELAY' undeclared (first use in this function) Nothing in /usr/src/UPDATING; nothing that Google can find. Did I miss something? I don't even know why it's being compiled, since it's not in my config file, so I've commented it out until if/when I get a chance to look at it... -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bktr_core.c:1261: error: `FNDELAY' undeclared
Skip it - someone else spotted the problem just before I did (seems to have been a broken commit). -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bktr_core.c commit breaks building kernels on RELENG_5
On Sun, 16 Jan 2005, Jon Noack wrote:
> This commit broke building kernels on RELENG_5 (see tinderbox logs):
> > cognet 2005-01-16 01:01:15 UTC
Thanks; I was wondering what broke...
> I believe this change was unintended:
> > @@ -1258,7 +1258,7 @@ vbi_read(bktr_ptr_t bktr, struct uio *ui
> > LOCK_VBI(bktr);
> > while(bktr->vbisize == 0) {
> > - if (ioflag & IO_NDELAY) {
> > + if (ioflag & FNDELAY) {
> > status = EWOULDBLOCK;
> > goto out;
> > }
Yep.
-- Dave
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: strange ucom (uplcom) error
On Tue, 18 Jan 2005, Andrew L. Neporada wrote: > > The not working (more expensive) one gets recognized as ucom0 and I have > > ucom0, also I can receive signal but not transmit. > > > [skip] > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > It can break old (working) PL2303 chip, but it works for me with newer > revision chip (tested under 4.10). Hmmm... That could explain something I saw. I've got two cables, bought from different vendors (same chipset). Both worked under 4.10, only one under 5.3 (different platforms). I'll try it when I get a moment. -- Dave ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [HEADS UP] perl symlinks in /usr/bin will be gone
On Sun, 30 Jan 2005, Holger Kipp wrote: > > I'm fine with this plan for 6-CURRENT. For 5-STABLE, it's a major > > user-visible change, and that is something that we promised to avoid > > with stable branches. > > It violates POLA on 5-STABLE, and it will violate POLA on 6-CURRENT, > especially as most perl programmers assume /usr/bin/perl to be the > correct path. I have *never* assumed that Perl was in /usr/bin, so for me the POLA simply doesn't apply. In fact, the POLA would seem to say that you don't put a 3rd-party product into a system area. -- Dave, who was taught by JohnL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
