RE: NATD question...
I typed that wrong in the e-mail, but not in my configuration file. redirect_port 192.168.x.x:http The question still stands: Why didn't this work? Thanks! -- Paul A. Howes -Original Message- From: Hideyuki KURASHINA [mailto:[EMAIL PROTECTED] Sent: Monday, July 28, 2003 3:53 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: NATD question... Hi, >>> On Mon, 28 Jul 2003 12:17:24 -0400, "Paul A. Howes" <[EMAIL PROTECTED]> said: > All, > > I am trying to redirect a port on my FreeBSD 5.1-based firewall to an > internal machine. My natd configuration contains a directive: > > redirect-port 192.168.x.x:http > > I performed a "kill -HUP" on the natd process, but it doesn't work. I can > verify that the internal Web server is functional, and accessible to the > internal network. I even added ipfw rules to allow for traffic on port > , but still nothing. > > Am I missing something obvious here? Thanks! That's a wrong directive. Use ``redirect_port''. ^ -- rushani ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
NATD question...
All, I am trying to redirect a port on my FreeBSD 5.1-based firewall to an internal machine. My natd configuration contains a directive: redirect-port 192.168.x.x:http I performed a "kill -HUP" on the natd process, but it doesn't work. I can verify that the internal Web server is functional, and accessible to the internal network. I even added ipfw rules to allow for traffic on port , but still nothing. Am I missing something obvious here? Thanks! -- Paul A. Howes ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: SMBus support...
Sergey, Thanks! Where is this documented? -- Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sergey A. Osokin Sent: Wednesday, February 26, 2003 7:10 AM To: Paul A. Howes Cc: [EMAIL PROTECTED] Subject: Re: SMBus support... Try to use device ichsmb, maybe its helps you. -- Rgdz,/"\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SMBus support...
All, My motherboard has SMBus support: [EMAIL PROTECTED]:31:3:class=0x0c0500 card=0x24c28086 chip=0x24c38086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801DB (ICH4) SMBus Controller' class= serial bus subclass = SMBus ...but there is no driver. I didn't see a module in /boot/kernel that looked likely, and there isn't a driver listed in /usr/src/sys/i386/conf/NOTES for it. Is there a way to enable SMBus support on 5.0-RELEASE? Thanks! -- Paul A. Howes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: buildworld dies with Signal 4
Paulius, I had the exact same problem less than a week ago. The solution was the edit my kernel build configuration file and add the following two lines: options DISABLE_PSE options DISABLE_PG_G This changes the VM subsystem so that it uses 4 kB pages instead of the default 4 MB pages. There is a bug in some hardware that only shows up under heavy CPU & memory loading, such as a buildworld incurs. Someone had told me that there is a 10% - 15% performance penalty from doing this, but I don't run the system hard enough to be able to notice. -- Paul A. Howes -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paulius Bulotas Sent: Tuesday, February 25, 2003 11:21 AM To: [EMAIL PROTECTED] Subject: Re: buildworld dies with Signal 4 On 03 02 25, Steve Kargl wrote: > On Tue, Feb 25, 2003 at 05:12:52PM +0200, Paulius Bulotas wrote: > > and I'm trying to make buildworld today, but it crashes in various > > places with Signal 4. > Do you have CPUTYPE=p4? How much memory > is in the computer? You are right, it's CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1799.81-MHz 686-class CPU) real memory = 527695872 (503 MB) on Intel 845G motherboard and in make.conf I have CPUTYPE and other compile time options commented out (because some time ago I was unable to build mozilla) sometimes I get Signal 10... Paulius To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: cc: Internal error: Illegal instruction (program as)
Soren, I have a machine that uses a SiS 648, but it has other problems... I'm one of the unlucky individuals who bought the ASUS implementation of this board, and ended up with a flaky P.O.S. I'm seriously thinking of swapping it for a Tyan S2662 (Granite Bay) motherboard, or waiting a few months for the 800 MHz FSB boards and chips to come out. My wife does a great deal of photo restoration, and the faster FSB would be a major improvement over the ASUS board. I haven't bothered to test any of my systems in an over clocked state, as the stability is more important to me, and my work, than wringing out the last MHz of performance. :) -- Paul A. Howes -Original Message- From: Soeren Schmidt [mailto:[EMAIL PROTECTED] Sent: Monday, February 24, 2003 7:15 AM To: [EMAIL PROTECTED] Subject: Re: cc: Internal error: Illegal instruction (program as) Could very well be that, this is a SiS 648 system with DDR333 RAM.. I can provoke something that looks like this problem if I overclock it severely ie run it a ~3Ghz with 233Mhz mem clock... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: cc: Internal error: Illegal instruction (program as)
Jiawei, I always remove the contents of /usr/obj prior to performing a buildworld, and I could reproduce this behavior every time. -- Paul A. Howes -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of leafy Sent: Monday, February 24, 2003 7:08 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: cc: Internal error: Illegal instruction (program as) On Mon, Feb 24, 2003 at 12:10:46PM +0100, Soeren Schmidt wrote: > > inverse provided in the kernel configuration file (ENABLE_PSE & > > ENABLE_PG_G). > > Just for the record but my [EMAIL PROTECTED]/533 512MB/DDR does *not* show this > problem no matter how hard I beat it. > > -S?en Try this: DON'T remove /usr/obj before doing a buildworld, just let it accumulate. It will show up someday (it's not deterministic). Even sh(1) can die during the build along with make(1) and as and gcc. My P4 never showed such behaviour if I properly remove /usr/obj before a build. Jiawei Ye -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: cc: Internal error: Illegal instruction (program as)
All; These two kernel options seem to have solved the problem. Builds now run smoothly and error-free. I read the comments in NOTES about these options and something clicked: I recall that most Pentium processors will only deal with 4 kB pages. Aren't 4 MB pages a feature of the Xeon processor, as it can address much more memory? If that is the case, then these options should be the default, and their inverse provided in the kernel configuration file (ENABLE_PSE & ENABLE_PG_G). -- Paul A. Howes -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Hay Sent: Saturday, February 22, 2003 1:05 PM To: Paul A. Howes Cc: [EMAIL PROTECTED] Subject: Re: cc: Internal error: Illegal instruction (program as) On Sat, Feb 22, 2003 at 11:43:01AM -0500, Paul A. Howes wrote: > All, > > I am receiving some strange errors during a buildworld of 5.0-RELEASE-p2 > from 5.0-RELEASE-p1. The location of where the failure varies, but the > program that causes the failure is the same every time: "as". > > The errors are a variety of signal 10 and signal 4. I do find an > "as.core" file under /usr/obj, but as is stripped, so there are no > debugging symbols or listing that I can provide. > > The strange thing is that I have been able to successfully build > XFree86, KDE, and many other ports on this system. I followed the > 4.x-to-5.0 upgrade directions to the letter about a month ago, and have > had no major problems before this. > > Any help would be greatly appreciated! > > -- > Paul A. Howes > > > > > Hardware > > Tyan S2099GNNR motherboard > Intel P4-2.4/533 > Crucial 512 MB PC2100 DIMM > Maxtor 20 GB hard drive. > > I see it is a P4, try adding options DISABLE_PSE and DISABLE_PG_G to your kernel. My 1.8G P4 do the same without them. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cc: Internal error: Illegal instruction (program as)
All, I am receiving some strange errors during a buildworld of 5.0-RELEASE-p2 from 5.0-RELEASE-p1. The location of where the failure varies, but the program that causes the failure is the same every time: "as". The errors are a variety of signal 10 and signal 4. I do find an "as.core" file under /usr/obj, but as is stripped, so there are no debugging symbols or listing that I can provide. The strange thing is that I have been able to successfully build XFree86, KDE, and many other ports on this system. I followed the 4.x-to-5.0 upgrade directions to the letter about a month ago, and have had no major problems before this. Any help would be greatly appreciated! -- Paul A. Howes Hardware Tyan S2099GNNR motherboard Intel P4-2.4/533 Crucial 512 MB PC2100 DIMM Maxtor 20 GB hard drive. dmesg Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-RELEASE-p1 #2: Thu Feb 13 08:39:59 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src-5.0/sys/HYDROGEN Preloaded elf kernel "/boot/kernel/kernel" at 0xc047. Preloaded userconfig_script "/boot/kernel.conf" at 0xc04700a8. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04700f8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 2430010060 Hz CPU: Pentium 4 (2430.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febfbff real memory = 536805376 (511 MB) avail memory = 516771840 (492 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled VESA: v2.0, 8128k memory, flags:0x0, mode table:0xc03b34a2 (122) VESA: ATI MACH64 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE31 Using $PIR table, 11 entries at 0xc00fdeb0 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe000-0xe3ff at device 0.0 o n pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 uhci0: port 0xd800-0xd81f irq 12 at device 29.0 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 uhci1: port 0xd000-0xd01f irq 5 at d evice 29.1 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd400-0xd41f irq 11 at device 29.2 on pci0 usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 pci2: at device 1.0 (no driver attached) ahc0: port 0xc400-0xc4ff mem 0xe6042000-0xe604 2fff irq 11 at device 4.0 on pci2 aic7880: Ultra Single Channel A, SCSI Id=6, 16/253 SCBs pci2: at device 8.0 (no driver attached) em0: port 0xcc00-0xcc3f mem 0xe602-0xe603,0xe600-0xe601 irq 12 at device 10.0 on pci2 em0: Speed:100 Mbps Duplex:Full isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0 x7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 31.3 (no driver attached) speaker0 port 0x61 on acpi0 fdc0: port 0x3f7,0x3f0-0 x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xd1000-0xd27ff,0xd-0xd07ff,0xc8000-0xc,0xc -0xc7fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to den y, logging disabled acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0% ad0: 19541MB [39703/16/63] at ata0-master UDMA66 ad1: 38172MB [77557/16/63] at ata0-slave UDMA100 acd0: CDROM at ata1-slave PIO3 Waiting 2 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 11) Mounting root from ufs:/dev/ad0s1a fxp0: p
Question about KLDs...
All, This may be a fairly elementary question, but I have not seen this addressed in the Handbook at all -- Which is the preferred method for using drivers: KLDs or compiling into the kernel? Are there some that work better one way than the other? Inquiring minds would like to know! :-) Thanks! -- Paul A. Howes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
A couple of 5.0-RELEASE bugs...
I think I may have found a few bugs in 5.0 that need to be addressed. The first problem is with GCC, which means it may not be FreeBSD-specific. I build world and kernel with the CPUTYPE flag set to "p4" in /etc/make.conf, then installed it. Everything seemed to work fine, except periodically "make" and "as" would crash: make with a signal 10 and as with a signal 11. There was no rhyme or reason to the timing. I could re-run the same compilation with no error the next time through. On a whim, I removed the CPUTYPE flag from make.conf and rebuilt/reinstalled binutils and cc. After that, everything seemed to work fine. Just to be safe, I rebuilt and installed both world and kernel without the "p4" modifier. The second problem is related to the "NOMANCOMPRESS" flag in make.conf. When installing the XFree86-4 port, I found that the "install" and "package" targets would stop with an error saying that they couldn't find gzip'd versions of the man pages. Of course that made sense when I specifically didn't want the man pages compressed! I think some of the scripts are not paying attention to that flag. If there's anything that I can do to help further investigate either of these, please let me know. -- Paul A. Howes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message