Re: vmmap: bad software everywhere
i'm sure you could fathom the idea that some people care more about streaming video on their browsers than address randomization, the same way some people care more about speedier local lookups to a stationary sync db than making sure a package has correct @want-lib by trashing the ftp server on every query some of these people may even call the alternative they're not using stupid what does that do? nothing On Sun, Jun 5, 2011 at 9:47 AM, Marc Espie es...@nerim.net wrote: On Sun, Jun 05, 2011 at 09:46:48AM -0400, Nico Kadel-Garcia wrote: On Fri, Jun 3, 2011 at 6:26 PM, Marc Espie es...@nerim.net wrote: On Fri, Jun 03, 2011 at 06:11:31PM -0400, Nico Kadel-Garcia wrote: On Tue, May 31, 2011 at 6:51 AM, Marc Espie es...@nerim.net wrote: How comes nobody in other OSes noticed ? Well, people probably did, and tweaked their allocators to work, by using preferably the low address space, and having addresses that increase slowly, so that a lot of pointers are below 4GB, and a lot of pointer diffs are under 4GB. Or you could just be engaging in an ad hominem attack without actually looking at their implementations and assuming they're not doing it right because they're not you or your favorite platform. But hey, we don't know anyone who'd do *that* in the OpenBSD community. Right? Wrong. An ad hominem attack would require me asserting all this for a fact, which is not what I'm doing. Notice the probably ? it makes all the difference in the world. No, I'm afraid it really doesn't require asserting the truth. To quote from Wikipedia, An ad hominem (Latin: to the man), short for argumentum ad hominem, is an attempt to link the truth of a claim to a negative characteristic or belief of the person advocating it It's what I just did to you, in turn. How's it feel? An example or two would have lent powerful credence to your claim. The fix for mono, which Marc Espie notes in this thread, is a very powerful such indicator. I tend to publish findings early, when I don't have THAT many built examples yet. There's also some teamwork, specifically, I don't personally oversee everything in OpenBSD. Nobody does. But we do notice trends, and do some design work based on that. You can call that ad hominem if you wish, do any kind of rhethoric. For me, putting a probably in front of a working hypothesis is enough to go forward. I expect the facts to be disputed, I don't care much for the rhethoric part o it... I would even venture this is a fundamental activity for us to go forward. If you lose yourself in gruntwork, you don't see the bigger picture. Sometimes, we do have the luxury of saying this is complete shit, it shouldn't work, and then we break bad software. On the other hand, secure by default, runs GENERIC is the other tenet of our culture - reproducible defaults, no need to tinker with configs to get things to work, and also, proceed cautiously, do not invent stupid APIS when we don't need to.
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
I don't want to engage in language wars, as i wrote before there is a gap in programming culture and reinforcing trust in my favorite lang or OS won't help. We trust our languages to mean something but writing correct programs strangely is still a struggle even to skilled programmers, and takes much testing. Again, i don't mean to hurt but C is really not KISS, at all. Its paradigm is appropriate for system but its grammar is a huge mess. And we're all happy to struggle with it ? Is it out of pride ? There is no easy fix but i recognize this is the core source of many ugly bugs. They're just symptoms of this. And noone cares at all.
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
The answer is too write all OS code in Machine language for each Architecture! YEA! We're waiting for your code! I'm super duper excited! :-0 On Mon, 06 Jun 2011 11:10 +0200, Thomas de Grivel billi...@gmail.com wrote: I don't want to engage in language wars, as i wrote before there is a gap in programming culture and reinforcing trust in my favorite lang or OS won't help. We trust our languages to mean something but writing correct programs strangely is still a struggle even to skilled programmers, and takes much testing. Again, i don't mean to hurt but C is really not KISS, at all. Its paradigm is appropriate for system but its grammar is a huge mess. And we're all happy to struggle with it ? Is it out of pride ? There is no easy fix but i recognize this is the core source of many ugly bugs. They're just symptoms of this. And noone cares at all.
AT-2972LX10/LC
Is it supported by broadcom driver? Has anybody any experience? (the AT-2972LX10/LC would be good for me if it would be supported by any net OpenBSD driver, there's no info on product's datasheet; I googled it, but didn't find positive results.) Network controller is Broadcom BCM 5715S. The proper manpage tells, that bge driver supports BCM57xx network controller. Does it mean that xx may stand for exactly two characters (e.g. digits) or more too? In other words: does it mean that BCM5715S is supported? Marek Czubenko Uczelniane Centrum Information Communication Informatyczne Technology Centre Uniwersytet Miko3aja Kopernika Nicolaus Copernicus University Pl. Rapackiego 1, 87-100 Toruq Pl. Rapackiego 1, 87-100 Torun tel: +48 56 611-27-38 phone: +48 56 611-27-38 PGP: http://www.umk.pl/~mc10/pgp_public_key
Reverse-proxy PF ?
Hi all I look the doc, ftp-proxy, no reverse-proxy PF ?. Varnish, ultimate soluce ? Cordialy
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
On 06/06/11 11:36, Eric Furman wrote: I'm super duper excited! :-0 do you need a towel ? -- Thomas de Grivel http://b.lowh.net/billitch I must plunge into the water of doubt again and again.
Re: i386 current crashes on boot
On 06/05/11 11:22, Nigel Taylor wrote: Hi, I rebuilt GENERIC.MP from cvs (current 4th June 2011). This crashed on boot. I reverted to old bsd.mp from April this booted. I downloaded bsd.mp from a mirror site this booted (date 14th May 2011). I downloaded a more recent bsd.mp from ftp.openbsd.org (4 June 2011 GENERIC.MP #57), this crashed on boot in the same place as built from cvs. Below I have typed from screen the panic. wsdisplay0 at vga1 mux 1:console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeibdrm0 at vga1: apic 2 int 18 drm0 at radeondrm0 azalia0 at pci1 dev 5 function 1 ATI RS780 HD Audio rev 0x00: msi azalia0: no supported codecs panic: intr_disestablish: bogus irq 160 Stopped at Debugger+0x4: popl %ebp Debugger(d08ebba2,d0bb4a34,d098c3b0,d0bb4a34,d0a5ddb8) at Debuuger+0x4 panic(d098c3b0,a0,d0a3f4a0,3dc,3dc) at panic+0x5d isa_disestablish(0,d68f1480,5d,5,d9bb4a84) at isa_intr_disestabish+0ca azalia_pci_detach(d68bea00,0,2000,0,0,a0,d05d3990,d68bea00,d68bea1 4,5,0,80012900,2000,0,0) at azalia_pci_detach+0x14a azalia_pci_attach(d68ae5080,d68bea00,d0bb4b54md03e77db,d05ab9f0) at azalia_pci_attach+0x1b9 config_attach(d68ae580,d09c92a0,d0bb4b54,d05adb70,d0bb4b44) at config_attach+0x157 pci_probe_deveice(d68ae580,80012900,0,0,8ae580) at pci_probe_device+0x420 pci_enuimerate_bus(d68ae580,0,0,d03e77db,0) at pci_enumerate_bus+0x11c config_attach(d6923800,d09c9020,d0bb4c6c,d061e1e0,0) at config_attach+0x157 ppbattach(d68ae780,d6923800,d0bb4d54,d03e77db,d05ab9f0) at ppbattach+0x2b8 trace isa_intr_disestablish azailia_pci_detach azailia_pci_attach config_attach pci_probe_device pci_enumerate_bus config_attach ppbattach config_attach pci_probe_device pci_enumerate_bus config_attach mainbus_attach config_attach config_rootfound cpu_confgiure main ps PID PPID PGRP UID SFLAGS WAit COMMAND *0 -10 0 7 0x00200swapper dmesg from snapshot downloaded from mirror OpenBSD 4.9-current (GENERIC.MP) #112: Sat May 14 09:59:17 MDT 2011 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: AMD Athlon(tm) II X2 240e Processor (AuthenticAMD 686-class, 1024KB L2 cache) 2.81 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT real mem = 3488739328 (3327MB) avail mem = 3421507584 (3263MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 08/04/09, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.5 @ 0x9f400 (69 entries) bios0: vendor American Megatrends Inc. version 080014 date 08/04/2009 bios0: FOXCONN A7GM-S 2.0 acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT acpi0: wakeup devices PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PCE7(S4) PCEB(S4) PCEC(S4) SBAZ(S4) PS2K(S3) PS2M(S3) P0PC(S4) UHC1(S4) UHC2(S4) UHC3(S4) USB4(S4) UHC5(S4) UHC6(S4) UHC7(S4) PCE2(S4) PCE9(S4) PCEA(S4) PWRB(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) II X2 240e Processor (AuthenticAMD 686-class, 1024KB L2 cache) 2.81 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpiprt2 at acpi0: bus -1 (PCE3) acpiprt3 at acpi0: bus -1 (PCE4) acpiprt4 at acpi0: bus 3 (P0PC) acpiprt5 at acpi0: bus -1 (PCE2) acpiprt6 at acpi0: bus 2 (PCE9) acpiprt7 at acpi0: bus -1 (PCEA) acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpitz0 at acpi0: critical temperature 60 degC acpibtn0 at acpi0: PWRB bios0: ROM list: 0xc/0xea00 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 AMD RS780 Host rev 0x00 ppb0 at pci0 dev 1 function 0 AMD RS780 PCIE rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon HD 3200 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 2 int 18 drm0 at radeondrm0 azalia0 at pci1 dev 5 function 1 ATI RS780 HD Audio rev 0x00: apic 2 int 19 azalia0: no supported codecs ppb1 at pci0 dev 9 function 0 AMD RS780 PCIE rev 0x00 pci2 at ppb1 bus 2 re0 at pci2 dev 0 function 0 Realtek 8168 rev 0x03: RTL8168D/8111D (0x2800), apic 2 int 17, address 00:22:68:80:e9:f7 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 ahci0 at pci0 dev 17 function 0 ATI SBx00 SATA rev 0x00: apic 2 int 22, AHCI 1.1 scsibus0 at ahci0: 32 targets ohci0 at pci0 dev 18 function 0 ATI SB700 USB rev 0x00: apic 2 int 16, version 1.0,
Re: smtpd and no DH parameters found in
On Sun, May 22, 2011 at 11:59:32PM +, Kevin Chadwick wrote: On Sun, 22 May 2011 23:12:21 +0100 Mikolaj Kucharski wrote: If I'm using 4096-bit RSA key, do I need to use 4096-bit size DH parameters file? No Do they need to match? No Is it okay to have DH smaller or even bigger? Yes, some programs like dovecot manage it automatically so maybe? there's more info in the source code. Do you mean more info in dovecot sources? PS. I have delivery disabled for misc@, please keep me in CC. -- best regards q#
Re: i386 current crashes on boot
Date: Mon, 06 Jun 2011 11:13:12 +0100 From: Nigel Taylor njtay...@asterisk.demon.co.uk On 06/05/11 11:22, Nigel Taylor wrote: Hi, I rebuilt GENERIC.MP from cvs (current 4th June 2011). This crashed on boot. I reverted to old bsd.mp from April this booted. I downloaded bsd.mp from a mirror site this booted (date 14th May 2011). I downloaded a more recent bsd.mp from ftp.openbsd.org (4 June 2011 GENERIC.MP #57), this crashed on boot in the same place as built from cvs. Below I have typed from screen the panic. wsdisplay0 at vga1 mux 1:console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeibdrm0 at vga1: apic 2 int 18 drm0 at radeondrm0 azalia0 at pci1 dev 5 function 1 ATI RS780 HD Audio rev 0x00: msi azalia0: no supported codecs panic: intr_disestablish: bogus irq 160 Stopped at Debugger+0x4: popl %ebp Debugger(d08ebba2,d0bb4a34,d098c3b0,d0bb4a34,d0a5ddb8) at Debuuger+0x4 panic(d098c3b0,a0,d0a3f4a0,3dc,3dc) at panic+0x5d isa_disestablish(0,d68f1480,5d,5,d9bb4a84) at isa_intr_disestabish+0ca azalia_pci_detach(d68bea00,0,2000,0,0,a0,d05d3990,d68bea00,d68bea1 4,5,0,80012900,2000,0,0) at azalia_pci_detach+0x14a azalia_pci_attach(d68ae5080,d68bea00,d0bb4b54md03e77db,d05ab9f0) at azalia_pci_attach+0x1b9 config_attach(d68ae580,d09c92a0,d0bb4b54,d05adb70,d0bb4b44) at config_attach+0x157 pci_probe_deveice(d68ae580,80012900,0,0,8ae580) at pci_probe_device+0x420 pci_enuimerate_bus(d68ae580,0,0,d03e77db,0) at pci_enumerate_bus+0x11c config_attach(d6923800,d09c9020,d0bb4c6c,d061e1e0,0) at config_attach+0x157 ppbattach(d68ae780,d6923800,d0bb4d54,d03e77db,d05ab9f0) at ppbattach+0x2b8 trace isa_intr_disestablish azailia_pci_detach azailia_pci_attach config_attach pci_probe_device pci_enumerate_bus config_attach ppbattach config_attach pci_probe_device pci_enumerate_bus config_attach mainbus_attach config_attach config_rootfound cpu_confgiure main ps PID PPID PGRP UID SFLAGS WAit COMMAND *0 -10 0 7 0x00200swapper dmesg from snapshot downloaded from mirror OpenBSD 4.9-current (GENERIC.MP) #112: Sat May 14 09:59:17 MDT 2011 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: AMD Athlon(tm) II X2 240e Processor (AuthenticAMD 686-class, 1024KB L2 cache) 2.81 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT real mem = 3488739328 (3327MB) avail mem = 3421507584 (3263MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 08/04/09, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.5 @ 0x9f400 (69 entries) bios0: vendor American Megatrends Inc. version 080014 date 08/04/2009 bios0: FOXCONN A7GM-S 2.0 acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT acpi0: wakeup devices PCE3(S4) PCE4(S4) PCE5(S4) PCE6(S4) PCE7(S4) PCEB(S4) PCEC(S4) SBAZ(S4) PS2K(S3) PS2M(S3) P0PC(S4) UHC1(S4) UHC2(S4) UHC3(S4) USB4(S4) UHC5(S4) UHC6(S4) UHC7(S4) PCE2(S4) PCE9(S4) PCEA(S4) PWRB(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) II X2 240e Processor (AuthenticAMD 686-class, 1024KB L2 cache) 2.81 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (P0P1) acpiprt2 at acpi0: bus -1 (PCE3) acpiprt3 at acpi0: bus -1 (PCE4) acpiprt4 at acpi0: bus 3 (P0PC) acpiprt5 at acpi0: bus -1 (PCE2) acpiprt6 at acpi0: bus 2 (PCE9) acpiprt7 at acpi0: bus -1 (PCEA) acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpitz0 at acpi0: critical temperature 60 degC acpibtn0 at acpi0: PWRB bios0: ROM list: 0xc/0xea00 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 AMD RS780 Host rev 0x00 ppb0 at pci0 dev 1 function 0 AMD RS780 PCIE rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon HD 3200 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 2 int 18 drm0 at radeondrm0 azalia0 at pci1 dev 5 function 1 ATI RS780 HD Audio rev 0x00: apic 2 int 19 azalia0: no supported codecs ppb1 at pci0 dev 9 function 0 AMD RS780 PCIE rev 0x00 pci2 at ppb1 bus 2 re0 at pci2 dev 0 function 0 Realtek 8168 rev 0x03: RTL8168D/8111D (0x2800), apic 2 int 17, address 00:22:68:80:e9:f7 rgephy0 at re0 phy 7: RTL8169S/8110S
serious security improvement in OpenBSD
I think the following diff will totally improve OpenBSD security (overall) --- etc/master.passwd.old Sat Jul 10 02:37:16 2010 +++ etc/master.passwd Mon Jun 6 15:04:15 2011 @@ -1,4 +1,4 @@ -root::0:0:daemon:0:0:Charlie :/root:/bin/ksh +root::0:0:daemon:0:0:Chuck Norris :/root:/bin/ksh daemon:*:1:1::0:0:The devil himself:/root:/sbin/nologin operator:*:2:5::0:0:System :/operator:/sbin/nologin bin:*:3:7::0:0:Binaries Commands and Source:/:/sbin/nologin Who is this 'Charlie' guy anyway??? regards, Giannis [demime 1.01d removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
Re: serious security improvement in OpenBSD
On Mon, Jun 06, 2011 at 03:06:54PM +0300, Kapetanakis Giannis wrote: I think the following diff will totally improve OpenBSD security (overall) --- etc/master.passwd.old Sat Jul 10 02:37:16 2010 +++ etc/master.passwd Mon Jun 6 15:04:15 2011 @@ -1,4 +1,4 @@ -root::0:0:daemon:0:0:Charlie :/root:/bin/ksh +root::0:0:daemon:0:0:Chuck Norris :/root:/bin/ksh daemon:*:1:1::0:0:The devil himself:/root:/sbin/nologin operator:*:2:5::0:0:System :/operator:/sbin/nologin bin:*:3:7::0:0:Binaries Commands and Source:/:/sbin/nologin Who is this 'Charlie' guy anyway??? Your diff is incorrect ... Who is this Chuck Norris Root anyway ? -- Gilles Chehade http://www.poolp.org
Re: serious security improvement in OpenBSD
On 06/06/11 15:06, Kapetanakis Giannis wrote: I think the following diff will totally improve OpenBSD security (overall) --- etc/master.passwd.old Sat Jul 10 02:37:16 2010 +++ etc/master.passwd Mon Jun 6 15:04:15 2011 @@ -1,4 +1,4 @@ -root::0:0:daemon:0:0:Charlie:/root:/bin/ksh +root::0:0:daemon:0:0:Chuck Norris:/root:/bin/ksh daemon:*:1:1::0:0:The devil himself:/root:/sbin/nologin operator:*:2:5::0:0:System:/operator:/sbin/nologin bin:*:3:7::0:0:Binaries Commands and Source:/:/sbin/nologin Who is this 'Charlie' guy anyway??? Chuck does not su - to exec Root does su - chuck Giannis [demime 1.01d removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
Re: serious security improvement in OpenBSD
On 06/06/11 15:11, Gilles Chehade wrote: On Mon, Jun 06, 2011 at 03:06:54PM +0300, Kapetanakis Giannis wrote: I think the following diff will totally improve OpenBSD security (overall) --- etc/master.passwd.old Sat Jul 10 02:37:16 2010 +++ etc/master.passwd Mon Jun 6 15:04:15 2011 @@ -1,4 +1,4 @@ -root::0:0:daemon:0:0:Charlie:/root:/bin/ksh +root::0:0:daemon:0:0:Chuck Norris:/root:/bin/ksh daemon:*:1:1::0:0:The devil himself:/root:/sbin/nologin operator:*:2:5::0:0:System:/operator:/sbin/nologin bin:*:3:7::0:0:Binaries Commands and Source:/:/sbin/nologin Who is this 'Charlie' guy anyway??? Your diff is incorrect ... Who is this Chuck Norris Root anyway ? True. Here is version 2: --- etc/master.passwd Sat Jul 10 02:37:16 2010 +++ etc/master.passwd.chuck Mon Jun 6 15:22:57 2011 @@ -1,4 +1,5 @@ -root::0:0:daemon:0:0:Charlie :/root:/bin/ksh +chuck::-1:-1:daemon:-1:-1:Norris :/root:/bin/ksh +root::0:0:daemon:0:0:Chuck Norris :/root:/bin/ksh daemon:*:1:1::0:0:The devil himself:/root:/sbin/nologin operator:*:2:5::0:0:System :/operator:/sbin/nologin bin:*:3:7::0:0:Binaries Commands and Source:/:/sbin/nologin [demime 1.01d removed an attachment of type application/pkcs7-signature which had a name of smime.p7s]
Re: AT-2972LX10/LC
On 2011-06-06, Marek Czubenko marek.czube...@umk.pl wrote: Is it supported by broadcom driver? Has anybody any experience? (the AT-2972LX10/LC would be good for me if it would be supported by any net OpenBSD driver, there's no info on product's datasheet; I googled it, but didn't find positive results.) Network controller is Broadcom BCM 5715S. It's very likely to work, /sys/dev/pci/if_bge.c matches the 5715S's device ID. But I couldn't say for sure. The proper manpage tells, that bge driver supports BCM57xx network controller. Does it mean that xx may stand for exactly two characters (e.g. digits) or more too? no, it's just a shortcut. some new chip might come out with the number starting BCM57 and not be supported.
i386 softraid crypto panic
Hi, I'm experiencing a panic after an upgrade from yesterday's snapshot (SHA256 (bsd.rd) = d56181843c4355c64d84f8583e0946289ba0b2055b1ba194ce38cb28f725b29b) Everything but / is under a softraid cryto discipline so I did a bioctl -c C -l /dev/wd0d softraid0 before running /upgrade. The upgrade went ok but upon reboot, the bioctl command end up with the following panic: panic: kernel diagnostic assertion sc-sc_dis[sc-sd_target] == sd failed: file ../../../../dev/softraid.c, line 3372 Stopped at Debugger+0x4: popl %ebp (I cannot include the 'trace' and 'ps' because the keyboard is not working at this point) dmesg before panic: OpenBSD 4.9-current (GENERIC.MP) #62: Sun Jun 5 15:17:07 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP RTC BIOS diagnostic error 11memory_size cpu0: Intel(R) Core(TM)2 Duo CPU E8600 @ 3.33GHz (GenuineIntel 686-class) 3.33 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,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE real mem = 3487096832 (3325MB) avail mem = 3419242496 (3260MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/31/09, BIOS32 rev. 0 @ 0xffea0, SMBIOS rev. 2.5 @ 0xf0450 (82 entries) bios0: vendor Dell Inc. version A05 date 07/31/2009 bios0: Dell Inc. OptiPlex 960 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET SLIC SSDT SSDT SSDT acpi0: wakeup devices VBTN(S4) PCI0(S5) PCI4(S5) PCI2(S5) PCI3(S5) PCI1(S5) PCI5(S5) PCI6(S5) MOU_(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 332MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E8600 @ 3.33GHz (GenuineIntel 686-class) 3.33 GHz cpu1: 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,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 4 (PCI4) acpiprt1 at acpi0: bus 2 (PCI2) acpiprt2 at acpi0: bus 3 (PCI3) acpiprt3 at acpi0: bus 1 (PCI1) acpiprt4 at acpi0: bus -1 (PCI5) acpiprt5 at acpi0: bus -1 (PCI6) acpiprt6 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C1, PSS acpicpu1 at acpi0: C1, PSS acpibtn0 at acpi0: VBTN bios0: ROM list: 0xc/0x1 0xd/0x2000! 0xd2000/0x2000 cpu0: Enhanced SpeedStep 3326 MHz: speeds: , 3000, 2667, 2333, 2000 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel Q45 Host rev 0x03 ppb0 at pci0 dev 1 function 0 Intel Q45 PCIE rev 0x03: msi pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Radeon HD 3470 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 8 int 16 drm0 at radeondrm0 Intel Q45 HECI rev 0x03 at pci0 dev 3 function 0 not configured pciide0 at pci0 dev 3 function 2 Intel Q45 PT IDER rev 0x03: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using apic 8 int 18 for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) Intel Q45 KT rev 0x03 at pci0 dev 3 function 3 not configured em0 at pci0 dev 25 function 0 Intel ICH10 D BM LM rev 0x02: apic 8 int 21, address 00:24:e8:47:9f:46 uhci0 at pci0 dev 26 function 0 Intel 82801JD USB rev 0x02: apic 8 int 16 uhci1 at pci0 dev 26 function 1 Intel 82801JD USB rev 0x02: apic 8 int 17 uhci2 at pci0 dev 26 function 2 Intel 82801JD USB rev 0x02: apic 8 int 22 ehci0 at pci0 dev 26 function 7 Intel 82801JD USB rev 0x02: apic 8 int 22 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 82801JD HD Audio rev 0x02: msi azalia0: codecs: Analog Devices AD1984A audio0 at azalia0 ppb1 at pci0 dev 28 function 0 Intel 82801JD PCIE rev 0x02: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 1 Intel 82801JD PCIE rev 0x02: msi pci3 at ppb2 bus 3 uhci3 at pci0 dev 29 function 0 Intel 82801JD USB rev 0x02: apic 8 int 23 uhci4 at pci0 dev 29 function 1 Intel 82801JD USB rev 0x02: apic 8 int 17 uhci5 at pci0 dev 29 function 2 Intel 82801JD USB rev 0x02: apic 8 int 18 ehci1 at pci0 dev 29 function 7 Intel 82801JD USB rev 0x02: apic 8 int 23 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb3 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0xa2 pci4 at ppb3 bus 4 pcib0 at pci0 dev 31 function 0 Intel 82801JDO LPC rev 0x02 pciide1 at pci0 dev 31 function 2
Re: bgpd exiting abnormally after ospf up/down
On 2011-06-03, Stuart Henderson s...@spacehopper.org wrote: On 2011-06-03, Mindless Gr nomindles...@yahoo.com wrote: Today, after some link flaps, bgpd exited, i started it again and works, it seams that bgpd cant handle such situations very well, i have included here my configuration and messages to help developers recongize the bug, or if it is normal behaviour. if you need any extra informations, i will be happy to share them to you :) Jun 3 12:46:40 brdr0 bgpd[15610]: dispatch_rtmsg[change] mpath route not found fwiw, that happens on -current as of May 3 too. And I noticed similar with snmpd, though it stayed running - looks like it probably coincides with an overflowing route socket. 10:20:16 ospfd[11628]: reloading interface list and routing table 10:20:18 ospfd[11628]: reloading interface list and routing table 10:22:19 bgpd[19059]: neighbor xx.10 (...): socket error: Operation timed out 10:29:34 bgpd[19059]: neighbor xx.6: received notification: Cease, administratively down 10:29:34 bgpd[19059]: neighbor xx.6: state change Established - Idle, reason: NOTIFICATION received 10:29:38 bgpd[1288]: nexthop aaa now valid: via xx.244 10:29:39 bgpd[1288]: nexthop bbb now valid: via xx.244 10:29:39 bgpd[1288]: nexthop ccc now valid: via xx.244 10:29:39 bgpd[1288]: nexthop ddd now valid: via xx.244 10:29:39 snmpd[30215]: dispatch_rtmsg[delete] mpath route not found 10:29:39 ospfd[11628]: reloading interface list and routing table 10:29:42 last message repeated 2 times 10:30:05 bgpd[19059]: neighbor xx.6: state change Idle - Connect, reason: Start 10:30:05 bgpd[19059]: neighbor xx.6: connect: No route to host 10:30:05 bgpd[19059]: neighbor xx.6: state change Connect - Active, reason: Connection open failed 10:30:31 bgpd[1288]: nexthop aaa now valid: via xx.244 10:30:31 bgpd[1288]: nexthop bbb now valid: via xx.244 10:30:31 bgpd[1288]: nexthop ccc now valid: via xx.244 10:30:31 bgpd[1288]: nexthop ddd now valid: via xx.244 10:30:34 ospfd[11628]: reloading interface list and routing table
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
I'm super duper excited! :-0 do you need a towel ? do you need a keyboard or two? Now that you have decided to write your own OS from scratch in s-expressions like language? bwaaahh
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
On 6 June 2011 06:10, Thomas de Grivel billi...@gmail.com wrote: I don't want to engage in language wars, as i wrote before there is a gap in programming culture and reinforcing trust in my favorite lang or OS won't help. We trust our languages to mean something but writing correct programs strangely is still a struggle even to skilled programmers, and takes much testing. Again, i don't mean to hurt but C is really not KISS, at all. Its paradigm is appropriate for system but its grammar is a huge mess. And we're all happy to struggle with it ? Is it out of pride ? There is no easy fix but i recognize this is the core source of many ugly bugs. They're just symptoms of this. And noone cares at all. Oh great, you pointed out something that *could* be better. Yeah, C has its problems, so how are *YOU* going to start fixing it ? Now, again, I lost the part where you say what you are doing to make it better. You made no questions and no statements that could result in any productive work what-so-ever. Honestly, what are you trying to achieve ?
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
On Mon, Jun 06, 2011 at 05:36:03AM -0400, Eric Furman wrote: The answer is too write all OS code in Machine language for each Architecture! YEA! We're waiting for your code! I'm super duper excited! :-0 Perhaps he should go work on this project: BareMetal OS BareMetal is a 64-bit OS for x86-64 based computers. The OS is written entirely in Assembly, whil e applications can be written in Assembly or C/C++. Clearly someone is trying to get rid of ugly languages!
Re: serious security improvement in OpenBSD
Le Mon, 06 Jun 2011 15:06:54 +0300, Kapetanakis Giannis bil...@edu.physics.uoc.gr a icrit : Who is this 'Charlie' guy anyway??? That is a good question. I've searched in the past looking old system passwd to find who decided this name for the root account but with no luck. Looks like Charlie is a tribute to Charlie Root (a famous baseball player):http://en.wikipedia.org/wiki/Charlie_Root Does someone remember who, when and why? Regards.
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
brainfuck OS sould be a good idea too... :D of course this is a joke, forth language should be more usefull From: Chris Bennett ch...@bennettconstruction.biz Sent: Mon Jun 06 18:49:16 CEST 2011 To: misc@openbsd.org Subject: Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems. On Mon, Jun 06, 2011 at 05:36:03AM -0400, Eric Furman wrote: The answer is too write all OS code in Machine language for each Architecture! YEA! We're waiting for your code! I'm super duper excited! :-0 Perhaps he should go work on this project: BareMetal OS BareMetal is a 64-bit OS for x86-64 based computers. The OS is written entirely in Assembly, whil e applications can be written in Assembly or C/C++. Clearly someone is trying to get rid of ugly languages! Cordialement Francois Pussault 3701 - 8 rue Marcel Pagnol 31100 ToulouseB FranceB +33 6 17 230 820 B +33 5 34 365 269 fpussa...@contactoffice.fr
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
On Mon, 6 Jun 2011 11:49:16 -0500 Chris Bennett wrote: BareMetal is a 64-bit OS for x86-64 based computers. The OS is written entirely in Assembly, I believe some/all newer models? of the Sonicwall range were rewritten in assembly, to increase performance. My cousin loves em.
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
On Mon, Jun 06, 2011 at 11:49:16AM -0500, Chris Bennett wrote: On Mon, Jun 06, 2011 at 05:36:03AM -0400, Eric Furman wrote: The answer is too write all OS code in Machine language for each Architecture! YEA! We're waiting for your code! I'm super duper excited! :-0 Perhaps he should go work on this project: BareMetal OS BareMetal is a 64-bit OS for x86-64 based computers. The OS is written entirely in Assembly, whil e applications can be written in Assembly or C/C++. Clearly someone is trying to get rid of ugly languages! http://www.menuetos.net/ ?
Re: Reverse-proxy PF ?
You should try nginx. R hvom .org wrote, On 6/6/2011 3:54 AM: Hi all I look the doc, ftp-proxy, no reverse-proxy PF ?. Varnish, ultimate soluce ? Cordialy
OpenBSD crash (tomcat + subsonic possibly)
Hello, I am running Subsonic 4.4 over SSL, java 7 (jdk-1.7.0.00beta122), and tomcat 6.0.20 to stream music through a nice interface. There are times (not always) when I am uploading GBs (5-10) of music data (remotely with scp), and the system crashes: user ttyp1XXX.XXX.XX.XXX Mon Jun 6 16:21 - crash (00:26) I am pretty positive it is caused by subsonic trying to read and index all the extra files, but I would like to ask: 1)Has anyone experienced issues by using the above combination? 2)What system log files should I look into? (I currently know, and have checked dmesg, lastlog, daemon, authlog, daily.out, messages, but couldn't find anything relevant about the cause, except the crash in lastlog.) Mike
Re: i386 softraid crypto panic
On Mon, Jun 6, 2011 at 9:40 AM, Manuel GIRAUD manuel.gir...@univ-nantes.fr wrote: I'm experiencing a panic after an upgrade from yesterday's snapshot (SHA256 (bsd.rd) = d56181843c4355c64d84f8583e0946289ba0b2055b1ba194ce38cb28f725b29b) Everything but / is under a softraid cryto discipline so I did a bioctl -c C -l /dev/wd0d softraid0 before running /upgrade. The upgrade went ok but upon reboot, the bioctl command end up with the following panic: panic: kernel diagnostic assertion sc-sc_dis[sc-sd_target] == sd failed: file ../../../../dev/softraid.c, line 3372 Stopped at Debugger+0x4: popl %ebp There is no such line in the source, so apparently there was a patch, but it looks like it's been removed now.
Re: i386 softraid crypto panic
On Mon, Jun 06, 2011 at 02:47:45PM -0400, Ted Unangst wrote:
On Mon, Jun 6, 2011 at 9:40 AM, Manuel GIRAUD
manuel.gir...@univ-nantes.fr wrote:
I'm experiencing a panic after an upgrade from yesterday's snapshot
(SHA256 (bsd.rd) =
d56181843c4355c64d84f8583e0946289ba0b2055b1ba194ce38cb28f725b29b)
Everything but / is under a softraid cryto discipline so I did a
bioctl -c C -l /dev/wd0d softraid0 before running /upgrade. The
upgrade went ok but upon reboot, the bioctl command end up with the
following panic:
panic: kernel diagnostic assertion sc-sc_dis[sc-sd_target] == sd
failed: file ../../../../dev/softraid.c, line 3372
Stopped at Debugger+0x4: popl %ebp
There is no such line in the source, so apparently there was a patch,
but it looks like it's been removed now.
That line is from my softraid scsibus diff, which was included in the
Jun 5 snapshots. There was a bug where it didn't properly unwind a
failed BIOCCREATERAID attempt.
The diff below fixes this issue, and I haven't been able to reproduce
any other panics in my testing with RAID 0, RAID 1, and crypto
softraid configurations.
Index: softraid.c
===
RCS file: /home/mdempsky/anoncvs/cvs/src/sys/dev/softraid.c,v
retrieving revision 1.230
diff -u -p -r1.230 softraid.c
--- softraid.c 3 May 2011 17:08:51 - 1.230
+++ softraid.c 6 Jun 2011 17:25:43 -
@@ -87,7 +87,8 @@ struct cfdriver softraid_cd = {
/* scsi discipline */
void sr_scsi_cmd(struct scsi_xfer *);
-void sr_minphys(struct buf *bp, struct scsi_link *sl);
+void sr_minphys(struct buf *, struct scsi_link *);
+intsr_scsi_probe(struct scsi_link *);
void sr_copy_internal_data(struct scsi_xfer *,
void *, size_t);
intsr_scsi_ioctl(struct scsi_link *, u_long,
@@ -167,7 +168,7 @@ extern void (*softraid_disk_attach)(str
/* scsi glue */
struct scsi_adapter sr_switch = {
- sr_scsi_cmd, sr_minphys, NULL, NULL, sr_scsi_ioctl
+ sr_scsi_cmd, sr_minphys, sr_scsi_probe, NULL, sr_scsi_ioctl
};
/* native metadata format */
@@ -1632,6 +1633,7 @@ void
sr_attach(struct device *parent, struct device *self, void *aux)
{
struct sr_softc *sc = (void *)self;
+ struct scsibus_attach_args saa;
DNPRINTF(SR_D_MISC, \n%s: sr_attach, DEVNAME(sc));
@@ -1656,6 +1658,18 @@ sr_attach(struct device *parent, struct
printf(\n);
+ sc-sc_link.adapter_softc = sc;
+ sc-sc_link.adapter = sr_switch;
+ sc-sc_link.adapter_target = SR_MAX_LD;
+ sc-sc_link.adapter_buswidth = SR_MAX_LD;
+ sc-sc_link.luns = 1;
+
+ bzero(saa, sizeof(saa));
+ saa.saa_sc_link = sc-sc_link;
+
+ sc-sc_scsibus = (struct scsibus_softc *)config_found(sc-sc_dev,
+ saa, scsiprint);
+
softraid_disk_attach = sr_disk_attach;
sr_boot_assembly(sc);
@@ -1910,19 +1924,10 @@ sr_scsi_cmd(struct scsi_xfer *xs)
DNPRINTF(SR_D_CMD, %s: sr_scsi_cmd: scsibus%d xs: %p
flags: %#x\n, DEVNAME(sc), link-scsibus, xs, xs-flags);
- sd = sc-sc_dis[link-scsibus];
+ sd = sc-sc_dis[link-target];
if (sd == NULL) {
- s = splhigh();
- sd = sc-sc_attach_dis;
- splx(s);
-
- DNPRINTF(SR_D_CMD, %s: sr_scsi_cmd: attaching %p\n,
- DEVNAME(sc), sd);
- if (sd == NULL) {
- printf(%s: sr_scsi_cmd NULL discipline\n,
- DEVNAME(sc));
- goto stuffup;
- }
+ printf(%s: sr_scsi_cmd NULL discipline\n, DEVNAME(sc));
+ goto stuffup;
}
if (sd-sd_deleted) {
@@ -1948,19 +1953,6 @@ sr_scsi_cmd(struct scsi_xfer *xs)
wu-swu_dis = sd;
wu-swu_xs = xs;
- /* the midlayer will query LUNs so report sense to stop scanning */
- if (link-target != 0 || link-lun != 0) {
- DNPRINTF(SR_D_CMD, %s: bad target:lun %d:%d\n,
- DEVNAME(sc), link-target, link-lun);
- sd-sd_scsi_sense.error_code = SSD_ERRCODE_CURRENT |
- SSD_ERRCODE_VALID;
- sd-sd_scsi_sense.flags = SKEY_ILLEGAL_REQUEST;
- sd-sd_scsi_sense.add_sense_code = 0x25;
- sd-sd_scsi_sense.add_sense_code_qual = 0x00;
- sd-sd_scsi_sense.extra_len = 4;
- goto stuffup;
- }
-
switch (xs-cmd-opcode) {
case READ_COMMAND:
case READ_BIG:
@@ -2036,6 +2028,28 @@ stuffup:
complete:
sr_scsi_done(sd, xs);
}
+
+int
+sr_scsi_probe(struct scsi_link *link)
+{
+ struct sr_softc *sc = link-adapter_softc;
+ struct sr_discipline*sd;
+
+ KASSERT(link-target SR_MAX_LD link-lun == 0);
+
+ sd = sc-sc_dis[link-target];
Known softraid(4) issue in Jun 5 snapshot
As a heads up to all softraid(4) users, there's a known issue with a softraid patch included in the Jun 5 snapshot kernels. In particular, unsuccessful attempts to create a softraid logical disk using bioctl(8) (i.e., bioctl -c) can result in a kernel panic. I encourage softraid(4) users to skip this snapshot release. The next snapshot release will include a fix for this issue. Sorry for the inconvenience! :(
Re: OpenBSD crash (tomcat + subsonic possibly)
On Mon, Jun 6, 2011 at 11:31 AM, Michael Sioutis papito@gmail.com wrote: I am running Subsonic 4.4 over SSL, java 7 (jdk-1.7.0.00beta122), and tomcat 6.0.20 to stream music through a nice interface. It would help if you also included what version of OpenBSD you're using, preferably by including the output of dmesg. That's sort of a vital detail.
Re: OpenBSD crash (tomcat + subsonic possibly)
OpenBSD 4.9! Mike On Mon, Jun 6, 2011 at 10:59 PM, Matthew Dempsky matt...@dempsky.org wrote: On Mon, Jun 6, 2011 at 11:31 AM, Michael Sioutis papito@gmail.com wrote: I am running Subsonic 4.4 over SSL, java 7 (jdk-1.7.0.00beta122), and tomcat 6.0.20 to stream music through a nice interface. It would help if you also included what version of OpenBSD you're using, preferably by including the output of dmesg. That's sort of a vital detail. [demime 1.01d removed an attachment of type text/x-log which had a name of dmesg.log]
Re: OpenBSD crash (tomcat + subsonic possibly)
On Mon, Jun 6, 2011 at 11:31 AM, Michael Sioutispapito@gmail.com wrote: I am running Subsonic 4.4 over SSL, java 7 (jdk-1.7.0.00beta122), and tomcat 6.0.20 to stream music through a nice interface. Its easier and faster to send more information than needed and having it ignored, than it is to go back and forth asking for what is needed Please reply the dmesg, output of pkg_info andget the crash dump ready to be sent out if someone asks for it. Fell free to include anything else that you think is pertinent to this problem.
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
On Mon, Jun 06, 2011 at 10:31:29AM -0500, Amit Kulkarni wrote: do you need a keyboard or two? Now that you have decided to write your own OS from scratch in s-expressions like language? We should send this guy bullshit to the Linux kernel mailing-list so they can have some fun too. Hey. Those guys are doing open source, we can share the fun even if they're stuck stuffing penguins at home while we get red-leather chicks on our side... -- Threepwood
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
On Mon, Jun 06, 2011 at 01:33:31PM -0300, Christiano F. Haesbaert wrote: Honestly, what are you trying to achieve ? I bet 10 canadian dollars on his 15 minute fame, and eternal storage in Google newsgroup servers of YARGTKBTOD* (*) Yet Another Random Guy That Knows Better Than OpenBSD Developers -- Bill Gates
Re: Interesting panic during boot
On Fri, 3 Jun 2011, Dave Anderson wrote: On Fri, 3 Jun 2011, Kenneth R Westerback wrote: On Fri, Jun 03, 2011 at 01:09:47PM -0400, Dave Anderson wrote: While gathering notebook dmesgs I encountered this panic during boot (at a Best Buy, on a demo system labelled Toshiba r835-p50x, booting from a USB stick loaded with an i386 snapshot dated 5/24). The root device DUID shown is correct. panic: root device (e0166bb8f33fc15d) not found stopped at Debugger_0x4: popl %ebp [trace] Debugger(d08e2194.d0ba9d54.d08bf2f0.d0ba9d54.15c6a) at Debugger+0x4 panic(d08bf2f0.e0.16.6b.b8) at panic+0x5d setroot(d3a99800.0.4000.d0ba9e94.0) at setroot+0xa05 diskconf(d08b73d7.0.d08bd109.0,0) at diskconf+0x12e main(d02004ba.d02004c2.0.0.0) at main+0x570 [ps] PID PPID PGRP UID S FLAGS WAIT COMMAND 9 0 00 3 0x100200 bored crypto 8 0 00 3 0x100200 pftm pfpurge 7 0 00 3 0x100200 usbtskusbtask 6 0 00 3 0x100200 usbatsk usbatsk 5 0 00 3 0x100200 acpi0 acpi0 4 0 00 3 0x100200 bored syswq 3 0 00 3 0x40100200idle0 2 0 00 3 0x100200 kmalloc kmthread 1 0 00 3 0 initexec swapper * 0-1 00 70x80200swapper [All of the above was hand-copied from the screen, so there may be typos.] I hope that this is enough information to enable someone to track down the problem. If more is needed, let me know what it is and I'll try to get it. Dave -- Dave Anderson d...@daveanderson.com The dmesg is needed. This looks like the disk/usb stick is not being found by the OS. I was afraid of that. Dealing with the first apparent problem, that most of the dmesg scrolls off the screen, looks to be easy; a quick look at the source reveals that ddb has an apparently undocumented 'dmesg' command. Actually capturing the dmesg looks to be harder; given that this is a store demo system to which I have very limited access I'm not sure I've got any better way than hand-writing it all. I've got a couple of ideas for easier ways to try, but it will take a few days. Are there any parts of the dmesg that are known to be unnecessary for this purpose, so I can avoid the work of copying them if I have to fall back to writing everything down and retyping it? Now that I've had time to think about this a bit, I'd guess that the problem is some new USB controller that OpenBSD doesn't yet understand. If so, am I correct that all that's really needed is the vendor ID and device ID of the controller? I'll check for this first, now that I know how to view the whole dmesg after the panic. FWIW this stick boots just fine on lots of other systems, both before and after this problem system. I got a chance to poke at this system again today, and found a USB port from which I could boot. The offending device appears to be 'NEC PCIE-XHCI rev 0x04 at pci4 dev 0 function 0 not configured'. I also found another system (labelled Dell Inspiron 17r-6457dbk) which exhibits a similar problem but again was able to find a working USB port; this appears to use the same new device: 'NEC PCIE-XHCI rev 0x04 at pci2 dev 0 function 0 not configured'. I'm sending both dmesgs to dm...@openbsd.org and also including them here in case that's useful. Dave OpenBSD 4.9-current (GENERIC) #3: Mon May 23 21:40:58 MDT 2011 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Core(TM) i3-2310M CPU @ 2.10GHz (GenuineIntel 686-class) 2.10 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,PCLMUL,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX real mem = 2853560320 (2721MB) avail mem = 2796097536 (2666MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 03/04/11, SMBIOS rev. 2.5 @ 0xaaefe000 (43 entries) bios0: vendor TOSHIBA version Version 2.10 date 03/04/2011 bios0: TOSHIBA PORTEGE R835 acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC MCFG ASF! BOOT SLIC SSDT SSDT SSDT SSDT acpi0: wakeup devices LANC(S4) HDEF(S3) RP02(S4) PXSX(S4) RP04(S4) PXSX(S4) USBB(S4) USBC(S4) EHC1(S4) EHC2(S4) PWRB(S4) LID_(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 99MHz cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEGP) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus 4 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6
Sun Blade 1500 (non-Silver) OBP
Hi, I recently got a Sun Blade 1500 Red at an eBay auction. I have a Sun Type 7 keyboard which won't work on this old OBP (4.9.5), and have read that it should work with later versions. Problem is, it has a very old OBP. AFAIK, the old Sunsolve FTPs used to have the firmwares available for download but these no longer exists. Does anyone have version 4.30.4.a (Patch ID: 140686-02) (or at least a version = 4.17) and be willing to share this with me? Thank you, Bjorn
Re: OpenBSD crash (tomcat + subsonic possibly)
PKG_INFO log available as attached! I only have a minfree file in /var/crash.. On Mon, Jun 6, 2011 at 11:13 PM, LeviaComm Networks n...@leviacomm.net wrote: On Mon, Jun 6, 2011 at 11:31 AM, Michael Sioutispapito@gmail.com wrote: I am running Subsonic 4.4 over SSL, java 7 (jdk-1.7.0.00beta122), and tomcat 6.0.20 to stream music through a nice interface. Its easier and faster to send more information than needed and having it ignored, than it is to go back and forth asking for what is needed Please reply the dmesg, output of pkg_info andget the crash dump ready to be sent out if someone asks for it. Fell free to include anything else that you think is pertinent to this problem. [demime 1.01d removed an attachment of type text/x-log which had a name of pkg_info.log]
IPF is not and never was a cash cow
And anyone that tries to represent it as such is lieing. In fact I've never made money off of it and never I've never tried to make money off it. Now if you all make money off of pf, well and good for you. My goal for ipf was never to make money off of it. Please correct your presentation. Darren
Re: serious security improvement in OpenBSD
Hi Patrick, Patrick Lamaiziere wrote on Mon, Jun 06, 2011 at 06:59:48PM +0200: Le Mon, 06 Jun 2011 15:06:54 +0300, Kapetanakis Giannis bil...@edu.physics.uoc.gr a icrit : Who is this 'Charlie' guy anyway??? That is a good question. I've searched in the past looking old system passwd to find who decided this name for the root account but with no luck. http://minnie.tuhs.org/cgi-bin/utree.pl?file=4BSD/etc/passwd has root::0:10:Ernie Co-vax,508JE,0204:/:/bin/csh on Nov 16, 1980 http://minnie.tuhs.org/cgi-bin/utree.pl?file=4.1cBSD/etc/passwd has root::0:10:Charlie,458E,7750:/:/bin/csh on Feb 27, 1983 http://minnie.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/etc/passwd has root::0:10:Charlie :/:/bin/csh on Sep 25, 1983 Looks like Charlie is a tribute to Charlie Root (a famous baseball player):http://en.wikipedia.org/wiki/Charlie_Root No idea. Does someone remember who, when and why? It looks like it happened in 1981 or 1982 at the CSRG in Berkeley, and Charlie was a person or machine or joke located in office 458, next door to Bill Joy. That's partial information and guesswork, but no wonder, i wasn't there. Bill Joy will probably know; and maybe Eric Allman and Kirk McKusick, who are listed in the 4.1cBSD passwd file as well. The following CD set seems likely to contain more information: http://www.mckusick.com/csrg/ Yours, Ingo
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
How about he proves to us he can write good lisp code first, by maintaining ecl and maxima and sbcl for a while ?
COMPRANET 5.0 Manejo Óptimo del Sistema (EL CURSO MÁS IMPORTANTE DEL MOMENTO)
172871 [IMAGE] Pms Capacitacisn Efectiva de Mixico presenta: El programa mas importante del momento Manejo Sptimo del Sistema Compranet 5.0 Exclusivas presentaciones: 27 de Junio en la Ciudad de Mixico. 29 de Junio en Guadalajara, Jalisco. 01 de Julio en Monterrey, Nuevo Lesn. Expositor: Mtro. Alberto Ledesma Gonzalez 10 horas de entrenamiento Empresa Registrada ante la STPS Reg. COLG640205CP30005 Smguenos en Twitter@pmscapacitacion o bien en Facebook PMS de Mixico Mayores informes responda este correo electrsnico con los siguientes datos. Empresa: Nombre: Telifono: Email: Nzmero de Interesados: Y en breve le haremos llegar la informacisn completa del evento. O bien comunmquense a nuestros telifonos un ejecutivo con gusto le atendera Tels. (33) 8851-2365, (33)8851-2741. Copyright (C) 2010, PMS Capacitacisn Efectiva de Mixico S.C. Derechos Reservados. PMS de Mixico, El logo de PMS de Mixico son marcas registradas. ADVERTENCIA PMS de Mixico no cuenta con alianzas estratigicas de ningzn tipo dentro de la Republica Mexicana. NO SE DEJE ENGAQAR - DIGA NO A LA PIRATERIA. Todos los logotipos, marcas comerciales e imagenes son propiedad de sus respectivas corporaciones y se utilizan con fines informativos solamente. Este Mensaje ha sido enviado a misc@openbsd.org como usuario de Pms de Mixico o bien un usuario le refiris para recibir este boletmn. Como usuario de Pms de Mixico, en este acto autoriza de manera expresa que Pms de Mixico le puede contactar vma correo electrsnico u otros medios. Si usted ha recibido este mensaje por error, haga caso omiso de el y reporte su cuenta respondiendo este correo con el subject BAJACOMPRANET Unsubscribe to this mailing list, reply a blank message with the subject UNSUBSCRIBE BAJACOMPRANET Tenga en cuenta que la gestisn de nuestras bases de datos es de suma importancia y no es intencisn de la empresa la inconformidad del receptor. [demime 1.01d removed an attachment of type image/jpeg which had a name of compranet.jpg]
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
X86 machine language sucks big rocks. Everyone should write in microcode for full speed! Sent from my iPhone On Jun 6, 2011, at 12:49 PM, Chris Bennett ch...@bennettconstruction.biz wrote: On Mon, Jun 06, 2011 at 05:36:03AM -0400, Eric Furman wrote: The answer is too write all OS code in Machine language for each Architecture! YEA! We're waiting for your code! I'm super duper excited! :-0 Perhaps he should go work on this project: BareMetal OS BareMetal is a 64-bit OS for x86-64 based computers. The OS is written entirely in Assembly, whil e applications can be written in Assembly or C/C++. Clearly someone is trying to get rid of ugly languages!
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
I see your brainfuck and raise you APL Sent from my iPhone On Jun 6, 2011, at 1:11 PM, Francois Pussault fpussa...@contactoffice.fr wrote: brainfuck OS sould be a good idea too... :D of course this is a joke, forth language should be more usefull From: Chris Bennett ch...@bennettconstruction.biz Sent: Mon Jun 06 18:49:16 CEST 2011 To: misc@openbsd.org Subject: Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems. On Mon, Jun 06, 2011 at 05:36:03AM -0400, Eric Furman wrote: The answer is too write all OS code in Machine language for each Architecture! YEA! We're waiting for your code! I'm super duper excited! :-0 Perhaps he should go work on this project: BareMetal OS BareMetal is a 64-bit OS for x86-64 based computers. The OS is written entirely in Assembly, whil e applications can be written in Assembly or C/C++. Clearly someone is trying to get rid of ugly languages! Cordialement Francois Pussault 3701 - 8 rue Marcel Pagnol 31100 ToulouseB FranceB +33 6 17 230 820 B +33 5 34 365 269 fpussa...@contactoffice.fr
PowerMath - Your Virtual Mathematics Assistant
PowerMath - Your Virtual Mathematics Assistant Mathematics Made Easy Summer 2011 Computer Animation Lesson-Shows : Courses in Arithmetic, Algebra, Geometry, Trigonometry, Pre-Calculus, Calculus, Probability and Statistics covering Middle-School, High-School and University level Mathematics, for Students and Instructors. PowerMath has been featured on among others . . . Exclusion: If you no longer wish to receive email from PowerClassroom Software invoke deletePlease do NOT reply to this e-mail if you wish to unsubscribe, instead use the instructions above. Any/all information collected from our customers will not be sold, shared, or rented.
Re: OpenBSD crash (tomcat + subsonic possibly)
On 06/06/2011 04:03 PM, Michael Sioutis wrote: PKG_INFO log available as attached! I only have a minfree file in /var/crash.. On Mon, Jun 6, 2011 at 11:13 PM, LeviaComm Networksn...@leviacomm.net wrote: On Mon, Jun 6, 2011 at 11:31 AM, Michael Sioutispapito@gmail.com wrote: I am running Subsonic 4.4 over SSL, java 7 (jdk-1.7.0.00beta122), and tomcat 6.0.20 to stream music through a nice interface. Its easier and faster to send more information than needed and having it ignored, than it is to go back and forth asking for what is needed Please reply the dmesg, output of pkg_info andget the crash dump ready to be sent out if someone asks for it. Fell free to include anything else that you think is pertinent to this problem. [demime 1.01d removed an attachment of type text/x-log which had a name of pkg_info.log] Attachments are stripped by the list manager software. Please include your dmesg and other info inline with your message text.
Re: Interesting panic during boot
On Mon, Jun 06, 2011 at 04:24:13PM -0400, Dave Anderson wrote: On Fri, 3 Jun 2011, Dave Anderson wrote: On Fri, 3 Jun 2011, Kenneth R Westerback wrote: On Fri, Jun 03, 2011 at 01:09:47PM -0400, Dave Anderson wrote: While gathering notebook dmesgs I encountered this panic during boot (at a Best Buy, on a demo system labelled Toshiba r835-p50x, booting from a USB stick loaded with an i386 snapshot dated 5/24). The root device DUID shown is correct. panic: root device (e0166bb8f33fc15d) not found stopped at Debugger_0x4: popl %ebp [trace] Debugger(d08e2194.d0ba9d54.d08bf2f0.d0ba9d54.15c6a) at Debugger+0x4 panic(d08bf2f0.e0.16.6b.b8) at panic+0x5d setroot(d3a99800.0.4000.d0ba9e94.0) at setroot+0xa05 diskconf(d08b73d7.0.d08bd109.0,0) at diskconf+0x12e main(d02004ba.d02004c2.0.0.0) at main+0x570 [ps] PID PPID PGRP UID S FLAGS WAIT COMMAND 9 0 00 3 0x100200 bored crypto 8 0 00 3 0x100200 pftm pfpurge 7 0 00 3 0x100200 usbtskusbtask 6 0 00 3 0x100200 usbatsk usbatsk 5 0 00 3 0x100200 acpi0 acpi0 4 0 00 3 0x100200 bored syswq 3 0 00 3 0x40100200idle0 2 0 00 3 0x100200 kmalloc kmthread 1 0 00 3 0 initexec swapper * 0-1 00 70x80200swapper [All of the above was hand-copied from the screen, so there may be typos.] I hope that this is enough information to enable someone to track down the problem. If more is needed, let me know what it is and I'll try to get it. Dave -- Dave Anderson d...@daveanderson.com The dmesg is needed. This looks like the disk/usb stick is not being found by the OS. I was afraid of that. Dealing with the first apparent problem, that most of the dmesg scrolls off the screen, looks to be easy; a quick look at the source reveals that ddb has an apparently undocumented 'dmesg' command. Actually capturing the dmesg looks to be harder; given that this is a store demo system to which I have very limited access I'm not sure I've got any better way than hand-writing it all. I've got a couple of ideas for easier ways to try, but it will take a few days. Are there any parts of the dmesg that are known to be unnecessary for this purpose, so I can avoid the work of copying them if I have to fall back to writing everything down and retyping it? Now that I've had time to think about this a bit, I'd guess that the problem is some new USB controller that OpenBSD doesn't yet understand. If so, am I correct that all that's really needed is the vendor ID and device ID of the controller? I'll check for this first, now that I know how to view the whole dmesg after the panic. FWIW this stick boots just fine on lots of other systems, both before and after this problem system. I got a chance to poke at this system again today, and found a USB port from which I could boot. The offending device appears to be 'NEC PCIE-XHCI rev 0x04 at pci4 dev 0 function 0 not configured'. I also found another system (labelled Dell Inspiron 17r-6457dbk) which exhibits a similar problem but again was able to find a working USB port; this appears to use the same new device: 'NEC PCIE-XHCI rev 0x04 at pci2 dev 0 function 0 not configured'. I'm sending both dmesgs to dm...@openbsd.org and also including them here in case that's useful. Excellent! Thanks for the investigation. XHCI sounds like usb3, and I don't believe we support that yet. Ken
Re: Seems OpenBSD isn't absolutely alone in it's quest, atleast on embedded systems.
On Mon, Jun 06, 2011 at 08:17:11PM -0400, goodb...@gmail.com wrote: X86 machine language sucks big rocks. x86 is not executed on x86 processors since the Pentium 4. Intel (and AMD) are using RISC cores at the heart of their processors. x86 instructions are translated into RISC code and this code is the one that gets executed. The x86 CISC is just a shell around an RISC heart. -- Overflow
