Re: OpenBSD 5.1 XEN HVM DomU - kernel panic
On Wed, Jun 06, 2012 at 04:04:22PM +0200, Andre Keller wrote: > is any body running OpenBSD as a XEN HVM guest? I have a difficult time > accomplish that... Hi, I'm insane and I do that for a long time, because I don't really have a lot of options there. > The XEN guest does boot up and is usable. When f.e. do a cvs checkout of > ports the machine panics about every other time. I'm on Centos 5 without problems here, both with 5.1-release and -current snapshot. The performance is horrible as always, though. > ddb> trace > cpu_switchto() at cpu_switchto+0x4b Hint: when you are seeing crashes inside a context switch, someone may be interested in what processes took part in the switch, like "show proc $rdi" and "show proc $rsi". Then, "sh reg" and "x /x,30 $rsp" for starters. (pity it won't fit all on one screen) Also, you can say if you ran other versions of OpenBSD on the same configuration, or messed with the hypervisor's kernel lately, or if it is a new install on an out of the box dom0 that just happens to fail. -- Martin Pelikan OpenBSD 5.1-current (GENERIC) #258: Mon Jun 11 11:52:20 MDT 2012 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 535797760 (510MB) avail mem = 499265536 (476MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe901f (10 entries) bios0: vendor Xen version "3.1.2-194.3.1.el5" date 03/07/2012 bios0: Red Hat HVM domU acpi0 at bios0: rev 2, ACPI control unavailable mpbios0 at bios0: Intel MP Specification 1.4 cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz, 2388.47 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,SBF,SSE3,DS-CPL,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF cpu0: 4MB 64b/line 16-way L2 cache cpu0: apic clock running at 99MHz mpbios0: bus 0 is type ISA ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 48 pins ioapic0: misconfigured as apic 0, remapped to apid 1 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02 pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00 pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility wd0 at pciide0 channel 0 drive 0: wd0: 16-sector PIO, LBA48, 10240MB, 20971520 sectors wd0(pciide0:0:0): using PIO mode 0, DMA mode 2 pciide0: channel 1 disabled (no drives) piixpm0 at pci0 dev 1 function 2 "Intel 82371AB Power" rev 0x03: SMBus disabled vga1 at pci0 dev 2 function 0 "Cirrus Logic CL-GD5446" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) "XenSource Platform Device" rev 0x01 at pci0 dev 3 function 0 not configured em0 at pci0 dev 4 function 0 "Intel PRO/1000MT (82540EM)" rev 0x03: apic 1 int 5, address 00:16:3e:90:cc:2d isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16450, no fifo 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 spkr0 at pcppi0 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: density unknown fd1 at fdc0 drive 1: density unknown nvram: invalid checksum mtrr: Pentium Pro MTRR support vscsi0 at root scsibus0 at vscsi0: 256 targets softraid0 at root scsibus1 at softraid0: 256 targets root on wd0a (4792285ca7b2d7f5.a) swap on wd0b dump on wd0b clock: unknown CMOS layout
Re: pf and ICMP in asymmetric routing setups
On 2012-06-12, Simon Perreault wrote: > On 2012-06-12 14:08, Bernd wrote: >> I've got two OpenBSD 5.1-stable/amd64 boxes employed which do all the >> routing for our AS (OpenBGPd and OpenOSPFd). I see asymmetric traffic (I >> thought it to be that way), which itself doesn't really create problems. >> However, I see problems with ICMP. pf seems to drop all but the first >> response from any of the hosts within our network (seen from the Internet). >> >> Any idea how to deal with this? As soon as I turn off pf, everything >> runs smoothly. > > Without having the details of your setup, the big principle is: pf is > stateful (by default). Statefulness doesn't play well with asymmetric > routing. I'm sure if you investigate a little bit more you'll discover > it's not limited to ICMP. > > In the end the solution will be one of: remove statefulness, avoid > asymmetric routing, or share state with pfsync. If using pfsync for this, you would want to look at "defer", see pfsync(4). Sloppy states might be more appropriate for this scenario though, and would let you use other things which require state tracking, e.g. pflow(4).
Ley, Reglamento, Manual y su Aplicacion
 © 2012 Conference Corporativo S.C. Asista a los 45 Mejores Cursos en México de la Serie:ADQUISICIONES y OBRAS PÚBLICAS Incluye 4 cursos de ALTO IMPACTO para el CIERRE de GESTIÓN 2012: 1) Taller para la Elaboración Puntual de las Memorias Documentales 2) Curso sobre el LIBRO BLANCO y las Memorias Documentales del Sector Público Mexicano 3) Curso sobre CÓMO SOLVENTAR OBSERVACIONES 4) Taller para la Elaboración del ACTA DE ENTREGA RECEPCIÓN Y RENDICIÓN DE CUENTAS Cursos, Contenidos y Metodologías Desarrollados en Alianza con las Mejores Universidades Europeas con Calidad ISO 9000. Haga click para desplegar información Curso 1 Licitaciones Electrónicas de las ADQUISICIONES - COMPRANET 5.0 para Servidores Públicos (Convocantes). Curso 2 Licitaciones Electrónicas de las OBRAS PÚBLICAS - COMPRANET 5.0 para Servidores Públicos (Convocantes). Curso 3 (NUEVO) LIBRO BLANCO y las Memorias Documentales del Sector Público Mexicano. Curso 4 ACTA DE ENTREGA RECEPCIÓN Y RENDICIÓN DE CUENTAS (NUEVO). Curso 5 Cómo Solventar Observaciones (BASADO EN JURISPRUDENCIA DEFINIDA DE LA SUPREMA CORTE DE JUSTICIA DE LA NACIÓN) (Incluye Acuerdo por el Cual se Establecen las Disposiciones Generales para la Realización de Auditorías, Revisiones y Visitas de Inspección). Curso 6 Ley Federal de Responsabilidades Administrativas. Curso 7 Ley de Adquisiciones. Curso 8 Ley de Obras Públicas. Curso 9 MANUAL Administrativo de ADQUISICIONES. Curso 10 MANUAL Administrativo de OBRAS PÚBLICAS. Curso 11 Manual Administrativo de RECURSOS MATERIALES y SERVICIOS GENERALES. Curso 12 Investigación de Mercados y los Criterios de Evaluación para Adquisiciones Gubernamentales. Curso 13 Licitaciones y Contrataciones de las Adquisiciones. Curso 14 Licitaciones y Contrataciones de las Obras Públicas. Curso 15 Reglamento de la Ley de Adquisiciones. Curso 16 Reglamento de la Ley de Obras Públicas. Curso 17 Almacenes e Inventarios Gubernamentales. Curso 18 Criterios de Evaluación de Propuestas Económicas en Adquisiciones. Curso 19 Criterios de Evaluación de Propuestas Económicas en Obra Pública. Curso 20 Matriz de Administración de Riesgos (MAR). Curso 21 Bitácora Electrónica de la Obra Púbica. Curso 22 Prevención y Solución de Inconformidades. Curso 23 Auditoría de Adquisiciones para Auditores. Curso 24 Auditoría de Obra Pública para Auditores. Curso 25 Auditoría de Adquisiciones para Auditados. Curso 26 Auditoría de Obra Pública para Auditados. Curso 27 Procedimiento Administrativo y Defensa Estratégica de los Servidores Públicos. Curso 28 POBALINES y los Mecanismos para la Evaluación de Proposiciones. Curso 29 Régimen Jurídico de las Responsabilidades de los Servidores Públicos. Curso 30 Residencia, Supervisión y Control de Obras Públicas. Curso 31 PRECIOS UNITARIOS. Curso 32 Clasificador por Objeto del Gasto. Curso 33 Desincorporación Patrimonial de Bienes Muebles. Curso 34 Reglas de Registro y Valoración del Patrimonio. Curso 35 Administración del Parque Vehicular en el Gobierno Mexicano. Curso 36 Ley Federal de Presupuesto y Responsabilidad Hacendaria y su Reglamento. Curso 37 Manual de Contabilidad Gubernamental. Curso 38 Manual Administrativo de RECURSOS HUMANOS. Curso 39 Servicio Profesional de Carrera y su Reglamento. Curso 40 Manual del Servicio Profesional de Carrera. Curso 41 Manual Administrativo de Aplicación General en Materia de Tecnologías de la Información y Comunicaciones (TIC). Curso 42 Manual de Transparencia. Curso 43 Disposiciones en Materia de Control Interno y su Manual Administrativo. Curso 44 Auditorías, Revisiones y Visitas de Inspección. Curso 45 Lineamientos sobre Indicadores para Medir los Avances Físicos y Financieros. Atención Ejecutiva Centro de Atención Telefónica: DF y Área Metropolitana (55) 91 40 30 30 Lada sin costo: (01 800) 439 66 66 ESTE MAIL CUMPLE CON LAS POLíTICAS ANTISPAM INTERNACIONALES Y LOCALES. Para darse de baja sólo haga click aquí
