RE: RELENG_5 problems with Intel 855 (RELENG_4 boots fine) (solved!)
At 01:29 PM 01/04/2005, Gray Lilley wrote: Can you try setting hw.pci.enable_io_modes=0 at the loader prompt then booting? Thanks! That did the trick!! OK set hw.pci.enable_io_modes=0 OK boot /boot/kernel/acpi.ko text=0x41520 data=0x1da4+0x112c syms=[0x4+0x7630+0x4+0x9c97] KDB: debugger backends: ddb KDB: current backend: ddb 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-PRERELEASE #0: Fri Apr 1 09:06:22 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/nfs ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) M processor 1500MHz (1500.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x695 Stepping = 5 Features=0xa7e9fbbf real memory = 534642688 (509 MB) avail memory = 513507328 (489 MB) ioapic0 irqs 0-23 on motherboard npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 0.3 (no driver attached) pcib1: at device 1.0 on pci0 pci1: on pcib1 agp0: port 0xe300-0xe307 mem 0xed00-0xed07,0xe000-0xe7ff irq 16 at device 2.0 on pci0 agp0: detected 892k stolen memory agp0: aperture size is 128M pci0: at device 2.1 (no driver attached) pcib2: at device 30.0 on pci0 pci2: on pcib2 puc0: port 0xd300-0xd307,0xd200-0xd207 irq 16 at device 4.0 on pci2 sio4: on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode sio5: on puc0 sio5: type 16550A sio5: unable to activate interrupt in fast mode - using normal mode puc1: port 0xd500-0xd507,0xd400-0xd407 irq 16 at device 4.1 on pci2 sio6: on puc1 sio6: type 16550A sio6: unable to activate interrupt in fast mode - using normal mode sio7: on puc1 sio7: type 16550A sio7: unable to activate interrupt in fast mode - using normal mode pci2: at device 5.0 (no driver attached) twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0xd700-0xd70f mem 0xec00-0xec7f irq 18 at device 6.0 on pci2 twe0: 2 ports, Firmware FE7X 1.05.00.068, BIOS BE7X 1.08.00.048 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) acpi_tz0: on acpi0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 pmtimer0 on isa0 orm0: at iomem 0xd-0xd0fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ppc0: parallel port not found. Timecounter "TSC" frequency 1500059900 Hz quality 800 Timecounters tick every 10.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 3100 packets/entry by default ad0: 38166MB [77545/16/63] at ata0-master UDMA100 acd0: CDROM at ata1-master PIO4 twed0: on twe0 twed0: 76318MB (156299440 sectors) Mounting root from ufs:/dev/ad0s1a Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. kernel dumps on /dev/ad0s1b swapon: adding /dev/ad0s1b as swap device Starting file system checks: /dev/ad0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1a: clean, 331086 free (990 frags, 41262 blocks, 0.2% fragmentation) /dev/ad0s1e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1e: clean, 500291 free (203 frags, 62511 blocks, 0.0% fragmentation) /dev/ad0s1d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1d: clean, 6260810 free (48418 frags, 776549 blocks, 0.6% fragmentation) /dev/ad0s1f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s1f: clean, 9698700 free (252 frags, 1212306 blocks, 0.0% fragmentation) Setting hostname: nfs.sentex.ca. lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 Flushed all rules. 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 65000 allow ip from any to any Firewall rules loaded, starting divert daemons:. Firewall logging enabled net.inet.ip.fw.enable: 1 -> 1 Additional routing options:. Starting devd. Mounting NFS file systems:. Starting syslogd. Apr 1 12:07:52 nfs syslogd: kernel boot file is /boot/kernel/kernel ___ freebs
RELENG_5 problems with Intel 855 (RELENG_4 boots fine)
=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x3585, revid=0x02 bus=0, slot=0, func=3 class=08-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x3581, revid=0x02 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 3, range 32, base e000, size 27, enabled map[14]: type 1, range 32, base ed00, size 19, enabled map[18]: type 4, range 32, base e300, size 3, enabled pcib0: matched entry for 0.2.INTA pcib0: slot 2 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x3582, revid=0x02 bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=16 powerspec 1 supports D0 D1 D3 current D0 map[10]: type 3, range 32, base , size 27, memory disabled But RELENG_4 works fine. I think its getting hung up on the onboard NICs, not sure. However, I can load them as a KLD. If I disable the NICs in the BIOS, it still hangs on the same location FreeBSD 4.10-STABLE #1: Fri Nov 12 10:17:46 EST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/gas Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1500059328 Hz CPU: Intel(R) Celeron(R) M processor 1500MHz (1500.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x695 Stepping = 5 Features=0xa7e9fbbf real memory = 531496960 (519040K bytes) config> q avail memory = 513236992 (501208K bytes) Preloaded elf kernel "kernel" at 0xc03d5000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03d509c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 13 entries at 0xc00fde90 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xe800-0xebff at device 0.0 on pci0 pci0: (vendor=0x8086, dev=0x3584) at 0.1 pci0: (vendor=0x8086, dev=0x3585) at 0.3 pcib1: at device 1.0 on pci0 pci1: on pcib1 agp1: port 0xe300-0xe307 mem 0xec10-0xec17,0xe000-0xe7ff irq 10 at device 2.0 on pci0 agp1: detected 3964k stolen memory agp1: aperture size is 128M pci0: (vendor=0x8086, dev=0x3582) at 2.1 uhci0: port 0xe000-0xe01f irq 10 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 0xe100-0xe11f irq 9 at device 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 0xe200-0xe21f irq 7 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 29.7 irq 5 pcib2: at device 30.0 on pci0 pci2: on pcib2 pci2: (vendor=0x11ab, dev=0x4320) at 0.0 irq 11 pci2: (vendor=0x11ab, dev=0x4320) at 1.0 irq 15 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ichsmb0: port 0x5000-0x501f irq 12 at device 31.3 on pci0 smbus0: on ichsmb0 smb0: on smbus0 pci0: (vendor=0x8086, dev=0x24c5) at 31.5 irq 12 orm0: at iomem 0xd-0xd0fff,0xd1000-0xd1fff on isa0 pmtimer0 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default IPsec: Initialized Security Association Processing. ad0: 38166MB [77545/16/63] at ata0-master UDMA100 Mounting root from ufs:/dev/ad0s1a and if I do a kld load. skc0: port 0xd000-0xd0ff mem 0xec04-0xec043fff irq 11 at device 0.0 on pci2 skc0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter skc1: port 0xd100-0xd1ff mem 0xec044000-0xec047fff irq 15 at device 1.0 on pci2 skc1: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter sk0: on skc0 sk0: Ethernet address: 00:01:80:5c:0c:cd sk1: on skc1 sk1: Ethernet address: 00:01:80:5c:0c:cc miibus0: on sk0 e1000phy0: on miibus0 e1000phy0: 1000baseTX-FDX, 100baseTX-F
Re: USB device causes kernel panic
At 07:39 AM 01/04/2005, Gerrit Kühn wrote: Hi folks, I have a XS-Drive Pro VP300 (Vosonic) here which runs fine as USB1 device, but completely screws up my system when pluggeg into a USB2 port. I'm running (%:~)- uname -a FreeBSD arc.pmp.uni-hannover.de 5.3-STABLE FreeBSD 5.3-STABLE #2: Thu Dec 9 12:00:08 CET 2004 Hi, Try updating to the latest RELENG_5. There have been a lot of USB bug fixes since Dec. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RELENG_5 buildworld problems using MODULES_WITH_WORLD=true
With the following make.conf NOGAMES=true# do not build games (games/ subdir) MODULES_WITH_WORLD=true # build modules when building kernel NO_MODULES=true KERNCONF=test make buildworld dies at ... ===> sys/modules/arcnet rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/contrib/altq -I@/../include /usr/src/sys/modules/arcnet/../../net/if_arcsubr.c ===> sys/modules/arl rm -f .depend mkdep -f .depend -a -nostdinc -I/usr/src/sys/modules/arl/../.. -D_KERNEL -DKLD_MODULE -I- -I/usr/src/sys/modules/arl/../.. -I. -I@ -I@/contrib/altq -I@/../include /usr/src/sys/modules/arl/../../dev/arl/if_arl.c /usr/src/sys/modules/arl/../../dev/arl/if_arl_isa.c ===> sys/modules/asr rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/contrib/altq -I@/../include /usr/src/sys/modules/asr/../../dev/asr/asr.c /usr/src/sys/modules/asr/../../dev/asr/asr.c:140:21: opt_asr.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/asr. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. If I build the modules with the kernel, all is OK. I am guessing http://lists.freebsd.org/pipermail/cvs-all/2005-March/111998.html was what broke it. ---Mike ---- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gdbe based disk encryption
At 02:51 PM 22/03/2005, Tejas Kokje wrote: Is there a way GEOM based disk encryption can be used with FreeBSD 4.10 kernel ? According to handbook, gdbe only works for 5.3 release. Hi, There was a thread about this recently on the freebsd-hackers mailing list, and basically the answer is no. You will need to switch to the RELENG_5 series. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_5 and FAST_IPSEC limits
At 04:23 PM 15/03/2005, Sam Leffler wrote:
Mike Tancsa wrote:
Hi,
We are running into a case where there are too many SAs, and doing a
setkey -D would fail with a
"recv: Resource temporarily unavailable"
after displaying most of the associations.
Is there a way to get around this, or is there a hard limit ?
# setkey -D | grep ^172 | wc
186 3725096
When the remotes are renegotiating, and there are a lot of tunnels in the
state of mature and dying, this number can go up to 341, but not
higher. This also seems to send racoon into a hung state that we then
need to kill off and restart.
It was suggested in a post that /usr/src/sys/net/raw_cb.h get changed from
#define RAWSNDQ 8192
#define RAWRCVQ 8192
to something larger like
#define RAWSNDQ 24576
#define RAWRCVQ 24576
If this is the underlying issue, will it work on its own, or are there
other values that need to be tuned ? Will I need to recompile any
userland apps (e.g. racoon, setkey) and are there any other values I
would need to adjust
Looks like you're hitting the limit on returning status information
through a PF_KEY socket. FWIW this is not related to FAST_IPSEC; it's an
issue with PF_KEY and is common to both IPsec implementations.
Upping the raw socket buffer sizes should permit more information to be
returned but you may always exceed this limit as you can create more SA's
than can be reported in a single msg. Some groups have dealt with this by
changing the PF_KEY api, e.g. to report an incomplete msg so the user-mode
app can retrieve more data with additional reads. If upping the socket
buffer limits doesn't help then you might search for patches.
Hi and Thanks for the response! We will start by increasing the 2
values. Are there any potential negative side effects of doing so that we
need to be aware of ? i.e. anything else that would need to be changed as a
result ?
I am pretty sure racoon was getting hung up in pfkey.c in this loop
while (1) {
if (msg)
racoon_free(msg);
msg = pk_recv(s, &len);
if (msg == NULL) {
if (len < 0)
goto done;
else
continue;
}
if (msg->sadb_msg_type != SADB_DUMP || msg->sadb_msg_pid
!= pid)
continue;
ml = msg->sadb_msg_len << 3;
bl = buf ? buf->l : 0;
buf = vrealloc(buf, bl + ml);
if (buf == NULL) {
plog(LLV_ERROR, LOCATION, NULL,
"failed to reallocate buffer to dump.\n");
goto fail;
}
memcpy(buf->v + bl, msg, ml);
if (msg->sadb_msg_seq == 0)
break;
}
goto done;
Should have core dumped him at the time :( Oh well, thats what happens when
you do 5am maint! If we plan for the worst case scenario for msg size, I
guess this loop should not be an issue.
---Mike
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RELENG_5 and FAST_IPSEC limits
Hi, We are running into a case where there are too many SAs, and doing a setkey -D would fail with a "recv: Resource temporarily unavailable" after displaying most of the associations. Is there a way to get around this, or is there a hard limit ? # setkey -D | grep ^172 | wc 186 3725096 When the remotes are renegotiating, and there are a lot of tunnels in the state of mature and dying, this number can go up to 341, but not higher. This also seems to send racoon into a hung state that we then need to kill off and restart. It was suggested in a post that /usr/src/sys/net/raw_cb.h get changed from #define RAWSNDQ 8192 #define RAWRCVQ 8192 to something larger like #define RAWSNDQ 24576 #define RAWRCVQ 24576 If this is the underlying issue, will it work on its own, or are there other values that need to be tuned ? Will I need to recompile any userland apps (e.g. racoon, setkey) and are there any other values I would need to adjust ---Mike ---- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: re driver trobles (RELENG_5)
At 08:46 AM 10/03/2005, Dmitry Morozovsky wrote: whenever promisc mode turned on, renegotiating occurs, leading to 3 to 45 (depending on STP settings on the switch) network unavailability. Moreover, some other re(4) setting changes seem to disturb link state unneededly (such as ifconfig re0 -vlanhwtag) The em does this as well. Its most annoying when its connected to a switch with STP on it. Even when you alias the interface it does this :( ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld broken ?
At 02:19 PM 28/02/2005, David O'Brien wrote: On Mon, Feb 28, 2005 at 03:51:34PM +, Robert Watson wrote: > On Mon, 28 Feb 2005, Mike Tancsa wrote: > > /usr/src/lib/libkvm/kvm_proc.c > > /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': > > /usr/src/lib/libkvm/kvm_proc.c:269: warning: assignment makes integer from > > pointer without a cast > > /usr/src/lib/libkvm/kvm_proc.c:341: error: structure has no member named > > `p_runtime' > > I ran into this a few minutes ago also -- it looks like David merged the > kernel but not user space portions of a change to process time > measurement. I sent him an e-mail ping a few minutes ago -- if it isn't > fixed shortly, I'll see about getting it fixed myself. How come the tenderbox report sfor RELENG_5 don't go to this mailing list? I was watching this list while waiting for my own 'make world' to finish. (but then passed out) Perhaps it didnt pick up the changes ? I am not sure what it updates off of, but I noticed this morning my local cvsup server had problems for a couple of hours syncing up with cvsup.freebsd.org. des would be able to confirm. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
buildworld broken ?
2 different machines die in sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 bsdxml.h /usr/obj/usr/src/i386/usr/include ===> lib/libkvm rm -f .depend mkdep -f .depend -a-DLIBC_SCCS -I/usr/src/lib/libkvm /usr/src/lib/libkvm/kvm.c /usr/src/lib/libkvm/kvm_i386.c /usr/src/lib/libkvm/kvm_file.c /usr/src/lib/libkvm/kvm_getloadavg.c /usr/src/lib/libkvm/kvm_getswapinfo.c /usr/src/lib/libkvm/kvm_proc.c cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm.c cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_i386.c cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_file.c cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_getloadavg.c cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_getswapinfo.c cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm -c /usr/src/lib/libkvm/kvm_proc.c /usr/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist': /usr/src/lib/libkvm/kvm_proc.c:269: warning: assignment makes integer from pointer without a cast /usr/src/lib/libkvm/kvm_proc.c:341: error: structure has no member named `p_runtime' *** Error code 1 Stop in /usr/src/lib/libkvm. *** 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. [nfs]# Boring make.conf with PERL_VER=5.8.5 PERL_VERSION=5.8.5 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo KERNCONF=nfs NO_GAMES=true# do not build games (games/ subdir) #NO_MODULES= true# do not build modules with the kernel #MODULES_WITH_WORLD=true # do not build modules when building kernel IPFW2=TRUE ---- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA RAID Support
At 01:19 PM 24/02/2005, Dustin Wilhoit wrote: Trying using your browsers FIND command and search for SATA, There are several SATA Raid controllers supported by FreeBSD. Controllers supported by the aac(4) driver include: Dell CERC SATA RAID 2 The twa(4) driver supports the following PATA/SATA RAID controllers: AMCC's 3ware 9500S-4LP AMCC's 3ware 9500S-8 AMCC's 3ware 9500S-8MI AMCC's 3ware 9500S-12 AMCC's 3ware 9500S-12MI As well as the 3ware twe(4) driver supports the 8xxx series SATA RAID controllers. I have a number of these and they work REALLY well in RELENG_4 and RELENG_5. There are also management / monitoring tools for both the twa and twe based cards that do pretty well everything you would expect. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: supporting ICH6 SATA controller
At 07:34 PM 21/02/2005, Gipan Dhillon wrote: hello please help me. ok my computer has an sata hard drive on it. but the problem is i cant find the driver for it to install before installing XP my motherboards chipset is 915G my I/O controller is 82801 FB ICH6. now after days of searching i came up across this site where you had said this one seemed to get workign fine patch attatched. i cannot find the patch though. also by patch do you mean floppy files? please can you please help me get my computer to take my Sata Drive as SATA and not udma (ATA/100)??? Please help me RELENG_5 works with this controller / chipset for me. Perhaps try one of the recent RELENG_5 snapshots at ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/Feb_2005/5.3-STABLE-SNAP001-i386-miniinst.iso eg fxp0: port 0xd000-0xd03f mem 0xd000-0xdfff irq 10 at device 8.0 on pci1 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:01:80:57:29:a9 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.2 on pci0 # atacontrol cap 0 0 ATA channel 0, Master, device ad0: Protocol Serial ATA v1.0 device model ST3120026AS serial number 3JT1BSB2 firmware revision 3.18 cylinders 16383 heads 16 sectors/track 63 lba supported 234441648 sectors lba48 supported 234441648 sectors dma supported overlap not supported Feature Support EnableValue Vendor write cacheyes yes read ahead yes yes SATA NCQ no- 0/0x00 SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 65278/0xFEFE automatic acoustic management no no 0/0x00 254/0xFE ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FW: 5.3-Stable network issue
At 12:28 PM 11/02/2005, Martin Minkus wrote: Is there some coincidence that rl1 is at irq 11 and is the card that has problems? diablo:/usr/src# dmesg |grep 11 Timecounter "i8254" frequency 1193182 Hz quality 0 pci_cfgintr: 0:11 INTA BIOS irq 11 pci_cfgintr: 0:7 INTD routed to irq 11 rl1: port 0xe800-0xe8ff mem 0xd7001000-0xd70010ff irq 11 at device 11.0 on pci0 diablo:/usr/src# Hi, There were a couple of postings about the Realtek cards having "slowness" problems and such. Did you try the patch that was posted ? Index: if_rl.c === RCS file: /usr/store/mlaier/fcvs/src/sys/pci/if_rl.c,v retrieving revision 1.145 diff -u -r1.145 if_rl.c --- if_rl.c 9 Aug 2004 20:22:17 - 1.145 +++ if_rl.c 30 Jan 2005 18:24:23 - @@ -964,7 +964,7 @@ #endif ifp->if_capenable = ifp->if_capabilities; IFQ_SET_MAXLEN(&ifp->if_snd, IFQ_MAXLEN); - ifp->if_snd.ifq_drv_maxlen = IFQ_MAXLEN; + ifp->if_snd.ifq_drv_maxlen = 0; IFQ_SET_READY(&ifp->if_snd); callout_handle_init(&sc->rl_stat_ch); ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Server reboots when silo overflows - FreeBSD 4.11
At 12:37 AM 11/02/2005, Lefteris Tsintjelis wrote: > >sio5: 1 more silo overflow (total 7) > >puc0: port > >0xb000-0xb007,0xb400-0xb407,0xb800-0xb807,0xd000-0xd007 mem > >0xea80-0xea80003f irq 14 at device 12.0 on pci2 > >sio4: configured irq 14 not in bitmap of probed irqs 0x8000 > >sio4: type 16550A > >sio5: configured irq 14 not in bitmap of probed irqs 0x8000 > >sio5: type 16550A > > How do you have device sio configured in your kernel ? Are you trying to > specify the ports for the puc attached serial ports ? All you need is > > device sio > device puc device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 device sio2at isa? disable port IO_COM3 irq 5 device sio3at isa? disable port IO_COM4 irq 9 device puc No other sio specific devices for puc other than the kernel's default. The sio0/1 never gave me any trouble though. Its the sio4/5 (puc) that fail me. BTW this bug is old and run to it again about a year ago. > Also, enable crash dumps and build a debug kernel. I enabled the debug symbols already and I have a few crash dumps. What can do I do next? Take out the sio2 and sio3 definitions and just have device sio device puc leave sio0 and sio1 as is. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Server reboots when silo overflows - FreeBSD 4.11
At 11:42 AM 10/02/2005, Lefteris Tsintjelis wrote: Hi, There seems to be a serious problem with the puc device driver. When the driver expiriences overflows the server simply reboots! device puc options PUC_FASTINTR I have tried to rebuild a new kernel without the PUC_FASTINTR option but without much luck. It still keeps on rebooting right after a few silo overflow errors. puc0: port 0xb000-0xb007,0xb400-0xb407,0xb800-0xb807,0xd000-0xd007 mem 0xea80-0xea80003f irq 14 at device 12.0 on pci2 sio4: configured irq 14 not in bitmap of probed irqs 0x8000 sio4: type 16550A sio5: configured irq 14 not in bitmap of probed irqs 0x8000 sio5: type 16550A How do you have device sio configured in your kernel ? Are you trying to specify the ports for the puc attached serial ports ? All you need is device sio device puc Also, enable crash dumps and build a debug kernel. Add makeoptionsDEBUG=-g to your kernel config and at bootup time add dumpdev="/dev/da0s1b" # Device name to crashdump to (or NO). dumpdir="/var/crash"# Directory where crash dumps are to be stored Assuming your swap is on da0s1b ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: system panic
At 05:03 PM 26/01/2005, Vlad wrote: -- Syslog messages: Jan 26 13:55:53 delta kernel: pid 673 (httpd), uid 80: exited on signal 4 Jan 26 13:55:53 delta kernel: Jan 26 13:55:53 delta kernel: pid 673 (httpd), uid 80: exited on signal 4 Jan 26 13:55:57 delta kernel: pid 674 (httpd), uid 80: exited on signal 4 Jan 26 13:55:57 delta kernel: Jan 26 13:55:57 delta kernel: pid 674 (httpd), uid 80: exited on signal 4 Jan 26 13:56:05 delta kernel: pid 676 (httpd), uid 80: exited on signal 4 Did you compile your system with any particular CPU flags ? The signal 4 indicates an illegal instruction. e.g. if you compiled for i686, but are running on an older C3 that does not support all of the i686 instruction set. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Disabling write-behind on IDE drives, and SMART
At 04:39 PM 20/01/2005, Jim C. Nasby wrote: Question one: how do I disable write caching on IDE drives? I know the setting is hw.ata.wc=0, but where do I put that? In loader.conf? This is FreeBSD 4.10, btw. Yes, you can put it in there. Also, has any thought been given to making the default 0, like it is for SCSI devices? I'm honestly surprised and disappointed that the default is speed over data integrity. It has been discussed quite a bit before and for a number of reasons, the default on was chosen. (google if you want to see the various reasons) Question two: is there any support for SMART in FreeBSD? RELENG_5 with /usr/ports/sysutils/smartmontools/ works really well. But you need to move to RELENG_5. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bad disk or kernel (ATA Driver) problem?
At 04:13 PM 19/01/2005, Karl Denninger wrote: I'm having a lot of trouble believing this is an actual disk problem. Among other things, its happening at different places - not always at the same block. If you have the drives on a RELENG_5 box, try /usr/ports/sysutils/smartmontools/ Its quite handy to sort of various drive issues as well as to monitor for ongoing errors via the daemon. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFLAGS=-O2 -pipe problems in RELENG_5 ?
At 05:48 PM 17/01/2005, Kris Kennaway wrote: > > I let the box run over night building world 8 times with -j2 through -j5 > > and all worked just fine. > > Ok, that should put hardware out of the question. > > Sorry, no more ideas, besides getting rid of CPUTYPE as that is know to > cause problems. Well, not in general, but in certain isolated cases. Like I said before, switching back to -O makes the system stable once again. I let it run continuous buildworlds without issue for 24hrs along with burnP6, and memtest running in the background. No problem. The machine is still on the bench so if anyone wants me to try and debug it somehow I am happy to test. ---Mike ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFLAGS=-O2 -pipe problems in RELENG_5 ?
At 05:51 PM 13/01/2005, Ulrich Spoerlein wrote: On Wed, 12.01.2005 at 17:38:56 -0500, Mike Tancsa wrote: > I did a buildworld /buildkernel with a RELENG_5 box using the following > flags > > > CPUTYPE=i686 > KERNCONF=recycle > CFLAGS=-O2 -pipe > COPTFLAGS=-O2 -pipe > NO_MODULES=true# do not build modules with the kernel > MODULES_WITH_WORLD=true # do not build modules when building kernel I'm using -Os -pipe ever since installing 5.x after the gcc update. Haven't encountered any problem so far.. There are some differences between O2 and Os according to the man page. Are you using that on your kernel and for buildworld ? ICEs (internal compiler errors) usually point to serious hardware problems. Check that your RAM is OK and the CPU not overheating. heating is not an issue. I have changed the power supply and RAM just in case. Like I said, if I get rid of the O2 optimization and just use -O it works just fine. I have run into bad hardware where make buildworld exposes the problems, but I had never been able to "work around" it by changing to -O instead of O2. I let the box run over night building world 8 times with -j2 through -j5 and all worked just fine. Looking at /usr/src/UPDATING, it appears O2 does not work. However, that seems to contradict statements on the list that it works. 20040728: System compiler has been upgraded to GCC 3.4.2-pre. As with any major compiler upgrade, there are several issues to be aware of. GCC 3.4.x has broken C++ ABI compatibility with previous releases yet again and users will have to rebuild all their C++ programs with the new compiler. A new unit-at-a-time optimization mode, which is default in this compiler release, is more aggressive in removing unused static symbols. This is the likely cause of 'make buildworld' breakages with non-default CFLAGS where optimization level is set to -O2 or higher. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CFLAGS=-O2 -pipe problems in RELENG_5 ?
trfile/strfile.c
/usr/src/games/fortune/strfile/strfile.c: In function `add_offset':
/usr/src/games/fortune/strfile/strfile.c:344: internal compiler error: Bus
error
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
*** Error code 1
Stop in /usr/src/games/fortune/strfile.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
[ns4-new]#
If I change it back to just -O, it builds just fine. I thought RELENG_5
was supposed to be safe with -O2 ?
---Mike
Mike Tancsa, tel +1 519 651 3400
Sentex Communications,[EMAIL PROTECTED]
Providing Internet since 1994www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unstable 5.3 boxes
At 06:29 PM 05/01/2005, Mitch Parks wrote: It seems both my test and production boxes are not stable with 5.3-Release. I'm hoping for some insight in how to make at least the production box not crash. The crashes have been at different times of the day and I've found no suspicious log activity. At the moment it's been 9 days since the last crash, but it has also crashed in less than a day. ACPI and HT have always been enabled on this box without problems. I would update to RELENG_5 and disable in the BIOS HTT. HTT for the most part works against you with the current scheduler and seems to add more instability. But there have been quite a few fixes in RELENG_5 that you might benefit from. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Poor performance with 3Ware 7506LP RAID
At 06:53 AM 23/12/2004, Igor Robul wrote: Hello, we have performance problem with 3Ware 7506LP RAID5. For example if we execute rsync for large array of data, then 'systat -vmstat' shows 100% load on twed0, and many other processes wait disk I/O. Also, which SATA RAID controller would you recomend for Samba/Courier-IMAP server for company with 80 users? I think the 7xxx series is not so great for RAID5 speed wise. I know on our 7810, its lucky to get 15MB/s on block writes on 6 160G ST3160021A... I havent tested the 8xxx series in RAID5, but supposedly they are faster as is the 9000. But I dont know about the stability of the 9xxx series drivers (twe vs twa). If speed and reliability is what you want, look at RAID10. Our one mail server on RAID10 sees about 15-40 concurrent connections a second at peak times. With a lot of RAM and Maildir format, there is hardly any blocking going on. ---Mike ___ 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]"
CPUTYPE changes ? (RELENG_5)
I have in the past used CPUTYPE=i686 in /etc/make.conf But today, I am getting # make buildworld "Makefile.inc1", line 117: CPUTYPE global should be set with ?=. *** Error code 1 Stop in /usr/src. # This no longer seems to work. What is the correct syntax for this ? The rest is fairly generic CPUTYPE=i686 PERL_VER=5.8.5 PERL_VERSION=5.8.5 PERL_ARCH=mach NOPERL=yo NO_PERL=yo NO_PERL_WRAPPER=yo KERNCONF=west1 CFLAGS=-O -pipe COPTFLAGS=-O -pipe NO_MODULES=true# do not build modules with the kernel MODULES_WITH_WORLD=true # do not build modules when building kernel ---Mike ---- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: misc/74786: Smartlink Modem causes interrupt storm on RELENG_4 and RELENG_5
[cc'ing to FreeBSD-Stable] Hi, I know that the proposed patches I submitted are not the best patches, but given that the next release of RELENG_4 is coming out, would it not be better to commit those to RELENG_4 as they allow the modem to work when it shares an interrupt with another device ? The sio and interrupt handling code in RELENG_5 is different enough that I doubt the patches you are proposing would make it back to RELENG_4. This at least lets the modem work and prevents the machine from locking up in an interrupt storm on RELENG_4 without breaking any functionality (as far as I know). ---Mike At 02:22 AM 08/12/2004, Bruce Evans wrote: I think I understand this now. sio can indeed drive the interrupt (after you open an sio device, but not immediately at the end of the attach except in the serial console case). The main bugs are: 1. sio asks for exclusive access to the interrupt for no good reason (some buses like isa might only support exclusive accesses, but sio doesn't care). uhci gets access first in your configuration, so allocation of the interrupt resource fails. 2. Error handling for the failure in (1) is null, so both devices are "successfully" attached. 3. sio sets a flag to tell it to use polling if there is no interrupt resource, but it doesn't set the flag if the interrupt resource couldn't be allocated or if the interrupt couldn't be set up. 4. Upper layers provide negative help for debugging (3) using their own version of (3). They print "irq N" in boot messages if an interrupt resource justs exists. This doesn't mean that the device is using it. 5. Device interrupts are still enabled in polling mode. This depends on nothing else sucessfully setting up the (shared) interrupt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.3R crashing repeateadly
At 08:15 PM 08/12/2004, Cristóvão Dalla Costa wrote: I've disabled SMP with the kern.smp.disabled=1 sysctl and I'll see what happens next. Strangely though the kernel seems to think the system has only one cpu despite it being hyperthreaded: You want to turn HT off in the BIOS. The scheduler will not make use of it, and in fact will most likely hurt performance. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS-UP: RELENG_4 -> 4.11-PRERELEASE
At 09:59 AM 06/12/2004, Ken Smith wrote: If you are in a position to help with testing and/or debugging for the upcoming release by all means feel free to begin looking for things that need to be fixed. However if you are working with a system that OK, here is another bug that would be nice to get fixed. The problem is in both RELENG_4 and RELENG_5 http://www.freebsd.org/cgi/query-pr.cgi?pr=74821 I am sure the patches are very ugly looking, but it does fix the problem and it doesnt break default functionality. Without them, anyone using PPPoE against an ERX (most of Canada and a lot of Europe) will not always know if the link goes away. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS-UP: RELENG_4 -> 4.11-PRERELEASE
At 09:59 AM 06/12/2004, Ken Smith wrote: If you are in a position to help with testing and/or debugging for the upcoming release by all means feel free to begin looking for things that need to be fixed. Any chance someone can take a look at http://www.freebsd.org/cgi/query-pr.cgi?pr=74786 It hits RELENG_4 particularly hard, although RELENG_5 suffers the same problem. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: status of ehci(4) in 5.3-stable?
At 05:55 AM 16/11/2004, Marc "UBM" Bocklet wrote: Hiho! :-) What is the current status of ehci(4) in 5.3-stable, i.e. what are my chances that if I buy it will just or probably work? I think your chances would be better using a firewire adaptor and HD. On the Intel 865 boards I have tried with, USB 2.0 is pretty broken for me. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
crash on STABLE
object = 0x0
actcount = 0
vnodes_skipped = 0
maxlaunder = 32
s = 0
#9 0xc01d44fb in vm_pageout () at /usr/src/sys/vm/vm_pageout.c:1405
error = 0
s = 0
pass = 0
And from a few days ago with a slightly older kernel
(kgdb) bt
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487
#1 0xc014c868 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316
#2 0xc014cc9c in poweroff_wait (junk=0xc02312ec, howto=-107197) at
/usr/src/sys/kern/kern_shutdown.c:595
#3 0xc01fac3f in trap_fatal (frame=0xef83ce3c, eva=166771204) at
/usr/src/sys/i386/i386/trap.c:974
#4 0xc01fa8f9 in trap_pfault (frame=0xef83ce3c, usermode=0, eva=166771204)
at /usr/src/sys/i386/i386/trap.c:867
#5 0xc01fa4cf in trap (frame={tf_fs = 16, tf_es = -278724592, tf_ds =
-278724592, tf_edi = 135249920, tf_esi = 35,
tf_ebp = -276574588, tf_isp = -276574616, tf_ebx = -277882352,
tf_edx = 166771184, tf_ecx = 8968288, tf_eax = 515857,
tf_trapno = 12, tf_err = 0, tf_eip = -1071834672, tf_cs = 8,
tf_eflags = 66054, tf_esp = 0, tf_ss = -277126336})
at /usr/src/sys/i386/i386/trap.c:466
#6 0xc01d19d0 in vm_page_lookup (object=0xef6fda10, pindex=35) at
/usr/src/sys/vm/vm_page.c:515
#7 0xc01c9b4e in vm_fault (map=0xef7b6340, vaddr=135249920, fault_type=2
'\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:292
#8 0xc01fa88b in trap_pfault (frame=0xef83cfa8, usermode=1, eva=135252524)
at /usr/src/sys/i386/i386/trap.c:847
#9 0xc01fa3a3 in trap (frame={tf_fs = 673906735, tf_es = 673906735, tf_ds
= -1078001617, tf_edi = 135252524, tf_esi = 16,
tf_ebp = -1077950596, tf_isp = -276574252, tf_ebx = 135538448,
tf_edx = 4, tf_ecx = 4, tf_eax = 9, tf_trapno = 12,
tf_err = 7, tf_eip = 134877998, tf_cs = 31, tf_eflags = 66118,
tf_esp = -1077950636, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:377
#10 0x80a132e in ?? ()
#11 0x8069ff8 in ?? ()
#12 0x80646fc in ?? ()
#13 0x809a563 in ?? ()
#14 0x806e834 in ?? ()
#15 0x804c21a in ?? ()
(kgdb)
(kgdb) bt
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487
#1 0xc014c868 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316
#2 0xc014cc9c in poweroff_wait (junk=0xc022b140, howto=-1058224168) at
/usr/src/sys/kern/kern_shutdown.c:595
#3 0xc01d1875 in vm_page_insert (m=0xc0ecc7d8, object=0xef7ddb24,
pindex=31) at /usr/src/sys/vm/vm_page.c:375
#4 0xc01d1d54 in vm_page_alloc (object=0xef7ddb24, pindex=31, page_req=0)
at /usr/src/sys/vm/vm_page.c:845
#5 0xc01c9cb4 in vm_fault (map=0xef679140, vaddr=3217027072, fault_type=2
'\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:363
#6 0xc01fa88b in trap_pfault (frame=0xf14d7fa8, usermode=1,
eva=3217031156) at /usr/src/sys/i386/i386/trap.c:847
#7 0xc01fa3a3 in trap (frame={tf_fs = -1078001617, tf_es = 673906735,
tf_ds = -1078001617, tf_edi = 673963483,
tf_esi = 673963424, tf_ebp = -1077964400, tf_isp = -246579244,
tf_ebx = 673954988, tf_edx = 1, tf_ecx = 0,
tf_eax = -1077936144, tf_trapno = 12, tf_err = 7, tf_eip =
673590804, tf_cs = 31, tf_eflags = 66071, tf_esp = -1077964456,
tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:377
#8 0x28262e14 in ?? ()
#9 0x80514c4 in ?? ()
#10 0x805bb01 in ?? ()
#11 0x805a14e in ?? ()
#12 0x8059d87 in ?? ()
#13 0x809fa83 in ?? ()
#14 0x809de83 in ?? ()
#15 0x806e834 in ?? ()
#16 0x804c21a in ?? ()
(kgdb)
Mike Tancsa, tel +1 519 651 3400
Sentex Communications,[EMAIL PROTECTED]
Providing Internet since 1994www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3ware raid
At 04:30 PM 26/10/2004, Darren Pilgrim wrote: > Hello > > I was wandering if anybody out there has had any success using 3ware > 7506-8 cards with Freebsd 4.10. I was previously using a Promise > controller SX6000, and was having problems with this card. This is something of a FAQ. There's a long list of people using 3ware 6/7/8xxx series cards in FreeBSD 4.x boxes with great success. AFAIK that extends to 5.x as well. Yes, I am one who always seems to pipe up. I use this very card specifically on a busy pop3/imap server. The mail spool is made up of 4 drives in RAID10 and 2 other ports are used for the base OS in RAID1. Its been in service in this config for over a year without issue. When it comes time to replace bad drives, all has worked as expected for us. We dont use hot swap trays (dont really trust the electrical design of many of them), so we do it while powered down. Literally, shutdown, pull the bad drive, put in the new, go into the BIOS (or you can use the cmd line tools), add the new drive to the RAID set, exit out and let it boot and thats it. The controller rebuilds in the background and notifies you when done. There were at some point a bad batch of 7000 series cards that needed to be RMA'd (perhaps 2+ yrs ago now ?). But other than that one time hardware issue, they work great on all the platforms we have (i386 on FreeBSD, Linux, Win2k). We also use most of the other cards, except for the 9xxx series which we have no experience with yet. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: twe on 4.10 question
At 03:19 AM 22/10/2004, Sergey Shyman wrote: Does anybody use the following RAID controller on 4.10: 3ware Escalade 7006-2 IDE Raid controller Yes, we have numerous boxes deployed with various 3ware cards including that one. All our critical servers running FreeBSD, Linux and Win32 use these cards. Does it have any problems with stability/performance? It works VERY well for us in both respects on RELENG_4 and RELENG_5. It will be used in RAID1 (2 IDE drives) configuration on 4.10-RELEASE system (of course with latest patches). One note, the download info for their web management program (http://www.3ware.com/support/download.asp) implies its only available for the 8000 series card which is false, as it is in fact designed to work with the 7xxx and 8xxx cards. Although I havent run into disk compatibility issues, some people have issues with particular firmwares on certain Maxtor drives. I run mostly with Segate drives right now, but in the past have run Maxtor, quantum and Fujitsu, all without problems. YMMV ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Repeated panics... in the serial code ?
OK, I think
http://www.freebsd.org/cgi/query-pr.cgi?pr=72935
is the cause of this.
---Mike
At 02:14 AM 14/10/2004, Mike Tancsa wrote:
We have a number of RELENG_4 boxes that are dumping core with crash dumps
generally in the same place. Unfortunately, we are not sure just yet how
to repeat the dump and sometimes we do not get a full dump as the hardware
watchdog interrupts the dump process :(.
The boxes are running a 4 port PCI serial card (lava) but we have seen a
similar issue with a Titan serial card as well.
IdlePTD at physical address 0x003f5000
initial pcb at physical address 0x003493c0
panicstr: free: multiple frees
panic messages:
---
panic: free: multiple frees
syncing disks... 3
done
Uptime: 12d10h34m24s
dumping to dev #ad/0x20001, offset 1575040
dump ata0: resetting devices .. done
(kgdb) bt
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487
#1 0xc016926b in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316
#2 0xc0169690 in poweroff_wait (junk=0xc02d983f, howto=4) at
/usr/src/sys/kern/kern_shutdown.c:595
#3 0xc0164c87 in free (addr=0xc18f8880, type=0xc032d120) at
/usr/src/sys/kern/kern_malloc.c:385
#4 0xc018371e in cblock_free_cblocks (number=22) at
/usr/src/sys/kern/tty_subr.c:194
#5 0xc0183754 in clist_free_cblocks (clistp=0xc138fb38) at
/usr/src/sys/kern/tty_subr.c:208
#6 0xc017e89e in ttyclose (tp=0xc138fb00) at /usr/src/sys/kern/tty.c:247
#7 0xc02c67e9 in sioclose (dev=0xc11cc600, flag=7, mode=8192,
p=0xcbef8ee0) at /usr/src/sys/isa/sio.c:1669
#8 0xc01a2f78 in spec_close (ap=0xd56a7e44) at
/usr/src/sys/miscfs/specfs/spec_vnops.c:591
#9 0xc026a6d2 in ufsspec_close (ap=0xd56a7e44) at
/usr/src/sys/ufs/ufs/ufs_vnops.c:1854
#10 0xc026ac99 in ufs_vnoperatespec (ap=0xd56a7e44) at
/usr/src/sys/ufs/ufs/ufs_vnops.c:2394
#11 0xc019ea28 in vn_close (vp=0xd564a400, flags=7, cred=0xc0a36680,
p=0xcbef8ee0) at vnode_if.h:218
#12 0xc019f353 in vn_closefile (fp=0xc134a380, p=0xcbef8ee0) at
/usr/src/sys/kern/vfs_vnops.c:693
#13 0xc015ed2b in fdrop (fp=0xc134a380, p=0xcbef8ee0) at
/usr/src/sys/sys/file.h:218
#14 0xc015ec74 in closef (fp=0xc134a380, p=0xcbef8ee0) at
/usr/src/sys/kern/kern_descrip.c:1441
#15 0xc015ddab in close (p=0xcbef8ee0, uap=0xd56a7f80) at
/usr/src/sys/kern/kern_descrip.c:623
#16 0xc02b75f5 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds =
-1078001617, tf_edi = -1077937232, tf_esi = -1077936924,
tf_ebp = -1077939744, tf_isp = -714440748, tf_ebx = -1077939748,
tf_edx = -1077936924, tf_ecx = 5, tf_eax = 6,
tf_trapno = 7, tf_err = 2, tf_eip = 672039156, tf_cs = 31,
tf_eflags = 647, tf_esp = -1077939804, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1175
#17 0xc02ab915 in Xint0x80_syscall ()
#18 0x804a9bf in ?? ()
#19 0x8049412 in ?? ()
#20 0x8048fca in ?? ()
(kgdb) bt full
#0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487
error = 0
#1 0xc016926b in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316
howto = 256
#2 0xc0169690 in poweroff_wait (junk=0xc02d983f, howto=4) at
/usr/src/sys/kern/kern_shutdown.c:595
fmt = 0xc02d983f "free: multiple frees"
bootopt = 256
buf = "free: multiple frees", '\000'
#3 0xc0164c87 in free (addr=0xc18f8880, type=0xc032d120) at
/usr/src/sys/kern/kern_malloc.c:385
kbp = (struct kmembuckets *) 0xc02d983f
kup = (struct kmemusage *) 0xc0a19b2c
freep = (struct freelist *) 0xc18f8880
size = 128
s = 6493208
ksp = (struct malloc_type *) 0x100
#4 0xc018371e in cblock_free_cblocks (number=22) at
/usr/src/sys/kern/tty_subr.c:194
number = 22
i = 4
#5 0xc0183754 in clist_free_cblocks (clistp=0xc138fb38) at
/usr/src/sys/kern/tty_subr.c:208
clistp = (struct clist *) 0xc138fb38
#6 0xc017e89e in ttyclose (tp=0xc138fb00) at /usr/src/sys/kern/tty.c:247
tp = (struct tty *) 0xc138fb00
s = 6493208
#7 0xc02c67e9 in sioclose (dev=0xc11cc600, flag=7, mode=8192,
p=0xcbef8ee0) at /usr/src/sys/isa/sio.c:1669
com = (struct com_s *) 0xc11ce800
mynor = 0
s = 0
tp = (struct tty *) 0xc138fb00
#8 0xc01a2f78 in spec_close (ap=0xd56a7e44) at
/usr/src/sys/miscfs/specfs/spec_vnops.c:591
vp = (struct vnode *) 0xd564a400
p = (struct proc *) 0xcbef8ee0
dev = 0xc11cc600
#9 0xc026a6d2 in ufsspec_close (ap=0xd56a7e44) at
/usr/src/sys/ufs/ufs/ufs_vnops.c:1854
ap = (struct vop_close_args *) 0xd56a7e44
vp = (struct vnode *) 0x0
#10 0xc026ac99 in ufs_vnoperatespec (ap=0xd56a7e44) at
/usr/src/sys/ufs/ufs/ufs_vnops.c:2394
ap = (struct vop_generic_args *) 0x0
#11 0xc019ea28 in vn_close (vp=0xd564a400, flags=7, cred=0xc0a36680,
p=0xcbef8ee0) at vnode_if.h:218
rc = -1053514880
a = {a_desc = 0xc0321280, a_vp = 0xd564a400, a_fflag = 7, a_cred
= 0xc0a36680, a_p = 0xcbef8ee0}
vp = (struct vnode *) 0xd564a400
fflag = 0
cred = (struct ucred *) 0x0
Repeated panics... in the serial code ?
36924, tf_ecx = 5, tf_eax = 6, tf_trapno = 7, tf_err = 2, tf_eip = 672039156, tf_cs = 31, tf_eflags = 647, tf_esp = -1077939804, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1175 #17 0xc02ab915 in Xint0x80_syscall () cannot read proc at 0xcbef8ee0 (kgdb) Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.10-STABLE #5: Mon Sep 13 17:12:22 EDT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/gas Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 2400410264 Hz CPU: Intel(R) Celeron(R) CPU 2.40GHz (2400.41-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff real memory = 267321344 (261056K bytes) config> q avail memory = 256217088 (250212K bytes) Preloaded elf kernel "kernel" at 0xc03d6000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03d609c. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 8 entries at 0xc00fdee0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: port 0xd000-0xd007 mem 0xfa00-0xfa07,0xf000-0xf7ff irq 15 at device 2.0 on pci0 agp0: detected 892k stolen memory agp0: aperture size is 128M uhci0: port 0xc000-0xc01f irq 15 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 uhid0: APC Back-UPS ES 500 FW:801.e5.D USB FW:e5, rev 1.10/1.06, addr 2, iclass 3/0 uhci1: port 0xc400-0xc41f irq 5 at device 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 0xc800-0xc81f irq 10 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 uhci3: port 0xcc00-0xcc1f irq 15 at device 29.3 on pci0 usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pcib1: at device 30.0 on pci0 pci1: on pcib1 rl0: port 0xa000-0xa0ff mem 0xf900-0xf9ff irq 15 at device 4.0 on pci1 rl0: Ethernet address: 00:50:fc:ee:1b:34 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto puc0: port 0xa400-0xa407 irq 12 at device 5.0 on pci1 sio2: type 16550A fxp0: port 0xa800-0xa83f mem 0xf9001000-0xf9001fff irq 11 at device 8.0 on pci1 fxp0: Ethernet address 00:01:80:54:b5:65 inphy0: on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto puc1: port 0xb000-0xb007,0xac00-0xac07 irq 10 at device 10.0 on pci1 sio3: type 16550A sio4: type 16550A puc2: port 0xb800-0xb807,0xb400-0xb407 irq 10 at device 10.1 on pci1 sio5: type 16550A sio6: type 16550A isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ichsmb0: port 0x5000-0x501f irq 12 at device 31.3 on pci0 smbus0: on ichsmb0 smb0: on smbus0 orm0: at iomem 0xc-0xc9fff on isa0 pmtimer0 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold atkbdc0: at port 0x60,0x64 on isa0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry by default IPsec: Initialized Security Association Processing. ad0: 38166MB [77545/16/63] at ata0-master UDMA100 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Packet passing performance study on exotic hardware.
At 12:18 PM 08/10/2004, David Gilbert wrote: Idle_poll is default 1, I'm not positive we tested 0. I don't think there is much idle time here. Actually, on RELENG_5, I think the default is now zero. With a releng_5 BETA7 box in between 2 other hosts, with idle_poll set to the default on zero, using /usr/local/netperf/netperf -l 30 -H 10.10.10.1 -i 10,2 -I 99,10 -t UDP_STREAM -- -m 1000 -s 32768 32768 I see about 483Mb. If I set it to 1, I get just over 500Mb. This was with an HZ of 1000 ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Packet passing performance study on exotic hardware.
At 10:08 AM 08/10/2004, David Gilbert wrote: Right out of the box, FreeBSD 5.3 (with polling) passed about 200 kpps. net.isr.enable=1 increased that without polling to about 220 Did you have kern.polling.idle_poll at 0 or 1 ? In my tests a few weeks ago this seemed to make a difference, but the load avg gets messed up. Also, HZ does seem to make a difference at least in my tests on BETA5. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
panics after updating to RELENG_4 aug 25 from May 17th
e fdc0at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device ata options UFS_DIRHASH device atadisk # ATA disk drives options ATA_STATIC_ID #Static device numbering # Allow ncr to attach legacy NCR devices when # both sym and ncr are configured device twe # 3ware Escalade device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0at atkbdc? irq 12 device vga0at isa? device sc0 at isa? flags 0x100 device npx0at nexus? port IO_NPX irq 13 device sio0at isa? port IO_COM1 flags 0x10 irq 4 device ppc0at isa? irq 7 device ppbus # Parallel port bus (required) device ppi # Parallel port interface device device fxp # Intel EtherExpress PRO/100B (82557, 82558) device miibus # MII bus support device rl # RealTek 8129/8139 pseudo-device loop# Network loopback pseudo-device ether # Ethernet support pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gif 4 # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) pseudo-device bpf #Berkeley packet filter options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=1000 #limit verbosity options IPV6FIREWALL#firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPV6FIREWALL_VERBOSE_LIMIT=1000 options IPDIVERT#divert sockets options IPFW2 pseudo-device disc#Discard device (ds0, ds1, etc) Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1800036140 Hz CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1800.04-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febf9ff M> real memory = 1065287680 (1040320K bytes) config> q avail memory = 1033629696 (1009404K bytes) Preloaded elf kernel "kernel" at 0xc02bc000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02bc09c. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled Using $PIR table, 10 entries at 0xc00fde70 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 rl0: port 0xd000-0xd0ff mem 0xec00-0xecff irq 15 at device 8.0 on pci0 rl0: Ethernet address: 00:50:fc:5b:d5:4a miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0xe000-0xe00f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 orm0: at iomem 0xc-0xcbfff on isa0 pmtimer0 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 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 ppc0: parallel port not found. ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to deny, logging limited to 1000 packets/entry by default ad0: 57241MB [116301/16/63] at ata0-master UDMA100 Mounting root from ufs:/dev/ad0s1a ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.10-STABLE - ADSL PPPoE
At 10:25 PM 04/06/2004, Rafael R Obelheiro wrote: This is the culprit. I was having the same problem (PPPoE stopped working), but recompiling my system with the previous (1.2.2.14) of ng_ether.c solved it. Archie, is it possible to fix this (either by reverting the patch or by applying a new one)? Try recompiling mpd. Those patches broke binary compatibility. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Odd network issue ... *very* slow scp between two servers
At 12:48 PM 06/03/2004, Marc G. Fournier wrote: the fxp device is running: media: Ethernet autoselect (100baseTX ) the em device is running: media: Ethernet 100baseTX what does netstat -ni show on both machines for those NICs ? Is the switch managed ? If so, see if there are any errors. Also run the tests where there is little load going on. A load of 7 is going to impact something that needs cpu power (i.e. the ssh encryption) ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Testers needed: Joe's MFC of USB code
At 09:16 PM 25/02/2004, Julian Elischer wrote: Is anyone testing this.. Yes. I just applied it to a couple of boxes. We were able to panic the box previously with ucom devices. I will see if its fixed tomorrow at the office. ---Mike DO I have to commit it (it works for me) to get people to test it :-) As I mentionned it is required for USB 2.0 > > > julian > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD constantly crashing
Sig 11s can also be caused by plain old bugs. In this case, I suspect qmailadmin. I have seen it barf in similar circumstances where upgrading the OS causes it to get upset about something no longer being what it expects. As for your system crashes, thats something else. Have a look at the handbook about creating a debug kernel and what info to provide with respect to crash dumps. ---Mike At 01:43 AM 27/01/2004, Stanislav Grozev wrote: On Tue, Jan 27, 2004 at 01:58:44AM -0500, Marina Brown wrote: > The answer seems to be in your dmesg. > > pid 28555 (qmailadmin), uid 89: exited on signal 11 > > ...that means you have bad ram in your new computer. It's common > for computer stores to sell ram that is less than perfect. Replace the > ram and you should be fine. > It's not that - the RAM has been changed at least twice. And this particular version of qmailadmin is just buggy, it has crashed before on other machines also (some with Linux, some with FreeBSD). > Marina Brown > > -tacho ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: official 3ware support ?
At 01:55 PM 24/12/2003, Vinod Kashyap wrote: Yes, 3ware now supports FreeBSD! The driver you find on the 3ware website has been extensively tested on 4.8, and not yet on 4.9. Hi, I was just playing around with your beta driver on 4.9 STABLE. Am I safe to assume that if I dont have PAE enabled and have <=2G of RAM installed, the driver should work ? Also, will there be an updated 3dmd ? Thanks for officially supporting FreeBSD! ---Mike The changes in this driver should soon make their way into RELENG_4. They are already checked into HEAD. Thanks, Vinod. -Original Message- From: Mike Tancsa [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 24, 2003 8:48 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: official 3ware support ? While looking for firmware updates on the 3ware site, I notice they now have FreeBSD drivers available for download marked as "beta" The readme with the drivers download says, "This directory contains the 3ware driver (twe.ko) for 7000 series storage controllers, and the corresponding source code. The latest source code can be downloaded from the freebsd kernel tree, by running cvsup. The source code can be found at: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/modules/twe http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/twe " However, what is in RELENG_4 differs from what is downloaded from the 3ware site. Also, its marked 4.8. Will it work with 4.9 which has all the PAE changes in it? ---Mike -------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" DISCLAIMER: The information contained in this electronic mail transmission is intended by 3ware for the use of the named individual or entity to which it is directed and may contain information that is confidential or privileged and should not be disseminated without prior approval from 3ware ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
to hyperthread or not to hyperthread
We are replacing a box that is fairly busy with many different processes (sendmail / pop3). The new MB and CPU is hyperthreading capable. Is it worth it to enable this ? Does anyone have any real world experiences with it in RELENG_4 that say one way or the other to use or not use it ? dmesg shows, CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (2992.52-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs ---Mike ---- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
At 11:25 AM 24/11/2003, Michael Nottebrock wrote: > And for > sure its an ERX on the other end ? Actually it's an NRP - it seems Cisco does a better job with their PPPoE implementation. OK, thanks. The problem I see is only against an ERX. So either misconfigured ERX or something about Juniper's implementation. As the original poster was connecting against Frace Telecom and I to Bell Canada and given that VJ Header compression also does not play well with FreeBSD's I am leaning to the ERX. Back to the original question of how best to work around this. I will be deploying close to 100 boxes, most of which will talk to an ERX. It would be nice if I could avoid having to manually patch the boxes each time I do an update. If I work with my programmers here to come up with a patch, is there even a chance that someone would commit it to HEAD and then MFC it back to RELENG_4? Who is looking after PPP these days anyways ? ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
At 10:59 AM 24/11/2003, Michael Nottebrock wrote: On Monday 24 November 2003 16:46, Mike Tancsa wrote: > Are you sure you actually connect to an ERX on the other end, and its > actually negotiating LQR ? e.g. if you add LQM to the logging section, do > you see > tun0: LQM: deflink: Will send LQR every 10.00 secs > or do you see > tun0: LQM: deflink: LQR/ECHO LQR not negotiated Yes. LQM: deflink: Will send LQR every 30.00 secs I even found this way back in my ppp.log: Phase: deflink: ** Too many LQR packets lost ** So it's actually doing what it should. :) But is it doing that because its never hearing the LQR reply ? And for sure its an ERX on the other end ? ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
Are you sure you actually connect to an ERX on the other end, and its actually negotiating LQR ? e.g. if you add LQM to the logging section, do you see tun0: LQM: deflink: Will send LQR every 10.00 secs or do you see tun0: LQM: deflink: LQR/ECHO LQR not negotiated What do you have for your ppp.conf ? I have enable lqr accept lqr set lqrperiod 10 Like I said, its very possible the telco has the ERX misconfigured and yes, its impossible to get this level of detail out of them :-( ---Mike At 10:17 AM 24/11/2003, Michael Nottebrock wrote: On Monday 24 November 2003 15:32, Mike Tancsa wrote: > The problem is that LQR is agreed to with the ERX (the PPPoE terminating > device on the other end), but it never works. Works for me. I guess there really are many providers with misconfigured equipment out there. Actually, I know people who cannot use lqr although they're using the same provider as I do (but they 'dial in' to a different AC). Trying to actually get such an obscure technical thing through any big telco/provider hotline to someone who can actually understand what you want is pretty futile, too. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Expert input required: P4 odd signals, no apparent memory fault, DISABLE_PSE?
How recent is your copy of RELENG_4 ? The PSE disable code was committed to the tree already as well as a fix so it would work with APM on the 17th. By default it is disabled. If you look at your dmesg.boot you should see Warning: Pentium 4 CPU: PSE disabled ---Mike At 11:38 AM 20/10/2003, Jan Grant wrote: I'm tracking -STABLE on a 1.8GHz P4 with 512MB of memory. Roughly since the PAE changes were MFCed, I've been seeing memory-corruption-related errors under specific circumstances: for example, a run of portsdb -fUu can be guaranteed to generate SIGBUS, SIGILL and SIGSEGVs in a handful of sh, sed, etc. processes. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: latest stable won't boot on Dell Inspiron 8200
Try adding options NO_PSE_HACK options DISABLE_PSE It fixed it for me on my CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2393.93-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 Features=0xbfebfbff ---Mike At 04:16 PM 07/10/2003, Janet Sullivan wrote: I cvsup'd to today's stable, only to end up with a kernel that wouldn't boot all the way. It would freeze after printing out the line Mounting root from ufs:/dev/ad0s2a I backed up to stable from 2003.10.06.00.00.00, and my laptop now boots fine again. I'll try to to narrow this down further, but a recent commit seems to have broken stable for me, with either my custom kernel or GENERIC. My dmesg is below. Thanks. 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 4.9-RC #0: Tue Oct 7 12:54:27 MST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NAGI Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.70GHz (1695.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febf9ff real memory = 536748032 (524168K bytes) avail memory = 518496256 (506344K bytes) Preloaded elf kernel "kernel" at 0xc03b2000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 11 entries at 0xc00fbb90 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xe800-0xebff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 drm0: port 0xc000-0xc0ff mem 0xfcff-0xfcff,0xe000-0xe7ff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xe800 64MB info: [drm] Initialized radeon 1.8.0 20020828 on minor 0 uhci0: port 0xbf80-0xbf9f irq 11 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 0xbf20-0xbf3f irq 11 at device 29.2 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 pcib2: at device 30.0 on pci0 pci2: on pcib2 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xec80-0xecff mem 0xf8fffc00-0xf8fffc7f irq 11 at device 0.0 on pci2 xl0: Ethernet address: 00:06:5b:bb:69:96 miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto chip0: irq 11 at device 1.0 on pci2 chip1: irq 11 at device 1.1 on pci2 fwohci0: mem 0xf8ff8000-0xf8ffbfff,0xf8fff000-0xf8fff7ff irq 11 at device 1.2 on pci2 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channel is 4. fwohci0: EUI64 35:4f:c0:00:39:b1:c4:21 fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 if_fwe0: on firewire0 if_fwe0: Fake Ethernet address: 36:4f:c0:b1:c4:21 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) chip2: irq 11 at device 3.0 on pci2 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xbfa0-0xbfaf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 irq 0 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pcm0: port 0xdc80-0xdcbf,0xd800-0xd8ff irq 11 at device 31.5 on pci0 pcm0: pci0: (vendor=0x8086, dev=0x2486) at 31.6 irq 11 orm0: at iomem 0xc-0xc on isa0 pmtimer0 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A 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 lpt0: on ppbus0 lpt0: Interrupt-driven port IP Filter: v3.4.31 initialized. Default = block all, Logging = enabled ad0: 38154MB [77520/16/63] at ata0-master UDMA100 acd0: DVD-ROM at ata0-slave WDMA2 Mounting root from ufs:/dev/ad0s2a swapon: adding /dev/ad0s2b as swap device Automatic boot in progress... /dev/ad0s2a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s2a: clean, 23717 free (293 frags, 2928 blocks, 0.6% fragmentation) /dev/ad0s2e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s2e: clean, 14952 free (240 frags, 1839 blocks, 1.0% fragmentation) /dev/ad0s2g: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s2g: clean, 521477 free (18917 frags, 62820 blocks, 1.4% fragmentation) /dev/ad0s2f: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s2f: clean, 292396 free (252 frags, 365
Re: good address will not resolve in freebsd (_ in host names)
No, but like I said, more and more people are starting to use it. What is the big deal about _ vs - ? I am all for following convention, but sometimes it leads to the Judean Popular People's front vs the People's popular Front of Judea type stuff Also, as someone else pointed out, I think the RFC has changed since then. ---Mike At 02:35 PM 07/10/2003, Lowell Gilbert wrote: Mike Tancsa <[EMAIL PROTECTED]> writes: > More and more zones are starting to use _ in their host names (for > better or worse). Worse. >Has their been any discussion about making this > change in FreeBSD ? Have you tried it? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: good address will not resolve in freebsd (_ in host names)
More and more zones are starting to use _ in their host names (for better or worse). Has their been any discussion about making this change in FreeBSD ? ---Mike At 11:31 AM 07/10/2003, David Malone wrote: > It has to be in the resolver because windows pulls it from the same > NS's. You could edit: /usr/src/lib/libc/net/res_comp.c and look for the line that says: #define hyphenchar(c) ((c) == 0x2d) and replace that with: #define hyphenchar(c) ((c) == 0x2d || (c) == 0x5f) Then recompile and install libc cd /usr/src/lib/libc && make depend && make && make install David. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DMA related disc issues
At 04:42 PM 05/10/2003, moron wrote: Up until quite recently the machine has had a single drive in it and been performing flawlessly, no disk problems or anything of that nature (nothing untoward in messages, not spontaneous reboots, etc.). I have performed a few CVSups and make worlds over the last month to deal with security issues and such and about two weeks ago I added the second Seagate drive to the system. Shortly after adding the new drive (but also around the time of a CVSup), the Ok, it took me a while, but now I remember why this was dejavu. I saw the same thing on a similar setup. The one maxtor ata 133 was working fine. I added a slave, and all of a sudden errors on both. Not sure if its the maxtor or issue with ATA133. But I fixed the problem by forcing everything down to ATA100. I have this run at startup time /sbin/atacontrol mode 3 udma100 udma100 where 3 is the channel on which I have # atacontrol info 3 Master: ad6 ATA/ATAPI rev 6 Slave: ad7 ATA/ATAPI rev 6 and all has been happy for months. Also, double check that the jumpers are correctly set on all your IDE devices. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: "No route to host after certain time" is fxp only?
Hi, There was for sure an issue with the original patch. The latest revision cures the problem described by many below. ---Mike At 08:31 AM 28/09/2003, Administrator IPA wrote: Dear Mike. I saw the problem only on two machines: a SMP system with a Intel Ether Express/100 (fxp) running RELENG_5_1 and a older UP machine running RELENG_4_8, also equipted with a Intel EtherExpress/100. All other machines, either UP or SMP machines runninf RELENG_5_1 have em0 NICs (Intel EtherExpress/1000). They never showed up the reported problems until now. maybe it's a driver related problem? Hope this helps, sorry if it is boring ;-) Oliver On Wed, 24 Sep 2003, Mike Tancsa wrote: > > Not sure what the pattern is to trigger it. What is the output of > ifconfig -a > netstat -nra > > on the problem machine ? On my test machine in the back its been up for > 3hrs without issue. > > ---Mike > > > At 04:33 PM 24/09/2003, Jeff Love wrote: > >Is this happening only with fxp (intel) network cards? I run them, and > >have only seen this problem detailed regarding fxp cards thus far on this list. > > > >Any idea if there is a fix forthcoming? > > > >Jeff Love > >Burgh Gaming > > > >Jeff Love wrote: > > > >>Just wanted to note that this problem seems to not be isolated. > >>I'm seeing similar problems with RELENG_4_8 cvsup dated 00:24 09/23/03 > >>eastern US time. Machine loses routing, reboot brings things to normal > >>for a few hours. > >>I'm not going to implement the ARP security patch on any of my other > >>boxen just yet. > > > > > >___ > >[EMAIL PROTECTED] mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [full build as of Sept. 24] "No route to host" after certain time...
If you have all the aliases on lo0 does it work ? i.e. just have x.y.z.33 on fxp0. However, another poster had a problem with a /20 subnet. I wonder if its an incorrect mask calculation ? ---Mike At 12:05 PM 24/09/2003, Pawel Malachowski wrote: There are: x.y.z/24 with one IP address, x.y.z.1 is the default route. a.b.c.0/27 and a.b.c.32/28 with aliased addresses. fxp0: flags=8843 mtu 1500 inet x.y.z.33 netmask 0xff00 broadcast x.y.z.255 inet a.b.c.34 netmask 0xfff0 broadcast a.b.c.47 inet a.b.c.27 netmask 0xffe0 broadcast a.b.c.31 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff00 inet a.b.c.35 netmask 0x inet a.b.c.36 netmask 0x inet a.b.c.37 netmask 0x inet a.b.c.28 netmask 0x inet a.b.c.29 netmask 0x Internet: DestinationGatewayFlagsRefs Use Netif Expire a.b.c.28 a.b.c.28 UH 00lo0 a.b.c.29 a.b.c.29 UH 00lo0 a.b.c.35 a.b.c.35 UH 00lo0 a.b.c.36 a.b.c.36 UH 00lo0 a.b.c.37 a.b.c.37 UH 00lo0 127.0.0.1 127.0.0.1 UH 00lo0 x.y.z link#1 UC 10 fxp0 x.y.z.54 00:01:02:03:04:05 UHLW1 506 fxp0 1123 Of course I can also see in logs messages like: /kernel: arplookup a.b.c.1 failed: host is not on local network -- Pawe³ Ma³achowski ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [full build as of Sept. 24] "No route to host" after certain time...
Hi, can you clarify that
My rc.local script is something like:
LAN0=fxp0
IP=192.168.x.y
ifconfig ${LAN0} inet add ${IP}/24
route add default 192.168.x.1
ifconfig ${LAN0} inet add ${A}/28
ifconfig ${LAN0} inet add ${B}/32
ifconfig ${LAN0} inet add ${C}/32
ifconfig ${LAN0} inet add ${D}/32
# A, B, C, D are from the same /28 and everything worked perfectly in the past
are all out of the original /24 on LAN0 ?
---Mike
At 11:34 AM 24/09/2003, Pawel Malachowski wrote:
On Wed, Sep 24, 2003 at 11:16:07AM -0400, Mike Tancsa wrote:
> What if you alias those IP address to lo0 ? Does it correct the problem ?
I've moved all /32 addresses from fxp0 to lo0, it doesn't fix the problem.
After first reboot route table was complete, however after second reboot
default route and one local route were not present.
--
Pawe³ Ma³achowski
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvs commit: src/contrib/sendmail/src version.c
Thanks! ---Mike At 05:19 PM 19/09/2003, Gregory Neil Shapiro wrote: gshapiro2003/09/19 14:19:36 PDT FreeBSD src repository Modified files:(Branch: RELENG_4) contrib/sendmail/src version.c Log: Include a patch number in the version header in case 8.12.10 isn't MFC'ed before 4.9-RELEASE. 8.12.10 will be imported into -CURRENT this weekend. Approved by:re (murray) Revision ChangesPath 1.1.1.3.2.16 +1 -1 src/contrib/sendmail/src/version.c ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Release Engineering Status Report
I was directly experiencing the problems with the PAE commits. Since tegge's commits I have not had those panics. And for the record I was never upset :-) ---Mike At 12:30 PM 16/09/2003, Scott Long wrote: Ok, thanks for the update. Since it is 17 days after Aug 30 and people are still upset, the status was very unclear to the Release Engineering Team. So I guess we ened to solicit updates from the people who were directly experiencing problems, and ask for everyone else to test it as much as possible. Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic, AGAIN!
At 08:51 PM 29/08/2003 -0300, wrote: Hi all, recently i ordered an email here for list speaking that my server had given crash. Hi, There is a more extensive patch by [EMAIL PROTECTED] that fixes a few more bugs. See the message http://docs.freebsd.org/cgi/getmsg.cgi?fetch=682689+0+current/freebsd-stable Date: Thu, 28 Aug 2003 20:20:11 + (GMT) From: Tor Egge <[EMAIL PROTECTED]> Subject: Re: Ok, are all the panics fixed now? I am running it on 3 machines right now. A couple of busy mail servers and a very busy webserver (AMD SMP XP) ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ok, are all the panics fixed now?
At 11:42 PM 27/08/2003 +0400, Maxim Konovalov wrote: It's simple: we need to backout all these untested MFCs. I dont think people throw in untested MFCs into STABLE. They do their best effort and with that, there will still be some bugs. Its that simple. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ok, are all the panics fixed now?
At 01:34 PM 27/08/2003 -0500, Mike Silbersack wrote: Ok, I booted with hw.physmem="16M", and a buildworld paniced with "free/cache page dirty". (I was taking a nap at the time the buildworld crashed, we'll talk about that soon.) (Are you guys running with INVARIANTS?) Nope, I am not. Should I be ? ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kernel panic: vm_page_remove
At 01:46 PM 26/08/2003 -0300, Vitor de Matos Carvalho wrote: Hi, I have a machine Athlon XP2000+ with 512MB DDR, and a HD SCSI to be serving of proxy, running only squid. It was functioning normally, when he gave the following message to me of error in/var/log/messages: Aug 26 11:31:03 < kern.crit > bolter/kernel: panic: vm_page_remove(): page not found in hash I was seeing the same type of panic. There was a commit made early this morning to /usr/src/sys/i386/i386/pmap.c that fixed this for me. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is rl broken?
At 05:47 PM 20/08/2003 +0200, Marco Trentini wrote: There were 2 commits to stable for the rl driver. The commit logs show My guess is you got the first commit, but not the second. rm -R'ing your src tree probably didnt do anything. It was the re-cvsup later which downloaded the second commit that fixed your problem. In general, I find that if I am tracking stable, its important to watch the cvs-commit mailing list. I don't think which the problem is that. http://www.freebsd.org/cgi/query-pr.cgi?pr=55727 Perhaps, but for some it is. It does seem that for people with the dlink branded cards there are still problems. But for me, the second commit fixed my problem with [EMAIL PROTECTED]:0:0: class=0x02 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/8130) Fast Ethernet Adapter' class= network subclass = ethernet ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvs commit: src/sys/dev/twe twe.c twe_compat.h twe_freebsd.c twe_tables.h tweio.h twereg.h twevar.h
What version of the firmware did you test with ? We have a few remote boxes so its good this extra stop gap is there as it would have led to a nasty surprise :-( When you figure this would be MFC'd ? For example, FreeBSD's RE's build box here has Monitor version: ME7X 1.01.00.034 Firmware version: FE7X 1.04.00.024 BIOS version: BE7X 1.07.02.008 PCB version: Rev3 Achip version: V3.20 Pchip version: V1.30 Model: 7210 Unit count: 1 Will this box blow up if a cvsup was done today and the new drivers were run ? ---Mike At 01:11 AM 11/08/2003 -0700, Paul Saab wrote: The latest firmware will be needed to use the 3ware management utilities and unfortunately there is no way to do this online. You will have to flash the controller using a floppy booting into DOS. I just put in changes to the API today which will stop the API from even being used unless it is with the latest driver. Bad mojo will happen if the the API were allowed to be run on older drivers. --On Sunday, August 10, 2003 8:54 PM -0400 Mike Tancsa <[EMAIL PROTECTED]> wrote: Hi, Thank you for your work on this card! I have quite a few boxes that run various 3wares cards with diverse firmware revs. Are there any caveats with respect to models and firmware versions in terms of how they might interact ? ---Mike At 01:25 PM 10/08/2003 -0700, Paul Saab wrote: ps 2003/08/10 13:25:46 PDT FreeBSD src repository Modified files:(Branch: RELENG_4) sys/dev/twe twe.c twe_compat.h twe_freebsd.c twe_tables.h tweio.h twereg.h twevar.h Log: MFC: Support for the 3ware API Revision ChangesPath 1.1.2.7 +92 -59src/sys/dev/twe/twe.c 1.1.2.4 +4 -1 src/sys/dev/twe/twe_compat.h 1.2.2.6 +77 -33src/sys/dev/twe/twe_freebsd.c 1.1.2.3 +3 -0 src/sys/dev/twe/twe_tables.h 1.1.2.3 +10 -0 src/sys/dev/twe/tweio.h 1.1.2.5 +1 -1 src/sys/dev/twe/twereg.h 1.1.2.5 +3 -1 src/sys/dev/twe/twevar.h ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: malloc does not return null when out of memory
At 08:15 PM 7/23/2003 -0700, Kris Kennaway wrote: On Wed, Jul 23, 2003 at 01:34:27PM -0400, Gabor wrote: > Here is the tail end of the output. It dies when trying to poke at > the memory using memset. If I just malloc without the memset, it > never even dies. Ah, the annual "memory overcommit" thread. I thought we were overdue for one. But why does the man page for malloc (3) say, If malloc() fails, a NULL pointer is returned. ---Mike -------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvs commit: src/sys/netipsec ipsec.c key.c
Hi all, I have been seeing memory allocation errors on a few FreeBSD boxes
running IPSEC. Does anyone know if the commit below addresses such a
problem ? Or is this a racoon issue ? I did a search on google and have
not seen anyone else mention this particular issue.
Jul 14 00:57:57 d1terA9 racoon: ERROR: pfkey.c:210:pfkey_handler():
pfkey ADD failed: Cannot allocate memory
The code appears to be
/* validity check */
if (msg->sadb_msg_errno) {
int pri;
/* when SPD is empty, treat the state as no error. */
if (msg->sadb_msg_type == SADB_X_SPDDUMP &&
msg->sadb_msg_errno == ENOENT)
pri = LLV_DEBUG;
else
pri = LLV_ERROR;
plog(pri, LOCATION, NULL,
"pfkey %s failed: %s\n",
s_pfkey_type(msg->sadb_msg_type),
strerror(msg->sadb_msg_errno));
goto end;
}
---Mike
At 06:38 PM 30/06/2003 -0700, Sam Leffler wrote:
sam 2003/06/30 18:38:13 PDT
FreeBSD src repository
Modified files:(Branch: RELENG_4)
sys/netipsec ipsec.c key.c
Log:
MFC: plug xform memory leaks
Revision ChangesPath
1.2.2.2 +2 -0 src/sys/netipsec/ipsec.c
1.3.2.2 +13 -2 src/sys/netipsec/key.c
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4.9R bug fix ?
Any chance someone can look at / commit the fix in PR 52349 before 4.9R ? Its a simple fix. As it is to netstat, I dont know of anyone who 'owns' that program to bug other than to make a general plea :-) ---Mike ---- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Zsh fork bomb paniced my kernel.
Yes and no. It seems that if certain resources get starved bad things will
happen. The OS will let you shoot yourself in the foot afterall. You can
protect yourself from yourself by adjusting the defaults in /etc/login.conf.
---Mike
At 05:55 PM 20/06/2003 +0200, William Fletcher wrote:
Hi,
My machine just bombed when I did the following stupid command.
:(){:|:};:
Zsh chewed up everything on the machine...
I ran it knowing I'd probably have to reboot.
But, I hardly expected it to panic.
Or, was that normal?
Anyway, the following is some detail...
Please mail me if there is more I'm ment to do.
Thanks in advance :)
[EMAIL PROTECTED]:~ %> uname -a
FreeBSD tulip.epweb.co.za 4.8-STABLE FreeBSD 4.8-STABLE #0: Wed Jun 11
10:09:55
SAST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/TULIP i386
Panic message:
IdlePTD at phsyical address 0x0042a000
initial pcb at physical address 0x0036e460
panicstr: vm_map_entry_create: kernel resources exhausted
initial pcb at physical address 0x0036e460
panicstr: vm_map_entry_create: kernel resources exhausted
panic messages:
---
panic: vm_map_entry_create: kernel resources exhausted
syncing disks... 2 2
done
Uptime: 7d7h13m45s
(kgdb) where
#0 0xc01682aa in dumpsys ()
#1 0xc016807b in boot ()
#2 0xc01684a0 in poweroff_wait ()
#3 0xc02553f0 in vm_map_entry_create ()
#4 0xc02555e9 in vm_map_insert ()
#5 0xc0255810 in vm_map_find ()
#6 0xc0178cfb in pipespace ()
#7 0xc0178dd2 in pipe_create ()
#8 0xc0178b54 in pipe ()
#9 0xc02c21f5 in syscall2 ()
#10 0xc02b3875 in Xint0x80_syscall ()
#11 0x28081e1f in ?? ()
#12 0x2808135b in ?? ()
#13 0x28080deb in ?? ()
#14 0x28080b6e in ?? ()
#15 0x28086b39 in ?? ()
#16 0x28086964 in ?? ()
#17 0x280863fc in ?? ()
#18 0x2808458a in ?? ()
#19 0x28081e1f in ?? ()
#20 0x2808135b in ?? ()
#21 0x28080deb in ?? ()
#22 0x28080b6e in ?? ()
#23 0x28086b39 in ?? ()
---Type to continue, or q to quit---
#24 0x28086964 in ?? ()
#25 0x280863fc in ?? ()
#26 0x2808458a in ?? ()
#27 0x28081e1f in ?? ()
#28 0x2808135b in ?? ()
#29 0x28080deb in ?? ()
#30 0x28080b6e in ?? ()
#31 0x28086b39 in ?? ()
#32 0x28086964 in ?? ()
#33 0x280863fc in ?? ()
#34 0x2808458a in ?? ()
#35 0x28081e1f in ?? ()
#36 0x2808135b in ?? ()
#37 0x28080deb in ?? ()
#38 0x28080b6e in ?? ()
#39 0x28086b39 in ?? ()
#40 0x28086964 in ?? ()
#41 0x280863fc in ?? ()
#42 0x2808458a in ?? ()
Cannot access memory at address 0xbfbfd040.
--
William Fletcher (ultraviolet)Powered by
http://www.FreeBSD.org/
IT Administrator, EPWeb networks.
http://www.epweb.co.za/
Tel: +27 (041) 395 6800
Fax: +27 (041) 395 6818
Support: [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: state of ide raid
At 02:34 PM 16/06/2003 -0400, Charles Sprickman wrote: I'll second that. I have the 3ware two port model and it seems to have "burped" and decided one of the disks was dead. I went to the management interface (web-only) and removed/added the "bad" drive and then rebuilt the mirror. Performance was fine during the rebuild. Now why the one drive went "bad" is a question I cannot answer... Supposedly the newest firmware supports SMART, but I don't think the FreeBSD driver nor the 3ware web interface do anything with that data. It does for me. Here is an example warning I get on bad drives. It also logs it to kern via syslog. SMART Threshold Exceeded condition detected on port 1 on controller ID:0. Check drive for media errors. (0xf) This was from a bad Fujitsu. ---Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.7-stable / crash
Do you have Plug and Play enabled in the BIOS ? If so turn it off and try a PCI config reset if that is available in your BIOS. Also, try and get the fxp0 card and the SCSI controller on a different IRQ. I have found they dont always play well together. If they are in a slot that has a shared IRQ, separate them for sure. ---Mike At 05:16 PM 10/03/2003 -0800, Mike Hoskins wrote: I had -stable crash this AM on a Dell Poweredge 1550... FreeBSD fubar.adept.org 4.7-STABLE FreeBSD 4.7-STABLE #6: Thu Feb 13 19:14:26 PST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FUBAR i386 Now I'm trying to determine exactly what happened. The only thing I have to go on are the following entries in messages around the time it happened: Mar 10 04:10:22 fubar /kernel: fxp0: SCB timeout: 0x80 0x0 0x50 0x0 Mar 10 04:10:23 fubar /kernel: fxp0: SCB timeout: 0x80 0x0 0x50 0x0 Mar 10 04:10:24 fubar /kernel: fxp0: SCB timeout: 0x10 0x0 0x50 0x0 Mar 10 04:10:41 fubar /kernel: fxp0: SCB timeout: 0x70 0x0 0x50 0x0 Mar 10 04:12:13 fubar /kernel: fxp0: device timeout Mar 10 04:12:13 fubar /kernel: fxp0: DMA timeout I haven't seen this on my machines before, but have seen it mentioned here and in the archives. I'm cvsuping now; Anything else that may be to blame? If you're curious, the full dmesg.boot, pciconf -lv and all related messages are online, http://www.adept.org/pub/fubar Should the cvsup make things better, or worse? :) -mrh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Still seeing SMP panics on a older dual PIII (with debug kernel and crash dumps)
At 10:45 AM 06/03/2003 -0500, Michael L. Squires wrote: > Its an older dual PIII. Can anyone tell me if the dumps point to a > hardware issue, or if its crashing in the same spot each time ? I can blast > it with buildworlds and it never dies. Generally I have yet to find bad > hardware that could pass that But always a first time. I have a P6DGH with two PII/300's running 4.8-RC2; mptable crashes with a "HOSED" error message for the extended table (indicative of a BIOS problems) but no crashes. A BIOS problem ? In what way ? ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FreeBSD Security Advisory FreeBSD-SA-03:04.sendmail
At 09:11 AM 03/03/2003 -0800, FreeBSD Security Advisories wrote: Module: contrib_sendmail Announced: 2003-03-03 Credits:Mark Dowd (ISS) Affects:All releases prior to 4.8-RELEASE and 5.0-RELEASE-p4 FreeBSD 4-STABLE prior to the correction date Corrected: 2003-03-03 1) Upgrade your vulnerable system to 4-STABLE; or to the RELENG_5_0, Hi, I dont see this in the cvsup commit logs yet ? ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: OpenSSL-related problem
apache13-modssl depends on this port. I take it this no longer the case ? ---Mike At 08:31 AM 24/02/2003 -0600, Jacques A. Vidrine wrote: You have the OpenSSL port installed. Remove it. Cheers, -- Jacques A. Vidrine <[EMAIL PROTECTED]> http://www.celabo.org/ NTT/Verio SME . FreeBSD UNIX . Heimdal Kerberos [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SMP problems post Jan 28th
Same panic as the night before. Are there any hints in the panic message as to what the problem might be ? ---Mike Fatal trap 12: page fault while in kernel mode mp_lock = 0102; cpuid = 1; lapic.id = fault virtual address = 0x20004 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0174830 stack pointer = 0x10:0xddf08c4c frame pointer = 0x10:0xddf08c58 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 32437 (find) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 0102; cpuid = 1; lapic.id = boot() called on cpu#1 syncing disks... 4 1 done Uptime: 23h58m34s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#1 cpu_reset: Stopping other CPUs cpu_reset: Restarting BSP cpu_reset_proxy: Grabbed mp lock cfpu_ rBeSsPet: BSP did not grab mp lock Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 629kB/785396kB available memory At 06:48 AM 2/11/2003 -0500, Mike Tancsa wrote: The previous kernel had been running fine for some time, and now at night around the running of periodic, the box will 'periodically' crash. It does not seem to do it each night, but almost every other night and always just after 3am when periodic runs. I can never get a crash dump, and I had to hook up a serial console to capture this at night. Also, I cant seem to force the issue by running periodic by hand. But, like I said, it always seems to happen a few minutes after 3am. (No, nothing else is scheduled to run then and no other boxes do anything to it at that time either) Fatal trap 12: page fault while in kernel mode mp_lock = 0102; cpuid = 1; lapic.id = fault virtual address = 0x65b046a5 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0174830 stack pointer = 0x10:0xde174c4c frame pointer = 0x10:0xde174c58 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 4203 (find) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 0102; cpuid = 1; lapic.id = boot() called on cpu#1 syncing disks... 4 2 done Uptime: 1d15h8m8s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#1 cpu_reset: Stopping other CPUs cpu_reset: Restarting BSP tpu_reset_proxy: Grabbed mp lock cfpour_reSsPe : BSP did not grab mp lock Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 629kB/785396kB available memory Any ideas how best to track this down ? There seem to been some commits on the 30th that might have had an effect. 4.7-STABLE FreeBSD 4.7-STABLE #0: Thu Feb 6 06:04:02 EST 2003 ns4# 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 4.7-STABLE #0: Thu Feb 6 06:04:02 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/smp Timecounter "i8254" frequency 1193182 Hz CPU: Intel Pentium III (801.82-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 805294080 (786420K bytes) config> q avail memory = 779272192 (761008K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 17 -> irq 11 IOAPIC #0 intpin 18 -> irq 10 IOAPIC #0 intpin 19 -> irq 12 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc03b5000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03b509c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 6 entries at 0xc00f0d20 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xb800-0xb80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0xe800-0xe80f at device 4.3 on pci0 fxp0: port 0xb000-0xb03f mem 0xe380-0xe38f,0xe400-0xe4000fff irq 12 at device 9.0 on pci0 fxp0: Ethernet address 00:02:b3:07:fd:8d inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX
SMP problems post Jan 28th
4 relaying (translation) pseudo-device bpf #Berkeley packet filter options IPFW2 options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=34100 #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default options IPV6FIREWALL#firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPV6FIREWALL_VERBOSE_LIMIT=100 options IPV6FIREWALL_DEFAULT_TO_ACCEPT options DUMMYNET options IPDIVERT#divert sockets options NETGRAPH#netgraph(4) system options NETGRAPH_ASYNC options NETGRAPH_BPF options NETGRAPH_ECHO options NETGRAPH_ETHER options NETGRAPH_HOLE options NETGRAPH_IFACE options NETGRAPH_KSOCKET options NETGRAPH_L2TP options NETGRAPH_LMI options NETGRAPH_MPPC_ENCRYPTION options NETGRAPH_ONE2MANY options NETGRAPH_PPP options NETGRAPH_PPPOE options NETGRAPH_PPTPGRE options NETGRAPH_RFC1490 options NETGRAPH_SOCKET options NETGRAPH_TEE options NETGRAPH_TTY options NETGRAPH_UI options NETGRAPH_VJC Mike Tancsa, tel +1 519 651 3400 Sentex Communications, [EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP: fast ipsec committed
At 09:11 AM 24/01/2003 -0800, Sam Leffler wrote: > At 09:39 PM 1/23/2003 -0800, Sam Leffler wrote: > >I just commited my "Fast IPsec" support. This is an implementation of the > >IPsec protocols that makes use of the kernel crypto framework. What this > >means is that if you have a hardware crypto card it will automatically be > >used by the protocols. If you don't have crypto hardware you will use the > >host cpu as before. > > Hi, > Apart from FAST_IPSEC and OpenSSL 0.9.7, what parts (if any) of > FreeBSD would currently make sure of the crypto hardware ? With OpenSSL you get lots of applications. I'm not sure if Kerberos also benefits. In the kernel there's nothing else at the moment but that's not to say that things like gbde couldn't use it. I also intend to use it to do AES for wireless security protocols. Thanks for the info! Just to confirm/clarify, without FAST_IPSEC enabled, none of the crypto hardware is used in IPSEC, correct ? ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Apache + latest stable
I have run into this problem before, especially with mod_php. There are
probably still some parts that apache links to that need to be recompiled
as well. Do you have php by chance ? If so, rebuild it as well as all its
dependencies.
---Mike
At 06:33 PM 1/15/2003 -0800, Mike Hoskins wrote:
Waited ~4 hours and tried cvsup again. No new checkouts, so apparently
nothing was broken enough during my last checkout to warrent any immediate
attention. Apache, even after a rebuild, still just dumps core. Any
clues as to what may be causing this? It doesn't seem to be SSL-specific,
root@mojo{root}# apachectl startssl
Bus error (core dumped)
/usr/local/sbin/apachectl startssl: httpd could not be started
root@mojo{root}# apachectl start
Bus error (core dumped)
/usr/local/sbin/apachectl start: httpd could not be started
On Wed, 15 Jan 2003, Mike Hoskins wrote:
> After building a recent stable,
>
> FreeBSD mojo.televoke.net 4.7-STABLE FreeBSD 4.7-STABLE #6: Wed Jan 15
> 13:56:31 PST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MOJO
> i386
>
> Apache just dumps core when I try to start it. I'm running,
>
> apache+mod_ssl-1.3.27+2.8.12
>
> I've rebuilt via portupgrade -f, with the same result. Nothing is logged
> to Apache logs, only the following in messages:
>
> Jan 15 15:44:33 mojo /kernel: pid 11103 (httpd), uid 0: exited on signal
> 10 (core dumped)
>
> A copy of the latest core is here,
>
> http://www.adept.org/pub/httpd.core
>
> Anyone else seeing this?
>
> --
> Mike Hoskins This message is RFC 1855 compliant,
> [EMAIL PROTECTED]www.adept.org/pub/rfcs/rfc1855.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, [EMAIL PROTECTED]
Providing Internet since 1994www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Fix for hanging of vr interface (Rhine Ethernet)
At 07:34 PM 23/12/2002 +0100, Thomas Nystrom wrote: Ok, I have found that the board should have a VT6103 PHY-chip. There is no specific support for that chip in FreeBSD and the default PHY driver is used instead. Hi, By no specific driver, does that mean none is needed ? Or just that nothing is available now, so the lowest common denominator is used. Basically, I am asking, is this "a bad thing" ? > Also, while pushing the board network wise, I got a > vr0: Using force reset command. > Is this normal ? Did you get some other message before or after the 'force reset' message? Nothing else that I saw. Did the interface work after the forced reset? Yes, it seemed to. Is there any extra debugging info I can provide ? ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Fix for hanging of vr interface (Rhine Ethernet)
At 01:07 AM 21/12/2002 +0100, Thomas Nystrom wrote: Is it possible for you to check the type and brand of the PHY-chip? You must locate the chip directly on the motherboard. Or tell me the type of the motherboard and I might grab some info about the board from the net. Hi, The Motherboard is a BioStar U8068. Chipset is Via VT8751 (pm4M266)/VT8235. There is nothing obvious on the board that says what rev. If you like, I could send you a couple of .jpg images of the motherboard if that helps. Also, while pushing the board network wise, I got a vr0: Using force reset command. Is this normal ? ---Mike /thn -- --- Svensk Aktuell Elektronik AB Thomas Nyström Box 10Phone: +46 8 35 92 85 S-191 21 Sollentuna Fax: +46 8 59 47 45 36 Sweden Email: [EMAIL PROTECTED] --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Recent -STABLE dying on install in opencrypto
I am seeing the same problem. I seem to have everything locally that was committed (based on whats at cvs-all) cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 netatm/spans/*.h /usr/include/netatm/spans cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 netatm/uni/*.h /usr/include/netatm/uni cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h /usr/include/ufs/ffs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/mfs/*.h /usr/include/ufs/mfs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ufs/*.h /usr/include/ufs/ufs cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 opencrypto/*.h /usr/include/crypto usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop in /usr/src/include. *** 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. At 08:30 PM 11/21/2002 -0800, Kris Kennaway wrote: On Thu, Nov 21, 2002 at 08:16:05PM -0800, John Merryweather Cooper wrote: > It looks like there's an error in the install routines for opencrypto. > Everything builds fine, but the installworld results in: This was only MFCed about 2 hours ago. You might have cvsupped in the middle of the change. Please wait a few hours and try again. Kris ---- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, [EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ppp(8) v. 3.1 : PPPoE lqr problem.
At 09:56 AM 10/1/2002 +0200, Thomas Quinot wrote: >Le 2002-10-01, Artur Pydo écrivait : > > > Since the end of August i had problems running my ADSL connection. > > > I discovered that ppp changed its behaviour regarding lqr after > > the upgrade from version 2.3.3 to 3.1. > >This is probably a coincidence. I saw that when France Telecom changed >some ADSL equipment: the new BASs indeed do not reply to LCP Echo >Request frames. I have notified them of this problem several times since >then, to no avail. And, their VJ Header compression is broken... We got burned by this big time when Bell Canada started switching away from Redback's SMSes... Knowledge Asset ID#: 1773.0 Subject: The ERX does not support IP header compression as described in RFC 2507 and RFC 2508. Type: SW Release: SW Version: Problem Description: The ERX does not support and does not yet have plans to support IP header compression. For a full description of IP header compression refer to RFC 2507 and RFC 2508. It basically says that multiple packets to and from the same destinations can get their headers compressed to save about 8 bytes per packet. This feature has been requested in case 10349 -- -------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.7-PRERELEASE FAILING!!
At 03:20 PM 19/09/2002 +0300, Odhiambo Washington wrote: >The first clue I have about all this is that I realized that mysql-server.sh >refused to start. When I attempted to start it manually the system >complained that >there was "&&" that was unexpected. So I am wondering whether the syntax >for /bin/sh Yes its changed in that it no longer honors what is considered to be a syntax error. So scripts which use that need to be fixed. ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FreeBSD 4.7-PRERELEASE & IPFilter
Thanks. Are the changes correct BTW ? I am going to cc to stable as a number of people have noted and asked this question. ---Mike At 10:35 PM 09/09/2002 +1000, Darren Reed wrote: >In some email I received from Mike Tancsa, sie wrote: > > The filtering works on my machine... Havent tried NAT yet. BTW, are those > > differences mentioned in the mailing list deliberate ? > >No. I suspect they're mostly from people fixing problems when they're >making changes to the FreeBSD kernel. > >Darren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Rocketport (rp) PCI card on stable ?
At 09:46 PM 06/09/2002 -0400, Charles Sprickman wrote: >On Fri, 6 Sep 2002, Mike Tancsa wrote: > > > Perhaps something about the cable ? > >What are you using to make a null modem (xover) cable? Maybe cu is >sensitive to CTS/RTS working and kermit is not? For now, just a null modem adaptor. We have only made 1 FreeBSD console cable and one Cisco cable so far. We made it just straight through for now in order to prove that it worked. We will make a proper null-modem cable next week. ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Rocketport (rp) PCI card on stable ?
At 05:30 PM 06/09/2002 -0400, Mike Nowlin wrote: >On Friday, September 6, 2002, at 05:15 PM, Mike Tancsa wrote: > >>At 09:51 PM 05/09/2002 -0400, Peter Radcliffe wrote: >>>I use kermit to /dev/cuaR0 and can get out to the console of other >>>machines fine. >> >> >>I finally got it to work! For some reason, I am unable to use cu to >>connect, but it works just great with kermit! Any reason why cu would >>not work ? Its no big deal, but I am curious. > >What arguments are you using? I do "cu -l /dev/cuaR1 -s9600" all the time proxy2# cu -s 9600 -l /dev/cuaR1 Connected. ~[proxy2]. Disconnected. proxy2# Just hangs there. proxy2# kermit C-Kermit 8.0.201, 8 Feb 2002, for FreeBSD 4.0 Copyright (C) 1985, 2002, Trustees of Columbia University in the City of New York. Type ? or HELP for help. (/usr/home/mdtancsa/) C-Kermit>set LINE /dev/cuaR1 (/usr/home/mdtancsa/) C-Kermit>set speed 9600 /dev/cuaR1, 9600 bps (/usr/home/mdtancsa/) C-Kermit>connect Connecting to /dev/cuaR1, speed 9600 Escape character: Ctrl-\ (ASCII 28, FS): enabled Type the escape character followed by C to get back, or followed by ? to see other options. FreeBSD/i386 (newhespborder.sentex.ca) (ttyd0) login: Perhaps something about the cable ? ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Rocketport (rp) PCI card on stable ?
I picked up a surplus Rocketport PCI card but am having problems getting it to run on STABLE. I can get it to work just fine under windows, so I know it works. But I cant get it to work with FreeBSD. I have the /dev/cuaR# devices, but alas, no joy. All I want to do is just be able to use it as a terminal server to connect to other FreeBSD boxes. Its detected as rp0: port 0xd000-0xd03f irq 10 at device 10.0 on pci0 RocketPort0 = 8 ports rp0: driver is using old-style compatibility shims I am just using cu, but I tried minicom as well without luck. Has anyone used this card with luck under STABLE ? ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Loosing network connection repeatedly without an identifiable cause
At 10:42 AM 15/08/2002 -0700, Michael A. Dickerson wrote: >Did you know there was trouble with the fxp driver in 4-STABLE a few days >ago? I was having similar bizarre problems (ping works in one Yes, luigi fixed it with a couple of commits. Also, this problem can be worked around by setting kern.ipc.mcl_pool_max=0 ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Changes to tar (was Re: strange SSH / tar problem)
Actually, someone pointed out this is a tar problem. I forgot that RELENG_4 has a whole new version of tar. tar (GNU tar) 1.13.25 vs 1.11.2. Old version of tar both forms work fine. granite# tar -czf t.tgz /tmp/root granite# tar -czf - /tmp/root > t2.tgz granite# tar -tzf t2.tgz root/ root/ps.out root/m.sort root/q.out root/nestat.out root/m.list root/s.dead root/s1 root/s2 root/exp.list root/dead.txt root/dsl.out root/code-red.txt root/mail.access.times root/own.txt root/ms.rot root/dead.sort root/files.txt root/mail.list root/f.out root/m.dort root/du.out root/list.txt root/list.txt2 root/dead.list root/deadmail/ granite# ls -l *.tgz -rw-r--r-- 1 root wheel 1424563 Jul 27 09:44 t.tgz -rw-r--r-- 1 root wheel 1424563 Jul 27 09:45 t2.tgz granite# new version of tar news% tar -czf - test-files > t2.tgz news% tar -czf t.tgz test-files news% tar -tzf t2.tgz test-files/ test-files/ps.out test-files/netstat.out test-files/mount.out test-files/ipfw.out test-files/if.out test-files/t.zip gzip: stdin: decompression OK, trailing garbage ignored tar: Child returned status 2 tar: Error exit delayed from previous errors news% ls -l *.tgz -rw-r--r-- 1 mdtancsa wheel 4320 Jul 27 09:46 t.tgz -rw-r--r-- 1 mdtancsa wheel 10240 Jul 27 09:46 t2.tgz news% At 04:13 PM 7/26/2002 -0400, Mike Tancsa wrote: >On a number of my servers I use tar via ssh to do frequent backups of >files to a central backup server. The backup server is running an older >ssh, but the same problem happens with the most recent versions. > >SSH-1.99-OpenSSH_2.9 FreeBSD localisations 20020307 > >If I do a tar over ssh the resulting file has an error at the end. > >e.g. source is running SSH-1.99-OpenSSH_3.4p1 FreeBSD-20020702 >destination (20020307) >tar -cpzf - /etc /usr/local/etc | /usr/bin/ssh >[EMAIL PROTECTED] "cat - > >/path-to-files/userid/backup.`date "+%y%m%d"`.tgz" > > >When I go to test the file, I get > >tar -tzf backup.020726.tgz > >usr/local/etc/apache.bak/httpd.conf.default > >gzip: stdin: decompression OK, trailing garbage ignored >usr/local/etc/apache.bak/access.conf.default >usr/local/etc/apache.bak/access.conf >tar: child returned status 2 > >It seems to work OK, but I was a bit surprised about the warning message > > From the source server >md5 * >MD5 (t.zip) = 868cd7e432dc2ad7049a2c61a2403194 >MD5 (t2.zip) = 90279347e332762c0fc43798b4ae4d57 >MD5 (webalizer.conf) = dd948a77ba729a471f7ade18088b3680 >tar -cpzf - /tmp/test-files | /usr/bin/ssh [EMAIL PROTECTED] >"cat - > /path-to-files/userid/testb.`date "+%y%m%d"`.tgz" > >and the target server > >tar -xzf testb.020726.tgz > >gzip: stdin: decompression OK, trailing garbage ignored >tar: child returned status 2 > >cd test-files/ >backupserver# md5 * >MD5 (t.zip) = 868cd7e432dc2ad7049a2c61a2403194 >MD5 (t2.zip) = 90279347e332762c0fc43798b4ae4d57 >MD5 (webalizer.conf) = dd948a77ba729a471f7ade18088b3680 > > >The sshd_config and ssh_config on both machines are stock. If I got from a >stable box as of today to another stable box as of today, the same error >happens. > > ---Mike > >Mike Tancsa, tel +1 519 651 3400 >Sentex Communications,[EMAIL PROTECTED] >Providing Internet since 1994www.sentex.net >Cambridge, Ontario Canada www.sentex.net/mike > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-stable" in the body of the message Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP: FreeBSD-STABLE now has OpenSSH 3.4p1
As a lot has changed with OpenSSH in FreeBSD, perhaps now is a good time to make the 2,1 the default instead ? ---Mike At 10:27 AM 7/5/2002 +0200, Dag-Erling Smorgrav wrote: >Ruslan Ermilov <[EMAIL PROTECTED]> writes: > > The default of "Protocol 1,2" in -STABLE's /etc/ssh/ssh_config > > was lost in this merge. Was this intentional? > >Yes-and-no. I never liked the old default, but didn't consciously >change it, I just forgot to merge it in when I MFCed. Does the new >default cause trouble for anyone? > >DES >-- >Dag-Erling Smorgrav - [EMAIL PROTECTED] > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-stable" in the body of the message Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
panic: ffs_clusteralloc: map mismatch
IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) pseudo-device bpf #Berkeley packet filter options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=32100 #limit verbosity options IPV6FIREWALL#firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPV6FIREWALL_VERBOSE_LIMIT=1200 options IPDIVERT#divert sockets pseudo-device vlan1 #VLAN support options QUOTA #enable disk quotas -------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
New resolver bug ?
Granted, its a rather strange entry, but why does backup2# nslookup -type=a mail.spicer.com Server: ns2.sentex.ca Address: 199.212.134.2 nslookup in free(): warning: junk pointer, too low to make sense Name:mail.spicer.com Address: 216.16.235.172 backup2# where as prior to the latest BIND commit, pyroxene% nslookup mail.spicer.com Server: ns.sentex.ca Address: 199.212.134.1 Name:mail.spicer.com Addresses: 216.16.235.172, 216.16.235.172 works. Also, telnet mail.spicer.com smtp just hangs, but telnet 216.16.235.172 smtp works ---Mike ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Mirror of 4.6RC2 ISO (was Re: FreeBSD 4.6-RC2 (i386) is now available.
At 02:16 AM 5/20/2002 +0100, Brian Somers wrote: > > Hi, > > Can you tell me the MD5 checksum of the image ? From the AUS > site, > > I got > > > > MD5 (4.6-RC2-install.iso) = 8cafce7c79b977500d2776bf74b7 > > > > ---Mike > >That's correct. >-- >Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]> Great! I have made a local North American copy of the ISO available at http://shell1.sentex.ca/4.6-RC2-install.iso I have allocated 5Mb of outbound bandwidth to it. ---Mike ---- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: overriding NETINET6 builds for sendmail
At 10:43 AM 07/05/2002 -0600, Ian wrote: >Add the following to your /etc/make.conf > > SENDMAIL_CFLAGS= -UNETINET6 Excellent! Thanks, I didnt know about that form. >Of course, that's a literal answer to the question you asked, and doesn't >imply that you should discount anything Gregory is saying, since when it >comes to sendmail, he's da man. He certainly is :) I am going to try and rebuild and retest my original configuration to make sure its not just pilot error on my part. ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: overriding NETINET6 builds for sendmail
At 09:31 AM 07/05/2002 -0700, Gregory Neil Shapiro wrote: >mike> At 09:20 AM 07/05/2002 -0700, Gregory Neil Shapiro wrote: > >> want to excuse this behavior, include WorkAroundBroken in > >mike> I had been using that, but it does not seem to work. e.g. the domain >mike> region.peel.on.ca > >How doesn't it work? May 7 00:04:35 granite sm-mta[61324]: g4740ZLu061324: ruleset=check_mail, arg1=<[EMAIL PROTECTED]>, relay=smtp2.sentex.ca [199.212.134.9], reject=451 4.1.8 Domain of sender address [EMAIL PROTECTED] does not resolve I have (had) define(`confBIND_OPTS', `+WorkAroundBroken')dnl But still the problem of the domain "not resolving" ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3ware problem
Actually, I am seeing the same thing /var/log/messages.0.gz:Apr 29 14:30:04 newflint /kernel: twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present. /var/log/messages.0.gz:Apr 29 14:30:18 newflint /kernel: twe0: unexpected status bit(s) 80 /var/log/messages.0.gz:Apr 29 14:30:18 newflint /kernel: twe0: PCI parity error: Reseat card, move card or buggy device present. /var/log/messages.0.gz:Apr 29 14:30:29 newflint /kernel: twe0: unexpected status bit(s) 80 /var/log/messages.0.gz:Apr 29 14:30:29 newflint /kernel: twe0: PCI parity error: Reseat card, move card or buggy device present.twe0: PCI parity error: Reseat card, move card or buggy device present. /var/log/messages.0.gz:Apr 29 14:30:31 newflint /kernel: twe0: PCI parity error: Reseat card, move card or buggy device present. /var/log/messages.0.gz:Apr 29 14:30:44 newflint /kernel: twe0: unexpected status bit(s) 80 /var/log/messages.0.gz:Apr 29 14:30:44 newflint /kernel: twe0: PCI parity error: Reseat card, move card or buggy device present. /var/log/messages.0.gz:Apr 29 14:30:54 newflint /kernel: twe0: unexpected status bit(s) 80 /var/log/messages.0.gz:Apr 29 14:30:54 newflint /kernel: twe0: PCI parity error: Reseat card, move card or buggy device present. Perhaps bogus firmware ? BIOS settings ? I moved it to two different machines, same problem. ---Mike At 11:25 PM 5/3/2002 -0700, Michael Smith wrote: > > > > ASUS P2B-DS mobo, dual p3. Promise fasttrak 66, 2 intel 10/100. > > > > Just upgraded to 4.5-stable as of 4/17, and put in a 3ware 7850 running 7.4 > > > > When it boots, right after the 3ware probes, I get this stream of errors > > (apparently unceasing): > > > > Waiting 15 seconds for SCSI devices to settle > > twe0: PCI parity error: Reseat card, move card or buggy device present. > > > Not sure what to do here. > >Read the error message, perhaps? > > > >-- >To announce that there must be no criticism of the president, >or that we are to stand by the president, right or wrong, is not >only unpatriotic and servile, but is morally treasonable to >the American public. - Theodore Roosevelt > > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-stable" in the body of the message Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
new ata code and vinum
While putting together a new news server, I did some quick tests on some of the new ATA hardware. So far so good in tests. It will be interesting to see how it takes a pounding with 30Mb/s being sent to it 24hrs a day :) Using PIII, 1G, 1G of RAM HighPoint RocketRAID 404 (370 chipset), ahc 2940U ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ad8 1500 40395 91.5 39973 51.5 14251 18.0 28391 91.5 41257 20.4 192.0 1.1 da0 1500 17198 40.2 15052 18.0 8030 9.9 15768 50.6 15846 7.4 297.8 1.8 vinumS 1500 32865 78.5 31383 42.1 10993 15.0 24679 83.5 32473 20.8 505.4 3.4 ar0 1500 47033 88.2 43172 53.7 16090 21.2 28676 93.5 44640 24.3 296.7 1.9 vinumI 1500 47819 89.5 43188 58.6 13715 18.9 20767 69.5 32029 19.0 365.6 2.0 The the drives being da0: Fixed Direct Access SCSI-2 device on ahc0: da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: Fixed Direct Access SCSI-2 device ar1: 114483MB [14594/255/63] status: READY subdisks: 0 READY ad8: 57241MB [116301/16/63] at ata4-master UDMA100 1 READY ad10: 57241MB [116301/16/63] at ata5-master UDMA100 ad8 was just a drive off the RocketRaid controllers, and ar0 being a stripe of the 2 drives. vinumI = vinum with 2 IDE drives (both on single channels) vinumS = vinum with 2 of the SCSI drives. ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
strange things with sendmail and quotas on STABLE
Given user Quotas for user test123: /var/mail: blocks in use: 20048, limits (soft = 2, hard = 2) inodes in use: 2, limits (soft = 0, hard = 0) OK, they are over their limit. No problem. What is strange is why does granite# mail -v test123 Subject: Your mailbox is full Hello, you are over the 20MB limit. You must clean out your old mail in order to get new mail EOT test123... Connecting to localhost.sentex.net. via relay... etc... work? This gets delivered, where as in the past it would bounce. Now even stranger, if I try and send a large message thats over a certain size, it will bounce as expected. granite# wc /tmp/r.out 3514650 34236 /tmp/r.out granite# cat /tmp/r.out | mail -s "test ignore" test123 This message bounces. Apr 19 16:09:46 granite sm-mta[52050]: g3JK9ksf052049: to=<[EMAIL PROTECTED]>, ctladdr=<[EMAIL PROTECTED]> (1001/1001), delay=00:00:00, xdelay=00:00:00, mailer=local, pri=64850, relay=local, dsn=5.2.2, stat=Service unavailable (/var/mail/test123: Disc quota exceeded) Apr 19 16:09:46 granite sm-mta[52050]: g3JK9ksf052049: g3JK9ksf052050: DSN: Service unavailable (/var/mail/test123: Disc quota exceeded) This did not used to be this way. Any ideas what might have changed this behaviour ? This is a buildworld from Thu Apr 18. ---Mike -------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: steps to rebuild a dead RAID1 array ?
At 10:57 AM 4/11/2002 +0200, Søren Schmidt wrote: >It seems Mike Tancsa wrote: > > Yet, when I go to do a rebuild, > > > > raidtest3# atacontrol rebuild ar0 > > atacontrol: ioctl(ATARAIDREBUILD): Operation not supported by device > > raidtest3# > > > > I guess there needs to be some way to tell the controller to use ad6 as > > part of the rebuild no ? > >You need to do a atacontrol detach on the failed device, then an >atacontrol attach on the new disk. BTW you dont need to boot >inbetween :) OK, tried that but still no luck raidtest3# atacontrol attach 3 Master: ad6 ATA/ATAPI rev 5 Slave: no device present raidtest3# atacontrol attach 3 Master: ad6 ATA/ATAPI rev 5 Slave: no device present raidtest3# atacontrol rebuild ar0 atacontrol: ioctl(ATARAIDREBUILD): Operation not supported by device raidtest3# raidtest3# atacontrol status ar0 ar0: ATA RAID1 subdisks: ad4 status: DEGRADED raidtest3# Also, I dont have a hot swappable case. These are just plain old drives. ---Mike >-Søren -------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP: sendmail 8.12.2 MFC'ed
Hi, One of the neat things I like about 8.12.2 are the milter facilities. Just wondering if http://www.sendmail.org/~ca/email/patches/milter.c.8.188.p could / would be committed to FreeBSD at some point ? ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: status of ATA subsystem
At 03:43 PM 4/1/2002 -0800, Dave Hayes wrote: >So I believe the properly phrased questions are > >a) "What is the stability status of the current changes to the ATA >subsystem in -STABLE?". I have it running on a number of machines with good results. Controllers I have it on are atapci0: port 0xf000-0xf00f at device 31.1 on pci0 atapci0: port 0xb800-0xb80f at device 4.1 on pci0 atapci1: (in RAID mode) with various IDE type drives. These are as of Sunday evening GMT -500 (i.e. past the last commit) ---Mike -------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: stable breaks HighPoint support
At 02:21 PM 3/26/02 +0100, Søren Schmidt wrote: >It seems Mike Tancsa wrote: > > > > It looks like something in stable seem to break High Point 404 support > > using the vendor's drivers and RAID administrator software. > > http://www.highpoint-tech.com/rr404_down.htm > >Highpoint's driver are for FreeBSD-4.5. > >They wont work with -stable and what is to become 4.6. > >The bright side is you wont even need them :) :-) True, but there is no equivalent RAID management software. ---Mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
stable breaks HighPoint support
) at /usr/src/sys/kern/kern_shutdown.c:316
316 dumpsys();
(kgdb) up
#2 0xc01d87a4 in poweroff_wait (junk=0xc03b8d79, howto=-1069840305) at
/usr/src/sys/kern/kern_shutdown.c:595
595 boot(bootopt);
(kgdb) up
#3 0xc034b1f5 in trap_fatal (frame=0xd2d44d64, eva=0) at
/usr/src/sys/i386/i386/trap.c:966
966 panic("%s", trap_msg[type]);
(kgdb) up
#4 0xc034ae6d in trap_pfault (frame=0xd2d44d64, usermode=0, eva=0) at
/usr/src/sys/i386/i386/trap.c:859
859 trap_fatal(frame, eva);
(kgdb) up
#5 0xc034a9cb in trap (frame={tf_fs = -797835240, tf_es = 16, tf_ds = 16,
tf_edi = -757838092, tf_esi = 2, tf_ebp = -757838424,
tf_isp = -757838448, tf_ebx = -757838228, tf_edx = -1042194560,
tf_ecx = 4, tf_eax = 0, tf_trapno = 12, tf_err = 0,
tf_eip = -1042218516, tf_cs = 8, tf_eflags = 66178, tf_esp = 0,
tf_ss = -757838384}) at /usr/src/sys/i386/i386/trap.c:458
458 (void) trap_pfault(&frame, FALSE, eva);
(kgdb) up
#6 0xc1e101ec in ?? ()
(kgdb) up
#7 0xc1e0fbb7 in ?? ()
(kgdb) up
#8 0xc1e05066 in ?? ()
(kgdb) up
#9 0xc1e05a61 in ?? ()
(kgdb) up
#10 0xc01dd3e8 in sysctl_root (oidp=0x0, arg1=0xd2d44ef4, arg2=2,
req=0xd2d44e6c) at /usr/src/sys/kern/kern_sysctl.c:1041
1041error = oid->oid_handler(oid, oid->oid_arg1,
oid->oid_arg2,
(kgdb) up
#11 0xc01dd5a1 in userland_sysctl (p=0xd0727d40, name=0xd2d44ef4,
namelen=2, old=0x0, oldlenp=0x0, inkernel=0, new=0xbfad,
newlen=28, retval=0xd2d44ef0) at /usr/src/sys/kern/kern_sysctl.c:1134
1134error = sysctl_root(0, name, namelen, &req2);
(kgdb) up
#12 0xc01dd457 in __sysctl (p=0xd0727d40, uap=0xd2d44f80) at
/usr/src/sys/kern/kern_sysctl.c:1070
1070error = userland_sysctl(p, name, uap->namelen,
(kgdb) up
#13 0xc034b539 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = -1079129004, tf_esi = -1079128884,
tf_ebp = -1079129076, tf_isp = -757837868, tf_ebx = 672168644,
tf_edx = 0, tf_ecx = 0, tf_eax = 202, tf_trapno = 22,
tf_err = 2, tf_eip = 671794456, tf_cs = 31, tf_eflags = 643, tf_esp
= -1079129136, tf_ss = 47})
at /usr/src/sys/i386/i386/trap.c:1167
1167error = (*callp->sy_call)(p, args);
(kgdb) up
#14 0xc0335a6b in Xint0x80_syscall ()
(kgdb) up
cannot read proc at 0
(kgdb)
raidtest2# kldstat
Id Refs AddressSize Name
12 0xc010 3b23cc kernel
21 0xc1e63000 1e000hpt374.ko
raidtest2# sysctl hpt374.status
hpt374.status:
Device Driver for HPT374 UDMA/ATA133 RAID Controller Driver Version 1.0
Physical device list
Controller/Bus/ID ModelCapacity Status Array
---
Logical device list
No. Type Name Capacity StatusOsDisk
-
raidtest2#
ad0: 19541MB [39703/16/63] at ata0-master UDMA33
ad8: 38166MB [77545/16/63] at ata4-master UDMA100
ad10: 38166MB [77545/16/63] at ata5-master UDMA100
acd0: CDROM at ata1-master PIO4
ad8 and ad10 are the ones on the controller.
---Mike
--------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications,[EMAIL PROTECTED]
Providing Internet since 1994www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
