Re: hoststated: fatal: relay_dispatch_pfe: desynchronized,
On Wed, 6 Jun 2007 21:29:42 +0300 Paulius Bulotas [EMAIL PROTECTED] wrote: well ;) probably you will have to wait for 4.2, but fix for similar problem (try to disable table, then enable it ;) so probably the same applies for host disabling, enabling... at least, with this patch it works for me. this will be taken care of by the end of the week. but give me some time to commit the reload support first.
AMD64 raid setup SATA - dmesg error/warning
Goodmorning, During boot my AMD64 machine with RAID setup shows me the following messages: raidctl: ioctl RAIDFRAME_CONFIGURE failed raid0: Device already configured! I have followed the instructions over at: http://www.eclectica.ca/howto/openbsd-software-raid-howto.php. Kernel additions to GENERIC are: option RAID_AUTOCONFIG pseudo-device raid4 'raidctl -s' shows everything *seems* to be fine; I am not sure why I get the error and warning. I also noticed the writing to disk is rather slow compared to IDE disks on other machines; or so it seems. All this makes me concerned the install is not correct / trustworthy. Any advice is highly appreciated, please let me know if I should supply other info than that below. Thanks! -- # raidctl -s raid0 raid0 Components: /dev/wd0d: optimal /dev/wd1d: optimal No spares. Parity status: clean Reconstruction is 100% complete. Parity Re-write is 100% complete. Copyback is 100% complete. # cat /etc/raid0.conf START array 1 2 0 START disks /dev/wd0d /dev/wd1d START layout 128 1 1 1 START queue fifo 100 # cat /etc/fstab /dev/raid0a / ffs rw 1 1 /dev/raid0g /home ffs rw,nodev,nosuid 1 2 /dev/raid0e /tmp ffs rw,nodev,nosuid 1 2 /dev/raid0d /usr ffs rw,nodev 1 2 /dev/raid0f /var ffs rw,nodev,nosuid 1 2 # dmesg OpenBSD 4.1 (GENERIC.RAID) #0: Tue Jun 5 18:30:18 CEST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.RAID real mem = 1072164864 (1047036K) avail mem = 906080256 (884844K) using 22937 buffers containing 107425792 bytes (104908K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf (40 entries) bios0: Sun Microsystems Sun Fire(TM) X2100 acpi at mainbus0 not configured cpu0 at mainbus0: (uniprocessor) cpu0: AMD Opteron(tm) Processor 150, 2412.65 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: Cool'n'Quiet K8 2412 MHz: speeds: 2400 2200 2000 1800 1000 MHz cpu0: AMD erratum 89 present, BIOS upgrade may be required pci0 at mainbus0 bus 0: configuration mode 1 NVIDIA nForce4 DDR rev 0xa3 at pci0 dev 0 function 0 not configured pcib0 at pci0 dev 1 function 0 NVIDIA nForce4 ISA rev 0xa3 nviic0 at pci0 dev 1 function 1 NVIDIA nForce4 SMBus rev 0xa2 iic0 at nviic0 adt0 at iic0 addr 0x2e: sch5017 rev 0x89 iic1 at nviic0 adt1 at iic1 addr 0x2e: sch5017 rev 0x89 ohci0 at pci0 dev 2 function 0 NVIDIA nForce4 USB rev 0xa2: irq 11, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 8 ports with 8 removable, self powered ehci0 at pci0 dev 2 function 1 NVIDIA nForce4 USB rev 0xa3: irq 3 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 uhub1: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1 uhub1: 8 ports with 8 removable, self powered pciide0 at pci0 dev 6 function 0 NVIDIA nForce4 IDE rev 0xf2: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) pciide0: channel 1 disabled (no drives) pciide1 at pci0 dev 7 function 0 NVIDIA nForce4 SATA rev 0xf3: DMA pciide1: using irq 10 for native-PCI interrupt wd0 at pciide1 channel 0 drive 0: WDC WD1200JS-00MHB0 wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1 at pciide1 channel 1 drive 0: WDC WD1200JD-00HBC0 wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd1(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 5 pciide2 at pci0 dev 8 function 0 NVIDIA nForce4 SATA rev 0xf3: DMA pciide2: using irq 11 for native-PCI interrupt ppb0 at pci0 dev 9 function 0 NVIDIA nForce4 PCI-PCI rev 0xa2 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb1 at pci0 dev 11 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci2 at ppb1 bus 2 ppb2 at pci0 dev 12 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci3 at ppb2 bus 3 ppb3 at pci0 dev 13 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci4 at ppb3 bus 4 bge0 at pci4 dev 0 function 0 Broadcom BCM5721 rev 0x11, BCM5750 B1 (0x4101): irq 5, address 00:e0:81:59:6d:eb brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb4 at pci0 dev 14 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci5 at ppb4 bus 5 pchb0 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pchb1 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00 pchb2 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00 pchb3 at pci0 dev 24 function 3 AMD AMD64 Misc Cfg rev 0x00 isa0 at pcib0 isadma0 at isa0 com0 at
Re: /usr/obj partition AWOL
On Wed, 6 Jun 2007, Otto Moerbeek wrote: On Wed, 6 Jun 2007, Markus Lude wrote: On Tue, Jun 05, 2007 at 07:51:48AM +0200, Otto Moerbeek wrote: On Tue, 5 Jun 2007, Markus Lude wrote: On Mon, Jun 04, 2007 at 06:02:59PM -0500, Emilio Perea wrote: I follow -current on an i386 at work and an amd64 at home, and rarely run into any problem which is not self-inflicted. So when I had a weird experience this weekend, I assumed it was my fault. What happened was that after the usual sequence of [build kernel; reboot; build userland; reboot] the system complained that it could not fsck wd1j and dropped into single-user mode. wd1j is mounted on /usr/obj, and I thought that something in the last build had messed it up, so I ran newfs wd1j and got newfs: /dev/rwd1j: Device not configured disklabel wd1 showed partitions d-i and k-p, but no j. I added the partition, ran newfs, and everything seemed fine. This afternoon I installed the i386 snapshot downloaded this morning (dated Jun 3 19:19) on the work pc, and after reboot it was missing the /usr/obj partition (sd0g in this case). Everything seems to be working fine on both computers, but I didn't expect the partitions to disappear. Did nobody else run into this problem? Or did everybody else who saw it thought it was too obvious to mention it to the mailing list? I had a similar problem on sparc64 with a snapshot from jun 2. The system was unable to fsck some partitions and dropped to single user mode. Here the problems were with the /usr, /var, /tmp and /home partitions. Some further (and larger partitions) weren't affected. I installed an older snapshot. Any suggestions how to get this fixed or what to test/try? There were some validations checkc added to partitions. If a bad partition is found, it will be marked unused. The checks were a little to strict for some cases. A fix for that went in yesterday, so try a new snap. Thanks for your info. After rebuilding kernel and userland the problem still exists, but now the affected partitions are /var, /home and /data. Hmm. Unmounting /data and doing a manual fsck -f runs without problems. If the problem persists, please report with full disklabel output. $ cat /etc/fstab /dev/wd0a / ffs rw 1 1 /dev/wd0d /tmp ffs rw,nodev,nosuid 1 2 /dev/wd0e /usr ffs rw,nodev 1 2 /dev/wd0f /var ffs rw,nodev,nosuid 1 2 /dev/wd0g /home ffs rw,nodev,nosuid 1 2 /dev/wd0h /data ffs rw,nodev,nosuid 1 2 /dev/wd1d /backup ffs rw,nodev,nosuid 1 2 with an actual kernel: $ sudo disklabel wd0 # /dev/rwd0c: type: ESDI disk: ESDI/IDE disk label: ST3120213A flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 16514064 ^^^ 1008 * 16383 = 16514064 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 1024128 0 4.2BSD 2048 16384 16 # Cyl 0 - 1015 b: 3072384 1024128swap # Cyl 1016 - 4063 c: 234441648 0 unused 0 0 # Cyl 0 -232580 ^ Your disk size and c partition size do not match. Can you send a dmesg, to see what the actual size of your disk is? This is really needed to see what is going on. Did you at any time edit the disk size by hand? d: 2048256 4096512 4.2BSD 2048 16384 16 # Cyl 4064 - 6095 e: 20479536 6144768 4.2BSD 2048 16384 16 # Cyl 6096 - 26412 disklabel: partition c: partition extends past end of unit disklabel: partition e: partition extends past end of unit older kernel: $ sudo disklabel wd0 [...] 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 1024128 0 4.2BSD 0 0 16 # Cyl 0 - 1015 b: 3072384 1024128swap # Cyl 1016 - 4063 c: 234441648 0 unused 0 0 # Cyl 0 -232580 d: 2048256 4096512 4.2BSD 0 0 16 # Cyl 4064 - 6095 e: 20479536 6144768 4.2BSD 0 0 16 # Cyl 6096 - 26412 f: 4095504 26624304 4.2BSD 0 0 16 # Cyl 26413 - 30475 g: 20479536 30719808 4.2BSD 0 0 16 # Cyl 30476 - 50792 h: 183242304 51199344 4.2BSD 0 0 16 # Cyl 50793 -232580 disklabel: partition c: partition extends past end of unit disklabel: partition e: partition extends past
Re: Quad ethernet card
Hi, Thanks for all the input, we have decided to go for a Dell PE860 with an Intel quad pro/1000 GT adapter. Best regards Fredrik Carlsson
Pf Issue with a large number of Packet
Hi All,
I am sorry to bother the list but I think I may have encountered a bug and I
would like to share with you guys. I have been using OpenBSD to build Firewall
for a long time in solution with VLAN + CARP. When computers in the protected
network downloads a file in HTTP, everything works for the First 15 Mo then it
stops.
When I tcpdump, On the external address, I get the folowing:
08:34:19.343833 mirrors.club-internet.fr.www so-bo01-std.55692: P
17637121:17638569(1448) ack 174 win 49232 nop,nop,timestamp 3651037459
313698521 (DF)
08:34:19.343870 so-bo01-std.55692 mirrors.club-internet.fr.www: . ack
17634225 win 1810 nop,nop,timestamp 313698522 3651037459 (DF)
08:34:19.614303 mirrors.club-internet.fr.www so-bo01-std.55692: P
20054337:20055785(1448) ack 174 win 49232 nop,nop,timestamp 3651037487
313698589 (DF)
08:34:19.614326 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:20.024189 mirrors.club-internet.fr.www so-bo01-std.55692: .
20009449:20010897(1448) ack 174 win 49232 nop,nop,timestamp 3651037528
313698589 (DF)
08:34:20.024210 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:20.844464 mirrors.club-internet.fr.www so-bo01-std.55692: .
20009449:20010897(1448) ack 174 win 49232 nop,nop,timestamp 3651037610
313698589 (DF)
08:34:20.844485 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:22.485887 mirrors.club-internet.fr.www so-bo01-std.55692: .
20009449:20010897(1448) ack 174 win 49232 nop,nop,timestamp 3651037774
313698589 (DF)
08:34:22.485907 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:24.234738 so-bo01-std.55692 mirrors.club-internet.fr.www: F 174:174(0)
ack 20009449 win 1851 nop,nop,timestamp 313699744 3651037482 (DF)
08:34:24.235872 mirrors.club-internet.fr.www so-bo01-std.55692: . ack 175
win 49232 nop,nop,timestamp 3651037949 313699744 (DF)
On the internal interfaces, I see nothing related to the host unreachable,
just a Reset after a while from the server.
- If I pfctl -d, everything works
- If I remove all the blocks statement in the pf.conf, it do not work
- If I rate limit the download to 50 ko/s, then I still have unreachable but
it able to recover, above and up to 100Mo, it would fail and the transfer
stall.
- If I create an empty rules file, then it works
Here are the two rules:
# Production Firewall vers le Second FireWall
service_granted={domain, ntp, smtp, snmp, http}
block out log on $if_interco all label Protection vers le Back
pass in on $if_interco proto {tcp, udp} from {$net_back, $net_interco} to any
port $service_granted keep state label Back Office vers l'Internet
Please advise
Regarde
Lio
Alionis
OpenBSD 4.1 crashed, pfsync problems??
Hi all, Last night my openbsd 4.1 has crashed and I don't know why. I am using this openbsd as a part of two carped firewalls. Crash dump: kernel: page fault trap code=0 Stopped at pfsync_insert_net_state+0x451: movl 0(%eax,%edx,4),%edx Show panic: the kernel did not panic Trace log: pfsync_insert_net_state(da2ff926,1,1e0,d08d4d48) at pfsync_insert_net_state+0x451 pfsync_input(da0e6d00,14,0,0,d2975030) at pfsync_input+0x3ef ipv4_input(da0e6d00,d297bc80,0,d08d3000,30) at ipv4_input+0x511 ipintr(d0200058,10,d08d0010,d03c0010,d08d3000) at ipintr+0x7e Bad frame pointer: 0xd08d4e24 Dump shows a problem with pfsync interface, and I think on two posible problems: network interface or problem with switches. Output of dmesg: OpenBSD 4.1 (FWCLUSTER02) #0: Thu May 3 09:38:24 CEST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/FWCLUSTER02 cpu0: Intel(R) Pentium(R) 4 CPU 3.20GHz (GenuineIntel 686-class) 3.21 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID,xTPR real mem = 2146795520 (2096480K) avail mem = 1951932416 (1906184K) using 4278 buffers containing 107462656 bytes (104944K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+ BIOS, date 02/02/04, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xfb030 (83 entries) bios0: Dell Computer Corporation PowerEdge 750 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc570/144 (7 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 6300ESB LPC rev 0x00) pcibios0: PCI bus #4 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x5600 0xce800/0x1000 0xec000/0x4000! acpi at mainbus0 not configured cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82875P Host rev 0x02 ppb0 at pci0 dev 3 function 0 Intel 82875P PCI-CSA rev 0x02 pci1 at ppb0 bus 1 em0 at pci1 dev 1 function 0 Intel PRO/1000CT (82547GI) rev 0x00: irq 3, address 00:c0:9f:3d:0e:b5 ppb1 at pci0 dev 28 function 0 Intel 6300ESB PCIX rev 0x02 pci2 at ppb1 bus 2 ppb2 at pci2 dev 1 function 0 IBM 133 PCIX-PCIX rev 0x02 pci3 at ppb2 bus 3 em1 at pci3 dev 4 function 0 Intel PRO/1000MT QP (82546EB) rev 0x01: irq 11, address 00:04:23:b8:4c:bc em2 at pci3 dev 4 function 1 Intel PRO/1000MT QP (82546EB) rev 0x01: irq 11, address 00:04:23:b8:4c:bd em3 at pci3 dev 6 function 0 Intel PRO/1000MT QP (82546EB) rev 0x01: irq 11, address 00:04:23:b8:4c:be em4 at pci3 dev 6 function 1 Intel PRO/1000MT QP (82546EB) rev 0x01: irq 11, address 00:04:23:b8:4c:bf uhci0 at pci0 dev 29 function 0 Intel 6300ESB USB rev 0x02: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 6300ESB USB rev 0x02: irq 10 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered Intel 6300ESB WDT rev 0x02 at pci0 dev 29 function 4 not configured Intel 6300ESB APIC rev 0x02 at pci0 dev 29 function 5 not configured ehci0 at pci0 dev 29 function 7 Intel 6300ESB USB rev 0x02: irq 7 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 uhub2: Intel EHCI root hub, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered ppb3 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0x0a pci4 at ppb3 bus 4 em5 at pci4 dev 2 function 0 Intel PRO/1000MT (82541GI) rev 0x00: irq 10, address 00:c0:9f:3d:0e:b6 ahc0 at pci4 dev 3 function 0 Adaptec AHA-3960D U160 rev 0x01: irq 11 scsibus0 at ahc0: 16 targets sd0 at scsibus0 targ 0 lun 0: SEAGATE, ST336607LW, DS09 SCSI3 0/direct fixed sd0: 34732MB, 49855 cyl, 2 head, 713 sec, 512 bytes/sec, 71132959 sec total ahc1 at pci4 dev 3 function 1 Adaptec AHA-3960D U160 rev 0x01: irq 10 scsibus1 at ahc1: 16 targets vga1 at pci4 dev 14 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ichpcib0 at pci0 dev 31 function 0 Intel 6300ESB LPC rev 0x02 pciide0 at pci0 dev 31 function 2 Intel 6300ESB SATA rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility atapiscsi0 at pciide0 channel 0 drive 0 scsibus2 at atapiscsi0: 2 targets cd0 at scsibus2 targ 0 lun 0: TEAC, CD-224E, K.9A SCSI0 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 ichiic0 at pci0 dev 31 function 3 Intel 6300ESB SMBus rev 0x02: SMBus disabled isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pccom0 at isa0 port
open(hd0a:/etc/boot.conf): Invalid argument
I've installed OpenBSD4.1 from the 3 CD set which I purchased shortly after it was released and have been running it on and off ever since. However, this morning I tried to boot it and it came up with the above error (full error listing below). I re-installed the whole OS yesterday (everything except bsd.mp and game41.tgz) and it was working fine. The only thing I did after re-install was add a few packages and ports and compile the LookXP source packages from http://lxp.sourceforge.net. I have not knowingly touched the boot.conf file at all so I'm at a loss as to how the above error is showing. I have read the biosboot(8) man page but it didn't help. I am new to OpenBSD having come from a brief linux background and would appreciate any help. I could always simply re-install OpenBSD4.1 again but this would be a last resort as: i) I'd like to know what the cause of the problem is and how to fix it - in case it happens again; ii) I wouldn't learn anything if I simply reinstalled everytime; and iii) I've spent a lot of time configuring icewm to get it like I want and am loathed to go through this process again. The full error list I'm getting is: Loading... probing: pc0 apm mem[632K 2046M a20=on] disk: fd0 hd0+* OpenBSD/i386 BOOT 2.13 open(hd0a:/etc/boot.conf): Invalid argument boot booting hd0a:/bsd: open hd0a:/bsd: Invalid argument failed(22). will try /obsd boot booting hda0:/obsd: open hda0a:/obsd: Invalid argument failed(22). will try /bsd.old boot booting hda0:/bsd.old: open hda0a:/bsd.old: Invalid argument failed(22). will try /bsd boot booting hda0:/bsd: open hda0a:/bsd: Invalid argument failed(22). will try /obsd boot booting hda0:/obsd: open hda0a:/obsd: Invalid argument failed(22). will try /bsd.old boot booting hda0:/bsd.old: open hda0a:/bsd.old: Invalid argument failed(22). will try /bsd Turning timeout off. boot _
Re: Quad ethernet card
* Chris Cappuccio [EMAIL PROTECTED] [2007-06-06 21:17]: Claudio Jeker [EMAIL PROTECTED] wrote: Sis(4) is plaing in the same league as rl(4). It works fine and I never had porblems with it but I would never use it in a router with high performance needs. No, the interface on sis is not as bad as the old rl chips. Also, the 83816 sis supports interrupt hold-off (like newer fxp). With recent openbsd changes, (such as only running nanotime() on interrupt instead of per-packet) the interrupt hold off feature now makes a significant difference under openbsd. int mitigation has always made quite some difference, but now it is even more, I agree. nontheless sis is not far up from rl. far away from the real ones. Off topic, newer if_vr chips (like 6105M used in new beta boards from Soekris and PCEngines) now have hw checksum, and they also fix the main performance problems with the older design which required multiple memory copies. So, we need to import driver enhancements from freebsd to take advantage of it. One thing vr doesn't support is an interrupt hold off which disqualifies it for any serious routing tasks. -- Henning Brauer, [EMAIL PROTECTED], [EMAIL PROTECTED] BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting - Hamburg Amsterdam
Re: OpenBSD 4.1 crashed, pfsync problems??
Marc Balmer wrote: * carlopmart wrote: Hi all, Last night my openbsd 4.1 has crashed and I don't know why. I am using this openbsd as a part of two carped firewalls. Crash dump: kernel: page fault trap code=0 Stopped at pfsync_insert_net_state+0x451: movl 0(%eax,%edx,4),%edx Show panic: the kernel did not panic Trace log: pfsync_insert_net_state(da2ff926,1,1e0,d08d4d48) at pfsync_insert_net_state+0x451 pfsync_input(da0e6d00,14,0,0,d2975030) at pfsync_input+0x3ef ipv4_input(da0e6d00,d297bc80,0,d08d3000,30) at ipv4_input+0x511 ipintr(d0200058,10,d08d0010,d03c0010,d08d3000) at ipintr+0x7e Bad frame pointer: 0xd08d4e24 Dump shows a problem with pfsync interface, and I think on two posible problems: network interface or problem with switches. Output of dmesg: OpenBSD 4.1 (FWCLUSTER02) #0: Thu May 3 09:38:24 CEST 2007 this is not a GENERIC kernel, god knows what you have changed, but noone can support custom kernels. [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/FWCLUSTER02 cpu0: Intel(R) Pentium(R) 4 CPU 3.20GHz (GenuineIntel 686-class) 3.21 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID,xTPR real mem = 2146795520 (2096480K) avail mem = 1951932416 (1906184K) using 4278 buffers containing 107462656 bytes (104944K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+ BIOS, date 02/02/04, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xfb030 (83 entries) bios0: Dell Computer Corporation PowerEdge 750 pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc570/144 (7 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 6300ESB LPC rev 0x00) pcibios0: PCI bus #4 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x5600 0xce800/0x1000 0xec000/0x4000! acpi at mainbus0 not configured cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82875P Host rev 0x02 ppb0 at pci0 dev 3 function 0 Intel 82875P PCI-CSA rev 0x02 pci1 at ppb0 bus 1 em0 at pci1 dev 1 function 0 Intel PRO/1000CT (82547GI) rev 0x00: irq 3, address 00:c0:9f:3d:0e:b5 ppb1 at pci0 dev 28 function 0 Intel 6300ESB PCIX rev 0x02 pci2 at ppb1 bus 2 ppb2 at pci2 dev 1 function 0 IBM 133 PCIX-PCIX rev 0x02 pci3 at ppb2 bus 3 em1 at pci3 dev 4 function 0 Intel PRO/1000MT QP (82546EB) rev 0x01: irq 11, address 00:04:23:b8:4c:bc em2 at pci3 dev 4 function 1 Intel PRO/1000MT QP (82546EB) rev 0x01: irq 11, address 00:04:23:b8:4c:bd em3 at pci3 dev 6 function 0 Intel PRO/1000MT QP (82546EB) rev 0x01: irq 11, address 00:04:23:b8:4c:be em4 at pci3 dev 6 function 1 Intel PRO/1000MT QP (82546EB) rev 0x01: irq 11, address 00:04:23:b8:4c:bf uhci0 at pci0 dev 29 function 0 Intel 6300ESB USB rev 0x02: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 29 function 1 Intel 6300ESB USB rev 0x02: irq 10 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered Intel 6300ESB WDT rev 0x02 at pci0 dev 29 function 4 not configured Intel 6300ESB APIC rev 0x02 at pci0 dev 29 function 5 not configured ehci0 at pci0 dev 29 function 7 Intel 6300ESB USB rev 0x02: irq 7 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 uhub2: Intel EHCI root hub, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered ppb3 at pci0 dev 30 function 0 Intel 82801BA AGP rev 0x0a pci4 at ppb3 bus 4 em5 at pci4 dev 2 function 0 Intel PRO/1000MT (82541GI) rev 0x00: irq 10, address 00:c0:9f:3d:0e:b6 ahc0 at pci4 dev 3 function 0 Adaptec AHA-3960D U160 rev 0x01: irq 11 scsibus0 at ahc0: 16 targets sd0 at scsibus0 targ 0 lun 0: SEAGATE, ST336607LW, DS09 SCSI3 0/direct fixed sd0: 34732MB, 49855 cyl, 2 head, 713 sec, 512 bytes/sec, 71132959 sec total ahc1 at pci4 dev 3 function 1 Adaptec AHA-3960D U160 rev 0x01: irq 10 scsibus1 at ahc1: 16 targets vga1 at pci4 dev 14 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ichpcib0 at pci0 dev 31 function 0 Intel 6300ESB LPC rev 0x02 pciide0 at pci0 dev 31 function 2 Intel 6300ESB SATA rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility atapiscsi0 at pciide0 channel 0 drive 0 scsibus2 at atapiscsi0: 2 targets cd0 at scsibus2 targ 0 lun 0: TEAC, CD-224E, K.9A SCSI0 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 ichiic0 at pci0 dev 31 function 3 Intel 6300ESB SMBus rev 0x02: SMBus disabled isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0
Re: semi transparent spamd-bridge
Mark Pecaut wrote: On 6/6/07, Christoph Schneeberger [EMAIL PROTECTED] wrote: case 1: src host is whitelisted, connection is allowed to 1.1.1.35, everything works fine. case 2: src host is grey-/blacklisted and therefor redirected to 127.0.0.1, in this case i get just a timeout when i try to telnet to port 25 of 1.1.1.35 which as I understand is caused by many reasons, among them that the src hosts expects tcp packets only from 1.1.1.35 and not from 1.1.1.5 which is the only ip from which the bridges spamd could use to talk to the src host (sender mta). Try some tcpdump'ing to see where it is failing, for example on lo0 or $ext_if. Add some 'log' to your rules. can the bridge talk to other internet hosts? Does it have a default gateway? Is spamd actually running? spamlogd? Is that the complete pf.conf? Give more complete information, including the obvious stuff. -Mark The setup is as follows (real, non-RFC1918 network is replaced by 1.1.1.X, the last octet is the one I actually use): | Mailsrv | | Bridge | | src mta | | |-| |-| | | 1.1.1.35 | | 1.1.1.5 | | 1.1.1.9 | The bridges IP is attached to if facing src mta. The complete pf.conf looks like: -- ext_if=fxp0 int_if=xl0 table spamd persist table spamd-white persist table whitelist persist file /etc/whitelist.txt rdr pass on $ext_if inet proto tcp from spamd to any port smtp - 127.0.0.1 port 8025 rdr pass on $ext_if inet proto tcp from !spamd-white to any port smtp - 127.0.0.1 port 8025 pass in log on $ext_if route-to lo0 inet proto tcp from any to 127.0.0.1 port 8025 keep state -- The bridge has a default gate of 1.1.1.1 and is able to ping i.e. www.openbsd.org. The bridge can also ping ips of either side of it and the bridge can be pinged from both sides and ssh'd into from both sides. When I telnet to 1.1.1.35 25 i get a timeout and nothing is captured wiht tcpdump -i lo0. When I dump with tcpdump -i fxp0 host 1.1.1.9 I only see the Syn Packet, repeated for a handful of times (I stopped it after 5). When I dump with tcpdump -i xl0 I see the same Syn Packet, but this time from 1.1.1.9 to 127.0.0.1 port 8025. I then checked on the bridge if spamd is listening with telnet 127.0.0.1 8025 which gave me the stuttering 250 msg, so spamd seems to be running. The part I am still completely missing is that even spamd talks to 1.1.1.9, it would have to talk to it from its ip 1.1.1.5 but 1.1.1.9 expects a Sack from 1.1.1.35 and I believe it would just discard a Sack from 1.1.1.5. So is the spamd/pf supposed to answer with the mailsrvs ip back when spamd talks ? Sorry for my confusion and thanks for the helping hands offered. Christoph -- Quis custodiet ipsos custodes?
Re: Pf Issue with a large number of Packet
I Think I have another piece of information, As the ping is very small, I
think there are too many packets going on at the same time. Therefore, the
system to check the states might not receive the packets in the right order
and therefore decide that certain packets arrived to early.
I hope it helps
Regards
Leo
Alionis
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lio
Goehrs
Sent: jeudi 7 juin 2007 09:35
To: misc@openbsd.org
Subject: Pf Issue with a large number of Packet
Hi All,
I am sorry to bother the list but I think I may have encountered a bug and I
would like to share with you guys. I have been using OpenBSD to build
Firewall
for a long time in solution with VLAN + CARP. When computers in the protected
network downloads a file in HTTP, everything works for the First 15 Mo then
it
stops.
When I tcpdump, On the external address, I get the folowing:
08:34:19.343833 mirrors.club-internet.fr.www so-bo01-std.55692: P
17637121:17638569(1448) ack 174 win 49232 nop,nop,timestamp 3651037459
313698521 (DF)
08:34:19.343870 so-bo01-std.55692 mirrors.club-internet.fr.www: . ack
17634225 win 1810 nop,nop,timestamp 313698522 3651037459 (DF)
08:34:19.614303 mirrors.club-internet.fr.www so-bo01-std.55692: P
20054337:20055785(1448) ack 174 win 49232 nop,nop,timestamp 3651037487
313698589 (DF)
08:34:19.614326 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:20.024189 mirrors.club-internet.fr.www so-bo01-std.55692: .
20009449:20010897(1448) ack 174 win 49232 nop,nop,timestamp 3651037528
313698589 (DF)
08:34:20.024210 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:20.844464 mirrors.club-internet.fr.www so-bo01-std.55692: .
20009449:20010897(1448) ack 174 win 49232 nop,nop,timestamp 3651037610
313698589 (DF)
08:34:20.844485 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:22.485887 mirrors.club-internet.fr.www so-bo01-std.55692: .
20009449:20010897(1448) ack 174 win 49232 nop,nop,timestamp 3651037774
313698589 (DF)
08:34:22.485907 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:24.234738 so-bo01-std.55692 mirrors.club-internet.fr.www: F
174:174(0)
ack 20009449 win 1851 nop,nop,timestamp 313699744 3651037482 (DF)
08:34:24.235872 mirrors.club-internet.fr.www so-bo01-std.55692: . ack 175
win 49232 nop,nop,timestamp 3651037949 313699744 (DF)
On the internal interfaces, I see nothing related to the host unreachable,
just a Reset after a while from the server.
- If I pfctl -d, everything works
- If I remove all the blocks statement in the pf.conf, it do not work
- If I rate limit the download to 50 ko/s, then I still have unreachable but
it able to recover, above and up to 100Mo, it would fail and the transfer
stall.
- If I create an empty rules file, then it works
Here are the two rules:
# Production Firewall vers le Second FireWall
service_granted={domain, ntp, smtp, snmp, http}
block out log on $if_interco all label Protection vers le Back
pass in on $if_interco proto {tcp, udp} from {$net_back, $net_interco} to any
port $service_granted keep state label Back Office vers l'Internet
Please advise
Regarde
Lio
Alionis
Re: Pf Issue with a large number of Packet
Hi All,
Well, I confirm that there is a problem, when the packets arrives to fast
(about 25 000 pks/s), then it is likely that the packet does not arrive in the
right order and then the system checking the validity of the number of the
packet breaks and blocks legitimate traffic.
Regards
Lio Goehrs
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lio
Goehrs
Sent: jeudi 7 juin 2007 09:35
To: misc@openbsd.org
Subject: Pf Issue with a large number of Packet
Hi All,
I am sorry to bother the list but I think I may have encountered a bug and I
would like to share with you guys. I have been using OpenBSD to build
Firewall
for a long time in solution with VLAN + CARP. When computers in the protected
network downloads a file in HTTP, everything works for the First 15 Mo then
it
stops.
When I tcpdump, On the external address, I get the folowing:
08:34:19.343833 mirrors.club-internet.fr.www so-bo01-std.55692: P
17637121:17638569(1448) ack 174 win 49232 nop,nop,timestamp 3651037459
313698521 (DF)
08:34:19.343870 so-bo01-std.55692 mirrors.club-internet.fr.www: . ack
17634225 win 1810 nop,nop,timestamp 313698522 3651037459 (DF)
08:34:19.614303 mirrors.club-internet.fr.www so-bo01-std.55692: P
20054337:20055785(1448) ack 174 win 49232 nop,nop,timestamp 3651037487
313698589 (DF)
08:34:19.614326 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:20.024189 mirrors.club-internet.fr.www so-bo01-std.55692: .
20009449:20010897(1448) ack 174 win 49232 nop,nop,timestamp 3651037528
313698589 (DF)
08:34:20.024210 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:20.844464 mirrors.club-internet.fr.www so-bo01-std.55692: .
20009449:20010897(1448) ack 174 win 49232 nop,nop,timestamp 3651037610
313698589 (DF)
08:34:20.844485 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:22.485887 mirrors.club-internet.fr.www so-bo01-std.55692: .
20009449:20010897(1448) ack 174 win 49232 nop,nop,timestamp 3651037774
313698589 (DF)
08:34:22.485907 so-knox01a-std mirrors.club-internet.fr: icmp: host
so-bo01-std unreachable
08:34:24.234738 so-bo01-std.55692 mirrors.club-internet.fr.www: F
174:174(0)
ack 20009449 win 1851 nop,nop,timestamp 313699744 3651037482 (DF)
08:34:24.235872 mirrors.club-internet.fr.www so-bo01-std.55692: . ack 175
win 49232 nop,nop,timestamp 3651037949 313699744 (DF)
On the internal interfaces, I see nothing related to the host unreachable,
just a Reset after a while from the server.
- If I pfctl -d, everything works
- If I remove all the blocks statement in the pf.conf, it do not work
- If I rate limit the download to 50 ko/s, then I still have unreachable but
it able to recover, above and up to 100Mo, it would fail and the transfer
stall.
- If I create an empty rules file, then it works
Here are the two rules:
# Production Firewall vers le Second FireWall
service_granted={domain, ntp, smtp, snmp, http}
block out log on $if_interco all label Protection vers le Back
pass in on $if_interco proto {tcp, udp} from {$net_back, $net_interco} to any
port $service_granted keep state label Back Office vers l'Internet
Please advise
Regarde
Lio
Alionis
spamd-setup: pfctl: Cannot allocate memory
Hi All, According to http://www.openbsd.org/spamd/ I have added a couple of new blacklists to my original spamd.conf, previously I had only spews1, china, and korea, and there was no problem. But now pfctl gives me an error: # /usr/libexec/spamd-setup -d Getting http://www.openbsd.org/spamd/spews_list_level1.txt.gz blacklist spews1 14482 entries Getting http://www.openbsd.org/spamd/spews_list_level2.txt.gz blacklist spews2 18103 entries Getting http://www.openbsd.org/spamd/chinacidr.txt.gz blacklist china 431 entries Getting http://www.openbsd.org/spamd/koreacidr.txt.gz blacklist korea 270 entries Getting http://www.openbsd.org/spamd/traplist.gz blacklist uatraplist 45380 entries Getting http://www.openbsd.org/spamd/nixspam.gz blacklist nixspam 39983 entries # pfctl: Cannot allocate memory. I know that there's not much shared memory in my system (and it's a slow machine), but there is plenty of swap area. While this command was running, I've been watching shared memory and swap usages with top, I see that kernel starts swapping, and frees up as much as 20MB shared memory, so spamd-setup fetches the lists successfully, but pfctl complains at the end (probably kernel cannot swap anything out anymore). To test if shared memory is the problem, if I stop httpd running on the same system, thus free at least 30MB RAM, spamd-setup (and pfctl at the end) runs without any problem, all the blacklists enabled. To avoid this issue I have to disable uatraplist and nixspam, which are obviously very large lists. Is there anything I can do in this case? (Other than, stopping httpd for example, during each spamd-setup run, or installing more RAM, which is out of the question.) Relevant head of dmesg may be: OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 166 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX cpu0: F00F bug workaround installed real mem = 100233216 (97884K) avail mem = 83529728 (81572K) OT: btw, I'm using www.openbsd.org to download these lists, because I've checked at least a couple of mirrors, they don't have them. I hope that's ok.
openldap-client / cyrus-sasl-2.1.21p3-ldap problem
Hello, I have a strange problem: --8 # pkg_add -i cyrus-sasl-2.1.21p3-ldap Error from http://ftp-stud.fht-esslingen.de/pub/OpenBSD/4.1/packages/i386/: ftp: Writing -: Broken pipe Can't install cyrus-sasl-2.1.21p3-ldap: can't resolve openldap-client-2.3.33 Can't install openldap-client-2.3.33: can't resolve cyrus-sasl-2.1.21p3-ldap Error from http://ftp-stud.fht-esslingen.de/pub/OpenBSD/4.1/packages/i386/: ftp: Writing -: Broken pipe Can't install cyrus-sasl-2.1.21p3-ldap: can't resolve openldap-client-2.3.33 # pkg_add -i openldap-client-2.3.33 Error from http://ftp-stud.fht-esslingen.de/pub/OpenBSD/4.1/packages/i386/: ftp: Writing -: Broken pipe Ambiguous: choose dependency for openldap-client-2.3.33: 0: cyrus-sasl-2.1.21p3 1: cyrus-sasl-2.1.21p3-db4 2: cyrus-sasl-2.1.21p3-ldap 3: cyrus-sasl-2.1.21p3-mysql Your choice: 2 Can't install openldap-client-2.3.33: can't resolve cyrus-sasl-2.1.21p3-ldap Can't install cyrus-sasl-2.1.21p3-ldap: can't resolve openldap-client-2.3.33 Error from http://ftp-stud.fht-esslingen.de/pub/OpenBSD/4.1/packages/i386/: ftp: Writing -: Broken pipe Can't install openldap-client-2.3.33: can't resolve cyrus-sasl-2.1.21p3-ldap --8 Looks like openldap depends on cyrus-sasl and vice versa. I found other with the same problem: http://archives.neohapsis.com/archives/openbsd/2007-05/0454.html Quote: I've found a relatively dirty workaround for this. i) install cyrus-sasl-2.1.21p3 ii) install openldap-client-2.3.33 iii) pkg_add -r cyrus-sasl-2.1.21p3-ldap This brings me another question. Replace parameter '-r' to pkg_add gracefully replaces an unflavored package with another flavored one. Is this an expected behaviour? Can somebody answer that question? I'll the workaround, but looks like a package problem to me. Regards Hagen Volpers
Re: Pf Issue with a large number of Packet
On 2007/06/07 11:57, Lio Goehrs wrote: - If I pfctl -d, everything works - If I remove all the blocks statement in the pf.conf, it do not work if you can post dmesg and some relevant 'pass' rules, that might help.
WRAP stalling at kernel entry point via pxeboot/tftp
List, I am attempting to get pxeboot working on a WRAP board with openbsd 4.1 generic however the loading of either kernel, bsd or bsd.rd, is stalling. I've search around the archives and have taken the steps mentioned here: http://marc.info/?l=openbsd-miscm=117978591113386w=2 I have updated the BIOS on the wrap board with a PXE.BIN downloaded from rom-o-matic.net which uses etherboot 5.4.3 and the NIC type natsemi:dp83815. below is the output from the wrap board: PC Engines WRAP.2B/2C v1.11 640 KB Base Memory 130048 KB Extended Memory 01F0 - no drive found ! ROM segment 0xe000 length 0x8000 reloc 0x Etherboot 5.4.3 (GPL) http://etherboot.org Drivers: NATSEMI Images: NBI ELF Multiboot a.out PXE Exports: PXE Protocols: DHCP TFTP Relocating _text from: [0008bb80,0009fd90) to [07eebdf0,07f0) Boot from (N)etwork (D)isk or (Q)uit? N Probing pci nic... [dp83815] natsemi_probe: MAC addr 00:0D:B9:04:47:F8 at ioaddr 0X1000 natsemi_probe: Vendor:0X100B Device:0X0020 dp83815: Transceiver default autoneg. enabled, advertise 100 full duplex. dp83815: Transceiver status 7869 advertising 05E1 dp83815: Setting full-duplex based on negotiated link capability. Searching for server (DHCP). Me: 192.168.1.200, DHCP: 192.168.1.1, TFTP: 192.168.1.1, Gateway 192.168.1.1 Loading 192.168.1.1:pxeboot ...(PXE)done probing: pc0 com0 pci pxe![2.1] mem[640K 125M a20=on] disk: net: mac 00:0d:b9:04:47:f8, ip 192.168.1.200, server 192.168.1.1 OpenBSD/i386 PXEBOOT 1.11 boot bsd1.rd booting tftp:bsd.rd: 4679892+742564 [52+169536+154918]=0x57b288 dp83815: Setting full-duplex based on negotiated link capability. entry point at 0x200120 the loading stalls at this point, tcpdump shows the following: 11:48:27.321421 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:28.319634 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:30.319653 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:34.319901 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:42.320416 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:47.320663 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:48.320728 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:49.320787 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:58.325352 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:59.325417 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:49:00.325480 arp who-has 192.168.1.200 tell 192.168.1.1 I have used a boot.conf which contains this: set tty pc0 I have tried com0 and the output freezes whilst I type bsd.rd Many thanks for your time
Re: Pf Issue with a large number of Packet
if you can post dmesg and some relevant 'pass' rules, that might help.
Sure, So far, I have started my test and I have far less problems now but I
don't think the solution is fine. As of Version 4.1, the rule keep state flags
S/SA is by default.
All my problems went away when I used the following rules:
pass out on $if_prod proto tcp from any to so_prod_ad port {http, https} no
state flags any label Internet vers la prod AD
pass in on $if_prod proto tcp from so_prod_ad port {http, https} to any no
state flags any label Reply From AD to the Internet
If go on keep state, then, when I launch a download at 25 Mo/s, then it
downloads about 35 Mo then stops and my log get full of
Jun 7 12:15:26 so-knox01a-std /bsd: pf: BAD state: TCP 193.189.125.227:51872
193.189.125.227:51872 77.72.91.10:80 [lo=936647122 high=936652914 win=5840
modulator=0] [lo=2657626173 high=2657632013 win=5792 modulator=0] 4:2 SA
seq=2660626928 (2660626928) ack=936647122 len=0 ackskew=0 pkts=3:1 dir=in,rev
Jun 7 12:15:26 so-knox01a-std /bsd: pf: State failure on: 1 | 5
Jun 7 12:15:26 so-knox01a-std /bsd: pf: BAD state: TCP 193.189.125.227:51876
193.189.125.227:51876 77.72.91.10:80 [lo=941137405 high=941143197 win=5840
modulator=0] [lo=2659274591 high=2659280431 win=5792 modulator=0] 4:2 SA
seq=2662275452 (2662275452) ack=941137405 len=0 ackskew=0 pkts=3:1 dir=in,rev
Jun 7 12:15:26 so-knox01a-std /bsd: pf: State failure on: 1 | 5
Jun 7 12:15:26 so-knox01a-std /bsd: pf: BAD state: TCP 193.189.125.227:51880
193.189.125.227:51880 77.72.91.10:80 [lo=941037484 high=941043276 win=5840
modulator=0] [lo=2663170100 high=2663175940 win=5792 modulator=0] 4:2 SA
seq=2666170841 (2666170841) ack=941037484 len=0 ackskew=0 pkts=3:1 dir=in,rev
Jun 7 12:15:26 so-knox01a-std /bsd: pf: State failure on: 1 | 5
From my understanding, State failure on: 1 means the sequence number was too
much ahead, based on the RFC. But, Today, with adaptive TCP Windows, we can
have so many packets going thru at the same time.
Leo
Re: OT: Michigan BSD user group
On 6/5/07, James Turner [EMAIL PROTECTED] wrote: I was wondering if anyone knows of any BSD user groups located in Michigan? I'm pretty sure the Southeast Michigan group is no longer meeting. Also would anyone in the Detroit/Ann Arbor area be interested in getting a BSD user group started? Feel free to contact me off list if you might be interested. I tried to contact you off-list but your mailserver is rejecting it... I've been interested in starting a Flint area unix users group. I can round up a good handful of people to make it to BUG's in the Detroit area.
Re: /usr/obj partition AWOL
On Tue, 5 Jun 2007, Emilio Perea wrote: On Tue, Jun 05, 2007 at 07:51:48AM +0200, Otto Moerbeek wrote: There were some validations checkc added to partitions. If a bad partition is found, it will be marked unused. The checks were a little to strict for some cases. A fix for that went in yesterday, so try a new snap. If the problem persists, please report with full disklabel output. The problem showed up on the latest snapshot as of now, which may well have been built before the fix you mention was incorporated. The home PC running -current has not had a problem since Saturday afternoon. The daily insecurity reports show four changes in this partition during the last couple of months. (Note that since this is on /usr/obj on a PC running -current, newfs is run just about every day.) It seems funny that on May 29 the fsize and bsize were changed to 0, but nothing weird happened until the day after they were changed to what appeared to be more reasonable numbers. Anyhow, in case the information is useful, the insecurity messages and current disklabel follow: == sd0 diffs (-OLD +NEW) == --- /var/backups/disklabel.sd0.currentFri Apr 21 01:31:35 2006 +++ /var/backups/disklabel.sd0Tue Apr 17 01:31:10 2007 @@ -26,4 +26,4 @@ d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 - 1647 e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 - 2059 f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 - 5356 - g: 4139682 13628208 4.2BSD 2048 16384 480 # Cyl 5357 - 6984* + g: 4139682 13628208 4.2BSD 2048 163841 # Cyl 5357 - 6984* The cpg change is due to making newfs cylinder unaware. . == sd0 diffs (-OLD +NEW) == --- /var/backups/disklabel.sd0.currentTue Apr 17 01:31:10 2007 +++ /var/backups/disklabel.sd0Wed May 30 01:32:08 2007 @@ -26,4 +26,4 @@ d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 - 1647 e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 - 2059 f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 - 5356 - g: 4139682 13628208 4.2BSD 2048 163841 # Cyl 5357 - 6984* + g: 4139682 13628208 4.2BSD 0 01 # Cyl 5357 - 6984* Here you are running with a new kernel, but userland is still old. Hense the 0 fsize and bsize == sd0 diffs (-OLD +NEW) == --- /var/backups/disklabel.sd0.currentWed May 30 01:32:08 2007 +++ /var/backups/disklabel.sd0Fri Jun 1 01:32:15 2007 @@ -26,4 +26,4 @@ d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 - 1647 e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 - 2059 f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 - 5356 - g: 4139682 13628208 4.2BSD 0 01 # Cyl 5357 - 6984* + g: 4139682 13628208 4.2BSD 2048 81921 # Cyl 5357 - 6984* newfs is run, but it is still using the old struct partition format. Hence the wrong fsize anf bsize. == sd0 diffs (-OLD +NEW) == --- /var/backups/disklabel.sd0.currentFri Jun 1 01:32:15 2007 +++ /var/backups/disklabel.sd0Tue Jun 5 01:32:10 2007 @@ -26,4 +26,4 @@ d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 - 1647 e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 - 2059 f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 - 5356 - g: 4139682 13628208 4.2BSD 2048 81921 # Cyl 5357 - 6984* + g: 4139682 13628208 4.2BSD 2048 163841 # Cyl 5357 - 6984* And here things are back in shape. # Inside MBR partition 3: type A6 start 63 size 17767827 # /dev/rsd0c: type: SCSI disk: SCSI disk label: ST39102LW flags: bytes/sector: 512 sectors/track: 212 tracks/cylinder: 12 sectors/cylinder: 2544 cylinders: 6962 total sectors: 17783240 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 209619363 4.2BSD 2048 16384 480 # Cyl 0*- 823 b: 1048128 2096256swap # Cyl 824 - 1235 c: 17783240 0 unused 0 0 # Cyl 0 - 6990* d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 - 1647 e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 - 2059 f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 - 5356 g: 4139682 13628208 4.2BSD 2048 163841 # Cyl 5357 - 6984* We have seen some reports now on disappearing paritions. On sparc and
Re: WRAP stalling at kernel entry point via pxeboot/tftp
Hello, your boot.conf should look like this: set tty com0 stty com0 38400 set timeout 5 Last time I booted wrap via pxe was 3.9, but this should work. Regards Hagen Volpers -Urspr|ngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von mgb Gesendet: Donnerstag, 7. Juni 2007 12:51 An: misc@openbsd.org Betreff: WRAP stalling at kernel entry point via pxeboot/tftp List, I am attempting to get pxeboot working on a WRAP board with openbsd 4.1 generic however the loading of either kernel, bsd or bsd.rd, is stalling. I've search around the archives and have taken the steps mentioned here: http://marc.info/?l=openbsd-miscm=117978591113386w=2 I have updated the BIOS on the wrap board with a PXE.BIN downloaded from rom-o-matic.net which uses etherboot 5.4.3 and the NIC type natsemi:dp83815. below is the output from the wrap board: PC Engines WRAP.2B/2C v1.11 640 KB Base Memory 130048 KB Extended Memory 01F0 - no drive found ! ROM segment 0xe000 length 0x8000 reloc 0x Etherboot 5.4.3 (GPL) http://etherboot.org Drivers: NATSEMI Images: NBI ELF Multiboot a.out PXE Exports: PXE Protocols: DHCP TFTP Relocating _text from: [0008bb80,0009fd90) to [07eebdf0,07f0) Boot from (N)etwork (D)isk or (Q)uit? N Probing pci nic... [dp83815] natsemi_probe: MAC addr 00:0D:B9:04:47:F8 at ioaddr 0X1000 natsemi_probe: Vendor:0X100B Device:0X0020 dp83815: Transceiver default autoneg. enabled, advertise 100 full duplex. dp83815: Transceiver status 7869 advertising 05E1 dp83815: Setting full-duplex based on negotiated link capability. Searching for server (DHCP). Me: 192.168.1.200, DHCP: 192.168.1.1, TFTP: 192.168.1.1, Gateway 192.168.1.1 Loading 192.168.1.1:pxeboot ...(PXE)done probing: pc0 com0 pci pxe![2.1] mem[640K 125M a20=on] disk: net: mac 00:0d:b9:04:47:f8, ip 192.168.1.200, server 192.168.1.1 OpenBSD/i386 PXEBOOT 1.11 boot bsd1.rd booting tftp:bsd.rd: 4679892+742564 [52+169536+154918]=0x57b288 dp83815: Setting full-duplex based on negotiated link capability. entry point at 0x200120 the loading stalls at this point, tcpdump shows the following: 11:48:27.321421 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mf i_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devic es.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup. qsphy_ca.shmmaxpgs. 11:48:28.319634 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mf i_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devic es.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup. qsphy_ca.shmmaxpgs. 11:48:30.319653 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mf i_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devic es.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup. qsphy_ca.shmmaxpgs. 11:48:34.319901 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mf i_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devic es.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup. qsphy_ca.shmmaxpgs. 11:48:42.320416 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mf i_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devic es.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup. qsphy_ca.shmmaxpgs. 11:48:47.320663 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:48.320728 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:49.320787 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:58.325352 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:59.325417 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:49:00.325480 arp who-has 192.168.1.200 tell 192.168.1.1 I have used a boot.conf which contains this: set tty pc0 I have tried com0 and the output freezes whilst I type bsd.rd Many thanks for your time
Re: WRAP stalling at kernel entry point via pxeboot/tftp
* mgb wrote: List, I am attempting to get pxeboot working on a WRAP board with openbsd 4.1 generic however the loading of either kernel, bsd or bsd.rd, is stalling. I've search around the archives and have taken the steps mentioned here: http://marc.info/?l=openbsd-miscm=117978591113386w=2 I have updated the BIOS on the wrap board with a PXE.BIN downloaded from rom-o-matic.net which uses etherboot 5.4.3 and the NIC type natsemi:dp83815. below is the output from the wrap board: PC Engines WRAP.2B/2C v1.11 640 KB Base Memory 130048 KB Extended Memory 01F0 - no drive found ! ROM segment 0xe000 length 0x8000 reloc 0x Etherboot 5.4.3 (GPL) http://etherboot.org Drivers: NATSEMI Images: NBI ELF Multiboot a.out PXE Exports: PXE Protocols: DHCP TFTP Relocating _text from: [0008bb80,0009fd90) to [07eebdf0,07f0) Boot from (N)etwork (D)isk or (Q)uit? N Probing pci nic... [dp83815] natsemi_probe: MAC addr 00:0D:B9:04:47:F8 at ioaddr 0X1000 natsemi_probe: Vendor:0X100B Device:0X0020 dp83815: Transceiver default autoneg. enabled, advertise 100 full duplex. dp83815: Transceiver status 7869 advertising 05E1 dp83815: Setting full-duplex based on negotiated link capability. Searching for server (DHCP). Me: 192.168.1.200, DHCP: 192.168.1.1, TFTP: 192.168.1.1, Gateway 192.168.1.1 Loading 192.168.1.1:pxeboot ...(PXE)done probing: pc0 com0 pci pxe![2.1] mem[640K 125M a20=on] disk: net: mac 00:0d:b9:04:47:f8, ip 192.168.1.200, server 192.168.1.1 OpenBSD/i386 PXEBOOT 1.11 boot bsd1.rd booting tftp:bsd.rd: 4679892+742564 [52+169536+154918]=0x57b288 dp83815: Setting full-duplex based on negotiated link capability. entry point at 0x200120 the loading stalls at this point, tcpdump shows the following: maybe it just looks like it is stalled... try setting the console to com0: boot stty com0 9600 boot set tty com0 boot bsd.rd 11:48:27.321421 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:28.319634 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:30.319653 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:34.319901 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:42.320416 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:47.320663 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:48.320728 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:49.320787 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:58.325352 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:59.325417 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:49:00.325480 arp who-has 192.168.1.200 tell 192.168.1.1 I have used a boot.conf which contains this: set tty pc0 I have tried com0 and the output freezes whilst I type bsd.rd Many thanks for your time
Re: Kernel MINIROOTSIZE 8192 = No Boot
On Wed, Jun 06, 2007 at 01:39:47PM -0400, Brian A. Seklecki wrote: The 1st stage loader just resets the prom before the kernel load. Can anyone else confirm this? You don't even need to elfrdsetroot(8) to test. Just compile bsd.rd with MINIROOTSIZE=16384. I've been using 32768 on my 4.0 systems for the bsd-appliance project. I've tested it on an AMD Athalon, an AMD Geode, and a VMWare machine. you need to raise NKPTP also to say 8... cu -- paranoic mickey (my employers have changed but, the name has remained)
Re: AMD64 raid setup SATA - dmesg error/warning
Once that a device is flagged for autoconfig, you can safely move the config file for it away from /etc (that data is now stored in meta-data on disk) Otherwise it will try to configure it once automatically, then once manually (safely failing the latter) ~BAS On Thu, 7 Jun 2007, Webcharge wrote: Goodmorning, During boot my AMD64 machine with RAID setup shows me the following messages: raidctl: ioctl RAIDFRAME_CONFIGURE failed raid0: Device already configured! I have followed the instructions over at: http://www.eclectica.ca/howto/openbsd-software-raid-howto.php. Kernel additions to GENERIC are: option RAID_AUTOCONFIG pseudo-device raid 4 'raidctl -s' shows everything *seems* to be fine; I am not sure why I get the error and warning. I also noticed the writing to disk is rather slow compared to IDE disks on other machines; or so it seems. All this makes me concerned the install is not correct / trustworthy. Any advice is highly appreciated, please let me know if I should supply other info than that below. Thanks! -- # raidctl -s raid0 raid0 Components: /dev/wd0d: optimal /dev/wd1d: optimal No spares. Parity status: clean Reconstruction is 100% complete. Parity Re-write is 100% complete. Copyback is 100% complete. # cat /etc/raid0.conf START array 1 2 0 START disks /dev/wd0d /dev/wd1d START layout 128 1 1 1 START queue fifo 100 # cat /etc/fstab /dev/raid0a / ffs rw 1 1 /dev/raid0g /home ffs rw,nodev,nosuid 1 2 /dev/raid0e /tmp ffs rw,nodev,nosuid 1 2 /dev/raid0d /usr ffs rw,nodev 1 2 /dev/raid0f /var ffs rw,nodev,nosuid 1 2 # dmesg OpenBSD 4.1 (GENERIC.RAID) #0: Tue Jun 5 18:30:18 CEST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.RAID real mem = 1072164864 (1047036K) avail mem = 906080256 (884844K) using 22937 buffers containing 107425792 bytes (104908K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf (40 entries) bios0: Sun Microsystems Sun Fire(TM) X2100 acpi at mainbus0 not configured cpu0 at mainbus0: (uniprocessor) cpu0: AMD Opteron(tm) Processor 150, 2412.65 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: Cool'n'Quiet K8 2412 MHz: speeds: 2400 2200 2000 1800 1000 MHz cpu0: AMD erratum 89 present, BIOS upgrade may be required pci0 at mainbus0 bus 0: configuration mode 1 NVIDIA nForce4 DDR rev 0xa3 at pci0 dev 0 function 0 not configured pcib0 at pci0 dev 1 function 0 NVIDIA nForce4 ISA rev 0xa3 nviic0 at pci0 dev 1 function 1 NVIDIA nForce4 SMBus rev 0xa2 iic0 at nviic0 adt0 at iic0 addr 0x2e: sch5017 rev 0x89 iic1 at nviic0 adt1 at iic1 addr 0x2e: sch5017 rev 0x89 ohci0 at pci0 dev 2 function 0 NVIDIA nForce4 USB rev 0xa2: irq 11, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 8 ports with 8 removable, self powered ehci0 at pci0 dev 2 function 1 NVIDIA nForce4 USB rev 0xa3: irq 3 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 uhub1: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1 uhub1: 8 ports with 8 removable, self powered pciide0 at pci0 dev 6 function 0 NVIDIA nForce4 IDE rev 0xf2: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) pciide0: channel 1 disabled (no drives) pciide1 at pci0 dev 7 function 0 NVIDIA nForce4 SATA rev 0xf3: DMA pciide1: using irq 10 for native-PCI interrupt wd0 at pciide1 channel 0 drive 0: WDC WD1200JS-00MHB0 wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5 wd1 at pciide1 channel 1 drive 0: WDC WD1200JD-00HBC0 wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd1(pciide1:1:0): using PIO mode 4, Ultra-DMA mode 5 pciide2 at pci0 dev 8 function 0 NVIDIA nForce4 SATA rev 0xf3: DMA pciide2: using irq 11 for native-PCI interrupt ppb0 at pci0 dev 9 function 0 NVIDIA nForce4 PCI-PCI rev 0xa2 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Rage XL rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb1 at pci0 dev 11 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci2 at ppb1 bus 2 ppb2 at pci0 dev 12 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci3 at ppb2 bus 3 ppb3 at pci0 dev 13 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci4 at ppb3 bus 4 bge0 at pci4 dev 0 function 0 Broadcom BCM5721 rev 0x11, BCM5750 B1 (0x4101): irq 5, address 00:e0:81:59:6d:eb brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 ppb4 at pci0 dev 14 function 0 NVIDIA nForce4 PCIE rev 0xa3 pci5 at ppb4 bus 5 pchb0 at
Re: WRAP stalling at kernel entry point via pxeboot/tftp
The below advice worked for me. Many thanks. openbsd misc wrote: Hello, your boot.conf should look like this: set tty com0 stty com0 38400 set timeout 5 Last time I booted wrap via pxe was 3.9, but this should work. Regards Hagen Volpers -Urspr|ngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von mgb Gesendet: Donnerstag, 7. Juni 2007 12:51 An: misc@openbsd.org Betreff: WRAP stalling at kernel entry point via pxeboot/tftp List, I am attempting to get pxeboot working on a WRAP board with openbsd 4.1 generic however the loading of either kernel, bsd or bsd.rd, is stalling. I've search around the archives and have taken the steps mentioned here: http://marc.info/?l=openbsd-miscm=117978591113386w=2 I have updated the BIOS on the wrap board with a PXE.BIN downloaded from rom-o-matic.net which uses etherboot 5.4.3 and the NIC type natsemi:dp83815. below is the output from the wrap board: PC Engines WRAP.2B/2C v1.11 640 KB Base Memory 130048 KB Extended Memory 01F0 - no drive found ! ROM segment 0xe000 length 0x8000 reloc 0x Etherboot 5.4.3 (GPL) http://etherboot.org Drivers: NATSEMI Images: NBI ELF Multiboot a.out PXE Exports: PXE Protocols: DHCP TFTP Relocating _text from: [0008bb80,0009fd90) to [07eebdf0,07f0) Boot from (N)etwork (D)isk or (Q)uit? N Probing pci nic... [dp83815] natsemi_probe: MAC addr 00:0D:B9:04:47:F8 at ioaddr 0X1000 natsemi_probe: Vendor:0X100B Device:0X0020 dp83815: Transceiver default autoneg. enabled, advertise 100 full duplex. dp83815: Transceiver status 7869 advertising 05E1 dp83815: Setting full-duplex based on negotiated link capability. Searching for server (DHCP). Me: 192.168.1.200, DHCP: 192.168.1.1, TFTP: 192.168.1.1, Gateway 192.168.1.1 Loading 192.168.1.1:pxeboot ...(PXE)done probing: pc0 com0 pci pxe![2.1] mem[640K 125M a20=on] disk: net: mac 00:0d:b9:04:47:f8, ip 192.168.1.200, server 192.168.1.1 OpenBSD/i386 PXEBOOT 1.11 boot bsd1.rd booting tftp:bsd.rd: 4679892+742564 [52+169536+154918]=0x57b288 dp83815: Setting full-duplex based on negotiated link capability. entry point at 0x200120 the loading stalls at this point, tcpdump shows the following: 11:48:27.321421 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:28.319634 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:30.319653 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:34.319901 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:42.320416 IP 192.168.1.1.32831 192.168.1.200.2905: UDP, length 222 [EMAIL PROTECTED]@.U..?.Y..0.nchrdev.ex_ca.ieee80211_merge_print_intvl.mfi_get_info.ep_eisa_ca.ath_power.aue_cd.cac_shutdown.piix_pci_icu.re_pci_devices.af2rtafidx.pciide_ca.fddprint.natsemi_pci_intr.rtw_ioctl.pciide_chansetup.qsphy_ca.shmmaxpgs. 11:48:47.320663 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:48.320728 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:49.320787 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:58.325352 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:48:59.325417 arp who-has 192.168.1.200 tell 192.168.1.1 ..Ze 11:49:00.325480 arp who-has 192.168.1.200 tell 192.168.1.1 I have used a boot.conf which contains this: set tty pc0 I have tried com0 and the output freezes whilst I type bsd.rd Many thanks for your time
Pinging redundant firewall problem (isakmpd+pf+pfsync+sasyncd+carp)
Hello, Intro: I am using isakmpd+sasyncd+carp+pf+pfsync to have a redundant firewall setup (OpenBSD 4.0). I have two firewall that carp-advertise at the same rate, and not preempt each other. This works fine. isakmpd is using x509 certificates to establish SAs. This is working fine. sasyncd is running on both and they share the SAs properly. pfsync has been configured and it is working well. I have the following setup (netmask is /24 everywhere): Redundant end FW1: Ext IP: 172.16.140.2 (static) Int IP: 172.16.36.2 (static) FW2: Ext IP: 172.16.140.3 (static) Int IP: 172.16.36.3 (static) FW1 and FW2 shared IP addresses (carp) Ext IP: 172.16.140.1 Int IP: 172.16.36.1 Non-redundant end: Ext IP: 172.16.142.1 (static) Int IP: 172.16.40.1 (static) Problem: Assume the gateway that has static IP 172.16.36.2 is the master. I ping from 172.16.40.1 to 172.16.36.1 (or 172.16.36.2) and the ping goes through. The moment I ping the backup (ping -c 1 -I 172.16.40.1 172.16.36.3) I get a reply, but I can no longer ping 172.16.36.2. Now I can only ping the second gateway (goes in through the master, goes out through the backup). Everything goes back to normal (I can ping 172.16.36.2) the moment a new quick mode is finished and new SAs are established. Question: Why is this happening? I would like to have remote access to the backup gateway, for instance for live status polling (that's why I have the static IP addresses), or sync NTP time on firewalls (time source over secure tunnel). I don't mind if when I ping 172.16.36.3 the packet goes in through the first gateway and goes out through the second (because the flows are already set). I just don't want to block the communication on messages to the backup gateway. Can anyone help with this issue? ./catalin - Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail
Re: hoststated: fatal: relay_dispatch_pfe: desynchronized,
--- src/usr.sbin/hoststated/relay.c.origWed Mar 7 19:40:32
2007 +++ src/usr.sbin/hoststated/relay.c Sun May 13 18:37:48 2007
@@ -1775,7 +1775,7 @@
fatalx(relay_dispatch_pfe: invalid
host id); if (host-flags F_DISABLE)
break;
- if (host-up == st.up) {
+ if (host-up != st.up) {
log_debug(relay_dispatch_pfe: host
%d = %d, host-id, host-up);
fatalx(relay_dispatch_pfe:
desynchronized);
This fix is wrong, please do not apply it (you should not receive
updates for a status you already know about).
current CVS version has no issues and I will pull a 4.1-release
version, try to reproduce the issue and apply -stable fixes.
Re: How to run and manage a DNS server.
Tom Van Looy wrote: http://lifewithdjbdns.org (henning@ wrote this ;-) It's not about bind but it has stuff about mysql and ISP-Environments. So it may be of your interest. Sam Fourman Jr. wrote: well here is a question, I was wondering if there would be anyway to make OpenBSD based DNS servers have a PostgreSQL backend. (I know there will be a performance hit) and does anyone know of a gtk front end for DNS management? or maybe a web based solution that is just DNS not like a full install of webmin. Sam Fourman Jr. On 6/6/07, Open Phugu [EMAIL PROTECTED] wrote: On 6/6/07, Bray Mailloux [EMAIL PROTECTED] wrote: Hello; This is my first time managing anything larger than a simple dhcp or pf box and I'm wondering if there is anyone available on this list who can answer a few questions I have concerning the creation and management of DNS servers. Give us details of what you want to accomplish and your questions. Everyone; Wow, thanks for all the information, I really appreciate it. Thanks, again; Bray.
Re: Kernel MINIROOTSIZE 8192 = No Boot
Just recompiled with: #define NKPTP_MIN 8 #define NKPTP_MAX 191 Same result. Thank you though. We'll revisit it in the future when the money is available? ~BAS On Thu, 7 Jun 2007, mickey wrote: On Wed, Jun 06, 2007 at 01:39:47PM -0400, Brian A. Seklecki wrote: The 1st stage loader just resets the prom before the kernel load. Can anyone else confirm this? You don't even need to elfrdsetroot(8) to test. Just compile bsd.rd with MINIROOTSIZE=16384. I've been using 32768 on my 4.0 systems for the bsd-appliance project. I've tested it on an AMD Athalon, an AMD Geode, and a VMWare machine. you need to raise NKPTP also to say 8... cu -- paranoic mickey (my employers have changed but, the name has remained) l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~James Maynard Keenan
Re: Kernel MINIROOTSIZE 8192 = No Boot
On 2007/06/07 11:52, Brian A. Seklecki wrote: Just recompiled with: #define NKPTP_MIN 8 #define NKPTP_MAX 191 Same result. Thank you though. We'll revisit it in the future when the money is available? this might be of interest: http://archive.netbsd.se/?ml=openbsd-techa=2006-09t=2321795
Re: Problem installing 4.1/sparc64 on Sun Blade 100
2007/5/31, Ted Bullock [EMAIL PROTECTED]: I had the same problem until I updated the firmware to 4.17.1 -Ted Landry Breuil wrote: Hello, i'm trying to install OpenBSD/Sparc64 on a Blade 100, tried various methods/versions (all described in INSTALL.sparc64), they all fail after 'Trying bsd' and stall. Where can i have a start point to debug what happens/doesn't happen ? I've tried : - 3.9-release Cdrom (original version from wim) - 4.1-release cd41.iso taken from mirror/4.1 - 4.1-current cd41.iso taken from snapshots - knowing cd-install are not really good on blades, i tried netbooting bsd.rd 4.1-release and -current, using another obsd box as rarpd/tftpd/rpc.bootparamd/nfsd/mountd server, set like described in diskless(8). The weird thing is that ofwboot.net is taken from tftpd after 'boot net bsd.rd', ran, i see the first twolines : OpenBSD 4.1 (obj) #0: -build-date- [EMAIL PROTECTED] :/usr/src/sys/arch/sparc64/compile/GENERIC then Trying bsd and stalled-nothing more on the screen. but i see no mount requests in mountd -d output. i tried following https://www-s.acm.uiuc.edu/wiki/comments/OpenBSD+Sparc64#notesdocumentation too. security-mode is set to none in OBP, and firmware version is 4.0.45, i don't think it needs a firmware upgrade. Could it be a hardware problem ? How can i get more debug information ? Thanks for any hints. Next step will be trying to use a floppy (gee, i have to find a floppy reader and a disk), or putting the disk in my U10 (which works fine) and try to do the install on it. Landry Upgrading to 4.17.1 didn't solved the issue here i'm still having the same problem, kernel hanging just after Trying bsd, either using netboot or cdrom and various versions. I had no problem installing -current on Ultra60, even with a really older firmware version.. Really annoying. If anyone has a hint to debug this issue.. Landry
Re: Kernel MINIROOTSIZE 8192 = No Boot
On Thu, Jun 07, 2007 at 11:52:24AM -0400, Brian A. Seklecki wrote: Just recompiled with: #define NKPTP_MIN 8 #define NKPTP_MAX 191 Same result. Thank you though. We'll revisit it in the future when the money is available? i said NKPTP. if 8 is not enough -- try 16 cu On Thu, 7 Jun 2007, mickey wrote: On Wed, Jun 06, 2007 at 01:39:47PM -0400, Brian A. Seklecki wrote: The 1st stage loader just resets the prom before the kernel load. Can anyone else confirm this? You don't even need to elfrdsetroot(8) to test. Just compile bsd.rd with MINIROOTSIZE=16384. I've been using 32768 on my 4.0 systems for the bsd-appliance project. I've tested it on an AMD Athalon, an AMD Geode, and a VMWare machine. you need to raise NKPTP also to say 8... cu -- paranoic mickey (my employers have changed but, the name has remained) l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~James Maynard Keenan -- paranoic mickey (my employers have changed but, the name has remained)
Re: /usr/obj partition AWOL
On Thu, 7 Jun 2007, Otto Moerbeek wrote: We have seen some reports now on disappearing paritions. On sparc and sparc64, there were actual bugs that have been fixed now. For all platforms, the suspect new consistency checking code now been disabled until we find out what is causing the mishap, and (very) recent kernels should be back to normal. Please report with dikslabel info and dmesg if things are still going wrong. Preferable with fdisk (if applicable) and old disklabel information as well. I have thinking a bit more about the problem, and it is very likely the following scenario happened: 1. Kernel upgrade by source. 2. Reboot 3. Kernel reads old disklabel format and converts it in-memory to the new v1 format. 4. Run a newfs using the old executable that does not know about the new disklabel format. newfs writes the block and fragment size info the old way, on a spot that is used in v1 labels to store the high 16 bits of the offset and size of a partition. The label is written with version = 1, since the in-memory copy is v1. 5. Reboot, the kernel now sees a v1 disklabel with very high offset and/or size, the new consistency code (which is now disabled) kicks in and marks the partition as unused. So the lesson here is: keep userland and kernel in sync, or use a snapshot to upgrade. -Otto
Re: open(hd0a:/etc/boot.conf): Invalid argument
On Thu, 7 Jun 2007, Shag Bag wrote: I've installed OpenBSD4.1 from the 3 CD set which I purchased shortly after it was released and have been running it on and off ever since. However, this morning I tried to boot it and it came up with the above error (full error listing below). I re-installed the whole OS yesterday (everything except bsd.mp and game41.tgz) and it was working fine. The only thing I did after re-install was add a few packages and ports and compile the LookXP source packages from http://lxp.sourceforge.net. I have not knowingly touched the boot.conf file at all so I'm at a loss as to how the above error is showing. I have read the biosboot(8) man page but it didn't help. I am new to OpenBSD having come from a brief linux background and would appreciate any help. I could always simply re-install OpenBSD4.1 again but this would be a last resort as: i) I'd like to know what the cause of the problem is and how to fix it - in case it happens again; ii) I wouldn't learn anything if I simply reinstalled everytime; and iii) I've spent a lot of time configuring icewm to get it like I want and am loathed to go through this process again. The full error list I'm getting is: Loading... probing: pc0 apm mem[632K 2046M a20=on] disk: fd0 hd0+* OpenBSD/i386 BOOT 2.13 open(hd0a:/etc/boot.conf): Invalid argument boot Well, evidently there's something wrong with /etc/boot.conf, right? First, if you haven't done it already, print out the man page for ed(1), even from a linux system. On paper. So boot the installation CD again. Instead of update or install, select shell At the prompt (#), mount your root partition. Do I know what it is? No. I'll guess that it is either /dev/sd0a or /dev/wd0a Anyway, mount it: # mount /dev/sd0a /mnt Now you can look at (and edit, using ed(1)) the file in question. (Maybe you get errors? Maybe you need to run fsck on that partition before mounting it?) # cat /mnt/etc/boot.conf Tell us what you see. You can edit it. The routine PeeCee installation doesn't even need this file to exist. To edit: # ed /mnt/etc/boot.conf What no manpage? Didn't print it out? Don't know how to use ed(1)? Expected ed to pop up help windows? Thought I was lying? Here's your second chance: # mount /dev/sd0d /mnt/usr Assuming sd0d is where your /usr is. Forgot where that is? # cat /mnt/etc/fstab read what it says. Maybe your /usr is on the same partition as /, (linux having poisoned your mind in this regard), in which case it's already mounted. (partition = what disklabel makes. Not what fdisk manipulates). The man page is right there /mnt/usr/share/man/cat1/ed.0 Try to more it. I don't recall if more is available on the bsd.cd ramdisk, if not you're going to have to read quickly. Try running /mnt/usr/bin/more Would rather use vi? Well, maybe it's there under /mnt/usr/bin/vi Maybe it will even work. But this is diverging from topic. Summary: you can mount and manipulate your harddrive(s) from the installation CD using sh. It is not scary, just touchy. The simple manipulation might be just: # mv /mnt/etc/boot.conf /mnt/etc/boot.conf.bad and try rebooting from the harddisk. I have an uneasy feeling that something else may be wrong. If you found this post highly useful and full of new info and startling concepts, there's a openbsd-newbies list at sfobug.org. Visit http://sfobug.org for further info. Dave
Mizani, KeraCare, D. Essentials others 25% Off
All of the following product lines 25% offnbsp;until Sundaynbsp;June 10, 2007This promotin will expire at midnight onnbsp;Sundaynbsp;June 10, 2007. For the convenience of our customers please find a shortcut to some of our most popular salon items below. No promotional code is necessary. The prices are already discounted 25%. Please feel free to share this e-mail with anyone who may find it useful.Keracare http://www.sheldeez.com/webcart11/webcart.php?RCATS=Kera+CareMizani http://www.sheldeez.com/webcart11/webcart.php?RCATS=MizaniStraight Request http://www.sheldeez.com/webcart11/webcart.php?RCATS=Straight+RequestDesign Essentials http://www.sheldeez.com/webcart11/webcart.php?RCATS=Design+EssentialsSilk 2 http://www.sheldeez.com/webcart11/webcart.php?RCATS=Silk2If you would like to be removed please click here.https://webcart.net/securehost/sheldeez.com/webcart11/nl_unsubscribe.php?ln=enEMAIL=misc%40openbsd.orgSRC=aah2Click here to unsubscribeSheldeez Management
multihomed NFS boot client
List, I have multiple client machines that pxeboot a kernel which mounts the root and swap through NFS, however these clients have more than one interface and the client is choosing the wrong interface to send on. Is there a way of telling the client which interface to use for the NFS part? nfs_boot: using interface ath0, with revarp bootparams panic: revarp failed, error=51 the interface above should be sis0, not ath0. Many thanks
Re: multihomed NFS boot client
I have multiple client machines that pxeboot a kernel which mounts the root and swap through NFS, however these clients have more than one interface and the client is choosing the wrong interface to send on. Is there a way of telling the client which interface to use for the NFS part? nfs_boot: using interface ath0, with revarp bootparams panic: revarp failed, error=51 the interface above should be sis0, not ath0. Very conveniently you managed to remove the three lines just before this. So I can't tell why it chose the wrong interface. If you want help, you have to give us all the information we might need!
Re: Problem installing 4.1/sparc64 on Sun Blade 100
2007/6/7, Landry Breuil [EMAIL PROTECTED]: 2007/5/31, Ted Bullock [EMAIL PROTECTED]: I had the same problem until I updated the firmware to 4.17.1 -Ted Landry Breuil wrote: Hello, i'm trying to install OpenBSD/Sparc64 on a Blade 100, tried various methods/versions (all described in INSTALL.sparc64), they all fail after 'Trying bsd' and stall. Where can i have a start point to debug what happens/doesn't happen ? I've tried : - 3.9-release Cdrom (original version from wim) - 4.1-release cd41.iso taken from mirror/4.1 - 4.1-current cd41.iso taken from snapshots - knowing cd-install are not really good on blades, i tried netbooting bsd.rd 4.1-release and -current, using another obsd box as rarpd/tftpd/rpc.bootparamd/nfsd/mountd server, set like described in diskless(8). The weird thing is that ofwboot.net is taken from tftpd after 'boot net bsd.rd', ran, i see the first twolines : OpenBSD 4.1 (obj) #0: -build-date- [EMAIL PROTECTED] :/usr/src/sys/arch/sparc64/compile/GENERIC then Trying bsd and stalled-nothing more on the screen. but i see no mount requests in mountd -d output. i tried following https://www-s.acm.uiuc.edu/wiki/comments/OpenBSD+Sparc64#notesdocumentation too. security-mode is set to none in OBP, and firmware version is 4.0.45, i don't think it needs a firmware upgrade. Could it be a hardware problem ? How can i get more debug information ? Thanks for any hints. Next step will be trying to use a floppy (gee, i have to find a floppy reader and a disk), or putting the disk in my U10 (which works fine) and try to do the install on it. Landry Upgrading to 4.17.1 didn't solved the issue here i'm still having the same problem, kernel hanging just after Trying bsd, either using netboot or cdrom and various versions. I had no problem installing -current on Ultra60, even with a really older firmware version.. Really annoying. If anyone has a hint to debug this issue.. I'm starting to suspect hardware, because even with this OBP upgrade i didn't manage to start the install of FreeBSD/sparc, NetBSD/sparc64, and various flavors of Linux/Sparc. All the installers start a kernel, and hangs at various places in kernel startup. It's not a question of serial console redirection, because i can ping the host when the boot starts, and it doesn't respond to pings as soon as it stalls during boot process. (And i don't have a db25 compatible serial cable..). Could it be memory ? hard disk ? Box has a 256mb + 512mb , and i don't know a way to test this memory without os on the box. Smth like memconf http://myweb.cableone.net/4schmidts/memconf.html or memtest for sparc would be appreciated. I'll try maybe setenv diag-switch? true setenv diag-level max reset but i really have no more ideas to boot this Blade 100. (and various flavors of openbsd works really well on Ultra 10 and ultra 60 here) Landry
Re: Problem installing 4.1/sparc64 on Sun Blade 100
On 6/7/07, Landry Breuil [EMAIL PROTECTED] wrote: 2007/6/7, Landry Breuil [EMAIL PROTECTED]: 2007/5/31, Ted Bullock [EMAIL PROTECTED]: I had the same problem until I updated the firmware to 4.17.1 -Ted Landry Breuil wrote: Hello, i'm trying to install OpenBSD/Sparc64 on a Blade 100, tried various methods/versions (all described in INSTALL.sparc64), they all fail after 'Trying bsd' and stall. Where can i have a start point to debug what happens/doesn't happen ? I've tried : - 3.9-release Cdrom (original version from wim) - 4.1-release cd41.iso taken from mirror/4.1 - 4.1-current cd41.iso taken from snapshots - knowing cd-install are not really good on blades, i tried netbooting bsd.rd 4.1-release and -current, using another obsd box as rarpd/tftpd/rpc.bootparamd/nfsd/mountd server, set like described in diskless(8). The weird thing is that ofwboot.net is taken from tftpd after 'boot net bsd.rd', ran, i see the first twolines : OpenBSD 4.1 (obj) #0: -build-date- [EMAIL PROTECTED] :/usr/src/sys/arch/sparc64/compile/GENERIC then Trying bsd and stalled-nothing more on the screen. but i see no mount requests in mountd -d output. i tried following https://www-s.acm.uiuc.edu/wiki/comments/OpenBSD+Sparc64#notesdocumentation too. security-mode is set to none in OBP, and firmware version is 4.0.45, i don't think it needs a firmware upgrade. Could it be a hardware problem ? How can i get more debug information ? Thanks for any hints. Next step will be trying to use a floppy (gee, i have to find a floppy reader and a disk), or putting the disk in my U10 (which works fine) and try to do the install on it. Landry Upgrading to 4.17.1 didn't solved the issue here i'm still having the same problem, kernel hanging just after Trying bsd, either using netboot or cdrom and various versions. I had no problem installing -current on Ultra60, even with a really older firmware version.. Really annoying. If anyone has a hint to debug this issue.. I'm starting to suspect hardware, because even with this OBP upgrade i didn't manage to start the install of FreeBSD/sparc, NetBSD/sparc64, and various flavors of Linux/Sparc. All the installers start a kernel, and hangs at various places in kernel startup. It's not a question of serial console redirection, because i can ping the host when the boot starts, and it doesn't respond to pings as soon as it stalls during boot process. (And i don't have a db25 compatible serial cable..). Could it be memory ? hard disk ? Box has a 256mb + 512mb , and i don't know a way to test this memory without os on the box. Smth like memconf http://myweb.cableone.net/4schmidts/memconf.html or memtest for sparc would be appreciated. I'll try maybe setenv diag-switch? true setenv diag-level max reset but i really have no more ideas to boot this Blade 100. (and various flavors of openbsd works really well on Ultra 10 and ultra 60 here) Landry I'm afraid it doesn't really help you much, but I got 4.1 installed on a Blade 100 from the CDs without a hitch :D Just so you know it's not an issue specific to all blades I guess. Jimmy.
Re: Problem installing 4.1/sparc64 on Sun Blade 100
2007/6/7, Maxim Belooussov [EMAIL PROTECTED]: I'm starting to suspect hardware, because even with this OBP upgrade i didn't manage to start the install of FreeBSD/sparc, NetBSD/sparc64, and various flavors of Linux/Sparc. All the installers start a kernel, and hangs at various places in kernel startup. It's not a question of serial console redirection, because i can ping the host when the boot starts, and it doesn't respond to pings as soon as it stalls during boot process. (And i don't have a db25 compatible serial cable..). Could it be memory ? hard disk ? Box has a 256mb + 512mb , and i don't know a way to test this memory without os on the box. Smth like memconf http://myweb.cableone.net/4schmidts/memconf.html or memtest for sparc would be appreciated. remove one of the ram sticks and try again? Ok, so sorry for all this noise, this was a hw issue. 'set diag-switch? true' at OBP prompt showed POST errors on DIMM1, I swapped both memory modules, and POST was happy. In five minutes, box was installed, and now happily runs -current. I really should learn OBP diagnostic commands. Definitely, this couldn't be an OpenBSD issue :) Thanks again to all devs for such a wonderful OS. Landry Dmesg for the record : http://gruiik.info/stuff/dmesg.lizzy
Re: Problem installing 4.1/sparc64 on Sun Blade 100
Could it be memory ? hard disk ? Box has a 256mb + 512mb , and i don't know a way to test this memory without os on the box. Smth like memconf There should be a memtest_obp_sparc whatever -- there's already one for the OBP platform on the Apple PowerPC platform. Most Sun shops have everything deployed HA and have a $4000/month support contract, though, so I've never actually had to test for bad ram on a Sparc. Memoryx.net says the Blade100/150 uses PC133 ECC, so you should be able to test it in an i386 machine w/ memtest. ~BAS http://myweb.cableone.net/4schmidts/memconf.html or memtest for sparc
Re: /usr/obj partition AWOL
On Thu, Jun 07, 2007 at 07:50:24PM +0200, Otto Moerbeek wrote: I have thinking a bit more about the problem, and it is very likely the following scenario happened: 1. Kernel upgrade by source. 2. Reboot 3. Kernel reads old disklabel format and converts it in-memory to the new v1 format. 4. Run a newfs using the old executable that does not know about the new disklabel format. newfs writes the block and fragment size info the old way, on a spot that is used in v1 labels to store the high 16 bits of the offset and size of a partition. The label is written with version = 1, since the in-memory copy is v1. 5. Reboot, the kernel now sees a v1 disklabel with very high offset and/or size, the new consistency code (which is now disabled) kicks in and marks the partition as unused. So the lesson here is: keep userland and kernel in sync, or use a snapshot to upgrade. I believe that's exactly what happened the first time. The catch is that kernel and userland were being built from the same cvs update, and I thought I was keeping them in sync. In this case it would probably have been better to skip the reboot between building the kernel and the userland. I'll take newfs out of my build script (back to rm -rf /usr/obj/*) and try to remember to use newfs before rebooting with a new kernel if I want to avoid the wait. Thanks again! Emilio
Laptop won't boot with latest i386 snapshot
Hello list! After doing a fresh install of todays snapshot on my HP Pavilion ZV5000 laptop, the system doesn't boot anymore. When it gets on the line below, the CPU goes full speed (the fan goes full power) and the system seems to hang: Texas Instruments PCI1620 Misc rev 0x01 at pci2 dev 4 function 2 not configured ohci2 at pci2 dev 7 function 0 NEC USB rev 0x43: irq 10, version 1.0, legacy support The line above is from an old succesfull dmesg that I took with 3.9-current. This old dmesg is at the end of the email. I think there's no way to post a dmesg of the failing boot because this latpop does not have a COM port =( If need be, I'll just write down the boot process and type it on another email. So, any ideas? It seems the problem is somehow USB related. Is there any serious modification to the USB code that may have caused this? Now, as a side note, while using 4.1-release I couldn't get the audio driver (auixp) to work properly using headphones. With headphones plugged in, I get no sound on them, and the laptop speakers won't mute automagically. It would be really nice to have this little quirk working =) Well, thanks everyone! OpenBSD 3.9-current (GENERIC) #693: Sat Apr 15 16:17:16 MDT 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz (GenuineIntel 686-class) 3 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID real mem = 401633280 (392220K) avail mem = 359100416 (350684K) using 4278 buffers containing 20185088 bytes (19712K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(e9) BIOS, date 12/15/04, BIOS32 rev. 0 @ 0xfd710 pcibios0 at bios0: rev 2.1 @ 0xfd710/0x8f0 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf10/208 (11 entries) pcibios0: no compatible PCI ICU found: ICU vendor 0x1002 product 0x434c pcibios0: PCI bus #4 is the last bus bios0: ROM list: 0xc/0xf000 0xd/0x6000! 0xd6000/0x1000 0xd7000/0x800! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 ATI Radeon IGP 9100 Host rev 0x02 ppb0 at pci0 dev 1 function 0 ATI Radeon IGP 9100 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon Mobility IGP 9100 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ohci0 at pci0 dev 19 function 0 ATI SB200 USB rev 0x01: irq 11, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: ATI OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1 at pci0 dev 19 function 1 ATI SB200 USB rev 0x01: irq 11, version 1.0, legacy support usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: ATI OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered piixpm0 at pci0 dev 20 function 0 ATI SB200 SMBus rev 0x16: SMI iic0 at piixpm0 pciide0 at pci0 dev 20 function 1 ATI IXP200 IDE rev 0x00: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: SAMSUNG HM120JC wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TEAC, DV-W28EW, C.0S SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 pcib0 at pci0 dev 20 function 3 ATI SB200 PCI-ISA rev 0x00 ppb1 at pci0 dev 20 function 4 ATI SB200 PCI-PCI rev 0x00 pci2 at ppb1 bus 2 Texas Instruments TSB43AB21 FireWire rev 0x00 at pci2 dev 0 function 0 not configured Broadcom BCM4306 rev 0x03 at pci2 dev 2 function 0 not configured rl0 at pci2 dev 3 function 0 Realtek 8139 rev 0x10: irq 11, address 00:0f:b0:4a:bc:aa rlphy0 at rl0 phy 0: RTL internal PHY cbb0 at pci2 dev 4 function 0 Texas Instruments PCI1620 CardBus rev 0x01: irq 10 cbb1 at pci2 dev 4 function 1 Texas Instruments PCI1620 CardBus rev 0x01: irq 10 Texas Instruments PCI1620 Misc rev 0x01 at pci2 dev 4 function 2 not configured ohci2 at pci2 dev 7 function 0 NEC USB rev 0x43: irq 10, version 1.0, legacy support usb2 at ohci2: USB revision 1.0 uhub2 at usb2 uhub2: NEC OHCI root hub, rev 1.00/1.00, addr 1 uhub2: 3 ports with 3 removable, self powered ohci3 at pci2 dev 7 function 1 NEC USB rev 0x43: irq 5, version 1.0, legacy support usb3 at ohci3: USB revision 1.0 uhub3 at usb3 uhub3: NEC OHCI root hub, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0 at pci2 dev 7 function 2 NEC USB rev 0x04: irq 11 usb4 at ehci0: USB revision 2.0 uhub4 at usb4 uhub4: NEC EHCI root hub, rev 2.00/1.00, addr 1 uhub4: 5 ports with 5 removable, self powered cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0x40 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 4 device 0 cacheline 0x8, lattimer 0x40
Re: Laptop won't boot with latest i386 snapshot
Thanks John! I had to disable ohci and ehci to succesfully boot the machine. Here's the dmesg: OpenBSD 4.1-current (GENERIC) #254: Thu Jun 7 00:24:55 MDT 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz (GenuineIntel 686-class) 3.01 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,CNXT-ID,xTPR real mem = 1206939648 (1151MB) avail mem = 1153245184 (1099MB) User Kernel Config UKC disable ehc\^H \^H\^H \^H\^H \^Hochi\^H \^H\^H \^H\^H \^Hhci 136 ohci* disabled 137 ohci* disabled UKC disable ehci 138 ehci* disabled 139 ehci* disabled UKC quit Continuing... mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 12/15/04, BIOS32 rev. 0 @ 0xfd710, SMBIOS rev. 2.31 @ 0xd7010 (36 entries) bios0: Hewlett-Packard Pavilion zv5200 (PU600UA#ABA) pcibios0 at bios0: rev 2.1 @ 0xfd710/0x8f0 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf10/208 (11 entries) pcibios0: no compatible PCI ICU found: ICU vendor 0x1002 product 0x434c pcibios0: PCI bus #4 is the last bus bios0: ROM list: 0xc/0xf000 0xd/0x6000! 0xd6000/0x1000 0xd7000/0x800! acpi0 at mainbus0: rev 0 acpi0: tables DSDT FACP APIC SSDT acpitimer at acpi0 not configured acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGPB) acpiprt2 at acpi0: bus 2 (P2P_) acpiec at acpi0 not configured acpicpu at acpi0 not configured acpicpu at acpi0 not configured acpitz at acpi0 not configured acpibtn at acpi0 not configured acpibtn at acpi0 not configured acpiac at acpi0 not configured acpibat at acpi0 not configured cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 ATI Radeon IGP 9100 Host rev 0x02 ppb0 at pci0 dev 1 function 0 ATI Radeon IGP 9100 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon Mobility IGP 9100 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ATI SB200 USB rev 0x01 at pci0 dev 19 function 0 not configured ATI SB200 USB rev 0x01 at pci0 dev 19 function 1 not configured piixpm0 at pci0 dev 20 function 0 ATI SB200 SMBus rev 0x16: SMI iic0 at piixpm0 pciide0 at pci0 dev 20 function 1 ATI IXP200 IDE rev 0x00: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: SAMSUNG HM120JC wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TEAC, DV-W28EW, C.0S SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 pcib0 at pci0 dev 20 function 3 ATI SB200 PCI-ISA rev 0x00 ppb1 at pci0 dev 20 function 4 ATI SB200 PCI-PCI rev 0x00 pci2 at ppb1 bus 2 TI TSB43AB21 FireWire rev 0x00 at pci2 dev 0 function 0 not configured Broadcom BCM4306 rev 0x03 at pci2 dev 2 function 0 not configured rl0 at pci2 dev 3 function 0 Realtek 8139 rev 0x10: irq 11, address 00:0f:b0:4a:bc:aa rlphy0 at rl0 phy 0: RTL internal PHY cbb0 at pci2 dev 4 function 0 TI PCI1620 CardBus rev 0x01: irq 10 cbb1 at pci2 dev 4 function 1 TI PCI1620 CardBus rev 0x01: irq 10 TI PCI1620 Misc rev 0x01 at pci2 dev 4 function 2 not configured NEC USB rev 0x43 at pci2 dev 7 function 0 not configured NEC USB rev 0x43 at pci2 dev 7 function 1 not configured NEC USB rev 0x04 at pci2 dev 7 function 2 not configured cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 3 device 0 cacheline 0x8, lattimer 0x40 pcmcia0 at cardslot0 cardslot1 at cbb1 slot 1 flags 0 cardbus1 at cardslot1: bus 4 device 0 cacheline 0x8, lattimer 0x40 pcmcia1 at cardslot1 auixp0 at pci0 dev 20 function 5 ATI IXP200 AC97 rev 0x00: irq 10 auixp0: soft resetting aclink ATI IXP200 Modem rev 0x01 at pci0 dev 20 function 6 not configured isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 viasio0 at isa0 port 0x4e/2: VT1211 rev 0x02: HM: not activated WDG: not activated npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 biomask e77d netmask ef7d ttymask pctr: user-level cycle counter enabled mtrr: Pentium Pro MTRR support softraid0 at root dkcsum: wd0 matches BIOS drive 0x80 root on wd0a swap on wd0b dump on wd0b ac97: codec id 0x41445374 (Analog Devices AD1981B) ac97: codec features headphone, 20 bit DAC, No 3D Stereo audio0 at auixp0 On 6/7/07, John Danks [EMAIL PROTECTED] wrote: When you see the boot prompt, type boot -c to get into UKC. From there type verbose and then quit. This will enable verbose boot messages so you can see
Re: Kernel MINIROOTSIZE 8192 = No Boot
It works; free beer on me for all on me ... (Columbia maybe) Thanks again, ~BAS On Thu, 7 Jun 2007, mickey wrote: On Thu, Jun 07, 2007 at 11:52:24AM -0400, Brian A. Seklecki wrote: Just recompiled with: #define NKPTP_MIN 8 #define NKPTP_MAX 191 Same result. Thank you though. We'll revisit it in the future when the money is available? i said NKPTP. if 8 is not enough -- try 16 cu On Thu, 7 Jun 2007, mickey wrote: On Wed, Jun 06, 2007 at 01:39:47PM -0400, Brian A. Seklecki wrote: The 1st stage loader just resets the prom before the kernel load. Can anyone else confirm this? You don't even need to elfrdsetroot(8) to test. Just compile bsd.rd with MINIROOTSIZE=16384. I've been using 32768 on my 4.0 systems for the bsd-appliance project. I've tested it on an AMD Athalon, an AMD Geode, and a VMWare machine. you need to raise NKPTP also to say 8... cu -- paranoic mickey (my employers have changed but, the name has remained) l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~James Maynard Keenan -- paranoic mickey (my employers have changed but, the name has remained) l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~James Maynard Keenan
Re: Quad ethernet card
Henning Brauer [EMAIL PROTECTED] wrote: int mitigation has always made quite some difference, but now it is even more, I agree. I could never see a difference on Soekris boxes with a 400 us delay in if_sis in earlier OpenBSD versions. But I never tried higher delays than that. nontheless sis is not far up from rl. far away from the real ones. I'd love to believe you, but tell me what you base this assertion on. Is this with real world comparisons of the same hardware running sis and rl (and a real chip like fxp...) ? if_rl does m_copydata() and bzero() all the time, where if_sis does not have to. The equivalent routine in if_sis (sis_encap) is about half the size. The whole sis driver is very simple and doesn't appear to do anything outrageous to support the chip. Is the bzero call where if_rl pads the frames in rl_encap a candidate to move to memset which gcc can better optimize? Hmm, it's only called for small packets that need to be padded to the minimum size for if_rl. One thing vr doesn't support is an interrupt hold off which disqualifies it for any serious routing tasks. There may be another way to do this with if_vr.
apcupsd core dumps upon machine shutdown
I installed apcupsd-3.12.4 on OBSD (3.8 and 4.1). I followed platforms/openbsd/README and everything seems to work fine except when I shutdown the system which gives me an apcupsd.core. Where does it come from? Is this because apcupsd is not killed during system shutdown? Any help would be appreciated. Regards, Thierry.