Re: OpenBSD on minimac
On Jun 12 23:18:57, Otto Moerbeek wrote: > You might be able to build a GENERIC with a line: > config bsd root on wd0a Yes, that does it. A kernel with a hardcoded root device (wd0a) doesn't have this problem and boots alright. Thank you! (It seems I will need to do this after every upgrade, unless I figure out what's going on between the confused ofw and the kernel.) Jan
Re: OpenBSD on minimac
> iirc the kernel gets a boot path from ofw, and tries to map that to a > unix device to find it's root partition. On Jun 13 00:23:43, Halvard wrote: > Try Self-Hypnosis for Personal Growth I guess I'm about to try that next, actually ...
Re: OpenBSD on minimac
On Jun 12 23:18:57, Otto Moerbeek wrote: > On Tue, Jun 12, 2012 at 11:04:35PM +0200, Jan Stary wrote: > > > On Jun 12 22:20:16, Otto Moerbeek wrote: > > > On Tue, Jun 12, 2012 at 10:00:05PM +0200, Jan Stary wrote: > > > > > > > On Jun 12 21:27:18, Jan Stary wrote: > > > > > On Jun 12 20:17:38, Jan Stary wrote: > > > > > > > There is another problem now though: > > > > > > > the booting sequence ends with > > > > > > > > > > > > > > bootpath /pci@f400/ata-6@d/disk@1:/bsd > > > > > > > root device: _ > > > > > > > > > > > > > > and that's where it stops, with '_' indicating the cursor. > > > > > Also, I cannot actually type anything here. > > > > > > > > > > Could this be that the installed /bsd does not > > > > > understand the DUID names in /etc/fstab? > > > > > > > > No, that's not it. I reinstalled yet again, using the old wd0.x > > > > instead of DUIDs, but the boot of the installed /bsd fails > > > > in the same way. > > > > > > > > > > > > > > > > I can still boot from the cd, with > > > > > > > > > > > > boot /pci@f400/ata-6@d/disk@1:,ofwboot /5.1/macppc/bsd > > > > > > > > > > > > That boots fine, with the dmesg ending with > > > > > > > > > > > > bootpath /pci@f400/ata-6@d/disk@0:/5.1/macppc/bsd > > > > > > root on wd0a (duid.a) swap on wd0b dump on wd0b > > > > > > > > What could be the difference between /5.1/macppc/bsd > > > > that boots fine and the installed /bsd that fails as above? > > > > > > > > If I just copy /5.1/macppc/bsd to /bsd, it fails the same, > > > > which puzzles me even more. > > > > > > > > The installed /bsd.rd boots fine - but that knows about > > > > root being on rd0a in advance, right? > > > > > > If ofw is is confused about the paths the following two scenarios can > > > happen: > > > > > > boot from cd: bsd gets an incorrect boot path from ofw that actually > > > points to the hard disk, and (by acccident) you boot ok. > > > > That's quite possibly what happens for me. > > Thank you for the insight. > > > > > boot from hd: bsd gets an incorrect boot path from ofw that points to > > > nowhere, so you don;t boot ok. > > > > Is there a way to unconfuse ofw and make it pass the right > > boot path to the kernels it boots? > > > > Not that I fully understand what a "bootpath" is. > > The pre-last line of the dmesg of both my boot attempts > > (from the CD, from the disk) seems to be the right path > > to the kernel that is actually booting. It's the "root device" > > where it gets stuck. > > iirc the kernel gets a boot path from ofw, and tries to map that to a > unix device to find it's root partition. If that is the case, then (1) the installed /bsd gets the bootpath "/pci@f400/ata-6@d/disk@1:/bsd" from ofw, but fails to map that to "/dev/wd0a" (2) /5.1/macppc/bsd gets "/pci@f400/ata-6@d/disk@0:/5.1/macppc/bsd" and maps that to "root on wd0a ..." - am I understanding that correctly? If so, is that /bsd's problem, (not to be able to figure out the root device), or do I need to somehow unconfuse ofw about the devices? I tried devalias hd /pci@f400/ata-6@d/disk@1 devalias cd /pci@f400/ata-6@d/disk@0 reset-all to set it straight, but that (a) doesn't solve it and (b) doesn't survive a reboot. > You might be able to build a GENERIC with a line: > > config bsd root on wd0a > > (instead of config bsd swap generic) > > That producs a kernel that will look for its root on wd0a. Thanks, I will try that. Meanwhile, I got the same advice from http://www.netbsd.org/ports/macppc/faq.html#dash-a (the whole page is actually quite helpful to a macppc newcomer). Jan
Re: OpenBSD on minimac
On Tue, Jun 12, 2012 at 11:04:35PM +0200, Jan Stary wrote: > On Jun 12 22:20:16, Otto Moerbeek wrote: > > On Tue, Jun 12, 2012 at 10:00:05PM +0200, Jan Stary wrote: > > > > > On Jun 12 21:27:18, Jan Stary wrote: > > > > On Jun 12 20:17:38, Jan Stary wrote: > > > > > > There is another problem now though: > > > > > > the booting sequence ends with > > > > > > > > > > > > bootpath /pci@f400/ata-6@d/disk@1:/bsd > > > > > > root device: _ > > > > > > > > > > > > and that's where it stops, with '_' indicating the cursor. > > > > Also, I cannot actually type anything here. > > > > > > > > Could this be that the installed /bsd does not > > > > understand the DUID names in /etc/fstab? > > > > > > No, that's not it. I reinstalled yet again, using the old wd0.x > > > instead of DUIDs, but the boot of the installed /bsd fails > > > in the same way. > > > > > > > > > > > > > I can still boot from the cd, with > > > > > > > > > > boot /pci@f400/ata-6@d/disk@1:,ofwboot /5.1/macppc/bsd > > > > > > > > > > That boots fine, with the dmesg ending with > > > > > > > > > > bootpath /pci@f400/ata-6@d/disk@0:/5.1/macppc/bsd > > > > > root on wd0a (duid.a) swap on wd0b dump on wd0b > > > > > > What could be the difference between /5.1/macppc/bsd > > > that boots fine and the installed /bsd that fails as above? > > > > > > If I just copy /5.1/macppc/bsd to /bsd, it fails the same, > > > which puzzles me even more. > > > > > > The installed /bsd.rd boots fine - but that knows about > > > root being on rd0a in advance, right? > > > > If ofw is is confused about the paths the following two scenarios can > > happen: > > > > boot from cd: bsd gets an incorrect boot path from ofw that actually > > points to the hard disk, and (by acccident) you boot ok. > > That's quite possibly what happens for me. > Thank you for the insight. > > > boot from hd: bsd gets an incorrect boot path from ofw that points to > > nowhere, so you don;t boot ok. > > Is there a way to unconfuse ofw and make it pass the right > boot path to the kernels it boots? > > Not that I fully understand what a "bootpath" is. > The pre-last line of the dmesg of both my boot attempts > (from the CD, from the disk) seems to be the right path > to the kernel that is actually booting. It's the "root device" > where it gets stuck. iirc the kernel gets a boot path from ofw, and tries to map that to a unix device to find it's root partition. > > I guess I will need to learn more about ofw than I thought > I would need. Sigh, the horrors of macintosh. You might be able to build a GENERIC with a line: config bsd root on wd0a (instead of config bsd swap generic) That producs a kernel that will look for its root on wd0a. > > > Now why you cannot type a boot path in response to the prompt I don't know. > > It's like it doesn't even know about the keyboard being there. > Is that the booting kernel's problem, or is it an ofw problem? I don't know the answer to that one. -Otto
Re: OpenBSD on minimac
On Jun 12 22:20:16, Otto Moerbeek wrote: > On Tue, Jun 12, 2012 at 10:00:05PM +0200, Jan Stary wrote: > > > On Jun 12 21:27:18, Jan Stary wrote: > > > On Jun 12 20:17:38, Jan Stary wrote: > > > > > There is another problem now though: > > > > > the booting sequence ends with > > > > > > > > > > bootpath /pci@f400/ata-6@d/disk@1:/bsd > > > > > root device: _ > > > > > > > > > > and that's where it stops, with '_' indicating the cursor. > > > Also, I cannot actually type anything here. > > > > > > Could this be that the installed /bsd does not > > > understand the DUID names in /etc/fstab? > > > > No, that's not it. I reinstalled yet again, using the old wd0.x > > instead of DUIDs, but the boot of the installed /bsd fails > > in the same way. > > > > > > > > > > I can still boot from the cd, with > > > > > > > > boot /pci@f400/ata-6@d/disk@1:,ofwboot /5.1/macppc/bsd > > > > > > > > That boots fine, with the dmesg ending with > > > > > > > > bootpath /pci@f400/ata-6@d/disk@0:/5.1/macppc/bsd > > > > root on wd0a (duid.a) swap on wd0b dump on wd0b > > > > What could be the difference between /5.1/macppc/bsd > > that boots fine and the installed /bsd that fails as above? > > > > If I just copy /5.1/macppc/bsd to /bsd, it fails the same, > > which puzzles me even more. > > > > The installed /bsd.rd boots fine - but that knows about > > root being on rd0a in advance, right? > > If ofw is is confused about the paths the following two scenarios can > happen: > > boot from cd: bsd gets an incorrect boot path from ofw that actually > points to the hard disk, and (by acccident) you boot ok. That's quite possibly what happens for me. Thank you for the insight. > boot from hd: bsd gets an incorrect boot path from ofw that points to > nowhere, so you don;t boot ok. Is there a way to unconfuse ofw and make it pass the right boot path to the kernels it boots? Not that I fully understand what a "bootpath" is. The pre-last line of the dmesg of both my boot attempts (from the CD, from the disk) seems to be the right path to the kernel that is actually booting. It's the "root device" where it gets stuck. I guess I will need to learn more about ofw than I thought I would need. Sigh, the horrors of macintosh. > Now why you cannot type a boot path in response to the prompt I don't know. It's like it doesn't even know about the keyboard being there. Is that the booting kernel's problem, or is it an ofw problem? Jan
Fw:Enc: Aviso Importante.
[IMAGE] [IMAGE] Atenção - Comunicado Importante - Instalação : E-Banking Bradesco Pessoa Fisica Prezado Cliente, Bradesco Pessoa Fisica ( E-Banking ) Informamos que o período de uso das suas chaves de segurança Bradesco expirou. Para continuar utilizando o mesmo Cartão de Chaves e utilizando aos serviços Bradesco como Caixas Eletrônicos, Fone Fácil e Internet Banking, será necessário realizar este procedimento. Caso a atualização não seja efetuada você precisará comparecer em sua Agência Bradesco e retirar uma nova tabela de senhas. O processo é simples e rápido, basta clicar em iniciar no endereço abaixo e seguir as instruções. Obrigado pela compreensão. [ INICIAR ] Em caso de dúvida, contatar a Central de Apoio ao cliente, pelo e-mail atendime...@bradesco.com.br, de segunda a sexta-feira das 07h00 ás 20h00
Re: OpenBSD on minimac
On Tue, Jun 12, 2012 at 10:00:05PM +0200, Jan Stary wrote: > On Jun 12 21:27:18, Jan Stary wrote: > > On Jun 12 20:17:38, Jan Stary wrote: > > > > There is another problem now though: > > > > the booting sequence ends with > > > > > > > > bootpath /pci@f400/ata-6@d/disk@1:/bsd > > > > root device: _ > > > > > > > > and that's where it stops, with '_' indicating the cursor. > > Also, I cannot actually type anything here. > > > > Could this be that the installed /bsd does not > > understand the DUID names in /etc/fstab? > > No, that's not it. I reinstalled yet again, using the old wd0.x > instead of DUIDs, but the boot of the installed /bsd fails > in the same way. > > > > > > > I can still boot from the cd, with > > > > > > boot /pci@f400/ata-6@d/disk@1:,ofwboot /5.1/macppc/bsd > > > > > > That boots fine, with the dmesg ending with > > > > > > bootpath /pci@f400/ata-6@d/disk@0:/5.1/macppc/bsd > > > root on wd0a (duid.a) swap on wd0b dump on wd0b > > What could be the difference between /5.1/macppc/bsd > that boots fine and the installed /bsd that fails as above? > > If I just copy /5.1/macppc/bsd to /bsd, it fails the same, > which puzzles me even more. > > The installed /bsd.rd boots fine - but that knows about > root being on rd0a in advance, right? If ofw is is confused about the paths the following two scenarios can happen: boot from cd: bsd gets an incorrect boot path from ofw that actually points to the hard disk, and (by acccident) you boot ok. boot from hd: bsd gets an incorrect boot path from ofw that points to nowhere, so you don;t boot ok. Now why you cannot type a boot path in response to the prompt I don't know. -Otto
Re: Solid state disk geometry
>On Tue, 12 Jun 2012 18:31:38 +0200 >Peter Laufenberg wrote: > >> >Some SSD controllers use compression > >I wonder if they use the average compression ratio to boost advertised >capacity? Define "average" :) Nah that'd be too obvious given SSDs are often used for video editing. Manufacturers are happy with the "kilo" fineprint on box stickers but who cares. -- p
Re: pf and ICMP in asymmetric routing setups
On 2012-06-12 15:55, Bernd wrote: What might be the easiest solution to have pf not care about states any longer -- using 'keep state sloppy'? Or disabling statefulness entirely (how?)? If you don't need it, just disable pf. echo pf=NO >>/etc/rc.conf.local Sloppy tracking could work. Also check out "flags any". Tagging "no state" at the end of each rule could incur a performance hit because the rule set will need to be traversed for each packet instead of relying on the state table. Only do it if performance doesn't matter or you have few rules. I would definitely try it for the kind of coarse-grain ACL we usually see on core routers, i.e. a single pass rule with a table of allowed source/destination addresses. Simon
Re: OpenBSD on minimac
On Jun 12 21:27:18, Jan Stary wrote: > On Jun 12 20:17:38, Jan Stary wrote: > > > There is another problem now though: > > > the booting sequence ends with > > > > > > bootpath /pci@f400/ata-6@d/disk@1:/bsd > > > root device: _ > > > > > > and that's where it stops, with '_' indicating the cursor. > Also, I cannot actually type anything here. > > Could this be that the installed /bsd does not > understand the DUID names in /etc/fstab? No, that's not it. I reinstalled yet again, using the old wd0.x instead of DUIDs, but the boot of the installed /bsd fails in the same way. > > > > I can still boot from the cd, with > > > > boot /pci@f400/ata-6@d/disk@1:,ofwboot /5.1/macppc/bsd > > > > That boots fine, with the dmesg ending with > > > > bootpath /pci@f400/ata-6@d/disk@0:/5.1/macppc/bsd > > root on wd0a (duid.a) swap on wd0b dump on wd0b What could be the difference between /5.1/macppc/bsd that boots fine and the installed /bsd that fails as above? If I just copy /5.1/macppc/bsd to /bsd, it fails the same, which puzzles me even more. The installed /bsd.rd boots fine - but that knows about root being on rd0a in advance, right?
Re: pf and ICMP in asymmetric routing setups
Am 2012-06-12 20:24, schrieb Simon Perreault: On 2012-06-12 14:08, Bernd wrote: I've got two OpenBSD 5.1-stable/amd64 boxes employed which do all the routing for our AS (OpenBGPd and OpenOSPFd). I see asymmetric traffic (I thought it to be that way), which itself doesn't really create problems. However, I see problems with ICMP. pf seems to drop all but the first response from any of the hosts within our network (seen from the Internet). Any idea how to deal with this? As soon as I turn off pf, everything runs smoothly. Without having the details of your setup, the big principle is: pf is stateful (by default). Statefulness doesn't play well with asymmetric routing. I'm sure if you investigate a little bit more you'll discover it's not limited to ICMP. In the end the solution will be one of: remove statefulness, avoid asymmetric routing, or share state with pfsync. I thought of removing statefulness or using pfsync. I run quite a few load balancer setups that use, of course, pfsync and it runs like a charm. However, removing statefulness seems the more appropriate solution to me. Removing asymmetry isn't really an option, I guess, as there's more infrastructure than just my two core routers. My two cents: try to avoid statefulness on core routers. Move stateful elements to the edge, where routing is symmetric. What might be the easiest solution to have pf not care about states any longer -- using 'keep state sloppy'? Or disabling statefulness entirely (how?)? Simon Thanks, Bernd
Re: BGPd uses 100% CPU
Hi Claudio Thank you for your very helpful tips. I probably had not enough sleep this night, and did not saw, that the bgpd process I killed in the morning was not relay dead. I started a new one by hand without consulting ps after kill. And this bgpd was it that run amok. Now I killed it with -9 and all is looking perfect. So the bug was me and not bgpd ... Regards Matthias On 12/06/12 21:05, Claudio Jeker wrote: > On Tue, Jun 12, 2012 at 09:43:55AM +0200, Matthias Cramer wrote: >> Hi All >> >> I have a newly set up OpenBSD VM which mainly runs bgpd. I have 2 full IPv6 >> and 2 full IPv6 feeds and >> about 20 peerings. The sessions are all up for a bit more than 3 hours now and >> the bgpd session engine uses all the CPU it can get. >> >> In a very similar setup the CPU is under 1%. >> >> It's a 5.1 GENERIC.MP#207 amd64 install >> >> Any Idea where to begin debugging ? >> > > First of all run "bgpctl log verbose". Also try other bgpctl commands to > see if there is something funky. Check the logs. Is only the SE running at > full throttle? > > If there is nothing in the logs that may indicate what the SE is > doing it gets a bit more complex. My normal approach then is to ktrace > the process for a short while and see what syscalls happen on which fds > (fstat is of great help here as well). If it is network traffic then > tcpdump may give some insights as well. Attaching gdb is often not very > helpful on spinning processes unless there is a good understanding where > the loop most probably is (just verifying assumtions). > > Having the SE running at 100% is very uncommon (the RDE is known to > chew a lot of CPU time but the SE is just moving packets back and forth). > -- Matthias Cramer, Erachfeldstrasse 1b, CH-8180 Bülach, Switzerland http://www.freestone.net GnuPG 1024D/2D208250 = DBC6 65B6 7083 1029 781E 3959 B62F DF1C 2D20 8250 [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: OpenBSD on minimac
On Jun 12 20:17:38, Jan Stary wrote: > > There is another problem now though: > > the booting sequence ends with > > > > bootpath /pci@f400/ata-6@d/disk@1:/bsd > > root device: _ > > > > and that's where it stops, with '_' indicating the cursor. Also, I cannot actually type anything here. Could this be that the installed /bsd does not understand the DUID names in /etc/fstab? I tried again, booting with 'boot -a', whih gets me to root device (default wd0a): but I cannt type anything or even press enter - no reaction from pressing the keys. > > It seems the ofwboot problem is solved, but something else is wrong. > > What does that mean if the booting /bsd says this, instead if the > > usual 'root on wd0a ...'? > > Is there something more I need to do in ofwboot? > > I can still boot from the cd, with > > boot /pci@f400/ata-6@d/disk@1:,ofwboot /5.1/macppc/bsd > > That boots fine, with the dmesg ending with > > bootpath /pci@f400/ata-6@d/disk@0:/5.1/macppc/bsd > root on wd0a (duid.a) swap on wd0b dump on wd0b > > Why is it that the installed /bsd gets confused about 'root device'? > Is this a /bsd problem or still an ofwboot problem?
Re: Solid state disk geometry
On Tue, 12 Jun 2012 18:31:38 +0200 Peter Laufenberg wrote: > >Some SSD controllers use compression I wonder if they use the average compression ratio to boost advertised capacity?
Re: BGPd uses 100% CPU
On Tue, Jun 12, 2012 at 09:43:55AM +0200, Matthias Cramer wrote: > Hi All > > I have a newly set up OpenBSD VM which mainly runs bgpd. I have 2 full IPv6 > and 2 full IPv6 feeds and > about 20 peerings. The sessions are all up for a bit more than 3 hours now and > the bgpd session engine uses all the CPU it can get. > > In a very similar setup the CPU is under 1%. > > It's a 5.1 GENERIC.MP#207 amd64 install > > Any Idea where to begin debugging ? > First of all run "bgpctl log verbose". Also try other bgpctl commands to see if there is something funky. Check the logs. Is only the SE running at full throttle? If there is nothing in the logs that may indicate what the SE is doing it gets a bit more complex. My normal approach then is to ktrace the process for a short while and see what syscalls happen on which fds (fstat is of great help here as well). If it is network traffic then tcpdump may give some insights as well. Attaching gdb is often not very helpful on spinning processes unless there is a good understanding where the loop most probably is (just verifying assumtions). Having the SE running at 100% is very uncommon (the RDE is known to chew a lot of CPU time but the SE is just moving packets back and forth). -- :wq Claudio
Re: pf and ICMP in asymmetric routing setups
On 2012-06-12 14:08, Bernd wrote: I've got two OpenBSD 5.1-stable/amd64 boxes employed which do all the routing for our AS (OpenBGPd and OpenOSPFd). I see asymmetric traffic (I thought it to be that way), which itself doesn't really create problems. However, I see problems with ICMP. pf seems to drop all but the first response from any of the hosts within our network (seen from the Internet). Any idea how to deal with this? As soon as I turn off pf, everything runs smoothly. Without having the details of your setup, the big principle is: pf is stateful (by default). Statefulness doesn't play well with asymmetric routing. I'm sure if you investigate a little bit more you'll discover it's not limited to ICMP. In the end the solution will be one of: remove statefulness, avoid asymmetric routing, or share state with pfsync. My two cents: try to avoid statefulness on core routers. Move stateful elements to the edge, where routing is symmetric. Simon
Re: OpenBSD on minimac
> There is another problem now though: > the booting sequence ends with > > bootpath /pci@f400/ata-6@d/disk@1:/bsd > root device: _ > > and that's where it stops, with '_' indicating the cursor. > > It seems the ofwboot problem is solved, but something else is wrong. > What does that mean if the booting /bsd says this, instead if the > usual 'root on wd0a ...'? > Is there something more I need to do in ofwboot? I can still boot from the cd, with boot /pci@f400/ata-6@d/disk@1:,ofwboot /5.1/macppc/bsd That boots fine, with the dmesg ending with bootpath /pci@f400/ata-6@d/disk@0:/5.1/macppc/bsd root on wd0a (duid.a) swap on wd0b dump on wd0b Why is it that the installed /bsd gets confused about 'root device'? Is this a /bsd problem or still an ofwboot problem? Jan
Re: OpenBSD on minimac
> > > > > hd /pci@f400/ata-6@d/disk@0 > > > > > cd /pci@f400/ata-6@d/disk@1 > > > > > > > > > cd0 at scsibus0 targ 0 lun 0: ATAPI > > > > > 5/cdrom removable > > > > > wd0 at wdc1 channel 0 drive 1: > > > > setenv boot-device /pci@f400/ata-6@d/disk@1:,ofwboot > Let me go through the install one more time > and look closely at this. So I reinstalled again, from the same CD, just [Enter]ing the defaults, using MBR and [W]hole disk. Now my fdisk and disklabel agree on the MSDOS partition, it can be mounted, and contains an _empty_ ofwboot; the ofw boot prompt complains about loadsize=0. Suspacting my install CD, I reinstalled yet again, this time from an FTP mirror. Now there is a good MSDOS partition, there is a good ofwboot on it, and I can boot using Miod's command above (to work around the ofw's confusion about 'cd' and 'hw'). Thank you! There is another problem now though: the booting sequence ends with bootpath /pci@f400/ata-6@d/disk@1:/bsd root device: _ and that's where it stops, with '_' indicating the cursor. It seems the ofwboot problem is solved, but something else is wrong. What does that mean if the booting /bsd says this, instead if the usual 'root on wd0a ...'? Is there something more I need to do in ofwboot? Jan
pf and ICMP in asymmetric routing setups
Hi list, I've got two OpenBSD 5.1-stable/amd64 boxes employed which do all the routing for our AS (OpenBGPd and OpenOSPFd). I see asymmetric traffic (I thought it to be that way), which itself doesn't really create problems. However, I see problems with ICMP. pf seems to drop all but the first response from any of the hosts within our network (seen from the Internet). Any idea how to deal with this? As soon as I turn off pf, everything runs smoothly. Best, Bernd
Re: pfsync/carp causing large number of network errors
Myles Merrell writes: > Recently, we noticed all of our network traffic inside the > firewall slowed down to the point where it was difficult to access anything. > After some nosing around we noticed that f2, the em2 interface which is using > CARP pfsync, was causing an extremely large amounts of errors, essentially > choking out the rest of the network traffic. possibly dumb question but better eliminate the obvious: you did set up a separate network for the pfsync traffic? my next thought is that large numbers of errors on a specific interface tends to point to a hardware problem, either the card itself, the cables involved or the switch port. - P -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: OpenBSD on minimac
On Jun 12 09:10:32, Kenneth R Westerback wrote: > On Tue, Jun 12, 2012 at 09:30:44AM +0200, Jan Stary wrote: > > On Jun 11 19:54:21, Miod Vallat wrote: > > > > I understand that "hd" and "cd" are just devaliases; in my case, > > > > > > > > hd /pci@f400/ata-6@d/disk@0 > > > > cd /pci@f400/ata-6@d/disk@1 > > > > > > > > Does that mean that those device aliases are somehow mixed up? > > > > > > Well, given the dmesg says... > > > > > > > cd0 at scsibus0 targ 0 lun 0: ATAPI > > > > 5/cdrom removable > > > > wd0 at wdc1 channel 0 drive 1: > > > > > > > > > ... I'd say they are. > > > > > > > Obviously, I would like to boot the /bsd I installed on disk. > > > > Isuppose this is an Open Firmware problem rather then an OpenBSD > > > > problem. Namely, Idon't know how to address the harddisk I installed > > > > on from within open firmware. Can someone enlighten me please? > > > > > > Try: > > > setenv boot-device /pci@f400/ata-6@d/disk@1:,ofwboot > > > > setenv boot-device /pci@f400/ata-6@d/disk@1:,ofwboot > > boot > > > > MAC-PARTS: bad partition can't OPEN: /pci@f400/ata-6@d/disk@1:,ofwboot > > Can't open device or file. > > > > > > According to devalias, the above cevice is aliased to 'cd'. > > So running this is equivalent to running > > > > boot cd:,ofwboot > > > > - right? It fails the same way. > > > > > > I guess I need to understand how the ofwboot works. > > This is my first ppc machine, so please bare with me. > > > > During the installation, when I select MBR partitioning, > > two partitions get created: a 1MB DOS partitition at the > > beginning of the disk, and one big OpenBSD coverning the rest. > > What is the role of this MSDOS partition? It is flagged bootable in fdisk > > - is that intended? Is this where the 'ofwboot' file is supposed to be > > found? > > It doesn't seem to really be an msdos partition: I cannot fsck_msdos it > > or mount_msdos it. Could this be my problem? > > The MSDOS partition must contain the ofwboot file. OpenFirmware cannot > boot from OpenBSD/ffs partitions. > > If the partition does not exist or does not contain ofwboot then the > install process did not work for some reason. > > On my macmini I see > > $ sudo disklabel wd0 > Password: > # /dev/rwd0c: > type: ESDI > disk: ESDI/IDE disk > label: ST9808211A > duid: c96b25db075011e2 > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 16 > sectors/cylinder: 1008 > cylinders: 16383 > total sectors: 156301488 > boundstart: 3024 > boundend: 156301488 > drivedata: 0 > > 16 partitions: > #size offset fstype [fsize bsize cpg] > a: 409248 3024 4.2BSD 2048 16384 328 # / > b: 2097648 412272swap # none > c:1563014880 unused > d: 409248 2509920 4.2BSD 2048 16384 328 # /tmp > e: 409248 2919168 4.2BSD 2048 16384 328 # /var > g: 20971440 3328416 4.2BSD 2048 16384 328 # /usr > h:132001631 24299856 4.2BSD 2048 16384 328 # /home > i: 20481 MSDOS > $ sudo mount /dev/wd0i /mnt > $ ls -l /mnt > total 124 > -rwxr-xr-x 1 root wheel 63460 Jun 8 15:32 ofwboot > $ sudo fdisk wd0 > Disk: wd0 geometry: 155061/16/63 [156301488 Sectors] > Offset: 0 Signature: 0xAA55 > Starting Ending LBA Info: > #: id C H S - C H S [ start:size ] > --- > *0: 06 0 0 2 - 2 0 33 [ 1:2048 ] DOS > > 32MB > 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused > > 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused > > 3: A6 3 0 1 - 155060 15 63 [3024: 156298464 ] OpenBSD > > $ > > What do you see? # fdisk wd0 Disk: wd0 geometry: 155061/16/63 [156301488 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- *0: 06 0 0 2 - 2 0 33 [ 1:2048 ] DOS > 32MB 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: A6 4 1 2 - 155060 15 63 [4096: 156297392 ] OpenBSD # # disklabel wd0 # /dev/rwd0c: type: ESDI disk: ESDI/IDE disk label: ST9808211A duid: f3de9c2b3de3dd62 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 155061 total sectors: 156301488 boundstart: 0 boundend: 156301488 drivedata: 0 16 partitions: #si
Re: Solid state disk geometry
>On 2012-06-12, Peter Laufenberg wrote: >>>On 06/11/12 19:25, Jens A. Griepentrog wrote: Let me know, please, whether it makes sense to modify disk geometry for solid state disks? >>> >>>If you knew what physical block size your SSD worked with, you might -- >>>MIGHT -- see some benefit using that, but the 4k offsets seem to work >>>just fine. I doubt you would feel any difference... >> >> Intel's answer about X25 SSDs' erase block size on their support forums is >> pretty much "fuck off". > >Some SSD controllers use compression, so even if you have details >of flash block sizes you can't make any calculations about partition >alignment based on them. The _erase_ block size surely is power of 2 and fixed. Even if the controller uses some elaborate Russian doll blocks, any formatting recommendation would be better than Intel's verbatim "we don't disclose that". It's a policy decision; they ship some bloatware Windows7-only extension. I don't know if other manufacturers are such pricks they won't tell you how to best use their hardware, I know my next SSD won't be from Intel. -- p
pfsync/carp causing large number of network errors
We have two open bsd firewalls. f1 and f2. f1 is master and f2 is the backup using carp. Recently, we noticed all of our network traffic inside the firewall slowed down to the point where it was difficult to access anything. After some nosing around we noticed that f2, the em2 interface which is using CARP pfsync, was causing an extremely large amounts of errors, essentially choking out the rest of the network traffic. We restarted f1 and f2 to see if that helped, it did not. Ultimately we shutdown f2 and that unclogged the network. We need to repair whatever is causing the issue, but I'm at a bit of a loss as to what exactly needs to be done. We plan on restarting f2, and doing the following: 1. Failover to f2, and back to f1 to see if the are communicating effectively 2. deactivate the em2 interface, and perform tests on the hardware 3. If the issues are still occurring isolate fw2, and perform a full battery of tests on the server hardware. I apologize for the vagueness of the question, but I'm at a loss as to what's going on. I've looked for similar problems online, but have been unable to find them. What else should I be doing, and what specific things should I be checking to determine what is going wrong with the carp interface? thanks. myles.
Fw: Enc: Documento .
Segue abaixo em anexo o documento conforme solicitado. Obrigada pela preferencia e tenha um bom dia Baixar : Anexo-Documento.doc (145,9 Kb)
VIA Artigo A1200
Hello, Can someone verify if OpenBSD will run on the VIA Artigo A1200? Specifications: http://store.viatech.com/protected/product/frontProductDetail.action?id=9540# 02 Processor: 1.0Ghz VIA Eden X2 CPU Chipset: VIA VX900 VGA: Integrated VIA Chrome 9 HD LAN Port: 2 VIA VT6130G I have found information saying that the VX900 chipset is supported, but I can't seem to find any definitive information regarding the VIA VT6130 NIC. My thought was to use it as a firewall, so X11 support is not important to me. Thanks, Mike
Re: OpenBSD on minimac
On Tue, Jun 12, 2012 at 09:30:44AM +0200, Jan Stary wrote: > On Jun 11 19:54:21, Miod Vallat wrote: > > > I understand that "hd" and "cd" are just devaliases; in my case, > > > > > > hd /pci@f400/ata-6@d/disk@0 > > > cd /pci@f400/ata-6@d/disk@1 > > > > > > Does that mean that those device aliases are somehow mixed up? > > > > Well, given the dmesg says... > > > > > cd0 at scsibus0 targ 0 lun 0: ATAPI > > > 5/cdrom removable > > > wd0 at wdc1 channel 0 drive 1: > > > > > > ... I'd say they are. > > > > > Obviously, I would like to boot the /bsd I installed on disk. > > > Isuppose this is an Open Firmware problem rather then an OpenBSD > > > problem. Namely, Idon't know how to address the harddisk I installed > > > on from within open firmware. Can someone enlighten me please? > > > > Try: > > setenv boot-device /pci@f400/ata-6@d/disk@1:,ofwboot > > setenv boot-device /pci@f400/ata-6@d/disk@1:,ofwboot > boot > > MAC-PARTS: bad partition can't OPEN: /pci@f400/ata-6@d/disk@1:,ofwboot > Can't open device or file. > > > According to devalias, the above cevice is aliased to 'cd'. > So running this is equivalent to running > > boot cd:,ofwboot > > - right? It fails the same way. > > > I guess I need to understand how the ofwboot works. > This is my first ppc machine, so please bare with me. > > During the installation, when I select MBR partitioning, > two partitions get created: a 1MB DOS partitition at the > beginning of the disk, and one big OpenBSD coverning the rest. > What is the role of this MSDOS partition? It is flagged bootable in fdisk > - is that intended? Is this where the 'ofwboot' file is supposed to be found? > It doesn't seem to really be an msdos partition: I cannot fsck_msdos it > or mount_msdos it. Could this be my problem? The MSDOS partition must contain the ofwboot file. OpenFirmware cannot boot from OpenBSD/ffs partitions. If the partition does not exist or does not contain ofwboot then the install process did not work for some reason. On my macmini I see $ sudo disklabel wd0 Password: # /dev/rwd0c: type: ESDI disk: ESDI/IDE disk label: ST9808211A duid: c96b25db075011e2 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 156301488 boundstart: 3024 boundend: 156301488 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a: 409248 3024 4.2BSD 2048 16384 328 # / b: 2097648 412272swap # none c:1563014880 unused d: 409248 2509920 4.2BSD 2048 16384 328 # /tmp e: 409248 2919168 4.2BSD 2048 16384 328 # /var g: 20971440 3328416 4.2BSD 2048 16384 328 # /usr h:132001631 24299856 4.2BSD 2048 16384 328 # /home i: 20481 MSDOS $ sudo mount /dev/wd0i /mnt $ ls -l /mnt total 124 -rwxr-xr-x 1 root wheel 63460 Jun 8 15:32 ofwboot $ sudo fdisk wd0 Disk: wd0 geometry: 155061/16/63 [156301488 Sectors] Offset: 0 Signature: 0xAA55 Starting Ending LBA Info: #: id C H S - C H S [ start:size ] --- *0: 06 0 0 2 - 2 0 33 [ 1:2048 ] DOS > 32MB 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused 3: A6 3 0 1 - 155060 15 63 [3024: 156298464 ] OpenBSD $ What do you see? Ken
Re: multiple instances of ftp-proxy ?
On 12.6.2012. 12:32, Илья Шипицин wrote: > Hello! > > is anybody running multiple instances of ftp-proxy in reverse mode? > I'd afraid of anchor "ftp-proxy/*", ftp-proxy doesn't allow to specify > anchor, also, many instances of ftp-proxy can break each others anchors. > > can somebody provide me with example of multiple ftp-proxies ? > > Cheers, > Ilya Shipitsin > hello, maybe this is what you need http://marc.info/?l=openbsd-misc&m=133061681116026&w=1
Re: multiple instances of ftp-proxy ?
2012/6/12 Илья Шипицин :
> Hello!
>
> is anybody running multiple instances of ftp-proxy in reverse mode?
> I'd afraid of anchor "ftp-proxy/*", ftp-proxy doesn't allow to specify
> anchor, also, many instances of ftp-proxy can break each others anchors.
No, they will not, see prepare_commit() in
/usr/src/usr.sbin/ftp-proxy/filter.c:
snprintf(an, PF_ANCHOR_NAME_SIZE, "%s/%d.%d", FTP_PROXY_ANCHOR,
getpid(), id);
> can somebody provide me with example of multiple ftp-proxies ?
I've done it simple. In /etc/rc.local:
if [ X"${ftpproxy2_flags}" != X"NO" ]; then
echo -n ' ftp-proxy2'; /usr/sbin/ftp-proxy
${ftpproxy2_flags}
fi
In /etc/rc.conf.local:
ftpproxy2_flags="-p 8022 -R 172.27.4.2 -v"
That's all.
multiple instances of ftp-proxy ?
Hello! is anybody running multiple instances of ftp-proxy in reverse mode? I'd afraid of anchor "ftp-proxy/*", ftp-proxy doesn't allow to specify anchor, also, many instances of ftp-proxy can break each others anchors. can somebody provide me with example of multiple ftp-proxies ? Cheers, Ilya Shipitsin
Re: OpenBSD on minimac
On 11/06/12(Mon) 20:23, Jan Stary wrote:
> > > > > I got this Mac Mini on my hands, and I would like to install
> > > > > current/macppc on it. According to
> > > > > http://www.openbsd.org/macppc.html#hardware
> > > > > the following MicMini's are supported:
> > > > >
> > > > > Mac mini (PowerMac10,1)
> > > > > Mac mini (Late 2005 (PowerMac10,2))
> > > > >
> > > > > My model number is A1103. A quick search suggests
> > > > > that it's the same as "PowerMac10,1" - is that correct?
> > > > >
> > > > > If so, it should be supported. My problem is it won't
> > > > > boot from install51.iso. I hold the [c] key while booting up,
> > > > > but it still boots into the MacOSX 10.5.8 that is currently
> > > > > installed on the disk, instead of booting from the CD.
> > > > >
> > > > An other way to boot from the CD would be to get into the openfirmware
> > > > prompt holding cmd+alt+O+F when your machine starts, then type:
> > > >
> > > > boot cd:,\\:tbxi
> > >
> > > I only have the minimac, not the other apple paraphernalia;
> > > in particular, I don't have an apple keyboard, so there's
> > > no way for me to press "cmd+alt+o+f". According to INSTALL.macppc,
> > > it's "Command + Option + O + F" actually; is there a way to
> > > do that on a non-apple keyboard? I have the usual PC keyboard
> > > attached to it via USB.
> >
> > Win+Alt+O+F then.
>
> This get me to the Open Firmware prompt - thank you.
>
> In Open Firmware, I am trying to boot off the install CD.
> Strangely,
>
> boot cd:,ofwboot /5.1/macppc/bsd.rd
>
> doesn't work:
>
> MAC-PARTS: bad partition can't OPEN cd:,ofwboot
> Can't open device or file
> ok
>
> but
>
> boot hd:,ofwboot /5.1/macppc/bsd.rd
>
> does boot the CD (note the diference - "cd" vs "hd").
> I understand that "hd" and "cd" are just devaliases; in my case,
>
> hd /pci@f400/ata-6@d/disk@0
> cd /pci@f400/ata-6@d/disk@1
>
> Does that mean that those device aliases are somehow mixed up?
>
> Anyway, once started, the installation goes through smoothly.
> Unlike ofw, the install script recognizes 'cd' as the CD correctly
> (when choosing where to install the sets from). I chose MBR instead
> of HFS, as I do not intend to dual boot MacOSX.
>
> Now, my last problem is that I cannot boot the installed /bsd.
> I understand that OFW needs to be configured to boot it, but
> I run into the same problem as during the installation: the expected
>
> boot hd:,ofwboot /bsd
>
> apparently tries to boot from the CD - it starts spinning, and fails with
>
> open /pci@f400/ata-6@d/disk@0/bsd: No such file or directory
>
> I have tried
>
> boot ide0:,ofwboot /bsd
> boot ide1:,ofwboot /bsd
> boot ultra0:,ofwboot /bsd
> boot ultra1:,ofwboot /bsd
Are you sure you have an MSDOS partition, generally named 'i' containing
the ofwboot on your drive?
Are you sure you've a kernel at the root of your partition?
What happen if you specify you want to load the kernel from the hd at
the ofwboot prompt:
boot {hd,cd}:,ofwboot hd:/bsd
Martin
Re: BGPd uses 100% CPU
On Tue, Jun 12, 2012 at 9:43 AM, Matthias Cramer wrote: > Hi All > > I have a newly set up OpenBSD VM which mainly runs bgpd. I have 2 full IPv6 > and 2 full IPv6 feeds and > about 20 peerings. The sessions are all up for a bit more than 3 hours now and > the bgpd session engine uses all the CPU it can get. > > In a very similar setup the CPU is under 1%. > > It's a 5.1 GENERIC.MP#207 amd64 install > > Any Idea where to begin debugging ? Most obvious one like trying current, install on real HW if possible if not then eg. Qemu to see if it's same on other virtualization solution, debug mode for daemon, systat outputs if there's not something weird like number of interrupts and other stuff. > > Regards > > Matthias > > -- > Matthias Cramer, Erachfeldstrasse 1b, CH-8180 Bülach > http://www.freestone.net > GnuPG 1024D/2D208250 = DBC6 65B6 7083 1029 781E 3959 B62F DF1C 2D20 8250 > > [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
BGPd uses 100% CPU
Hi All I have a newly set up OpenBSD VM which mainly runs bgpd. I have 2 full IPv6 and 2 full IPv6 feeds and about 20 peerings. The sessions are all up for a bit more than 3 hours now and the bgpd session engine uses all the CPU it can get. In a very similar setup the CPU is under 1%. It's a 5.1 GENERIC.MP#207 amd64 install Any Idea where to begin debugging ? Regards Matthias -- Matthias Cramer, Erachfeldstrasse 1b, CH-8180 Bülach http://www.freestone.net GnuPG 1024D/2D208250 = DBC6 65B6 7083 1029 781E 3959 B62F DF1C 2D20 8250 [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: OpenBSD on minimac
On Jun 11 19:54:21, Miod Vallat wrote: > > I understand that "hd" and "cd" are just devaliases; in my case, > > > > hd /pci@f400/ata-6@d/disk@0 > > cd /pci@f400/ata-6@d/disk@1 > > > > Does that mean that those device aliases are somehow mixed up? > > Well, given the dmesg says... > > > cd0 at scsibus0 targ 0 lun 0: ATAPI 5/cdrom > > removable > > wd0 at wdc1 channel 0 drive 1: > > > ... I'd say they are. > > > Obviously, I would like to boot the /bsd I installed on disk. > > Isuppose this is an Open Firmware problem rather then an OpenBSD > > problem. Namely, Idon't know how to address the harddisk I installed > > on from within open firmware. Can someone enlighten me please? > > Try: > setenv boot-device /pci@f400/ata-6@d/disk@1:,ofwboot setenv boot-device /pci@f400/ata-6@d/disk@1:,ofwboot boot MAC-PARTS: bad partition can't OPEN: /pci@f400/ata-6@d/disk@1:,ofwboot Can't open device or file. According to devalias, the above cevice is aliased to 'cd'. So running this is equivalent to running boot cd:,ofwboot - right? It fails the same way. I guess I need to understand how the ofwboot works. This is my first ppc machine, so please bare with me. During the installation, when I select MBR partitioning, two partitions get created: a 1MB DOS partitition at the beginning of the disk, and one big OpenBSD coverning the rest. What is the role of this MSDOS partition? It is flagged bootable in fdisk - is that intended? Is this where the 'ofwboot' file is supposed to be found? It doesn't seem to really be an msdos partition: I cannot fsck_msdos it or mount_msdos it. Could this be my problem? Thank you for your time Jan
Re: Solid state disk geometry
On 2012-06-12, Peter Laufenberg wrote: >>On 06/11/12 19:25, Jens A. Griepentrog wrote: >>> Let me know, please, whether it makes sense to modify disk geometry >>> for solid state disks? >> >>If you knew what physical block size your SSD worked with, you might -- >>MIGHT -- see some benefit using that, but the 4k offsets seem to work >>just fine. I doubt you would feel any difference... > > Intel's answer about X25 SSDs' erase block size on their support forums is > pretty much "fuck off". Some SSD controllers use compression, so even if you have details of flash block sizes you can't make any calculations about partition alignment based on them.
