Re: Strange c++ compilation
Le 01/12/2012 22:31, Philip Guenther a écrit : > Neither. The OpenBSD developers think that that's a useless** warning > and aren't interested in making the system header files that much > harder to read just to make it go away. > > What problem are you trying to solve by using -Wredundant-decls? Nothing important. I was just surprised to see a lot of warnings when compiling a project. Thanks for the answer. Has > it *ever* caught a problem in code that you then fixed? Or have you > always just followed modern best practices by only putting extern > function declarations in just one header file? > > > Philip Guenther > > ** some developers have much harsher language for this...
Re: ifOperStatus of em(4) devices always unknown when link is up
Am Montag, 3. Dezember 2012 schrieb InterNetX - Carsten Schoene :
> Hello,
>
> i've setup a OpenBSD 5.2 (amd64) system using flashrd on a DELL R610
> server,
> with an Intel PRO/1000 PF (82571EB) dualport fibre optics adapter.
> The system also have four broadcom BCM5709 copper interfaces.
>
> I try to monitor the linkstate of these interface using the default
> snmpd. The linkstate for the bnx interfaces are always correct ("up"), only
> the em interfaces report "unknown" when the link is in state "up"
>
>
Some drivers/chipsets don't report their link state correctly and unknown
is actually a "valid" fallback in this case. I will have a look at this.
Can you show me the output of "route -n monitor" while toggling the link?
Reyk
> # ifconfig em0
> em0: flags=8843 mtu 1500
> lladdr xx:xx:xx:xx:xx:xx
> description: Uplink
> priority: 0
> media: Ethernet 1000baseSX full-duplex
> status: active
> inet xxx:xxx:xxx:xxx netmask 0xfff8 broadcast xxx:xxx:xxx:xxx
> inet6 :::::%em0 pre
>
> # snmpwalk -v 1 -c public localhost IF | grep -i -E '(ifoper|ifdescr)'
> IF-MIB::ifDescr.1 = STRING: em0
> IF-MIB::ifDescr.2 = STRING: em1
> IF-MIB::ifDescr.3 = STRING: enc0
> IF-MIB::ifDescr.4 = STRING: lo0
> IF-MIB::ifDescr.5 = STRING: bnx0
> IF-MIB::ifDescr.6 = STRING: bnx1
> IF-MIB::ifDescr.7 = STRING: bnx2
> IF-MIB::ifDescr.8 = STRING: bnx3
> IF-MIB::ifOperStatus.1 = INTEGER: unknown(4)
> IF-MIB::ifOperStatus.2 = INTEGER: down(2)
> IF-MIB::ifOperStatus.3 = INTEGER: down(2)
> IF-MIB::ifOperStatus.4 = INTEGER: unknown(4)
> IF-MIB::ifOperStatus.5 = INTEGER: down(2)
> IF-MIB::ifOperStatus.6 = INTEGER: down(2)
> IF-MIB::ifOperStatus.7 = INTEGER: up(1)
> IF-MIB::ifOperStatus.8 = INTEGER: up(1)
>
> If i shutdown the interface "ifconfig em0 down", it's state is correctly
> reported as "down".
>
> I can reproduce this on a vmware virtual machine running a plain OpenBSD
> 5.2 ( no flashrd setup).
> The used intel based adapter is reported as "Intel PRO/1000MT (82545EM)"
> and behaves the same
> like on my physical server. I also disabled the "connected" state from
> vmware side and the
> interface reports it's state correctly as "lowerLayerDown(7)" within snmp.
>
> I also tested with 5.1 release on vmware, with the same results.
>
> It looks like a kernel/driver problem for me.
>
> Any help would be appreciated.
>
>
> Regards,
> --
> Carsten Schöne
Re: PRIMERGY RX200 S2 installation problems
indeed. Looks like the mixed it up. As long as I get the 'current' log I'll
send it to the list.
Thanks
On Mon, Dec 3, 2012 at 6:23 PM, Sebastian Reitenbach <
sebas...@l00-bugdead-prods.de> wrote:
>
> Am Montag, 03. Dezember 2012 17:57 CET, Tony Berth <
> tonybe...@googlemail.com> schrieb:
>
> > it is the current one (2012-12-02)
>
>
> > > OpenBSD 5.2 (RAMDISK_CD) #287: Wed Aug 1 10:19:00 MDT 2012
> > > der...@i386.openbsd.org:/usr/src/sys/sys/arch/i386/compile/RAMDISK_CD
>
> but dmesg says its not so current like you think it is.
>
> Sebastian
>
> >
> > Thanks
> >
> > On Mon, Dec 3, 2012 at 6:52 PM, Kenneth R Westerback <
> kwesterb...@rogers.com
> > > wrote:
> >
> > > On Mon, Dec 03, 2012 at 06:08:34PM +0200, Tony Berth wrote:
> > > > here is the installation dmesg when trying to install the 5.2 i386
> > > snapshot:
> > >
> > > And the installation dmesg from a -current snapshot would be even
> > > more useful.
> > >
> > > Ken
> > >
> > > >
> > > > -
> > > > LSI Logic Corp. MPT IME BIOS
> > > > Copyright 1995-2005 LSI Logic Corp.
> > > > MPTBIOS-IME-5.13.08
> > > >
> > > > CD-ROM: 9F
> > > > Loading /5.2/I386/CDBOOT
> > > > probing: pc0 apm pci mem[616K 2046M a20=on]
> > > > disk: hd0+* cd0
> > > > >> OpenBSD/i386 CDBOOT 3.17
> > > > boot>
> > > > booting cd0a:/5.2/i386/bsd.rd: 5973772+958284
> [52+229744+218028]=0x709d1c
> > > > entry point at 0x200128
> > > > Copyright (c) 1982, 1986, 1989, 1991, 1993
> > > > The Regents of the University of California. All rights reserved.
> > > > Copyright (c) 19995-2012 OpenBSD. All rights reserved.
> > > > http://www.OpenBSD.org
> > > > OpenBSD 5.2 (RAMDISK_CD) #287: Wed Aug 1 10:19:00 MDT 2012
> > > > der...@i386.openbsd.org:
> /usr/src/sys/sys/arch/i386/compile/RAMDISK_CD
> > > > cpu0: Intel(R) Xeon(TM) CPU 3.00 GHz ("GenuineIntel" 686-class)
> > > > cpu0: FPU, V86, DE, PSE, TSC, MSR, PAE, MCE, CX8, APIC, SEP, MTRR,
> > > PGE,MCA,
> > > > CMOV, PAT, PSE36, CF
> > > >
> > >
> LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM.SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,CNXT-
> > > > ID,
> > > > CX16,xTPR
> > > > real mem = 2146414592 (2046MB)
> > > > avail mem = 2183640064 (2006MB)
> > > > mainbus0 at root
> > > > bios0 at mainbus0: AT/286+ BIOS, date 09/16/85, BIOS32 rev. 0 @
> 0xfd418,
> > > > SMBIOS
> > > > rev. 2.33 @ 0xdc010 (58 entries)
> > > > bios0: vendor FSC version "6.8 Rev. R04A5F1.1790" date 09/16/2005
> > > > bios0: FUJITSU SIEMENES PRIMERGY RX200S2
> > > > acpi0 at bios0: rev 0
> > > > acpi0: sleep states S0 S1 S4 S5
> > > > acpi0: tables DSDT FACP MCFC SPCR APIC BOOY SSDT
> > > > acpimadt0 at acpi0 addt 0xfee0: PC-AT compat
> > > > cpu0 at mainbus0: apid 0 (boot processor)
> > > > cpu0: apic clock running at 200MHz
> > > > cpu at mainbus0: not configured
> > > > cpu at mainbus0: not configured
> > > > cpu at mainbus0: not configured
> > > > ioacpi0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> > > > ioacpi1 at mainbus0: apid 3 pa 0xfec8, version 20, 24 pins
> > > > ioacpi2 at mainbus0: apid 4 pa 0xfec80400, version 20, 24 pins
> > > > acpiprt0 at acpi0: bus 2 (P2P3)
> > > > acpiprt1 at acpi0: bus 3 (P2P4)
> > > > acpiprt2 at acpi0: bus 0 (PCI0)
> > > > acpiprt3 at acpi0: bus 4 (PCIB)
> > > > bios0: ROM list: 0xc/0x8000 0xc8000/0x4000 0xdc000/0x4000!
> > > > pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> > > > pchb0 at pci0 dev 0 function 0 "Intel E7520 Host" rev 0x09
> > > > "Intel E7520 Error Reporting" rev 0x09 at pci0 dev 0 function 1 not
> > > > configured
> > > > ppb0 at pci0 dev 2 function 0 "Intel E7520 PCIE" rev 0x09
> > > > pci1 at ppb0 bus 1
> > > > ppb1 at pci1 dev 0 function 0 "Intel 6700PXH PCIE-PCIX" rev 0x09
> > > > pci2 at ppb1 bus 2
> > > > "Intel IOxAPIC" rev 0x09 at pci1 dev 0 function 1 not configured
> > > > ppb2 at pci1 dev 0 function 2 "Intel 6700PXH PCIE-PCIX" rev 0x09
> > > > pci3 at ppb2 bus 3
> > > > em0 at pci3 dev 3 function 0 "Intel PRO/1000MT (82545CM)" rev 0x04:
> apic
> > > 2
> > > > int1
> > > > 6, address 00:04:23:c4:01:16
> > > > mpi0 at pci3 dev 5 function 0 "Symbios Logic 53c1030" rev 0x07: msi
> > > > scsibus0 at mpi0: 16 targets, initiator 7
> > > > sd0 at scsibus0 targ 1 lun 0: SCSI2
> 0/direct
> > > fixed
> > > > sd0: 34700MB, 512 bytes/sector, 71065600 sectors
> > > > mpi0: timeout
> > > > mpi0: timeout
> > > > mpi0: timeout
> > > > mpi0: timeout
> > > > mpi0: timeout
> > > > mpi0: timeout
> > > > mpi0: phys disk Async at 0 MHz width 8bit offset 0 QAS 0 DT 0 IU 0
> > > > em1 at pci3 dev 6 function 0 "Intel PRO/100MT (82546GB)" rev 0x03:
> apic 2
> > > > int 1
> > > > 6uvm_fault (0xd07f31d8, 0x0, 0, 1) -> e
> > > > fatal page fault (6) in supervisor mode
> > > > trap type 6 code 0 eip 0 cs 50 eflags 10282 cr2 0 cpl 50
> > > > panic: trap type 6, code=0, pc=0
> > > > The operating system has halted
> > > > Please press any key to reboot
> > > > ---
> > > >
> > > > Thanks
> > > >
> > > > On Thu, Nov 29, 2012 at 2:25 PM, Nick Holland
> > > > wrote:
> > > >
> > > > > On 11/29/12
Re: PRIMERGY RX200 S2 installation problems
2012/12/3 Tony Berth : > it is the current one (2012-12-02) Well, this is actual snapshot: > OpenBSD 5.2-current (RAMDISK_CD) #86 Sun Dec 2 13:59:04 MST 2012 -- Michał Markowski
Re: several X servers on one host
On 12/03/12 20:56, Theo de Raadt wrote: >> PS. According to Wikipedia UNIX is a multitasking, _multiuser_ >> computer operating system, so it turns out that the loss of ability >> to run multiple startx/xinit sessions is equivalent to the loss >> of the essential UNIX feature- _multiuser_ support:( > > You have this very wrong. > > The problem is that step-by-step over the last 20 years, X itself > became less and less of a multiuser environment. > > This happened when direct hardware device handling was added to X, a > userland program, to support the retarded PC platform. > > Safety issues were ignored. Multiuser was ignored, too. You are as always accurate, Theo. I apologize... but it is very hard to imagine a modern UNIX without X. PS. X Windows System... X Window_s_ System?.. :( -- Alexei Malinin
Re: PRIMERGY RX200 S2 installation problems
Am Montag, 03. Dezember 2012 17:57 CET, Tony Berth
schrieb:
> it is the current one (2012-12-02)
> > OpenBSD 5.2 (RAMDISK_CD) #287: Wed Aug 1 10:19:00 MDT 2012
> > der...@i386.openbsd.org:/usr/src/sys/sys/arch/i386/compile/RAMDISK_CD
but dmesg says its not so current like you think it is.
Sebastian
>
> Thanks
>
> On Mon, Dec 3, 2012 at 6:52 PM, Kenneth R Westerback > wrote:
>
> > On Mon, Dec 03, 2012 at 06:08:34PM +0200, Tony Berth wrote:
> > > here is the installation dmesg when trying to install the 5.2 i386
> > snapshot:
> >
> > And the installation dmesg from a -current snapshot would be even
> > more useful.
> >
> > Ken
> >
> > >
> > > -
> > > LSI Logic Corp. MPT IME BIOS
> > > Copyright 1995-2005 LSI Logic Corp.
> > > MPTBIOS-IME-5.13.08
> > >
> > > CD-ROM: 9F
> > > Loading /5.2/I386/CDBOOT
> > > probing: pc0 apm pci mem[616K 2046M a20=on]
> > > disk: hd0+* cd0
> > > >> OpenBSD/i386 CDBOOT 3.17
> > > boot>
> > > booting cd0a:/5.2/i386/bsd.rd: 5973772+958284 [52+229744+218028]=0x709d1c
> > > entry point at 0x200128
> > > Copyright (c) 1982, 1986, 1989, 1991, 1993
> > > The Regents of the University of California. All rights reserved.
> > > Copyright (c) 19995-2012 OpenBSD. All rights reserved.
> > > http://www.OpenBSD.org
> > > OpenBSD 5.2 (RAMDISK_CD) #287: Wed Aug 1 10:19:00 MDT 2012
> > > der...@i386.openbsd.org:/usr/src/sys/sys/arch/i386/compile/RAMDISK_CD
> > > cpu0: Intel(R) Xeon(TM) CPU 3.00 GHz ("GenuineIntel" 686-class)
> > > cpu0: FPU, V86, DE, PSE, TSC, MSR, PAE, MCE, CX8, APIC, SEP, MTRR,
> > PGE,MCA,
> > > CMOV, PAT, PSE36, CF
> > >
> > LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM.SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,CNXT-
> > > ID,
> > > CX16,xTPR
> > > real mem = 2146414592 (2046MB)
> > > avail mem = 2183640064 (2006MB)
> > > mainbus0 at root
> > > bios0 at mainbus0: AT/286+ BIOS, date 09/16/85, BIOS32 rev. 0 @ 0xfd418,
> > > SMBIOS
> > > rev. 2.33 @ 0xdc010 (58 entries)
> > > bios0: vendor FSC version "6.8 Rev. R04A5F1.1790" date 09/16/2005
> > > bios0: FUJITSU SIEMENES PRIMERGY RX200S2
> > > acpi0 at bios0: rev 0
> > > acpi0: sleep states S0 S1 S4 S5
> > > acpi0: tables DSDT FACP MCFC SPCR APIC BOOY SSDT
> > > acpimadt0 at acpi0 addt 0xfee0: PC-AT compat
> > > cpu0 at mainbus0: apid 0 (boot processor)
> > > cpu0: apic clock running at 200MHz
> > > cpu at mainbus0: not configured
> > > cpu at mainbus0: not configured
> > > cpu at mainbus0: not configured
> > > ioacpi0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> > > ioacpi1 at mainbus0: apid 3 pa 0xfec8, version 20, 24 pins
> > > ioacpi2 at mainbus0: apid 4 pa 0xfec80400, version 20, 24 pins
> > > acpiprt0 at acpi0: bus 2 (P2P3)
> > > acpiprt1 at acpi0: bus 3 (P2P4)
> > > acpiprt2 at acpi0: bus 0 (PCI0)
> > > acpiprt3 at acpi0: bus 4 (PCIB)
> > > bios0: ROM list: 0xc/0x8000 0xc8000/0x4000 0xdc000/0x4000!
> > > pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> > > pchb0 at pci0 dev 0 function 0 "Intel E7520 Host" rev 0x09
> > > "Intel E7520 Error Reporting" rev 0x09 at pci0 dev 0 function 1 not
> > > configured
> > > ppb0 at pci0 dev 2 function 0 "Intel E7520 PCIE" rev 0x09
> > > pci1 at ppb0 bus 1
> > > ppb1 at pci1 dev 0 function 0 "Intel 6700PXH PCIE-PCIX" rev 0x09
> > > pci2 at ppb1 bus 2
> > > "Intel IOxAPIC" rev 0x09 at pci1 dev 0 function 1 not configured
> > > ppb2 at pci1 dev 0 function 2 "Intel 6700PXH PCIE-PCIX" rev 0x09
> > > pci3 at ppb2 bus 3
> > > em0 at pci3 dev 3 function 0 "Intel PRO/1000MT (82545CM)" rev 0x04: apic
> > 2
> > > int1
> > > 6, address 00:04:23:c4:01:16
> > > mpi0 at pci3 dev 5 function 0 "Symbios Logic 53c1030" rev 0x07: msi
> > > scsibus0 at mpi0: 16 targets, initiator 7
> > > sd0 at scsibus0 targ 1 lun 0: SCSI2 0/direct
> > fixed
> > > sd0: 34700MB, 512 bytes/sector, 71065600 sectors
> > > mpi0: timeout
> > > mpi0: timeout
> > > mpi0: timeout
> > > mpi0: timeout
> > > mpi0: timeout
> > > mpi0: timeout
> > > mpi0: phys disk Async at 0 MHz width 8bit offset 0 QAS 0 DT 0 IU 0
> > > em1 at pci3 dev 6 function 0 "Intel PRO/100MT (82546GB)" rev 0x03: apic 2
> > > int 1
> > > 6uvm_fault (0xd07f31d8, 0x0, 0, 1) -> e
> > > fatal page fault (6) in supervisor mode
> > > trap type 6 code 0 eip 0 cs 50 eflags 10282 cr2 0 cpl 50
> > > panic: trap type 6, code=0, pc=0
> > > The operating system has halted
> > > Please press any key to reboot
> > > ---
> > >
> > > Thanks
> > >
> > > On Thu, Nov 29, 2012 at 2:25 PM, Nick Holland
> > > wrote:
> > >
> > > > On 11/29/12 06:42, Tony Berth wrote:
> > > > > Thanks
> > > > >
> > > > > Both i386 and amd64 fail! But, are that many differences between
> > stable
> > > > and
> > > > > current?
> > > >
> > > > You caught us, nothing has changed in OpenBSD since 1995, we just drink
> > > > beer and increment the version number every six months.
> > > >
> > > >
> > > > The most significant changes tend to take place just AFTER unlocking of
> > > > a new version of OpenBSD -- i.e., BEFORE the CDs ship. So yes,
> > -current
> >
Re: PRIMERGY RX200 S2 installation problems
it is the current one (2012-12-02)
Thanks
On Mon, Dec 3, 2012 at 6:52 PM, Kenneth R Westerback wrote:
> On Mon, Dec 03, 2012 at 06:08:34PM +0200, Tony Berth wrote:
> > here is the installation dmesg when trying to install the 5.2 i386
> snapshot:
>
> And the installation dmesg from a -current snapshot would be even
> more useful.
>
> Ken
>
> >
> > -
> > LSI Logic Corp. MPT IME BIOS
> > Copyright 1995-2005 LSI Logic Corp.
> > MPTBIOS-IME-5.13.08
> >
> > CD-ROM: 9F
> > Loading /5.2/I386/CDBOOT
> > probing: pc0 apm pci mem[616K 2046M a20=on]
> > disk: hd0+* cd0
> > >> OpenBSD/i386 CDBOOT 3.17
> > boot>
> > booting cd0a:/5.2/i386/bsd.rd: 5973772+958284 [52+229744+218028]=0x709d1c
> > entry point at 0x200128
> > Copyright (c) 1982, 1986, 1989, 1991, 1993
> > The Regents of the University of California. All rights reserved.
> > Copyright (c) 19995-2012 OpenBSD. All rights reserved.
> > http://www.OpenBSD.org
> > OpenBSD 5.2 (RAMDISK_CD) #287: Wed Aug 1 10:19:00 MDT 2012
> > der...@i386.openbsd.org:/usr/src/sys/sys/arch/i386/compile/RAMDISK_CD
> > cpu0: Intel(R) Xeon(TM) CPU 3.00 GHz ("GenuineIntel" 686-class)
> > cpu0: FPU, V86, DE, PSE, TSC, MSR, PAE, MCE, CX8, APIC, SEP, MTRR,
> PGE,MCA,
> > CMOV, PAT, PSE36, CF
> >
> LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM.SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,CNXT-
> > ID,
> > CX16,xTPR
> > real mem = 2146414592 (2046MB)
> > avail mem = 2183640064 (2006MB)
> > mainbus0 at root
> > bios0 at mainbus0: AT/286+ BIOS, date 09/16/85, BIOS32 rev. 0 @ 0xfd418,
> > SMBIOS
> > rev. 2.33 @ 0xdc010 (58 entries)
> > bios0: vendor FSC version "6.8 Rev. R04A5F1.1790" date 09/16/2005
> > bios0: FUJITSU SIEMENES PRIMERGY RX200S2
> > acpi0 at bios0: rev 0
> > acpi0: sleep states S0 S1 S4 S5
> > acpi0: tables DSDT FACP MCFC SPCR APIC BOOY SSDT
> > acpimadt0 at acpi0 addt 0xfee0: PC-AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: apic clock running at 200MHz
> > cpu at mainbus0: not configured
> > cpu at mainbus0: not configured
> > cpu at mainbus0: not configured
> > ioacpi0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> > ioacpi1 at mainbus0: apid 3 pa 0xfec8, version 20, 24 pins
> > ioacpi2 at mainbus0: apid 4 pa 0xfec80400, version 20, 24 pins
> > acpiprt0 at acpi0: bus 2 (P2P3)
> > acpiprt1 at acpi0: bus 3 (P2P4)
> > acpiprt2 at acpi0: bus 0 (PCI0)
> > acpiprt3 at acpi0: bus 4 (PCIB)
> > bios0: ROM list: 0xc/0x8000 0xc8000/0x4000 0xdc000/0x4000!
> > pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> > pchb0 at pci0 dev 0 function 0 "Intel E7520 Host" rev 0x09
> > "Intel E7520 Error Reporting" rev 0x09 at pci0 dev 0 function 1 not
> > configured
> > ppb0 at pci0 dev 2 function 0 "Intel E7520 PCIE" rev 0x09
> > pci1 at ppb0 bus 1
> > ppb1 at pci1 dev 0 function 0 "Intel 6700PXH PCIE-PCIX" rev 0x09
> > pci2 at ppb1 bus 2
> > "Intel IOxAPIC" rev 0x09 at pci1 dev 0 function 1 not configured
> > ppb2 at pci1 dev 0 function 2 "Intel 6700PXH PCIE-PCIX" rev 0x09
> > pci3 at ppb2 bus 3
> > em0 at pci3 dev 3 function 0 "Intel PRO/1000MT (82545CM)" rev 0x04: apic
> 2
> > int1
> > 6, address 00:04:23:c4:01:16
> > mpi0 at pci3 dev 5 function 0 "Symbios Logic 53c1030" rev 0x07: msi
> > scsibus0 at mpi0: 16 targets, initiator 7
> > sd0 at scsibus0 targ 1 lun 0: SCSI2 0/direct
> fixed
> > sd0: 34700MB, 512 bytes/sector, 71065600 sectors
> > mpi0: timeout
> > mpi0: timeout
> > mpi0: timeout
> > mpi0: timeout
> > mpi0: timeout
> > mpi0: timeout
> > mpi0: phys disk Async at 0 MHz width 8bit offset 0 QAS 0 DT 0 IU 0
> > em1 at pci3 dev 6 function 0 "Intel PRO/100MT (82546GB)" rev 0x03: apic 2
> > int 1
> > 6uvm_fault (0xd07f31d8, 0x0, 0, 1) -> e
> > fatal page fault (6) in supervisor mode
> > trap type 6 code 0 eip 0 cs 50 eflags 10282 cr2 0 cpl 50
> > panic: trap type 6, code=0, pc=0
> > The operating system has halted
> > Please press any key to reboot
> > ---
> >
> > Thanks
> >
> > On Thu, Nov 29, 2012 at 2:25 PM, Nick Holland
> > wrote:
> >
> > > On 11/29/12 06:42, Tony Berth wrote:
> > > > Thanks
> > > >
> > > > Both i386 and amd64 fail! But, are that many differences between
> stable
> > > and
> > > > current?
> > >
> > > You caught us, nothing has changed in OpenBSD since 1995, we just drink
> > > beer and increment the version number every six months.
> > >
> > >
> > > The most significant changes tend to take place just AFTER unlocking of
> > > a new version of OpenBSD -- i.e., BEFORE the CDs ship. So yes,
> -current
> > > is significantly different than the most recent release.
> > >
> > > Now, step away from the "!" key, and lets see if we can help you help
> us
> > > help you.
> > >
> > > Here's the situation... apparently, no one has been installing OpenBSD
> > > on this particular machine before. Never heard of it myself, whatever
> > > that means. A quick google showed me a lot of PDF files I don't wish
> to
> > > look at, but apparently it is a rack-mount server.
> > >
> > > There's apparently a problem between this machine and
Re: several X servers on one host
> PS. According to Wikipedia UNIX is a multitasking, _multiuser_ > computer operating system, so it turns out that the loss of ability > to run multiple startx/xinit sessions is equivalent to the loss > of the essential UNIX feature- _multiuser_ support:( You have this very wrong. The problem is that step-by-step over the last 20 years, X itself became less and less of a multiuser environment. This happened when direct hardware device handling was added to X, a userland program, to support the retarded PC platform. Safety issues were ignored. Multiuser was ignored, too.
Re: PRIMERGY RX200 S2 installation problems
On Mon, Dec 03, 2012 at 06:08:34PM +0200, Tony Berth wrote:
> here is the installation dmesg when trying to install the 5.2 i386 snapshot:
And the installation dmesg from a -current snapshot would be even
more useful.
Ken
>
> -
> LSI Logic Corp. MPT IME BIOS
> Copyright 1995-2005 LSI Logic Corp.
> MPTBIOS-IME-5.13.08
>
> CD-ROM: 9F
> Loading /5.2/I386/CDBOOT
> probing: pc0 apm pci mem[616K 2046M a20=on]
> disk: hd0+* cd0
> >> OpenBSD/i386 CDBOOT 3.17
> boot>
> booting cd0a:/5.2/i386/bsd.rd: 5973772+958284 [52+229744+218028]=0x709d1c
> entry point at 0x200128
> Copyright (c) 1982, 1986, 1989, 1991, 1993
> The Regents of the University of California. All rights reserved.
> Copyright (c) 19995-2012 OpenBSD. All rights reserved.
> http://www.OpenBSD.org
> OpenBSD 5.2 (RAMDISK_CD) #287: Wed Aug 1 10:19:00 MDT 2012
> der...@i386.openbsd.org:/usr/src/sys/sys/arch/i386/compile/RAMDISK_CD
> cpu0: Intel(R) Xeon(TM) CPU 3.00 GHz ("GenuineIntel" 686-class)
> cpu0: FPU, V86, DE, PSE, TSC, MSR, PAE, MCE, CX8, APIC, SEP, MTRR, PGE,MCA,
> CMOV, PAT, PSE36, CF
> LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM.SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,CNXT-
> ID,
> CX16,xTPR
> real mem = 2146414592 (2046MB)
> avail mem = 2183640064 (2006MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 09/16/85, BIOS32 rev. 0 @ 0xfd418,
> SMBIOS
> rev. 2.33 @ 0xdc010 (58 entries)
> bios0: vendor FSC version "6.8 Rev. R04A5F1.1790" date 09/16/2005
> bios0: FUJITSU SIEMENES PRIMERGY RX200S2
> acpi0 at bios0: rev 0
> acpi0: sleep states S0 S1 S4 S5
> acpi0: tables DSDT FACP MCFC SPCR APIC BOOY SSDT
> acpimadt0 at acpi0 addt 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: apic clock running at 200MHz
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> cpu at mainbus0: not configured
> ioacpi0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> ioacpi1 at mainbus0: apid 3 pa 0xfec8, version 20, 24 pins
> ioacpi2 at mainbus0: apid 4 pa 0xfec80400, version 20, 24 pins
> acpiprt0 at acpi0: bus 2 (P2P3)
> acpiprt1 at acpi0: bus 3 (P2P4)
> acpiprt2 at acpi0: bus 0 (PCI0)
> acpiprt3 at acpi0: bus 4 (PCIB)
> bios0: ROM list: 0xc/0x8000 0xc8000/0x4000 0xdc000/0x4000!
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel E7520 Host" rev 0x09
> "Intel E7520 Error Reporting" rev 0x09 at pci0 dev 0 function 1 not
> configured
> ppb0 at pci0 dev 2 function 0 "Intel E7520 PCIE" rev 0x09
> pci1 at ppb0 bus 1
> ppb1 at pci1 dev 0 function 0 "Intel 6700PXH PCIE-PCIX" rev 0x09
> pci2 at ppb1 bus 2
> "Intel IOxAPIC" rev 0x09 at pci1 dev 0 function 1 not configured
> ppb2 at pci1 dev 0 function 2 "Intel 6700PXH PCIE-PCIX" rev 0x09
> pci3 at ppb2 bus 3
> em0 at pci3 dev 3 function 0 "Intel PRO/1000MT (82545CM)" rev 0x04: apic 2
> int1
> 6, address 00:04:23:c4:01:16
> mpi0 at pci3 dev 5 function 0 "Symbios Logic 53c1030" rev 0x07: msi
> scsibus0 at mpi0: 16 targets, initiator 7
> sd0 at scsibus0 targ 1 lun 0: SCSI2 0/direct fixed
> sd0: 34700MB, 512 bytes/sector, 71065600 sectors
> mpi0: timeout
> mpi0: timeout
> mpi0: timeout
> mpi0: timeout
> mpi0: timeout
> mpi0: timeout
> mpi0: phys disk Async at 0 MHz width 8bit offset 0 QAS 0 DT 0 IU 0
> em1 at pci3 dev 6 function 0 "Intel PRO/100MT (82546GB)" rev 0x03: apic 2
> int 1
> 6uvm_fault (0xd07f31d8, 0x0, 0, 1) -> e
> fatal page fault (6) in supervisor mode
> trap type 6 code 0 eip 0 cs 50 eflags 10282 cr2 0 cpl 50
> panic: trap type 6, code=0, pc=0
> The operating system has halted
> Please press any key to reboot
> ---
>
> Thanks
>
> On Thu, Nov 29, 2012 at 2:25 PM, Nick Holland
> wrote:
>
> > On 11/29/12 06:42, Tony Berth wrote:
> > > Thanks
> > >
> > > Both i386 and amd64 fail! But, are that many differences between stable
> > and
> > > current?
> >
> > You caught us, nothing has changed in OpenBSD since 1995, we just drink
> > beer and increment the version number every six months.
> >
> >
> > The most significant changes tend to take place just AFTER unlocking of
> > a new version of OpenBSD -- i.e., BEFORE the CDs ship. So yes, -current
> > is significantly different than the most recent release.
> >
> > Now, step away from the "!" key, and lets see if we can help you help us
> > help you.
> >
> > Here's the situation... apparently, no one has been installing OpenBSD
> > on this particular machine before. Never heard of it myself, whatever
> > that means. A quick google showed me a lot of PDF files I don't wish to
> > look at, but apparently it is a rack-mount server.
> >
> > There's apparently a problem between this machine and OpenBSD.
> >
> > You have three choices I see:
> > 1) provide one or two of these machines to developers.
> > 2) provide useful information to developers
> > 3) give up, as without either 1 or 2, we aren't going to be able to help
> > you.
> >
> > I'm going to guess you don't have the spare money/machine to provide a
> > few machines to the project.
> >
> > T
Re: several X servers on one host
On 12/03/12 16:29, Laurence Tratt wrote: > On Sun, Dec 02, 2012 at 11:53:44PM +0400, Alexei Malinin wrote: > >> Indeed, I ran two X servers at the same time a long time ago. >> But from time to time I have a need to do so (that is, to run one more X >> session on behalf of another person, without destroyingmy active X >> session)... > > I sometimes have to do this too, and similarly realised that running two X > servers on the same machine was rather difficult to get working. Based on a > program called xsandbox, I created a little script xcage: > > http://tratt.net/laurie/src/xcage/ > > Nested X sessions can be a little buggy -- at least on the machines I've used > them on -- but they're often better than the alternatives (e.g. VNC to > localhost). Nested X sessions via Xnest or Xephyr are useful (but only for single man working on the computer) but they are not of full value (not complete) as startx/xinit sessions (i. e. several men cannot work simultaneously on the computer). PS. According to Wikipedia UNIX is a multitasking, _multiuser_ computer operating system, so it turns out that the loss of ability to run multiple startx/xinit sessions is equivalent to the loss of the essential UNIX feature- _multiuser_ support:( -- Alexei Malinin
Re: PRIMERGY RX200 S2 installation problems
here is the installation dmesg when trying to install the 5.2 i386 snapshot:
-
LSI Logic Corp. MPT IME BIOS
Copyright 1995-2005 LSI Logic Corp.
MPTBIOS-IME-5.13.08
CD-ROM: 9F
Loading /5.2/I386/CDBOOT
probing: pc0 apm pci mem[616K 2046M a20=on]
disk: hd0+* cd0
>> OpenBSD/i386 CDBOOT 3.17
boot>
booting cd0a:/5.2/i386/bsd.rd: 5973772+958284 [52+229744+218028]=0x709d1c
entry point at 0x200128
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 19995-2012 OpenBSD. All rights reserved.
http://www.OpenBSD.org
OpenBSD 5.2 (RAMDISK_CD) #287: Wed Aug 1 10:19:00 MDT 2012
der...@i386.openbsd.org:/usr/src/sys/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel(R) Xeon(TM) CPU 3.00 GHz ("GenuineIntel" 686-class)
cpu0: FPU, V86, DE, PSE, TSC, MSR, PAE, MCE, CX8, APIC, SEP, MTRR, PGE,MCA,
CMOV, PAT, PSE36, CF
LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM.SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,CNXT-
ID,
CX16,xTPR
real mem = 2146414592 (2046MB)
avail mem = 2183640064 (2006MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 09/16/85, BIOS32 rev. 0 @ 0xfd418,
SMBIOS
rev. 2.33 @ 0xdc010 (58 entries)
bios0: vendor FSC version "6.8 Rev. R04A5F1.1790" date 09/16/2005
bios0: FUJITSU SIEMENES PRIMERGY RX200S2
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP MCFC SPCR APIC BOOY SSDT
acpimadt0 at acpi0 addt 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 200MHz
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioacpi0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioacpi1 at mainbus0: apid 3 pa 0xfec8, version 20, 24 pins
ioacpi2 at mainbus0: apid 4 pa 0xfec80400, version 20, 24 pins
acpiprt0 at acpi0: bus 2 (P2P3)
acpiprt1 at acpi0: bus 3 (P2P4)
acpiprt2 at acpi0: bus 0 (PCI0)
acpiprt3 at acpi0: bus 4 (PCIB)
bios0: ROM list: 0xc/0x8000 0xc8000/0x4000 0xdc000/0x4000!
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel E7520 Host" rev 0x09
"Intel E7520 Error Reporting" rev 0x09 at pci0 dev 0 function 1 not
configured
ppb0 at pci0 dev 2 function 0 "Intel E7520 PCIE" rev 0x09
pci1 at ppb0 bus 1
ppb1 at pci1 dev 0 function 0 "Intel 6700PXH PCIE-PCIX" rev 0x09
pci2 at ppb1 bus 2
"Intel IOxAPIC" rev 0x09 at pci1 dev 0 function 1 not configured
ppb2 at pci1 dev 0 function 2 "Intel 6700PXH PCIE-PCIX" rev 0x09
pci3 at ppb2 bus 3
em0 at pci3 dev 3 function 0 "Intel PRO/1000MT (82545CM)" rev 0x04: apic 2
int1
6, address 00:04:23:c4:01:16
mpi0 at pci3 dev 5 function 0 "Symbios Logic 53c1030" rev 0x07: msi
scsibus0 at mpi0: 16 targets, initiator 7
sd0 at scsibus0 targ 1 lun 0: SCSI2 0/direct fixed
sd0: 34700MB, 512 bytes/sector, 71065600 sectors
mpi0: timeout
mpi0: timeout
mpi0: timeout
mpi0: timeout
mpi0: timeout
mpi0: timeout
mpi0: phys disk Async at 0 MHz width 8bit offset 0 QAS 0 DT 0 IU 0
em1 at pci3 dev 6 function 0 "Intel PRO/100MT (82546GB)" rev 0x03: apic 2
int 1
6uvm_fault (0xd07f31d8, 0x0, 0, 1) -> e
fatal page fault (6) in supervisor mode
trap type 6 code 0 eip 0 cs 50 eflags 10282 cr2 0 cpl 50
panic: trap type 6, code=0, pc=0
The operating system has halted
Please press any key to reboot
---
Thanks
On Thu, Nov 29, 2012 at 2:25 PM, Nick Holland
wrote:
> On 11/29/12 06:42, Tony Berth wrote:
> > Thanks
> >
> > Both i386 and amd64 fail! But, are that many differences between stable
> and
> > current?
>
> You caught us, nothing has changed in OpenBSD since 1995, we just drink
> beer and increment the version number every six months.
>
>
> The most significant changes tend to take place just AFTER unlocking of
> a new version of OpenBSD -- i.e., BEFORE the CDs ship. So yes, -current
> is significantly different than the most recent release.
>
> Now, step away from the "!" key, and lets see if we can help you help us
> help you.
>
> Here's the situation... apparently, no one has been installing OpenBSD
> on this particular machine before. Never heard of it myself, whatever
> that means. A quick google showed me a lot of PDF files I don't wish to
> look at, but apparently it is a rack-mount server.
>
> There's apparently a problem between this machine and OpenBSD.
>
> You have three choices I see:
> 1) provide one or two of these machines to developers.
> 2) provide useful information to developers
> 3) give up, as without either 1 or 2, we aren't going to be able to help
> you.
>
> I'm going to guess you don't have the spare money/machine to provide a
> few machines to the project.
>
> The first piece of useful information we could use would be a COMPLETE
> dmesg, collected via a serial port as an install kernel boots. So, grab
> a null modem cable and another computer, and gather that for us...then
> maybe we can give you some suggestions. The dmesg tells us what is in
> your machine, how it is connected, and sometimes, an idea of what went
> wrong.
>
> Nick.
>
>
>
>
>
> > On Thu,
ifOperStatus of em(4) devices always unknown when link is up
Hello,
i've setup a OpenBSD 5.2 (amd64) system using flashrd on a DELL R610 server,
with an Intel PRO/1000 PF (82571EB) dualport fibre optics adapter.
The system also have four broadcom BCM5709 copper interfaces.
I try to monitor the linkstate of these interface using the default
snmpd. The linkstate for the bnx interfaces are always correct ("up"), only
the em interfaces report "unknown" when the link is in state "up"
# ifconfig em0
em0: flags=8843 mtu 1500
lladdr xx:xx:xx:xx:xx:xx
description: Uplink
priority: 0
media: Ethernet 1000baseSX full-duplex
status: active
inet xxx:xxx:xxx:xxx netmask 0xfff8 broadcast xxx:xxx:xxx:xxx
inet6 :::::%em0 pre
# snmpwalk -v 1 -c public localhost IF | grep -i -E '(ifoper|ifdescr)'
IF-MIB::ifDescr.1 = STRING: em0
IF-MIB::ifDescr.2 = STRING: em1
IF-MIB::ifDescr.3 = STRING: enc0
IF-MIB::ifDescr.4 = STRING: lo0
IF-MIB::ifDescr.5 = STRING: bnx0
IF-MIB::ifDescr.6 = STRING: bnx1
IF-MIB::ifDescr.7 = STRING: bnx2
IF-MIB::ifDescr.8 = STRING: bnx3
IF-MIB::ifOperStatus.1 = INTEGER: unknown(4)
IF-MIB::ifOperStatus.2 = INTEGER: down(2)
IF-MIB::ifOperStatus.3 = INTEGER: down(2)
IF-MIB::ifOperStatus.4 = INTEGER: unknown(4)
IF-MIB::ifOperStatus.5 = INTEGER: down(2)
IF-MIB::ifOperStatus.6 = INTEGER: down(2)
IF-MIB::ifOperStatus.7 = INTEGER: up(1)
IF-MIB::ifOperStatus.8 = INTEGER: up(1)
If i shutdown the interface "ifconfig em0 down", it's state is correctly
reported as "down".
I can reproduce this on a vmware virtual machine running a plain OpenBSD 5.2 (
no flashrd setup).
The used intel based adapter is reported as "Intel PRO/1000MT (82545EM)" and
behaves the same
like on my physical server. I also disabled the "connected" state from vmware
side and the
interface reports it's state correctly as "lowerLayerDown(7)" within snmp.
I also tested with 5.1 release on vmware, with the same results.
It looks like a kernel/driver problem for me.
Any help would be appreciated.
Regards,
--
Carsten Schöne
Re: several X servers on one host
On Sun, Dec 02, 2012 at 11:53:44PM +0400, Alexei Malinin wrote: > Indeed, I ran two X servers at the same time a long time ago. > But from time to time I have a need to do so (that is, to run one more X > session on behalf of another person, without destroyingmy active X > session)... I sometimes have to do this too, and similarly realised that running two X servers on the same machine was rather difficult to get working. Based on a program called xsandbox, I created a little script xcage: http://tratt.net/laurie/src/xcage/ Nested X sessions can be a little buggy -- at least on the machines I've used them on -- but they're often better than the alternatives (e.g. VNC to localhost). Laurie -- Personal http://tratt.net/laurie/ The Converge programming language http://convergepl.org/ https://github.com/ltratt http://twitter.com/laurencetratt
Re: Isolating Firefox in a nested X server, and running as a different user
On Sat, Dec 01, 2012 at 08:53:53PM -0800, Robert Connolly wrote: > Hello. > > In an effort to isolate Firefox (or any graphical browser) from my > user account, I have added a 'firefox' user and group, added > 'firefox' user to sshd_config to allow x11 forwarding, and ran the > following commands: > $ Xephyr :1 > $ ssh -Yf firefox@localhost firefox --display :1 > > This can be made nicer with a window manager, but I don't think that > is important here. > > From what I understand, this will prevent Firefox from having access > to my display, such as keystrokes and mouse movement. It will also > prevent Firefox from having access to my go-rwx files, and > modification permissions to my files. This sounds like all of the > isolation I want from Firefox, while still being able to use it. > > I would like to know if I am missing or forgetting anything. I don't > think a chroot for Firefox will gain me much. Other options include > using pf and systrace, but again I don't think this would gain me > much. Newer Xephyr which is not in Xenocara yet offer resizable window. You an also share clipboard with little scripts between X servers. jirib
