Re: OpenBSD 4.2 firewall freezing, even after patch 004 and 005
http://openbsd.org/faq/faq5.html#Why Yes, I get that. But here's the diff: 16,17c20,21 optionI486_CPU# CPU classes; at least one is REQUIRED optionI586_CPU --- #option I486_CPU# CPU classes; at least one is REQUIRED #option I586_CPU Believe me that it was freezing up with the GENERIC kernel, too. I'd welcome any other suggestions for getting to the bottom of this problem. --- knitti [EMAIL PROTECTED] wrote: On 1/21/08, Robert Carr [EMAIL PROTECTED] wrote: After a few days of running, the machine becomes totally unresponsive, forcing me to power-cycle the box. I can't find anything relevant about the freeze/crash in any logs. [...] ...and no core dump. What am I doing wrong? [...] OpenBSD 4.2 (NAVARONE-4.2) #0: Wed Jan 16 23:18:21 PST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/NAVARONE-4.2 http://openbsd.org/faq/faq5.html#Why --knitti Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Re: Problems with -current in CVS?
On Jan 22, 2008 8:34 AM, Dusty [EMAIL PROTECTED] wrote: I had this too, you need to build yourself a new version f gcc. I see someone posted faq5 .. you want to 'follow current' it has those instructions. On Jan 22, 2008 8:30 AM, Colby W. [EMAIL PROTECTED] wrote: I tried two different AnonCVS repositories (one in the USA and one in CAN) tonight but ran into the same problem when I tried rebuilding the kernel to bring my recent -release install up to -current. Per the instructions [1]: # cd usr/ ; cvs checkout -P src # cd /usr/src/sys/arch/i386/conf/ # config GENERIC ../../../../conf/files:1005: syntax error ../../../../conf/files:1006: syntax error ../../../../conf/files:1007: syntax error ../../../../conf/files:1008: syntax error ../../../../conf/files:1009: syntax error ../../../../conf/files:1010: syntax error ../../../../conf/files:1011: syntax error ../../../../conf/files:1012: syntax error ../../../../conf/files:1013: syntax error ../../../../conf/files:1014: syntax error ../../../../conf/files:1015: syntax error ../../../../conf/files:1016: syntax error ../../../../conf/files:1017: syntax error ../../../../conf/files:1018: syntax error ../../../../conf/files:1019: syntax error ../../../../conf/files:1020: syntax error ../../../../conf/files:1021: syntax error ../../../../conf/files:1022: syntax error ../../../../conf/files:1023: syntax error ../../../../conf/files:1024: syntax error ../../../../conf/files:1025: syntax error ../../../../conf/files:1026: syntax error ../../../../conf/files:1027: syntax error ../../../../conf/files:1028: syntax error ../../../../conf/files:1029: syntax error ../../../../conf/files:1030: syntax error ../../../../conf/files:1031: syntax error ../../../../conf/files:1032: syntax error ../../../../conf/files:1033: syntax error ../../../../conf/files:1034: syntax error ../../../../conf/files:1035: syntax error ../../../../conf/files:1036: syntax error ../../../../conf/files:1037: syntax error ../../../../conf/files:1038: syntax error *** Stop. Is this a problem with a config file checked into CVS or am I missing something? From what I can determine, there is no ../../../../conf/files but there is ../../../conf/files (one directory closer to /usr/src/sys/arch/i386/conf : ie., /usr/src/sys/conf/). Thanks in advance, Colby W. [1] http://www.openbsd.org/faq/faq5.html This is probobly due to the config flag day. Do as it says on Following -current: 2007/11/25 - config(8) flag day Extended capabilities require config(8) to be rebuilt on your system: # cd /usr/src/usr.sbin/config # make clean # make obj # make depend # make # make install I got the same errors when I forgot to do that so it's highy possible that config is the problem. BR dunceor
crypto.html
Hi folks, I would like to know if the www.openbsd.org/crypto.html is currently update with the last crypto capabilities of 4.2 release. Best Regards, Alvaro
HP Raid hardware
Hello all, I have to set up an OpenBSD getaway on an HP Proliant server but I must be sure about hardware compatibilities, in particular, for RAID controller. Which HP controller could you advice to me for full compatibility with OpenBSD, on HP Proliant ? Thanks for your answers. Max
Re: HP Raid hardware
What do you mean with full compliant ? The hardware compatibility (http://www.openbsd.org/i386.html) gives the list of supported HP SmartArray RAID devices. It had worked or currently works for me on DL360G1, DL360G2 and DL360G4p. ex on DL360G4 # sysctl hw.product ; bioctl ciss0 hw.product=ProLiant DL360 G4p Volume Status Size Device ciss0 0 Online 146804797440 sd0 RAID1 0 Online 146811543552 0:0.0 noencl COMPAQ BD14688278 1 Online 146811543552 0:1.0 noencl COMPAQ BD14688278 ex on DL360G2 # sysctl hw.product ; bioctl ciss0 hw.product=ProLiant DL360 G2 Volume Status Size Device ciss0 0 Online72833679360 sd0 RAID1 0 Invalid 0 0:0.0 noencl 1 Invalid 0 0:1.0 noencl 2 Invalid 0 0:2.0 noencl 3 Invalid 0 0:3.0 noencl 4 Invalid 0 0:4.0 noencl 5 Invalid 0 0:5.0 noencl 6 Invalid 0 0:6.0 noencl 7 Invalid 0 0:7.0 noencl 8 Invalid 0 0:8.0 noencl 9 Invalid 0 0:9.0 noencl 10 Invalid 0 0:10.0 noencl 11 Invalid 0 0:11.0 noencl 12 Invalid 0 0:12.0 noencl 13 Invalid 0 0:13.0 noencl 14 Invalid 0 0:14.0 noencl 15 Invalid 0 0:15.0 noencl 16 Online72834973696 1:0.0 noencl COMPAQ BD0726459C 17 Online72834973696 1:1.0 noencl COMPAQ BD07287B4C 18 Invalid 0 1:2.0 noencl 19 Invalid 0 1:3.0 noencl 20 Invalid 0 1:4.0 noencl 21 Invalid 0 1:5.0 noencl 22 Invalid 0 1:6.0 noencl 23 Invalid 0 1:7.0 noencl COMPAQ PROLIANT 6L2I 24 Invalid 0 1:8.0 noencl 25 Invalid 0 1:9.0 noencl 26 Invalid 0 1:10.0 noencl 27 Invalid 0 1:11.0 noencl 28 Invalid 0 1:12.0 noencl 29 Invalid 0 1:13.0 noencl 30 Invalid 0 1:14.0 noencl 31 Invalid 0 1:15.0 noencl Regards On 22/01/2008, Max [EMAIL PROTECTED] wrote: Hello all, I have to set up an OpenBSD getaway on an HP Proliant server but I must be sure about hardware compatibilities, in particular, for RAID controller. Which HP controller could you advice to me for full compatibility with OpenBSD, on HP Proliant ? Thanks for your answers. Max
Re: HP Raid hardware
Thanks for you answer. I know that hardware compatibilty page exists but drivers/hardware names are not really clear for me :| And does anyone know if HP SC40Ge SAS HBA RAID on Proliant DL160 G5 is supported ? Thx. Le 22 janv. 08 ` 11:47, Fridiric Pli a icrit : What do you mean with full compliant ? The hardware compatibility (http://www.openbsd.org/i386.html) gives the list of supported HP SmartArray RAID devices. It had worked or currently works for me on DL360G1, DL360G2 and DL360G4p. ex on DL360G4 # sysctl hw.product ; bioctl ciss0 hw.product=ProLiant DL360 G4p Volume Status Size Device ciss0 0 Online 146804797440 sd0 RAID1 0 Online 146811543552 0:0.0 noencl COMPAQ BD14688278 1 Online 146811543552 0:1.0 noencl COMPAQ BD14688278 ex on DL360G2 # sysctl hw.product ; bioctl ciss0 hw.product=ProLiant DL360 G2 Volume Status Size Device ciss0 0 Online72833679360 sd0 RAID1 0 Invalid 0 0:0.0 noencl 1 Invalid 0 0:1.0 noencl 2 Invalid 0 0:2.0 noencl 3 Invalid 0 0:3.0 noencl 4 Invalid 0 0:4.0 noencl 5 Invalid 0 0:5.0 noencl 6 Invalid 0 0:6.0 noencl 7 Invalid 0 0:7.0 noencl 8 Invalid 0 0:8.0 noencl 9 Invalid 0 0:9.0 noencl 10 Invalid 0 0:10.0 noencl 11 Invalid 0 0:11.0 noencl 12 Invalid 0 0:12.0 noencl 13 Invalid 0 0:13.0 noencl 14 Invalid 0 0:14.0 noencl 15 Invalid 0 0:15.0 noencl 16 Online72834973696 1:0.0 noencl COMPAQ BD0726459C 17 Online72834973696 1:1.0 noencl COMPAQ BD07287B4C 18 Invalid 0 1:2.0 noencl 19 Invalid 0 1:3.0 noencl 20 Invalid 0 1:4.0 noencl 21 Invalid 0 1:5.0 noencl 22 Invalid 0 1:6.0 noencl 23 Invalid 0 1:7.0 noencl COMPAQ PROLIANT 6L2I 24 Invalid 0 1:8.0 noencl 25 Invalid 0 1:9.0 noencl 26 Invalid 0 1:10.0 noencl 27 Invalid 0 1:11.0 noencl 28 Invalid 0 1:12.0 noencl 29 Invalid 0 1:13.0 noencl 30 Invalid 0 1:14.0 noencl 31 Invalid 0 1:15.0 noencl Regards On 22/01/2008, Max [EMAIL PROTECTED] wrote: Hello all, I have to set up an OpenBSD getaway on an HP Proliant server but I must be sure about hardware compatibilities, in particular, for RAID controller. Which HP controller could you advice to me for full compatibility with OpenBSD, on HP Proliant ? Thanks for your answers. Max
Re: HP Raid hardware
On Jan 22, 2008 11:59 AM, Max [EMAIL PROTECTED] wrote: Thanks for you answer. I know that hardware compatibilty page exists but drivers/hardware names are not really clear for me :| And does anyone know if HP SC40Ge SAS HBA RAID on Proliant DL160 G5 is supported ? You can find the supported controller details in the driver man pages!
Re: OpenBSD 4.2 i386 -snapshot- hangs at boot an Dell Poweredge2650
Hi, I think it was an hardware issue. With another PE2650 Server everything works fine, when acpi is disabled: OpenBSD 4.2-current (GENERIC) #642: Tue Jan 8 17:06:33 MST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Xeon(TM) CPU 2.80GHz (GenuineIntel 686-class) 2.79 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 = 4160192512 (3967MB) avail mem = 4046163968 (3858MB) User Kernel Config UKC disable acpi 414 acpi0 already disabled UKC exit Continuing... mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 10/05/06, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xfb2c0 (62 entries) bios0: vendor Dell Computer Corporation version A21 date 10/05/2006 bios0: Dell Computer Corporation PowerEdge 2650 acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 2.1 @ 0xf/0x1 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfc410/176 (9 entries) pcibios0: PCI Interrupt Router at 000:15:0 (ServerWorks CSB5 rev 0x00) pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x6000 0xce000/0x600 0xec000/0x4000! ipmi at mainbus0 not configured cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 ServerWorks CNB20-HE Host (GC-LE) rev 0x33 pchb1 at pci0 dev 0 function 1 ServerWorks CNB20-HE Host (GC-LE) rev 0x00 pci1 at pchb1 bus 3 bge0 at pci1 dev 6 function 0 Broadcom BCM5703X rev 0x02, BCM5703 A2 (0x1002): irq 11, address 00:0f:1f:6a:64:fc brgphy0 at bge0 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 bge1 at pci1 dev 8 function 0 Broadcom BCM5703X rev 0x02, BCM5703 A2 (0x1002): irq 10, address 00:0f:1f:6a:64:fe brgphy1 at bge1 phy 1: BCM5703 10/100/1000baseT PHY, rev. 2 pchb2 at pci0 dev 0 function 2 ServerWorks CNB20-HE Host (GC-LE) rev 0x00 pci2 at pchb2 bus 1 em0 at pci2 dev 8 function 0 Intel PRO/1000MT (82546EB) rev 0x01: irq 11, address 00:04:23:be:de:12 em1 at pci2 dev 8 function 1 Intel PRO/1000MT (82546EB) rev 0x01: irq 10, address 00:04:23:be:de:13 Dell DRAC 4 Embedded/Optional rev 0x00 at pci0 dev 4 function 0 not configured Dell PERC 3/Di rev 0x00 at pci0 dev 4 function 1 not configured Dell DRAC 3 Optional rev 0x00 at pci0 dev 4 function 2 not configured vga1 at pci0 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) piixpm0 at pci0 dev 15 function 0 ServerWorks CSB5 rev 0x93: SMI iic0 at piixpm0 iic0: addr 0x48 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00 09=00 0a=00 0b=00 0c=00 0d=00 0e=00 0f=00 10=00 11=00 12=00 13=00 14=00 15=00 16=00 17=00 18=00 19=00 1a=00 1b=00 1c=00 1d=00 1e=00 1f=00 20=00 21=00 22=00 23=00 24=00 25=00 26=00 27=00 28=00 29=00 2a=00 2b=00 2c=00 2d=00 2e=00 2f=00 30=00 31=00 32=00 33=00 34=00 35=00 36=00 37=00 38=00 39=00 3a=00 3b=00 3c=00 3d=00 3e=00 3f=00 40=00 41=00 42=00 43=00 44=00 45=00 46=00 47=00 48=00 49=00 4a=00 4b=00 4c=00 4d=00 4e=00 4f=00 50=00 51=00 52=00 53=00 54=00 55=00 56=00 57=00 58=00 59=00 5a=00 5b=00 5c=00 5d=00 5e=00 5f=00 60=00 61=00 62=00 63=00 64=00 65=00 66=00 67=00 68=00 69=00 6a=00 6b=00 6c=00 6d=00 6e=00 6f=00 70=00 71=00 72=00 73=00 74=00 75=00 76=00 77=00 78=00 79=00 7a=00 7b=00 7c=00 7d=00 7e=00 7f=00 80=00 81=00 82=00 83=00 84=00 85=00 86=00 87=00 88=00 89=00 8a=00 8b=00 8c=00 8d=00 8e=00 8f=00 90=00 91=00 92=00 93=00 94=00 95=00 96=00 97=00 98=00 99=00 9a=00 9b=00 9c=00 9d=00 9e=00 9f=00 a0=00 a1=00 a! 2=00 a3=00 a4=00 a5=00 a6=00 a7=00 a8=00 a9=00 aa=00 ab=00 ac=00 ad=00 ae=00 af=00 b0=00 b1=00 b2=00 b3=00 b4=00 b5=00 b6=00 b7=00 b8=00 b9=00 ba=00 bb=00 bc=00 bd=00 be=00 bf=00 c0=00 c1=00 c2=00 c3=00 c4=00 c5=00 c6=00 c7=00 c8=00 c9=00 ca=00 cb=00 cc=00 cd=00 ce=00 cf=00 d0=00 d1=00 d2=00 d3=00 d4=00 d5=00 d6=00 d7=00 d8=00 d9=00 da=00 db=00 dc=00 dd=00 de=00 df=00 e0=00 e1=00 e2=00 e3=00 e4=00 e5=00 e6=00 e7=00 e8=00 e9=00 ea=00 eb=00 ec=00 ed=00 ee=00 ef=00 f0=00 f1=00 f2=00 f3=00 f4=00 f5=00 f6=00 f7=00 f8=00 f9=00 fa=00 fb=00 fc=00 fd=00 fe=00 ff=00 words 00= 01= 02= 03= 04= 05= 06= 07= 08= 09= 0a= 0b= 0c= 0d= 0e= 0f= iic0: addr 0x49 00=00 01=00 02=00 03=00 04=00 05=00 06=00 07=00 08=00 09=00 0a=00 0b=00 0c=00 0d=00 0e=00 0f=00 10=00 11=00 12=00 13=00 14=00 15=00 16=00 17=00 18=00 19=00 1a=00 1b=00 1c=00 1d=00 1e=00 1f=00 20=00 21=00 22=00 23=00 24=00 25=00 26=00 27=00 28=00 29=00 2a=00 2b=00 2c=00 2d=00 2e=00 2f=00 30=00 31=00 32=00 33=00 34=00 35=00 36=00 37=00 38=00 39=00 3a=00 3b=00 3c=00 3d=00 3e=00 3f=00 40=00 41=00 42=00 43=00 44=00 45=00 46=00 47=00 48=00 49=00 4a=00 4b=00 4c=00 4d=00 4e=00 4f=00 50=00 51=00 52=00 53=00 54=00 55=00 56=00 57=00 58=00 59=00 5a=00 5b=00 5c=00 5d=00 5e=00 5f=00 60=00 61=00 62=00 63=00 64=00 65=00 66=00 67=00 68=00 69=00 6a=00 6b=00 6c=00 6d=00 6e=00 6f=00 70=00 71=00 72=00 73=00
Re: HP Raid hardware
On 2008/01/22 11:59, Max wrote: Thanks for you answer. I know that hardware compatibilty page exists but drivers/hardware names are not really clear for me :| And does anyone know if HP SC40Ge SAS HBA RAID on Proliant DL160 G5 is supported ? I don't know for sure, but it's almost certainly an mpi(4) device.
Re: Problems with -current in CVS?
On Jan 22, 2008 12:11 AM, Ben Calvert [EMAIL PROTECTED] wrote: wrong instructions. the correct instructions are at: http://openbsd.org/faq/current.html You should ALWAYS use a snapshot as the starting point for running - current. Upgrading by compiling your own source code is not supported. Ben Right, thanks. I figured I missed something rather important. :) --- Colby
Re: Problems with -current in CVS?
On Jan 22, 2008 8:11 AM, Ben Calvert [EMAIL PROTECTED] wrote: On Jan 21, 2008, at 10:30 PM, Colby W. wrote: I tried two different AnonCVS repositories (one in the USA and one in CAN) tonight but ran into the same problem when I tried rebuilding the kernel to bring my recent -release install up to -current. Per the instructions [1]: [1] http://www.openbsd.org/faq/faq5.html wrong instructions. the correct instructions are at: http://openbsd.org/faq/current.html You should ALWAYS use a snapshot as the starting point for running - current. Upgrading by compiling your own source code is not supported. Ben Not supported is not the same thing as not working. I usually do it and it works fine but sometimes it breaks, easy as that. BR dunceor
problem with re driver
Hello, re driver freeze OpenBSD 4.2-current. This driver doesn't bug in NetBSD or FreeBSD. Users with re at pcie bus are suffering from this bug. Someting like: ppb2 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x01: irq 10 pci3 at ppb2 bus 3 re0 at pci3 dev 0 function 0 Realtek 8168 rev 0x01: RTL8168 2 (0x3800), irq 10, address 00:1c:c0:0f:08:bf rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 In certain situation, we must force the re interface to 100baseTX, but it's not always true. So, is anybody using this driver *with a pcie bus* without problems? This situation could help to solve the problem. Thanks you Nicolas
Carp creates a wide route if netmask is not used when carp is configured
Hi, I am using isakmpd+pf+sasyncd+carp to set a VPN network (OpenBSD 4.0) Recently had a problem with carp... Basically ifconfig carp0 inet 172.16.140.1 255.255.255.0 advbase 1 ... versus ifconfig carp0 inet 172.16.140.1 netmask 255.255.255.0 advbase 1 ... The simple fact that I not put the word netmask creates a route 172.16/16 on carp0 interface which was causing a lot of trouble. Same thing with /etc/hostname.carp0 if the word netmask is not there. On the first firewall I have: - external 172.16.140.1/24 - internal 172.16.160.1/24 On the second firewall I have: - external 172.16.140.2/24 - internal 172.16.161.1/24 Problem description: 1. When the firewall is booting, it first configures the IP addresses (/etc/netstart). 2. The moment carp is configured I can see a new route 172.16/16 on interface carp0 (using route -n show). 3. A fraction of a second later a PC behind the first firewall sends a packet from the 172.16.160.2 to 172.16.161.2 (PC behind the second firewall) 4. An entry is added to the routing table assigning the destination IP to carp0 interface (external) since the packet matches the 172.16/16 route. 5. A seconds later the route is added route add -net 172.16.161.0/24 172.16.140.2 but the existing route 172.16.161.2 on interface carp0 is used (which makes sense because the narrower route has preference) Now if I put the work netmask in the hostname.carp0 (external) and hostname.carp1 (internal) this route is not created. A packet coming from a PC behind the firewall would be dropped as there is no route for it. A second later when the route is added the packets will be routed properly. The man carp page is correct but the other documentation www.openbsd.org/faq/pf/carp.html www.countersiege.com/doc/pfsync-carp www.lugbe.ch/action/reports/BSDCluster.pdf (German) http://www.nycbsdcon.org/2005/files/jdixon_firewall_failover.pdf in my opinion do not configure carp properly. What is nasty about this is that carp is configured and ifconfig carp shows everything is OK. If netmask is required than an error should be displayed. If it's optional, then in both cases the result should be the same. I remember a similar problem with carp where the command line parameter order did matter: http://www.webservertalk.com/archive248-2007-3-1848404.html Regards, Catalin - Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail
Re: Carp creates a wide route if netmask is not used when carp is configured
On 2008/01/22 10:14, catalin visinescu wrote: Basically ifconfig carp0 inet 172.16.140.1 255.255.255.0 advbase 1 ... N.B. ifconfig and hostname.if do *not* use the same format.
Re: OpenBSD 4.2 firewall freezing, even after patch 004 and 005
On Jan 21, 2008, at 10:58 PM, Robert Carr wrote: http://openbsd.org/faq/faq5.html#Why excerpt Some reasons why you should not build a custom kernel: You will not get any support from developers. You will be expected to reproduce any problem with a GENERIC kernel before developers take any problem report seriously. /excerpt Yes, I get that. apparently not [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/NAVARONE-4.2 http://openbsd.org/faq/faq5.html#Why --knitti ben
Re: Problems with -current in CVS?
In my update process, I always bootstrap a new version of gcc first, and do the kernel last. So far, this process has kept me out of problems like this. * Dusty [EMAIL PROTECTED] [2008-01-22 09:34:54]: I had this too, you need to build yourself a new version f gcc. I see someone posted faq5 .. you want to 'follow current' it has those instructions. On Jan 22, 2008 8:30 AM, Colby W. [EMAIL PROTECTED] wrote: I tried two different AnonCVS repositories (one in the USA and one in CAN) tonight but ran into the same problem when I tried rebuilding the kernel to bring my recent -release install up to -current. Per the instructions [1]: # cd usr/ ; cvs checkout -P src # cd /usr/src/sys/arch/i386/conf/ # config GENERIC ../../../../conf/files:1005: syntax error ../../../../conf/files:1006: syntax error ../../../../conf/files:1007: syntax error ../../../../conf/files:1008: syntax error ../../../../conf/files:1009: syntax error ../../../../conf/files:1010: syntax error ../../../../conf/files:1011: syntax error ../../../../conf/files:1012: syntax error ../../../../conf/files:1013: syntax error ../../../../conf/files:1014: syntax error ../../../../conf/files:1015: syntax error ../../../../conf/files:1016: syntax error ../../../../conf/files:1017: syntax error ../../../../conf/files:1018: syntax error ../../../../conf/files:1019: syntax error ../../../../conf/files:1020: syntax error ../../../../conf/files:1021: syntax error ../../../../conf/files:1022: syntax error ../../../../conf/files:1023: syntax error ../../../../conf/files:1024: syntax error ../../../../conf/files:1025: syntax error ../../../../conf/files:1026: syntax error ../../../../conf/files:1027: syntax error ../../../../conf/files:1028: syntax error ../../../../conf/files:1029: syntax error ../../../../conf/files:1030: syntax error ../../../../conf/files:1031: syntax error ../../../../conf/files:1032: syntax error ../../../../conf/files:1033: syntax error ../../../../conf/files:1034: syntax error ../../../../conf/files:1035: syntax error ../../../../conf/files:1036: syntax error ../../../../conf/files:1037: syntax error ../../../../conf/files:1038: syntax error *** Stop. Is this a problem with a config file checked into CVS or am I missing something? From what I can determine, there is no ../../../../conf/files but there is ../../../conf/files (one directory closer to /usr/src/sys/arch/i386/conf : ie., /usr/src/sys/conf/). Thanks in advance, Colby W. [1] http://www.openbsd.org/faq/faq5.html -- Travers Buda
Formulaires de contacts commerciaux
Si ce message ne s'affiche pas correctement, vous pouvez le visualiser en suivant ce lien. RECEVEZ vos FORMULAIRES DE CONTACT grbce au concept Centralead Et PROFITEZ de LâOFFRE DECOUVERTE A 30⬠HT Seulement* : 1 Vous recevrez pendant 3 mois ` compter de votre inscription, tous les formulaires des personnes qui souhaitent acheter vos produits ou services avec leurs coordonnies que nous recenserons chaque semaine Nous communiquons chaque semaine pour tous produits et services vers plus de 2 500 000 contacts, et centralisons toutes les demandes sous forme de formulaires renseignis (leads) (*offre valable pour toute inscription avant le 31janvier 2008) 2 Vous nâaurez plus quâ` les transmettre ` votre service commercial qui se chargera de finaliser des ventes Informations et inscription Si vous disirez ne plus recevoir de mail de notre part, cliquez ici
ICMP6 message size
Hi all, I have two hosts, one in OpenBSD 4.2 (stable) and another is Redhat ESv4u4 When I ping (ipv6) from OpenBSD to Redhat with custom size for icmp6 (-s option), I cannot go past 8184, 8185 and above give me an error EMSGSIZE. Whereas pinging from Redhat to OpenBSD I can go beyond 8184, infact I am able to go 1, above that I have not tried it yet. Is this behavior expected?, OpenBSD IPv6 Address: fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 Redhat IPv6 Address: fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 command: ping6 -s SIZE -c 5 HOST Test from OpenBSD Basic ping with 56 bytes: openbsd-test: [~] [84]$ ping6 -c 2 fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 PING6(56=40+8+8 bytes) fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 -- fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 16 bytes from fd1b:d92f:84f3:167:214:22ff:fe7b:cc68, icmp_seq=0 hlim=63 time=7.987 ms 16 bytes from fd1b:d92f:84f3:167:214:22ff:fe7b:cc68, icmp_seq=1 hlim=63 time=2.029 ms --- fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 ping6 statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 2.029/5.008/7.987/2.979 ms Ping with custom size set to 8184 bytes: openbsd-test: [~] [85]$ ping6 -c 2 -s 8184 fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 PING6(8232=40+8+8184 bytes) fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 -- fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 8192 bytes from fd1b:d92f:84f3:167:214:22ff:fe7b:cc68, icmp_seq=0 hlim=63 time=24.35 ms 8192 bytes from fd1b:d92f:84f3:167:214:22ff:fe7b:cc68, icmp_seq=1 hlim=63 time=19.296 ms --- fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 ping6 statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 19.296/21.823/24.350/2.527 ms Ping with custom size set to 8185 bytes: openbsd-test: [~] [86]$ ping6 -c 2 -s 8185 fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 PING6(8233=40+8+8185 bytes) fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 -- fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 ping6: sendmsg: Message too long ping6: wrote fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 8193 chars, ret=-1 ping6: sendmsg: Message too long ping6: wrote fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 8193 chars, ret=-1 --- fd1b:d92f:84f3:167:214:22ff:fe7b:cc68 ping6 statistics --- 2 packets transmitted, 0 packets received, 100.0% packet loss Test from Redhat: Basic ping: [EMAIL PROTECTED] ~]# ping6 -c 2 fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 PING fd1b:d92f:84f3:125:20c:29ff:fe8d:f732(fd1b:d92f:84f3:125:20c:29ff:fe8d:f732) 56 data bytes 64 bytes from fd1b:d92f:84f3:125:20c:29ff:fe8d:f732: icmp_seq=0 ttl=63 time=3.17 ms 64 bytes from fd1b:d92f:84f3:125:20c:29ff:fe8d:f732: icmp_seq=1 ttl=63 time=1.79 ms --- fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 1.797/2.487/3.178/0.692 ms, pipe 2 Ping with custom size set to 8184: [EMAIL PROTECTED] ~]# ping6 -c 2 -s 8184 fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 PING fd1b:d92f:84f3:125:20c:29ff:fe8d:f732(fd1b:d92f:84f3:125:20c:29ff:fe8d:f732) 8184 data bytes 8192 bytes from fd1b:d92f:84f3:125:20c:29ff:fe8d:f732: icmp_seq=0 ttl=63 time=9.37 ms 8192 bytes from fd1b:d92f:84f3:125:20c:29ff:fe8d:f732: icmp_seq=1 ttl=63 time=9.32 ms --- fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 9.322/9.349/9.377/0.100 ms, pipe 2 Ping with custom size set to 8185: [EMAIL PROTECTED] ~]# ping6 -c 2 -s 8185 fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 PING fd1b:d92f:84f3:125:20c:29ff:fe8d:f732(fd1b:d92f:84f3:125:20c:29ff:fe8d:f732) 8185 data bytes 8193 bytes from fd1b:d92f:84f3:125:20c:29ff:fe8d:f732: icmp_seq=0 ttl=63 time=9.36 ms 8193 bytes from fd1b:d92f:84f3:125:20c:29ff:fe8d:f732: icmp_seq=1 ttl=63 time=9.40 ms --- fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 9.362/9.382/9.403/0.099 ms, pipe 2 Ping with custom size set to 1: [EMAIL PROTECTED] ~]# ping6 -c 2 -s 1 fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 PING fd1b:d92f:84f3:125:20c:29ff:fe8d:f732(fd1b:d92f:84f3:125:20c:29ff:fe8d:f732) 1 data bytes 10008 bytes from fd1b:d92f:84f3:125:20c:29ff:fe8d:f732: icmp_seq=0 ttl=63 time=11.0 ms 10008 bytes from fd1b:d92f:84f3:125:20c:29ff:fe8d:f732: icmp_seq=1 ttl=63 time=21.0 ms --- fd1b:d92f:84f3:125:20c:29ff:fe8d:f732 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 11.086/16.044/21.002/4.958 ms, pipe 2 OpenBSD uname: OpenBSD openbsd-test.contoso.com 4.2 GENERIC#375 i386 ifconfig from OpenBSD: lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33208 groups: lo inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 pcn0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:0c:29:8d:f7:32 groups: egress
Re: RAIDframe sparc64
GENIUS! On 22 Jan 2008, at 20:27, Scott Francis wrote: On Nov 24, 2007 5:14 PM, David Newman [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/19/07 4:14 AM, Khalid Schofield wrote: Hi, can anyone tell me about RAIDframe under the sparc64 platform? Does it work? How good it is? How do I enable it in the kernel config since in GENERIC I can see no ref to it. RAIDframe works fine with sparc64. I've been running that way for a couple of years with no issues. Marcus Redivo wrote a nice howto for RAIDframe. I noted the sparc64-specific differences here: yup saw his howto some time ago but didn't see your notes as yet http://www.mail-archive.com/misc@openbsd.org/msg36094.html One thing I haven't figured out is upgrading, but this might help: http://www.mail-archive.com/misc@openbsd.org/msg43949.html thought I'd add my two cents - I finally got my root-on-RAID1 (netra, 2x73GB SCSI disks) running. The guide at http://www.linux.com/feature/52713 is pretty helpful, but there was one fairly important bit missing having to do specifically with sparc64 architecture ... unfortunately, I forgot to write it down, and now I don't remember what it was. :( When/if I remember, I'll make sure I send it on to the list (and probably add it to the docs at http://darkuncle.net/openbsd/). -- [EMAIL PROTECTED],darkuncle.net} || 0x5537F527 http://darkuncle.net/pubkey.asc for public key
Re: problem with re driver
On Tue, 22 Jan 2008, Nicolas Letellier wrote: re driver freeze OpenBSD 4.2-current. This driver doesn't bug in NetBSD or FreeBSD. Users with re at pcie bus are suffering from this bug. Someting like: ppb2 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x01: irq 10 pci3 at ppb2 bus 3 re0 at pci3 dev 0 function 0 Realtek 8168 rev 0x01: RTL8168 2 (0x3800), irq 10, address 00:1c:c0:0f:08:bf rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 In certain situation, we must force the re interface to 100baseTX, but it's not always true. This did not help in my case. As I tracked down multicast packets as the cause for the freezes I tried to disable the multicast filter. This is no good fix for the problem, but the symptoms went away. This is by the way the same thing the linux driver does (did I mention that it is not a real fix?). After adding the following patch the box did not freeze any longer: Index: re.c === RCS file: /var/cvs/src/sys/dev/ic/re.c,v retrieving revision 1.75 diff -u -p -r1.75 re.c --- re.c16 Jan 2008 09:52:34 - 1.75 +++ re.c22 Jan 2008 21:44:56 - @@ -570,6 +570,7 @@ re_setmulti(struct rl_softc *sc) case RL_HWREV_8101E: case RL_HWREV_8168_SPIN1: case RL_HWREV_8168_SPIN2: + hashes[1] = hashes[0] = 0x; CSR_WRITE_4(sc, RL_MAR0, swap32(hashes[1])); CSR_WRITE_4(sc, RL_MAR4, swap32(hashes[0])); break; dmesg part is this (full dmesg is in br#5599): pci0 at mainbus0 bus 0: configuration mode 1 (no bios) ppb1 at pci0 dev 6 function 0 ATI RX480 PCIE rev 0x00 pci2 at ppb1 bus 2 re0 at pci2 dev 0 function 0 Realtek 8168 rev 0x01: RTL8168 2 (0x3800), apic 2 int 18 (irq 10), address 00:19:db:60:e4:a2 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 So, is anybody using this driver *with a pcie bus* without problems? This situation could help to solve the problem. Without problems I would not call that. And the patch is really a hack. But it works, and the box does not freeze if someone starts a linux computer in the same LAN segment which does that multicast autoconf thingy. Best regards, Markus
Respond Please
Sir/Madam, I am Mr.Edawe John , and I am contacting you from Dakar, Senegal for a mutual business relationship and investment. I have some funds realized through contract execution and I need your cooperation to invest the funds. The first stage requires transferring the funds to your account for subsequent investment. I have chosen to contact you because you live in a country where I want to invest in. I therefore want you to work with me as a partner. On receipt of your response, I will send you full details of the transaction and more information about myself. I await your prompt response. Best regards, Edawe John.
Lid closed, system freeze with X11 on the console
Hi, I can easly reproduce system freeze on my ThinkPad X40 when I start Xorg and close the lid. System hangs right away, but when I select text console before I close the lid, everything is fine. Capslock, numlock doesn't work either after freeze. This happens after recent update. System without xorg.conf file. Can anyone confirm that? $ sysctl -n kern.version OpenBSD 4.2-current (GENERIC) #650: Fri Jan 18 15:08:48 MST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC -- best regards q# OpenBSD 4.2-current (GENERIC) #650: Fri Jan 18 15:08:48 MST 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 1200MHz (GenuineIntel 686-class) 1.20 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,SBF,EST,TM2 real mem = 1063743488 (1014MB) avail mem = 1020669952 (973MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 02/03/04, BIOS32 rev. 0 @ 0xfd740, SMBIOS rev. 2.33 @ 0xe0010 (56 entries) bios0: vendor IBM version 1UET63WW (1.14 ) date 02/03/2004 bios0: IBM 23717GU apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 100% apm0: AC on, battery charge high acpi at bios0 function 0x0 not configured pcibios0 at bios0: rev 2.1 @ 0xfd6d0/0x930 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdeb0/256 (14 entries) pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371FB ISA rev 0x00) pcibios0: PCI bus #3 is the last bus bios0: ROM list: 0xc/0xc800! 0xcc800/0x1000 0xcd800/0x1000 0xdc000/0x4000! 0xe/0x1 cpu0 at mainbus0 cpu0: Enhanced SpeedStep 1200 MHz (1180 mV): speeds: 1200, 1100, 1000, 900, 800, 600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82855GM Host rev 0x02 agp0 at pchb0: aperture at 0xe000, size 0x800 Intel 82855GM Memory rev 0x02 at pci0 dev 0 function 1 not configured Intel 82855GM Config rev 0x02 at pci0 dev 0 function 3 not configured vga1 at pci0 dev 2 function 0 Intel 82855GM Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) Intel 82855GM Video rev 0x02 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 29 function 0 Intel 82801DB USB rev 0x01: irq 11 uhci1 at pci0 dev 29 function 1 Intel 82801DB USB rev 0x01: irq 11 uhci2 at pci0 dev 29 function 2 Intel 82801DB USB rev 0x01: irq 11 ehci0 at pci0 dev 29 function 7 Intel 82801DB USB rev 0x01: irq 11 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb0 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0x81 pci1 at ppb0 bus 2 cbb0 at pci1 dev 0 function 0 Ricoh 5C476 CardBus rev 0x8d: irq 11 sdhc0 at pci1 dev 0 function 1 Ricoh 5C822 SD/MMC rev 0x13: irq 11 sdmmc0 at sdhc0 em0 at pci1 dev 1 function 0 Intel PRO/1000MT Mobile (82541GI) rev 0x00: irq 11, address 00:0a:e4:24:f5:f3 ipw0 at pci1 dev 2 function 0 Intel PRO/Wireless 2100 rev 0x04: irq 11, address 00:0c:f1:26:27:cc cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 3 device 0 cacheline 0x0, lattimer 0xb0 pcmcia0 at cardslot0 ichpcib0 at pci0 dev 31 function 0 Intel 82801DBM LPC rev 0x01: 24-bit timer at 3579545Hz pciide0 at pci0 dev 31 function 1 Intel 82801DBM IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: HITACHI_DK13FA-40B wd0: 16-sector PIO, LBA, 38154MB, 78140160 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 pciide0: channel 1 disabled (no drives) ichiic0 at pci0 dev 31 function 3 Intel 82801DB SMBus rev 0x01: irq 11 iic0 at ichiic0 spdmem0 at iic0 addr 0x51: 512MB DDR SDRAM non-parity PC2700CL2.5 auich0 at pci0 dev 31 function 5 Intel 82801DB AC97 rev 0x01: irq 11, ICH4 AC97 ac97: codec id 0x41445374 (Analog Devices AD1981B) ac97: codec features headphone, 20 bit DAC, No 3D Stereo audio0 at auich0 Intel 82801DB Modem rev 0x01 at pci0 dev 31 function 6 not configured usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 usb3 at uhci2: USB revision 1.0 uhub3 at usb3 Intel UHCI root hub rev 1.00/1.00 addr 1 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 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 aps0 at isa0 port 0x1600/31 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 biomask effd netmask effd ttymask mtrr: Pentium Pro MTRR support softraid0 at root root on wd0a swap on wd0b dump on wd0b (--) checkDevMem: using aperture driver /dev/xf86 (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32) This is a pre-release version of the X server
Re: Lid closed, system freeze with X11 on the console
On Jan 23, 2008 1:39 AM, Mikolaj Kucharski [EMAIL PROTECTED] wrote: Hi, I can easly reproduce system freeze on my ThinkPad X40 when I start Xorg and close the lid. System hangs right away, but when I select text console before I close the lid, everything is fine. Capslock, numlock doesn't work either after freeze. This happens after recent update. System without xorg.conf file. Can anyone confirm that? You happen to have a broken snaphot where the i810_drv.so file is a symlink to the newer intel driver instead of being the real version 1.4 .1 i810 driver. The kind of problems you're seeing with the intel driver is precisely the reason why we decided to keep the old version around. Update to a newer snapshot (or at least a newer xserver42) to go back to the working i810 driver. -- Matthieu
