Re: Jan 20 snapshot
Built kernel today. Running fine. Must have been something in the 20th snaps. Thanks, T OpenBSD 6.2-current (GENERIC.MP) #0: Sun Jan 21 20:37:23 MST 2018 basepr...@chester.traceyemery.net:/sys/arch/amd64/compile/GENERIC.MP real mem = 16951357440 (16166MB) avail mem = 16430694400 (15669MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbeb88018 (58 entries) bios0: vendor American Megatrends Inc. version "F2i" date 10/07/2014 bios0: Gigabyte Technology Co., Ltd. 970A-DS3P acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET BGRT SSDT IVRS acpi0: wakeup devices SBAZ(S4) PS2K(S3) P0PC(S4) GEC_(S4) UHC1(S4) UHC2(S4) USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) PC02(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 16 (boot processor) cpu0: AMD FX(tm)-8320 Eight-Core Processor, 3516.62 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative acpitimer0: recalibrated TSC frequency 3516148537 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 17 (application processor) cpu1: AMD FX(tm)-8320 Eight-Core Processor, 689.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD FX(tm)-8320 Eight-Core Processor, 688.98 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD FX(tm)-8320 Eight-Core Processor, 689.00 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu3: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu3: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu3: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 20 (application processor) cpu4: AMD FX(tm)-8320 Eight-Core Processor, 688.98 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu4: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu4: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu4: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu4: smt 0, core 4, package 0 cpu5 at mainbus0: apid 21 (application processor) cpu5: AMD FX(tm)-8320 Eight-Core Processor, 688.99 MHz cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MM
Jan 21 snapshot - fixed kernel crash
Hello,
TLDR
I just wanted to send a quick message to say that the Jan 21 snapshot fixed
a kernel issue for me on amd64. The Intel firmware was installed. It also
seems faster than 6.2. Thank you!
Background:
I have a mini PC for testing Elastic. I decided to use it as my desktop.
With 6.1 the video was not supported. With 6.2 it was. However, after a few
minutes in X I started getting regular kernel panics and the box became
unresponsive:
kernel: page fault trap, code=0
Stopped at pmap_flush_cache+0x30: clflush 0(%rdi)
ddb{0}>
Just as I was about to reproduce the issue so I could file a bug report I
remembered to try a snapshot. A few minutes later, I had upgraded and could
no longer reproduce the crash!
Anyway, thanks for all the hard work; each upgrade keeps getting better and
better!
Sincerely,
David
OpenBSD 6.2-current (GENERIC.MP) #382: Sun Jan 21 14:13:38 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 16813948928 (16035MB)
avail mem = 16297398272 (15542MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed9d0 (17 entries)
bios0: vendor American Megatrends Inc. version "P1.30H" date 08/16/2016
bios0: Logic Supply N3160
acpi0 at bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT AAFT MCFG SSDT SSDT SSDT UEFI LPIT
CSRT
acpi0: wakeup devices XHC1(S4) HDEF(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4)
PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PWRB(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU N3160 @ 1.60GHz, 1600.44 MHz
cpu0:
FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu0: 1MB 64b/line 16-way L2 cache
acpitimer0: recalibrated TSC frequency 1599954218 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 80MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) CPU N3160 @ 1.60GHz, 1600.01 MHz
cpu1:
FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu1: 1MB 64b/line 16-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Celeron(R) CPU N3160 @ 1.60GHz, 1600.01 MHz
cpu2:
FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu2: 1MB 64b/line 16-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Celeron(R) CPU N3160 @ 1.60GHz, 1600.01 MHz
cpu3:
FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT
cpu3: 1MB 64b/line 16-way L2 cache
cpu3: smt 0, core 3, package 0
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 115 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus -1 (RP03)
acpiprt4 at acpi0: bus -1 (RP04)
acpiec0 at acpi0: not present
acpicpu0 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(10@1000 mwait.1@0x64), C2(10@500 mwait.1@0x58),
C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: CLK0, resource for CAMD
acpipwrres1 at acpi0: CLK0, resource for CAM1
acpipwrres2 at acpi0: CLK1, resource for CAM2, CAM3
acpipwrres3 at acpi0: USBC, resource for XHC1
"NTN0530" at acpi0 not configured
"BCM2E64" at acpi0 not configured
"BCM4752" at acpi0 not configured
"SMO91D0" at acpi0 not configured
"INT33F7" at acpi0 not configured
"INT33BE" at acpi0 not configured
"INTCF1C" at acpi0 not configured
"MSFT0002" at acpi0 not configured
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
acpivideo0 at acpi0: GFX0
ac
Re: Jan 20 snapshot
Running on this 20180108 kernel now. Here's the dmesg. Seems to be running stable now. Normally, I'd be completely hung at this point. Hopefully, I haven't screwed all of this up with my intoxication, but, I'm too stubborn to not keep a system running! ;) On 1/21/18 4:10 PM, Stuart Henderson wrote: On 2018-01-21, Base Pr1me wrote: I'll try. Not sure I can keep it running long enough to get dmesg lol. Last upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try and get dmesg this week, when I have more time ... Or wait until newer snaps and try again. On Jan 21, 2018 10:37, "Sebastien Marie" wrote: On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: Anyone else's system hanging randomly after upgrading to yesterday's snapshot? This isn't a panic that drops to ddb. It's just freezing with no response to anything. A full dmesg would be welcome, and having the date of your previous version too. thanks. -- Sebastien Marie Moving back to a slightly older kernel and getting dmesg would be useful. If you have an working bsd.rd on the disk you can drop to a shell and mount the filesystems, save a copy of /var/run/dmesg.boot (interested to see any microcode-update related lines from the newer one). Here's a saved snapshot from a couple of weeks ago you could try: https://junkpile.org/bsd.mp.20180108.gz Hopefully that will be stable and you can then send a dmesg showing what's in the system. OpenBSD 6.2-current (GENERIC.MP) #333: Sun Jan 7 09:13:00 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16951357440 (16166MB) avail mem = 16430698496 (15669MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbeb88018 (58 entries) bios0: vendor American Megatrends Inc. version "F2i" date 10/07/2014 bios0: Gigabyte Technology Co., Ltd. 970A-DS3P acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET BGRT SSDT IVRS acpi0: wakeup devices SBAZ(S4) PS2K(S3) P0PC(S4) GEC_(S4) UHC1(S4) UHC2(S4) USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) PC02(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 16 (boot processor) cpu0: AMD FX(tm)-8320 Eight-Core Processor, 3516.57 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative acpitimer0: recalibrated TSC frequency 3516153538 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 17 (application processor) cpu1: AMD FX(tm)-8320 Eight-Core Processor, 3516.14 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD FX(tm)-8320 Eight-Core Processor, 3516.15 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD FX(tm)-8320 Eight-Core Processor, 3516.15 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAI
Re: Jan 20 snapshot
Got it ... I hope ... "Gin"ny and all On 1/21/18 4:10 PM, Stuart Henderson wrote: On 2018-01-21, Base Pr1me wrote: I'll try. Not sure I can keep it running long enough to get dmesg lol. Last upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try and get dmesg this week, when I have more time ... Or wait until newer snaps and try again. On Jan 21, 2018 10:37, "Sebastien Marie" wrote: On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: Anyone else's system hanging randomly after upgrading to yesterday's snapshot? This isn't a panic that drops to ddb. It's just freezing with no response to anything. A full dmesg would be welcome, and having the date of your previous version too. thanks. -- Sebastien Marie Moving back to a slightly older kernel and getting dmesg would be useful. If you have an working bsd.rd on the disk you can drop to a shell and mount the filesystems, save a copy of /var/run/dmesg.boot (interested to see any microcode-update related lines from the newer one). Here's a saved snapshot from a couple of weeks ago you could try: https://junkpile.org/bsd.mp.20180108.gz Hopefully that will be stable and you can then send a dmesg showing what's in the system. OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16951357440 (16166MB) avail mem = 16430669824 (15669MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xbeb88018 (58 entries) bios0: vendor American Megatrends Inc. version "F2i" date 10/07/2014 bios0: Gigabyte Technology Co., Ltd. 970A-DS3P acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG HPET BGRT SSDT IVRS acpi0: wakeup devices SBAZ(S4) PS2K(S3) P0PC(S4) GEC_(S4) UHC1(S4) UHC2(S4) USB3(S4) UHC4(S4) USB5(S4) UHC6(S4) UHC7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) PC02(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 16 (boot processor) cpu0: AMD FX(tm)-8320 Eight-Core Processor, 3516.53 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu0: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu0: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative acpitimer0: recalibrated TSC frequency 3516127432 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 17 (application processor) cpu1: AMD FX(tm)-8320 Eight-Core Processor, 3516.11 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu1: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu1: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 18 (application processor) cpu2: AMD FX(tm)-8320 Eight-Core Processor, 3516.11 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu2: 64KB 64b/line 2-way I-cache, 16KB 64b/line 4-way D-cache, 2MB 64b/line 16-way L2 cache, 8MB 64b/line 64-way L3 cache cpu2: ITLB 48 4KB entries fully associative, 24 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 19 (application processor) cpu3: AMD FX(tm)-8320 Eight-Core Processor, 3516.11 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,NODEID,TBM,TOPEXT,ITSC,BMI1 cpu3: 64KB 64b/line 2-way I-
Re: Jan 20 snapshot
Cool, thanks. I'll check this out this week. Much gratitude. I'm far too 'ginned' up at the moment. ;) On Jan 21, 2018 16:13, "Stuart Henderson" wrote: > On 2018-01-21, Base Pr1me wrote: > > I'll try. Not sure I can keep it running long enough to get dmesg lol. > Last > > upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try > > and get dmesg this week, when I have more time ... Or wait until newer > > snaps and try again. > > > > On Jan 21, 2018 10:37, "Sebastien Marie" wrote: > > > >> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > >> > Anyone else's system hanging randomly after upgrading to yesterday's > >> > snapshot? This isn't a panic that drops to ddb. It's just freezing > with > >> no > >> > response to anything. > >> > >> A full dmesg would be welcome, and having the date of your previous > >> version too. > >> > >> thanks. > >> -- > >> Sebastien Marie > >> > > > > Moving back to a slightly older kernel and getting dmesg would be useful. > > If you have an working bsd.rd on the disk you can drop to a shell and > mount the filesystems, save a copy of /var/run/dmesg.boot (interested > to see any microcode-update related lines from the newer one). > > Here's a saved snapshot from a couple of weeks ago you could try: > https://junkpile.org/bsd.mp.20180108.gz > > Hopefully that will be stable and you can then send a dmesg showing what's > in the system. > > >
Re: Jan 20 snapshot
On 2018-01-21, Base Pr1me wrote: > I'll try. Not sure I can keep it running long enough to get dmesg lol. Last > upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try > and get dmesg this week, when I have more time ... Or wait until newer > snaps and try again. > > On Jan 21, 2018 10:37, "Sebastien Marie" wrote: > >> On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: >> > Anyone else's system hanging randomly after upgrading to yesterday's >> > snapshot? This isn't a panic that drops to ddb. It's just freezing with >> no >> > response to anything. >> >> A full dmesg would be welcome, and having the date of your previous >> version too. >> >> thanks. >> -- >> Sebastien Marie >> > Moving back to a slightly older kernel and getting dmesg would be useful. If you have an working bsd.rd on the disk you can drop to a shell and mount the filesystems, save a copy of /var/run/dmesg.boot (interested to see any microcode-update related lines from the newer one). Here's a saved snapshot from a couple of weeks ago you could try: https://junkpile.org/bsd.mp.20180108.gz Hopefully that will be stable and you can then send a dmesg showing what's in the system.
Re: Jan 20 snapshot
Ok, thanks. On Jan 21, 2018 11:02, "Sebastien Marie" wrote: > On Sun, Jan 21, 2018 at 06:44:56PM +0100, Adam Wolk wrote: > > On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > > > Anyone else's system hanging randomly after upgrading to yesterday's > > > snapshot? This isn't a panic that drops to ddb. It's just freezing > with no > > > response to anything. > > > > I haven't notice any problems with: > > kern.version=OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55 > MST 2018 > > I reported a problem (unexpected reboots) with recent snapshots (and not > reproductible with rebuilt kernel). > > I quickly check with binary diffing for changes and snapshots have > uncommited changes. > > It is why I asked for dmesg and previous working snap. > -- > Sebastien Marie >
Re: Jan 20 snapshot
On Sun, Jan 21, 2018 at 06:44:56PM +0100, Adam Wolk wrote: > On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > > Anyone else's system hanging randomly after upgrading to yesterday's > > snapshot? This isn't a panic that drops to ddb. It's just freezing with no > > response to anything. > > I haven't notice any problems with: > kern.version=OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55 MST > 2018 I reported a problem (unexpected reboots) with recent snapshots (and not reproductible with rebuilt kernel). I quickly check with binary diffing for changes and snapshots have uncommited changes. It is why I asked for dmesg and previous working snap. -- Sebastien Marie
Re: Jan 20 snapshot
Ty. On Jan 21, 2018 10:45, "Adam Wolk" wrote: > On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > > Anyone else's system hanging randomly after upgrading to yesterday's > > snapshot? This isn't a panic that drops to ddb. It's just freezing with > no > > response to anything. > > I haven't notice any problems with: > kern.version=OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55 > MST 2018 > > Regards, > Adam >
Re: Jan 20 snapshot
I'll try. Not sure I can keep it running long enough to get dmesg lol. Last upgrade was ~1 1/2 weeks ago. I know, full of information today. I'll try and get dmesg this week, when I have more time ... Or wait until newer snaps and try again. On Jan 21, 2018 10:37, "Sebastien Marie" wrote: > On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > > Anyone else's system hanging randomly after upgrading to yesterday's > > snapshot? This isn't a panic that drops to ddb. It's just freezing with > no > > response to anything. > > A full dmesg would be welcome, and having the date of your previous > version too. > > thanks. > -- > Sebastien Marie >
Re: Jan 20 snapshot
On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > Anyone else's system hanging randomly after upgrading to yesterday's > snapshot? This isn't a panic that drops to ddb. It's just freezing with no > response to anything. I haven't notice any problems with: kern.version=OpenBSD 6.2-current (GENERIC.MP) #379: Sat Jan 20 14:30:55 MST 2018 Regards, Adam
Re: Jan 20 snapshot
On Sun, Jan 21, 2018 at 09:30:22AM -0700, Base Pr1me wrote: > Anyone else's system hanging randomly after upgrading to yesterday's > snapshot? This isn't a panic that drops to ddb. It's just freezing with no > response to anything. A full dmesg would be welcome, and having the date of your previous version too. thanks. -- Sebastien Marie
Jan 20 snapshot
Anyone else's system hanging randomly after upgrading to yesterday's snapshot? This isn't a panic that drops to ddb. It's just freezing with no response to anything.
Re: issue with xnf running 15th jan snapshot on Xen v. 4.5.1
Hi! I write here for the record so possible arvhive readers know that this thread ended in couple of private emails with developer and he fixed this problem. Short version and what i can narrate is that i used GENERIC i.e. single cpu kernel and my situation was specific to this kernel. Had i used GENERIC.MP i would have not noticed it. Now i happily run OpenBSD on Xen too, .MP or not .MP, thanks! Imre On 2016-01-19 19:48, Mike Belopuhov wrote: Hi, Thanks for taking your time to test and write a report. I've fixed a few issues since then and was going to ask you to test a -current kernel. Could you also please send bug reports like this to bugs@ rather than misc@. Thank you! Cheers, Mike
FYI Intel Bay Trail dmesg -current Jan 18.
Hello ! Maybe someone is interested, a dmesg of a Shuttle XS35V4 (Intel Bay Trail TXE) using the Snapshot from January 18. The machine is fanless and provides UEFI only. The only thing which doesn't work is the by default integrated Wi-Fi card. Weird behaviours : I used the machine before using a HDMI cable and a xorg.conf which is not needed since some Snapshots. If you boot the machine, after some time it switches to VGA only instead of HDMI. Yesterday I installed the Snapshot again on a SSD - using only a VGA cable - and saw a kind of flickering as I booted the installer (installation was not done). If are booth cables VGA and HDMI are connected I don't saw this behaviour (I don't / can't try the display port). Maybe this doesn't happen in a newer Snapshot. Thanks for the good work. $ xrandr -q Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 VIRTUAL1 disconnected (normal left inverted right x axis y axis) HDMI and VGA is connected. bsd.sp : OpenBSD 5.9-beta (GENERIC.MP) #1850: Mon Jan 18 13:38:16 MST 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error f real mem = 7970746368 (7601MB) avail mem = 7724994560 (7367MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebd30 (52 entries) bios0: vendor American Megatrends Inc. version "1.11 x64" date 08/26/2014 bios0: Shuttle Inc. XS35V4 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MCFG LPIT SLIC HPET SSDT SSDT SSDT UEFI acpi0: wakeup devices UAR5(S4) UAR8(S4) XHC1(S4) EHC1(S4) PXSX(S4) PXSX(S4) RLAN(S5) PXSX(S4) PXSX(S4) PWRB(S0) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.37 MHz cpu0: FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu0: 1MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 83MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.00 MHz cpu1: FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu1: 1MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.00 MHz cpu2: FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu2: 1MB 64b/line 16-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 2000.00 MHz cpu3: FPU,VME,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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT cpu3: 1MB 64b/line 16-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 87 pins acpimadt0: bogus nmi for apid 0 acpimadt0: bogus nmi for apid 2 acpimadt0: bogus nmi for apid 4 acpimadt0: bogus nmi for apid 6 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus 2 (RP02) acpiprt3 at acpi0: bus 3 (RP03) acpiprt4 at acpi0: bus 4 (RP04) acpiec0 at acpi0: not present acpicpu0 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(10@1500 mwait.1@0x52), C2(10@500 mwait.1@0x51), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(10@1500 mw
bsd.rd from -current Jan 18 fails to boot on MacBook4.1.
Hello ! Maybe someone is interested. I tried today to boot the Snapshot #1850 from January 18 on a MacBook 4.1 and it fails duribg boot with the following message. The install59.fs file works without problems and is also used before to setup a ThinkPad and a Shuttle XS35V4. Message : probing: pc0 mem[572K 64K 3031M 72K 172K 368K 4M 52K 28K 716K 292K 40K 16K 88K 4M 28K 20K 236K 5M 3M 144K 40K 3072M] disk: hd0 hd1 hd2 >> OpenBSD/amd64 EFIBOOT 3.29 boot> cannot open hd0a:/etc/random.seed: No such file or directory booting hd0a:/5.9/amd64/bsd.rd: 3293880+1404264+2409472+0+569344 [72+368520+240610]=0x7e8e38 entry point at 0xf000160[7205c766, 3404, 24448b12, a680a304] Then the machine reboots. dmesg from 5.8 which is currently running on the machine : OpenBSD 5.8 (GENERIC.MP) #1236: Sun Aug 16 02:31:04 MDT 2015 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 6389174272 (6093MB) avail mem = 6191644672 (5904MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe (42 entries) bios0: vendor Apple Inc. version "MB41.88Z.00C1.B00.0802091535" date 02/09/08 bios0: Apple Inc. MacBook4,1 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices ADP1(S3) LID0(S3) ARPT(S3) GIGE(S3) UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) UHC5(S3) EHC1(S3) EHC2(S3) EC__(S3) 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: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz, 1197.19 MHz cpu0: FPU,VME,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,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu0: 3MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2.1.3, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz, 1197.00 MHz cpu1: FPU,VME,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,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu1: 3MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf000, bus 0-255 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP05) acpiprt2 at acpi0: bus 3 (RP06) acpiprt3 at acpi0: bus 4 (PCIB) acpicpu0 at acpi0: !C3(100@57 mwait.3@0x31), !C2(500@1 mwait@0x10), C1(1000@1 mwait), PSS acpicpu1 at acpi0: !C3(100@57 mwait.3@0x31), !C2(500@1 mwait@0x10), C1(1000@1 mwait), PSS acpiac0 at acpi0: AC unit online acpibtn0 at acpi0: LID0 acpibtn1 at acpi0: PWRB acpibtn2 at acpi0: SLPB acpibat0 at acpi0: BAT0 not present acpivideo0 at acpi0: GFX0 cpu0: Enhanced SpeedStep 1197 MHz: speeds: 2400, 2200, 2000, 1800, 1600, 1400, 1200, 800 MHz memory map conflict 0xf00f8000/0x1000 memory map conflict 0xfed1c000/0x4000 memory map conflict 0xfffa/0x3 pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel GM965 Host" rev 0x03 vga1 at pci0 dev 2 function 0 "Intel GM965 Video" rev 0x03 intagp0 at vga1 agp0 at intagp0: aperture at 0xc000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1280x800 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel GM965 Video" rev 0x03 at pci0 dev 2 function 1 not configured uhci0 at pci0 dev 26 function 0 "Intel 82801H USB" rev 0x03: apic 1 int 20 uhci1 at pci0 dev 26 function 1 "Intel 82801H USB" rev 0x03: apic 1 int 16 ehci0 at pci0 dev 26 function 7 "Intel 82801H USB" rev 0x03: apic 1 int 21 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 82801H HD Audio" rev 0x03: msi azalia0: codecs: Realtek ALC885 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 82801H PCIE" rev 0x03: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 4 "Intel 82801H PCIE" rev 0x03: msi pci2 at ppb1 bus 2 "Broadcom BCM4321" rev 0x03 at pci2 dev 0 function 0 not configured ppb2 at pci0 dev 28 function 5 "Intel 82801H PCIE" rev 0x03: msi pci3 at ppb2 bus 3 mskc0 at pci3 dev 0 function 0 "Marvell Yukon 88E8058" rev 0x13, Yukon-2 EC Ultra rev. B0 (0x3): apic 1 int 17 msk0 at mskc0 port A: address 00:1e:c2:1d:d9:4d eephy0 at msk0 phy 0: 88E1149 Gigabit PHY, rev. 1 uhci2 at pci0 dev 29 function 0 "Intel 82801H USB" rev 0x03: apic 1 int 16 uhci3 at pci0 dev 29 function 1 "Intel 82801H USB" rev 0x03: apic 1 int 18 uhci4 at pci0 dev 29 function 2 "Intel 82801H USB" rev 0x03: ap
Re: issue with xnf running 15th jan snapshot on Xen v. 4.5.1
Hi, Thanks for taking your time to test and write a report. I've fixed a few issues since then and was going to ask you to test a -current kernel. Could you also please send bug reports like this to bugs@ rather than misc@. Thank you! Cheers, Mike On Sat, Jan 16, 2016 at 20:56 +0200, Imre Oolberg wrote: > Hi! > > I read a news today about Xen being enabled and tried it out with the Jan > 15th snapshot > > SHA256 (install59.iso) = > 8d16aeb686a1dcc3ce6e8c5192f8708d3878f7690429c843176c5e755386e4f9 > > on Xen v. 4.5.1 compiled from Xen sources on Debian v. 8 Jessie running on > an ordinary amd64 Intel platform. (Actually i am using this very Xen > platform to run my workstation as another virtual guest, so platform itselt > is running solid.) > > I booted it with > > # cat openbsd.cfg > builder = "hvm" > name = "openbsd" > memory = "512" > vcpus = 1 > vif = [ 'mac=00:16:3e:79:22:22,bridge=xenbr0' ] > disk = [ 'phy:/dev/vg_data_wd_1tb/openbsd,hda,w', > 'file:/tmp/install59.iso-20160115-ss.iso,hdd:cdrom,r'] > > boot="dc" > vnc=1 > > then connected with VNC and installed OpenBSD S.S. > > It boots afterwards ok and when configuring xnf0 network device with > ifconfig xnf0 192.168.10.128 (or with dhclient) i can ping it from outside > and it seems to work forever. Also i can see other lan packets passing by > xnf0 with tcpdump. But when i connect from outside say with ssh client then > it hangs (i.e. cant enter anything from vnc window, created simple cronjob > within OpenBSD and i see it stops updateing log file etc). While connecting > i see this traffic on dom0 > > root@moraal-dom0:/etc/xen# tcpdump -ni vif43.0 host 192.168.10.128 > > 19:55:05.985258 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [S], seq > 3673277459, win 29200, options [mss 1460,sackOK,TS val 40346540 ecr > 0,nop,wscale 7], length 0 > 19:55:05.985611 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [S.], seq > 3141065115, ack 3673277460, win 16384, options [mss > 1460,nop,nop,sackOK,nop,wscale 3,nop,nop,TS val 345100460 ecr 40346540], > length 0 > 19:55:05.986017 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [.], ack > 1, win 229, options [nop,nop,TS val 40346540 ecr 345100460], length 0 > 19:55:05.987116 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq > 1:33, ack 1, win 229, options [nop,nop,TS val 40346541 ecr 345100460], > length 32 > 19:55:06.012874 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [P.], seq > 1:22, ack 33, win 2168, options [nop,nop,TS val 345100460 ecr 40346541], > length 21 > 19:55:06.013151 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [.], ack > 22, win 229, options [nop,nop,TS val 40346547 ecr 345100460], length 0 > 19:55:06.022554 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [.], seq > 33:1481, ack 22, win 229, options [nop,nop,TS val 40346549 ecr 345100460], > length 1448 > 19:55:06.022562 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq > 1481:2001, ack 22, win 229, options [nop,nop,TS val 40346549 ecr 345100460], > length 520 > 19:55:06.023068 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [.], ack > 2001, win 1926, options [nop,nop,TS val 345100460 ecr 40346549], length 0 > 19:55:06.023416 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [P.], seq > 22:998, ack 2001, win 1926, options [nop,nop,TS val 345100460 ecr 40346549], > length 976 > 19:55:06.026537 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq > 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346550 ecr > 345100460], length 48 > 19:55:06.226645 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq > 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346601 ecr > 345100460], length 48 > 19:55:06.430626 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq > 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346652 ecr > 345100460], length 48 > 19:55:06.838658 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq > 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346754 ecr > 345100460], length 48 > 19:55:07.654663 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq > 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346958 ecr > 345100460], length 48 > 19:55:09.290635 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq > 2001:2049, ack 998, win 244, options [nop,nop,TS val 40347367 ecr > 345100460], length 48 > 19:55:12.558753 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq > 2001:2049, ack 998, win 244, options [nop,nop,TS val 40348184 ecr > 345100460], length 48 > 19:55:19.102779 IP 192.168.10.10.33616 > 192.168.
issue with xnf running 15th jan snapshot on Xen v. 4.5.1
Hi! I read a news today about Xen being enabled and tried it out with the Jan 15th snapshot SHA256 (install59.iso) = 8d16aeb686a1dcc3ce6e8c5192f8708d3878f7690429c843176c5e755386e4f9 on Xen v. 4.5.1 compiled from Xen sources on Debian v. 8 Jessie running on an ordinary amd64 Intel platform. (Actually i am using this very Xen platform to run my workstation as another virtual guest, so platform itselt is running solid.) I booted it with # cat openbsd.cfg builder = "hvm" name = "openbsd" memory = "512" vcpus = 1 vif = [ 'mac=00:16:3e:79:22:22,bridge=xenbr0' ] disk = [ 'phy:/dev/vg_data_wd_1tb/openbsd,hda,w', 'file:/tmp/install59.iso-20160115-ss.iso,hdd:cdrom,r'] boot="dc" vnc=1 then connected with VNC and installed OpenBSD S.S. It boots afterwards ok and when configuring xnf0 network device with ifconfig xnf0 192.168.10.128 (or with dhclient) i can ping it from outside and it seems to work forever. Also i can see other lan packets passing by xnf0 with tcpdump. But when i connect from outside say with ssh client then it hangs (i.e. cant enter anything from vnc window, created simple cronjob within OpenBSD and i see it stops updateing log file etc). While connecting i see this traffic on dom0 root@moraal-dom0:/etc/xen# tcpdump -ni vif43.0 host 192.168.10.128 19:55:05.985258 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [S], seq 3673277459, win 29200, options [mss 1460,sackOK,TS val 40346540 ecr 0,nop,wscale 7], length 0 19:55:05.985611 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [S.], seq 3141065115, ack 3673277460, win 16384, options [mss 1460,nop,nop,sackOK,nop,wscale 3,nop,nop,TS val 345100460 ecr 40346540], length 0 19:55:05.986017 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [.], ack 1, win 229, options [nop,nop,TS val 40346540 ecr 345100460], length 0 19:55:05.987116 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 1:33, ack 1, win 229, options [nop,nop,TS val 40346541 ecr 345100460], length 32 19:55:06.012874 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [P.], seq 1:22, ack 33, win 2168, options [nop,nop,TS val 345100460 ecr 40346541], length 21 19:55:06.013151 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [.], ack 22, win 229, options [nop,nop,TS val 40346547 ecr 345100460], length 0 19:55:06.022554 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [.], seq 33:1481, ack 22, win 229, options [nop,nop,TS val 40346549 ecr 345100460], length 1448 19:55:06.022562 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 1481:2001, ack 22, win 229, options [nop,nop,TS val 40346549 ecr 345100460], length 520 19:55:06.023068 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [.], ack 2001, win 1926, options [nop,nop,TS val 345100460 ecr 40346549], length 0 19:55:06.023416 IP 192.168.10.128.22 > 192.168.10.10.33616: Flags [P.], seq 22:998, ack 2001, win 1926, options [nop,nop,TS val 345100460 ecr 40346549], length 976 19:55:06.026537 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346550 ecr 345100460], length 48 19:55:06.226645 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346601 ecr 345100460], length 48 19:55:06.430626 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346652 ecr 345100460], length 48 19:55:06.838658 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346754 ecr 345100460], length 48 19:55:07.654663 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40346958 ecr 345100460], length 48 19:55:09.290635 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40347367 ecr 345100460], length 48 19:55:12.558753 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40348184 ecr 345100460], length 48 19:55:19.102779 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40349820 ecr 345100460], length 48 19:55:32.174732 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40353088 ecr 345100460], length 48 19:55:58.350805 IP 192.168.10.10.33616 > 192.168.10.128.22: Flags [P.], seq 2001:2049, ack 998, win 244, options [nop,nop,TS val 40359632 ecr 345100460], length 48 . Xen logs dont say much, what i can see approx. 1 minute after hang is guest rx stalled [1897100.139144] vif vif-43-0 vif43.0: Guest Rx ready ... [1897216.889975] vif vif-43-0 vif43.0: Guest Rx stalled I am using Open vSwitch on Xen dom0 with qu
Error in package courier-imap-4.16.2 current Jan 1 amd64
Hello I am not sure if this is the correct list, but... I recently installed courier from packages. After installing courier-imap; I tried to start it with "rcctl start courier_imap", and it seemed to hang. So, I tried running /usr/local/libexec/imapd.rc directly, and saw an endless loop of "-". Eventually, found in /usr/local/bin/makedat, near the end, it had: get_access | docidr | yes - "$tmpfile" "$dstfile" || exit 1 I was confused by the "yes"; looked up the man page, and saw it was the offending command. It seems, the line should be: get_access | docidr | /usr/local/libexec/makedatprog - "$tmpfile" "$dstfile" || exit 1 or something like that. I don't really know exactly "how" to submit a diff (I was barely able to discover the problem); but I wanted to point this out. Thanks Ted
Re: ntpd switching between synced and unsynced since snap from 22nd jan
Markus Lude wrote: > since updating to the latest snapshot on sparc64 from 22nd january ntpd > switches back and forth between synced and unsynced clock every few > minutes. Does anyone notice similar behavior? Yes, I see the same on -current (amd64, sparc64). -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: ntpd switching between synced and unsynced since snap from 22nd jan
On Tue, 28 Jan 2014 23:32:30 +0100, Markus Lude wrote: > Hello, > > since updating to the latest snapshot on sparc64 from 22nd january > ntpd switches back and forth between synced and unsynced clock every > few minutes. Does anyone notice similar behavior? I have the same on amd64, but it appears only since the snapshot from 24th. > my ntpd.conf: > servers de.pool.ntp.org > > Regards, > Markus > -- Vigdis
ntpd switching between synced and unsynced since snap from 22nd jan
Hello, since updating to the latest snapshot on sparc64 from 22nd january ntpd switches back and forth between synced and unsynced clock every few minutes. Does anyone notice similar behavior? my ntpd.conf: servers de.pool.ntp.org Regards, Markus
Re: npppd radius on current jan 21
On Wed, 30 Jan 2013 12:07:05 +0100 mxb wrote: > Yasuoka forgot to commit his fix. > I have it working. Oops, I forgot about that fix... I've commited. Also here is the diff. Thanks, Index: npppd_auth.c === RCS file: /cvs/src/usr.sbin/npppd/npppd/npppd_auth.c,v retrieving revision 1.11 retrieving revision 1.12 diff -u -p -r1.11 -r1.12 --- npppd_auth.c22 Sep 2012 20:22:48 - 1.11 +++ npppd_auth.c 31 Jan 2013 09:44:21 - 1.12 @@ -1,4 +1,4 @@ -/* $OpenBSD: npppd_auth.c,v 1.11 2012/09/22 20:22:48 espie Exp $ */ +/* $OpenBSD: npppd_auth.c,v 1.12 2013/01/31 09:44:21 yasuoka Exp $ */ /*- * Copyright (c) 2009 Internet Initiative Japan Inc. @@ -26,7 +26,7 @@ * SUCH DAMAGE. */ /**@file authentication realm */ -/* $Id: npppd_auth.c,v 1.11 2012/09/22 20:22:48 espie Exp $ */ +/* $Id: npppd_auth.c,v 1.12 2013/01/31 09:44:21 yasuoka Exp $ */ #include #include #include @@ -561,6 +561,10 @@ npppd_auth_radius_reload(npppd_auth_base break; memcpy(&rad->server[i].peer, &server->address, server->address.ss_len); + if (((struct sockaddr_in *)&rad->server[i].peer)->sin_port + == 0) + ((struct sockaddr_in *)&rad->server[i].peer)->sin_port + = htons(DEFAULT_RADIUS_AUTH_PORT); strlcpy(rad->server[i].secret, server->secret, sizeof(rad->server[i].secret)); rad->server[i].enabled = 1; @@ -578,6 +582,10 @@ npppd_auth_radius_reload(npppd_auth_base break; memcpy(&rad->server[i].peer, &server->address, server->address.ss_len); + if (((struct sockaddr_in *)&rad->server[i].peer)->sin_port + == 0) + ((struct sockaddr_in *)&rad->server[i].peer)->sin_port + = htons(DEFAULT_RADIUS_ACCT_PORT); strlcpy(rad->server[i].secret, server->secret, sizeof(rad->server[i].secret)); rad->server[i].enabled = 1; Index: parse.y === RCS file: /cvs/src/usr.sbin/npppd/npppd/parse.y,v retrieving revision 1.3 retrieving revision 1.4 diff -u -p -r1.3 -r1.4 --- parse.y 13 Nov 2012 17:10:40 - 1.3 +++ parse.y 31 Jan 2013 09:44:21 - 1.4 @@ -1,4 +1,4 @@ -/* $OpenBSD: parse.y,v 1.3 2012/11/13 17:10:40 yasuoka Exp $ */ +/* $OpenBSD: parse.y,v 1.4 2013/01/31 09:44:21 yasuoka Exp $ */ /* * Copyright (c) 2002, 2003, 2004 Henning Brauer @@ -677,7 +677,8 @@ radopt : ADDRESS address optport SECRET YYERROR; } n->address = $2; - ((struct sockaddr_in *)&n->address)->sin_port = $3; + ((struct sockaddr_in *)&n->address)->sin_port = + htons($3); n->secret = $5; TAILQ_INSERT_TAIL(&curr_radconf->servers, n, entry); }
Re: npppd radius on current jan 21
Yasuoka forgot to commit his fix.
I have it working.
//maxim
On 30 jan 2013, at 11:54, Robert Blacquiere wrote:
> Hi,
>
> I run in to a issue using npppd with radius. It look to me the parsing
> of radius port info is not working.
>
> I have: authentication section:
>
> authentication RADIUS type radius {
> authentication-server {
> address 192.168.0.1 port 1812 secret "hogehoge"
> }
> accounting-server {
> address 192.168.0.1 port 1813 secret "hogehoge"
> }
> }
>
> If i start npppd and try to authenticate is starts communicating with
> the radius server 192.168.0.1 on port 5127.
> If i change port number to 1645 (old radius) i get 27910 ...
>
> It really looks like there is a bug of memory corruption. Also i tried
> for fun port 1 and got port 256 in tcpdump.
>
> Also if
> address 192.168.0.1 secret "hogehoge"
> is used it completely does not talk to the radius server and in
> /var/log/daemon you get a message like
> npppd[]: connect() failed in radius_prepare_socket: Can't assign requested
> address
>
> Authenticating with localfile works fine and is tested.
>
> I have looked at parse.y and serveral other items in
> /usr/src/usr.sbin/npppd/npppd but my C is not up to it yet :(
>
> Can someone point me in direction to solve this.
>
> Note: It was working with the 5.1 release manual build and old
> config style.
>
> Regards
>
> Robert
npppd radius on current jan 21
Hi,
I run in to a issue using npppd with radius. It look to me the parsing
of radius port info is not working.
I have: authentication section:
authentication RADIUS type radius {
authentication-server {
address 192.168.0.1 port 1812 secret "hogehoge"
}
accounting-server {
address 192.168.0.1 port 1813 secret "hogehoge"
}
}
If i start npppd and try to authenticate is starts communicating with
the radius server 192.168.0.1 on port 5127.
If i change port number to 1645 (old radius) i get 27910 ...
It really looks like there is a bug of memory corruption. Also i tried
for fun port 1 and got port 256 in tcpdump.
Also if
address 192.168.0.1 secret "hogehoge"
is used it completely does not talk to the radius server and in
/var/log/daemon you get a message like
npppd[]: connect() failed in radius_prepare_socket: Can't assign requested
address
Authenticating with localfile works fine and is tested.
I have looked at parse.y and serveral other items in
/usr/src/usr.sbin/npppd/npppd but my C is not up to it yet :(
Can someone point me in direction to solve this.
Note: It was working with the 5.1 release manual build and old
config style.
Regards
Robert
Re: Jan 4, 2013 snapshot fails with DHCP
- Original Message - | On Fri, Jan 04, 2013 at 02:10:02PM -0800, James A. Peltier wrote: | > - Original Message - | > | On Jan 04 12:05:53, jpelt...@sfu.ca wrote: | > | > I just tried to use the latest amd64 snapshot to prepare for an | > | > upgrade to our firewall. We use DHCP during initial | > | > installation | > | > to PXE boot and perform the install at which point we configure | > | > through site52.tgz. However, during installation and after | > | > boot | > | > DHCP reports the following error | > | > | > | > Cannot lstat() '/var/db/dhclient.leases.bge0': No such file | > | > or | > | > directory | > | > | > | > it does this for all interfaces and DHCP fails to configure the | > | > interface. This does not happen with 5.2-RELEASE. | > | | > | I've had the same problem with this snapshot. | > | Simply escaping to shell and doing | > | | > | > /var/db/dhclient.leases.bge0 | > | dhclient bge0 | > | | > | solved that. | > | > Yes, I am aware of that, but it doesn't work by default and that | > doesn't help if you reboot and you are not at the console. It's a | > bug and so I am reporting it. ;) | | It was fixed a day or so ago, so newer snaps should not have the | problem. | | Ken | Thanks! I couldn't find the commit in source-changes so I wasn't sure it was fixed. -- James A. Peltier Manager, IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpelt...@sfu.ca Website : http://www.sfu.ca/itservices http://blogs.sfu.ca/people/jpeltier "The smartest people are constantly revising their understanding, reconsidering a problem they thought they’d already solved. They’re open to new points of view, new information, new ideas, contradictions, and challenges to their own way of thinking." - Jeff Bezos
Re: Jan 4, 2013 snapshot fails with DHCP
On Fri, Jan 04, 2013 at 02:10:02PM -0800, James A. Peltier wrote: > - Original Message - > | On Jan 04 12:05:53, jpelt...@sfu.ca wrote: > | > I just tried to use the latest amd64 snapshot to prepare for an > | > upgrade to our firewall. We use DHCP during initial installation > | > to PXE boot and perform the install at which point we configure > | > through site52.tgz. However, during installation and after boot > | > DHCP reports the following error > | > > | > Cannot lstat() '/var/db/dhclient.leases.bge0': No such file or > | > directory > | > > | > it does this for all interfaces and DHCP fails to configure the > | > interface. This does not happen with 5.2-RELEASE. > | > | I've had the same problem with this snapshot. > | Simply escaping to shell and doing > | > | > /var/db/dhclient.leases.bge0 > | dhclient bge0 > | > | solved that. > > Yes, I am aware of that, but it doesn't work by default and that doesn't help > if you reboot and you are not at the console. It's a bug and so I am > reporting it. ;) It was fixed a day or so ago, so newer snaps should not have the problem. Ken > > -- > James A. Peltier > Manager, IT Services - Research Computing Group > Simon Fraser University - Burnaby Campus > Phone : 778-782-6573 > Fax : 778-782-3045 > E-Mail : jpelt...@sfu.ca > Website : http://www.sfu.ca/itservices > http://blogs.sfu.ca/people/jpeltier > > "The smartest people are constantly revising their understanding, > reconsidering a problem they thought they???d already solved. They???re open > to new points of view, new information, new ideas, contradictions, and > challenges to their own way of thinking." - Jeff Bezos
Re: Jan 4, 2013 snapshot fails with DHCP
- Original Message - | On Jan 04 12:05:53, jpelt...@sfu.ca wrote: | > I just tried to use the latest amd64 snapshot to prepare for an | > upgrade to our firewall. We use DHCP during initial installation | > to PXE boot and perform the install at which point we configure | > through site52.tgz. However, during installation and after boot | > DHCP reports the following error | > | > Cannot lstat() '/var/db/dhclient.leases.bge0': No such file or | > directory | > | > it does this for all interfaces and DHCP fails to configure the | > interface. This does not happen with 5.2-RELEASE. | | I've had the same problem with this snapshot. | Simply escaping to shell and doing | | > /var/db/dhclient.leases.bge0 | dhclient bge0 | | solved that. Yes, I am aware of that, but it doesn't work by default and that doesn't help if you reboot and you are not at the console. It's a bug and so I am reporting it. ;) -- James A. Peltier Manager, IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpelt...@sfu.ca Website : http://www.sfu.ca/itservices http://blogs.sfu.ca/people/jpeltier "The smartest people are constantly revising their understanding, reconsidering a problem they thought they’d already solved. They’re open to new points of view, new information, new ideas, contradictions, and challenges to their own way of thinking." - Jeff Bezos
Re: Jan 4, 2013 snapshot fails with DHCP
On Jan 04 12:05:53, jpelt...@sfu.ca wrote: > I just tried to use the latest amd64 snapshot to prepare for an upgrade to > our firewall. We use DHCP during initial installation to PXE boot and > perform the install at which point we configure through site52.tgz. However, > during installation and after boot DHCP reports the following error > > Cannot lstat() '/var/db/dhclient.leases.bge0': No such file or directory > > it does this for all interfaces and DHCP fails to configure the interface. > This does not happen with 5.2-RELEASE. I've had the same problem with this snapshot. Simply escaping to shell and doing > /var/db/dhclient.leases.bge0 dhclient bge0 solved that.
Jan 4, 2013 snapshot fails with DHCP
I just tried to use the latest amd64 snapshot to prepare for an upgrade to our firewall. We use DHCP during initial installation to PXE boot and perform the install at which point we configure through site52.tgz. However, during installation and after boot DHCP reports the following error Cannot lstat() '/var/db/dhclient.leases.bge0': No such file or directory it does this for all interfaces and DHCP fails to configure the interface. This does not happen with 5.2-RELEASE. -- James A. Peltier Manager, IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpelt...@sfu.ca Website : http://www.sfu.ca/itservices http://blogs.sfu.ca/people/jpeltier "The smartest people are constantly revising their understanding, reconsidering a problem they thought they’d already solved. They’re open to new points of view, new information, new ideas, contradictions, and challenges to their own way of thinking." - Jeff Bezos
Re: openbsd.cs.fau.de downtime on Jan 14th
Hi, On Wed, Jan 11, 2012 at 12:27:56PM +0100, Simon Kuhnle wrote: > openbsd.cs.fau.de will be down on January 14th, > from 08:00 to approximately 12:00 o'clock > due to yearly power system maintenance works. Same problem I had last year: the RAID controller forgot his setup again and now I can't convince it to boot the system again... I could do a fresh install and sync again, but that controller will still continue to suck... I talked to grunk@, who has a complete SAS-kit for this box, including a new RAID controller and HDs. The other alternative is that I could bum a completely different server, which would suffice, too, but I need to ask some people. Anyway, openbsd.cs.fau.de will be down for at least 14 days, either until grunk visits Erlangen or I get the OK to pick up the new box. I'm sorry if this causes any inconvenience and I hope to bring back the mirror as soon as possible. Please remove the mirror (at least for the time being). Regards, Simon
Ocean freight from China ,Jan 2012
HiMuhammad IMRAN,Happy new year ,my dear friend. Hope we have good luck and close relationship in this nice year. We update O/F to your side, share it with you as normal. By the way, many carrier cut some vessels before our Chinese New year holiday, any accurate info, contact us any time. POD POL Carrier 20GP 40GP 40HQ LCL<3 CBM T/T Validity SURABAYA DALIAN APL 460 670 670 29 17 25TH,JAN TIANJIN PAN 380 650 650 17 16 QINGDAO SINO 355 620 620 19 13 LIANYUNGANG MCC 420 760 760 26 15 SHANGHAI MCC 310 620 620 18 13 NINGBO YML 310 630 630 15 11 XIAMEN APL 320 520 520 17 13 FUZHOU APL 320 520 520 26 13 SHANTOU CSCL 430 860 860 29 13 GUANGZHOU HANJIN 380 730 750 9 7 FOSHAN/SHUNDE ZIM 410 760 760 17 8 JIANGMEN CSCL 460 820 820 17 8 SHENZHEN OOCL 310 630 630 4 5 ZHUHAI WHL 440 820 820 26 10 Ben shi (MR) Overseas dept Shanghai Harvest International Logistics Co., Ltd Tel: 0086-21-63249293*803 Fax: 0086-21-63244312 ATT: sw...@harvest-log.comSkype: harvestlog1 Logis Website: www.harvest-log.com Trade Website: www.harvest-log.com/soupo Headoffice Address: Room 2108 ,Fude building ,No.,1688, North Sichuan Road,Hongkou District#,Shanghai, China we have 12 offices in Chinese mainland.they can help to handle local shipments.
Re: Jan
that is sage advice for any of us. I, myself got more than a little help here and got some good suggestions (including some hardware I forgot about). I think next month, I will get a framegrabber device with built-in ethernet port and can also manage BIOS and PCU tasks). reading never hurts and it is never a dumb thing to ask questions, especially if you are getting confused with some of the more technical prose that can populate a man page. :) -eric On Dec 11, 2011, at 11:26 PM, Zeb Packard wrote: > John Tate, > > Consider living a life of service, instead of complaining that the > list has not helped you enough, try to figure out what you can do to > better serve the list. So, work more before hitting the list, don't > panic, give it a day or two. Read the archives and relevant man pages > always, then if necessary make your question to the list as concise > and accurate as possible, for people who might have the same problem > in the future. > > Zeb
Re: Jan
John Tate, Consider living a life of service, instead of complaining that the list has not helped you enough, try to figure out what you can do to better serve the list. So, work more before hitting the list, don't panic, give it a day or two. Read the archives and relevant man pages always, then if necessary make your question to the list as concise and accurate as possible, for people who might have the same problem in the future. Zeb
Re: Jan
I guess you will have to learn the hardest and best way then. On your own John Tate wrote: > I will also add that if I am asking stupid questions then by axiom (look it > up in a dictionary) I AM SAYING I AM LEARNING. You tool! > > On Mon, Dec 12, 2011 at 9:17 AM, John Tate wrote: > > >> I never claimed to be an OpenBSD guru. Ever. I am an OpenBSD n00b. Here, >> I'll put this on the list. >> >> I am John Norman Tate born September 1987 to two loving parents and the >> only part of OpenBSD I think I am good with is using it in accordance to >> the manuals when I read them properly. I also understand the security >> principles pretty well, I've read Hacking: The Art of Exploitation and >> understood it's content. I trust OpenBSD like a man of faith trusts his >> religions guidance. I think that pisses you off, but you've imagined >> everything else. I keep saying: I am learning, not learned. You're just >> trying to assasinate my character by making arbitrary claims you hope >> others will not check! It will not work. >> -- >> www.johntate.org
Re: Jan
On Mon, 12 Dec 2011 10:54:36 +1100, richo wrote: Quoting the current resident full-of-himself little shit. I have a filter that sends stuff from him to /dev/null but he keeps getting answers that raise his google rating because you all go on quoting him. He is an oxygen thief - don't give him any more, please. Zero replies will do the best job. Thanks, *** NOTE *** Please DO NOT CC me. I subscribed to the list. Mail to the sender address that does not originate at the list server is tarpitted. The reply-to: address is provided for those who feel compelled to reply off list. Thankyou. Rod/ --- This life is not the real thing. It is not even in Beta. If it was, then OpenBSD would already have a man page for it.
Re: Jan
>> On Mon, Dec 12, 2011 at 9:17 AM, John Tate wrote: >>> I never claimed to be an OpenBSD guru. Ever. I am an OpenBSD n00b. Here, >>> I'll put this on the list. >>> ^^ On 12/12/11 09:21 +1100, John Tate wrote: >Whoops, I hate gmail sometimes. That was for Jan > orly? I fixed your top post. Again. Please stop making noise, your semi-legitimate technical if poorly thought out question threads blowing up is one thing, but this and the narcisism thread are purely masturbatory. Please stop. -- richo || Today's excuse: A star wars satellite accidently blew up the WAN. http://blog.psych0tik.net [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: Jan
I will also add that if I am asking stupid questions then by axiom (look it up in a dictionary) I AM SAYING I AM LEARNING. You tool! On Mon, Dec 12, 2011 at 9:17 AM, John Tate wrote: > I never claimed to be an OpenBSD guru. Ever. I am an OpenBSD n00b. Here, > I'll put this on the list. > > I am John Norman Tate born September 1987 to two loving parents and the > only part of OpenBSD I think I am good with is using it in accordance to > the manuals when I read them properly. I also understand the security > principles pretty well, I've read Hacking: The Art of Exploitation and > understood it's content. I trust OpenBSD like a man of faith trusts his > religions guidance. I think that pisses you off, but you've imagined > everything else. I keep saying: I am learning, not learned. You're just > trying to assasinate my character by making arbitrary claims you hope > others will not check! It will not work. > -- > www.johntate.org > -- www.johntate.org
Re: Jan
Whoops, I hate gmail sometimes. That was for Jan On Mon, Dec 12, 2011 at 9:21 AM, John Tate wrote: > In other words: stop wasting your breath I'm never leaving. If they kick > me out, well, I'll use seven proxies! > > > On Mon, Dec 12, 2011 at 9:17 AM, John Tate wrote: > >> I never claimed to be an OpenBSD guru. Ever. I am an OpenBSD n00b. Here, >> I'll put this on the list. >> >> I am John Norman Tate born September 1987 to two loving parents and the >> only part of OpenBSD I think I am good with is using it in accordance to >> the manuals when I read them properly. I also understand the security >> principles pretty well, I've read Hacking: The Art of Exploitation and >> understood it's content. I trust OpenBSD like a man of faith trusts his >> religions guidance. I think that pisses you off, but you've imagined >> everything else. I keep saying: I am learning, not learned. You're just >> trying to assasinate my character by making arbitrary claims you hope >> others will not check! It will not work. >> -- >> www.johntate.org >> > > > > -- > www.johntate.org > -- www.johntate.org
Re: Jan
In other words: stop wasting your breath I'm never leaving. If they kick me out, well, I'll use seven proxies! On Mon, Dec 12, 2011 at 9:17 AM, John Tate wrote: > I never claimed to be an OpenBSD guru. Ever. I am an OpenBSD n00b. Here, > I'll put this on the list. > > I am John Norman Tate born September 1987 to two loving parents and the > only part of OpenBSD I think I am good with is using it in accordance to > the manuals when I read them properly. I also understand the security > principles pretty well, I've read Hacking: The Art of Exploitation and > understood it's content. I trust OpenBSD like a man of faith trusts his > religions guidance. I think that pisses you off, but you've imagined > everything else. I keep saying: I am learning, not learned. You're just > trying to assasinate my character by making arbitrary claims you hope > others will not check! It will not work. > -- > www.johntate.org > -- www.johntate.org
Jan
I never claimed to be an OpenBSD guru. Ever. I am an OpenBSD n00b. Here, I'll put this on the list. I am John Norman Tate born September 1987 to two loving parents and the only part of OpenBSD I think I am good with is using it in accordance to the manuals when I read them properly. I also understand the security principles pretty well, I've read Hacking: The Art of Exploitation and understood it's content. I trust OpenBSD like a man of faith trusts his religions guidance. I think that pisses you off, but you've imagined everything else. I keep saying: I am learning, not learned. You're just trying to assasinate my character by making arbitrary claims you hope others will not check! It will not work. -- www.johntate.org
Re: [Full-disclosure] Final Penultimate last Call for Papers for CanSecWest 2011 (deadline Jan. 17th, conf March 9-11)
On Thu, Jan 13, 2011 at 1:15 PM, Dragos wrote: > On 2011-01-13, at 7:31 AM, valdis.kletni...@vt.edu wrote: > > It was my (apparently) lame attempt at being whimsical. Should have made it > I found it amusing. In fact I intend to steal it for my own uses. But maybe "postpenultimate" would be more less unclear. -Gregg
Re: [Full-disclosure] Final Penultimate last Call for Papers for CanSecWest 2011 (deadline Jan. 17th, conf March 9-11)
On 2011-01-13, at 7:31 AM, valdis.kletni...@vt.edu wrote: > On Thu, 13 Jan 2011 03:23:49 PST, Dragos Ruiu said: > >> It's been up on the site for a while with a Dec 29 deadline, >> but this is the real last call for submissions. > > > > If it's the real last call, it's not the penultimate, it's the ultimate. > The penultimate is "the second to last one". > > On 2011-01-13, at 8:02 AM, Randal L. Schwartz wrote: >>>>>> "Dragos" == Dragos Ruiu writes: > > Dragos> It's been up on the site for a while with a Dec 29 deadline, > Dragos> but this is the real last call for submissions. > > Really? Then why did you use "Penultimate" (which means "next to last") > instead of "Ultimate" in the subject line? > > Yours for a more literate education, And a few others... For the record, I'm perfectly aware of the definition of penultimate. It was my (apparently) lame attempt at being whimsical. Should have made it "Final, Really, Really, Last, Almost Definitely, Penultimate, Call For Papers." - to poke fun at ourselves and extending deadlines. In my defense it was 3 a.m. and I'd been working on stuff since six in the morning so I'm sure I wasn't firing on all cylinders. This is why I work with computers instead of doing stand up. I guess I should leave the humor to the SecurityClowns. cheers, --dr -- World Security Pros. Cutting Edge Training, Tools, and Techniques Vancouver, Canada, March 9-11 2011 http://cansecwest.com pgpkey http://dragos.com/ kyxpgp @dragosr
Re: Final Penultimate last Call for Papers for CanSecWest 2011 (deadline Jan. 17th, conf March 9-11)
On Thu, Jan 13, 2011 at 5:02 PM, Randal L. Schwartz wrote: >>>>>> "Dragos" == Dragos Ruiu writes: > > Dragos> It's been up on the site for a while with a Dec 29 deadline, > Dragos> but this is the real last call for submissions. > > Really? Then why did you use "Penultimate" (which means "next to last") > instead of "Ultimate" in the subject line? http://en.wikipedia.org/wiki/Humor > > Yours for a more literate education, > > -- > Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 > http://www.stonehenge.com/merlyn/> > Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. > See http://methodsandmessages.posterous.com/ for Smalltalk discussion
Re: Final Penultimate last Call for Papers for CanSecWest 2011 (deadline Jan. 17th, conf March 9-11)
> "Dragos" == Dragos Ruiu writes: Dragos> It's been up on the site for a while with a Dec 29 deadline, Dragos> but this is the real last call for submissions. Really? Then why did you use "Penultimate" (which means "next to last") instead of "Ultimate" in the subject line? Yours for a more literate education, -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion
Final Penultimate last Call for Papers for CanSecWest 2011 (deadline Jan. 17th, conf March 9-11)
"First they ignore you, then they ridicule you, then they fight you, then you win." -- Mahatma Ghandi. Well if Fox's new comedy show "Breaking In" is any indication, infosec has now entered Ghandi's second stage. http://goo.gl/ZpLDp [youtube] (hat tip to Adam O'Donnell for this humorous find, and Sam Bowne for the quote/quip) But on a slightly more serious note. CanSecWest is nearing in the second week of March, and this year I've waited on sending out the CFP note/reminder. It's been up on the site for a while with a Dec 29 deadline, but this is the real last call for submissions. If you don't get them in by this weekend they won't make the selections review process next week. We'll try to announce the selections the week following. After 11 years, most of you should know the drill, but for those who haven't submitted or attended before, the fine print and usual further information is attached below. Other info: We are doing more dojo training courses than ever this year (17!) and they will be up for registration next week. I've also confirmed with Aaron/TippingPoint/HP that we will again be holding PWN2OWN with both browser and mobile targets, so stand by for some announcements there. There will also be some other new experiments and conference goings on, some fascinating keynotes that have been invited, as well as some interesting new sponsors exhibiting new security wares that you'll see announced on the conference site in the coming weeks, but for now, get your talk proposals in so that our grumpy, cynical, and battle-scarred reviewers can complain about them, err, I mean provide informative feedback.;-) cheers, --dr (@dragosr) The usual CFP boilerplate info: Call For Papers The CanSecWest 2011 CFP is now open. Deadline is January 17th, 2011. CanSecWest CALL FOR PAPERS VANCOUVER, Canada -- The twelfth annual CanSecWest applied technical security conference - where the eminent figures in the international security industry will get together share best practices and technology - will be held in downtown Vancouver at the the Sheraton Wall Centre on March 9-11, 2011. The most significant new discoveries about computer network hack attacks and defenses, commercial security solutions, and pragmatic real world security experience will be presented in a series of informative tutorials. The CanSecWest meeting provides international researchers a relaxed, comfortable environment to learn from informative tutorials on key developments in security technology, and to collaborate and socialize with their peers in one of the world's most scenic cities - a short drive away from one of North America's top skiing areas. The CanSecWest conference will also feature the availability of the Security Masters Dojo expert network security sensei instructors, and their advanced, and intermediate, hands-on training courses - featuring small class sizes and practical application exercises to maximize information transfer. We would like to announce the opportunity to submit papers, and/or lightning talk proposals for selection by the CanSecWest technical review committee. This year we will be doing one hour talks, and some shorter talk sessions. Please make your paper proposal submissions before January 17th, 2011. Some invited papers have been confirmed, but a limited number of speaking slots are still available. The conference is responsible for travel and accommodations for the speakers. If you have a proposal for a tutorial session then please make your submission by emailing a synopsis of the material and your biography, papers and, speaking background to secwes...@cansecwest.com . Only slides will be needed for the March paper deadline, full text does not have to be submitted - but will be accepted if available. This year we will be opening CanSecWest presentation guidelines to include talks not in English (particularly Chinese and Korean) which we will offer to translate for the speaker if you are not a native English speaker. The CanSecWest 2011 conference consists of tutorials on technical details about current issues, innovative techniques and best practices in the information security realm. The audiences are a multi-national mix of professionals involved on a daily basis with security work: security product vendors, programmers, security officers, and network administrators. We give preference to technical details and new education for a technical audience. The conference itself is a single track series of presentations in a lecture theater environment. The presentations offer speakers the opportunity to showcase on-going research and collaborate with peers while educating and highlighting advancements in security products and techniques. The focus is on innovation, tutorials, and education instead of product pitches. Some commercial content is tol
Re: X freezing on Jan 8 & 9 snapshots
I have the same thing on a GENERIC.MP i386 I will send a dmesg shortly. I am on a really crappy connection here, so I would prefer to fix this over downloading another snap, if possible. I can only get another install48.iso through SFTP from my server. All FTP and HTTP connections stall from here. Thanks Chris Bennett
X freezing on Jan 8 & 9 snapshots
Just upgraded an amd64 system from the Nov.11 snap to Jan. 8th and now X freezes the system. Tried again with a clean install of the Jan 9th snap, thinking it might have been a fluke, but I'm still getting freezes. It had been working fine with the Nov. 11 snap; no xorg.conf needed. startx results in a black screen, the box does not respond to pings, I can't switch to virtual consoles, can't break into ddb, and I have to hold down the power button to turn it off. Running "X -configure" gets to the line reading: (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jan 9 23:35:32 2011 and then sits there with a blinking cursor; again the machine is totally unresponsive. Xorg.0.log is a zero-byte file. Dmesg follows, sorry I can't provide an Xorg.0.log or get to ddb. If any other info is helpful, I'd be happy to provide it. The one slightly unusual thing about this system is I usually use a DisplayPort to DVI adapter to drive the monitor. I did try switching to the VGA port and the same freeze happens there. OpenBSD 4.8-current (GENERIC.MP) #758: Sun Jan 9 15:46:09 MST 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2072645632 (1976MB) avail mem = 2003460096 (1910MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe9f80 (67 entries) bios0: vendor Hewlett-Packard version "786G1 v01.23" date 12/11/2009 bios0: Hewlett-Packard HP Compaq dc7900 Ultra-Slim Desktop acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC ASF! MCFG TCPA SLIC HPET acpi0: wakeup devices COM1(S4) COM2(S4) PCI0(S4) PEG1(S4) PEG2(S4) IGBE(S4) PCX1(S4) PCX2(S4) PCX5(S4) PCX6(S4) HUB_(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) EUS1(S3) EUS2(S3) PBTN(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Pentium(R) Dual-Core CPU E5200 @ 2.50GHz, 2494.11 MHz cpu0: FPU,VME,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,EST,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,NXE,LONG cpu0: 2MB 64b/line 8-way L2 cache cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Pentium(R) Dual-Core CPU E5200 @ 2.50GHz, 2493.73 MHz cpu1: FPU,VME,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,EST,TM2,SSSE3,CX16,xTPR,PDCM,XSAVE,NXE,LONG cpu1: 2MB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpimcfg0 at acpi0 addr 0xf400, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG1) acpiprt2 at acpi0: bus -1 (PEG2) acpiprt3 at acpi0: bus 32 (PCX1) acpiprt4 at acpi0: bus -1 (PCX2) acpiprt5 at acpi0: bus 48 (PCX5) acpiprt6 at acpi0: bus -1 (PCX6) acpiprt7 at acpi0: bus 7 (HUB_) acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpibtn0 at acpi0: PBTN cpu0: Enhanced SpeedStep 2493 MHz: speeds: 2500, 1800, 1200 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Q45 Host" rev 0x03 vga1 at pci0 dev 2 function 0 "Intel Q45 Video" rev 0x03 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1: apic 1 int 16 (irq 5) drm0 at inteldrm0 "Intel Q45 Video" rev 0x03 at pci0 dev 2 function 1 not configured "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 1 int 18 (irq 10) 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 1 int 19 (irq 5), address 00:26:55:48:b4:80 uhci0 at pci0 dev 26 function 0 "Intel 82801JD USB" rev 0x02: apic 1 int 20 (irq 10) uhci1 at pci0 dev 26 function 1 "Intel 82801JD USB" rev 0x02: apic 1 int 21 (irq 11) uhci2 at pci0 dev 26 function 2 "Intel 82801JD USB" rev 0x02: apic 1 int 22 (irq 5) ehci0 at pci0 dev 26 function 7 "Intel 82801JD USB" rev 0x02: apic 1 int 22 (irq 5) 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: apic 1 int 21 (irq 11) azalia0: codecs: Analog Devices AD1884A audio0 at azalia0 ppb0 at pci0 dev 28 function 0 "Intel 8280
Re: [RESOLVED] Jan 28 snapshot - em0 disappeared
Steve Williams wrote:
Hi,
I upgraded my system today. I'm not sure if it was previously a
snapshot or actually 4.6. Regardless, I upgraded it to the snapshot
from January 28. I booted the snapshot iso and did an upgrade. Ran
sysmerge & slowly working my way through all the ports.
I went from:
OpenBSD 4.6 (GENERIC) #58: Thu Jul 9 21:24:42 MDT 2009
to
OpenBSD 4.7-beta (GENERIC.MP) #402: Wed Jan 27 19:29:54 MST 2010
I am getting an error in the dmesg, and em0 no longer appears in
ifconfig:
em0 at pci0 dev 25 function 0 "Intel ICH9 IGP AMT" rev 0x02: apic 8
int 21 (irq 3)em0: The EEPROM Checksum Is Not Valid
em0: Unable to initialize the hardware
This is an onboard NIC, so it's not like I can replace it.
I booted the 4.6 install CD and went into the shell to confirm that it
could still see the em0 post upgrade, and it was there no problem
I have included the following files:
1) dmesg from January 28 snapshot
2) dmesg from 4.6
3) pcidump -v from January 28 snapshot
Does anyone have any ideas?
This isn't life threatening as I have already have another NIC in one
of the slots and additional slots available, but I would like to know
what the problem is and how to go about fixing it. I haven't been
able to find the magic google incantation to provide guidance :-(
Thanks,
Steve Williams
Snapshot dmesg
--
OpenBSD 4.7-beta (GENERIC.MP) #402: Wed Jan 27 19:29:54 MST 2010
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
RTC BIOS diagnostic error 11
cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 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,EST,TM2,CX16,xTPR
real mem = 2101956608 (2004MB)
avail mem = 2027941888 (1933MB)
RTC BIOS diagnostic error 11
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 11/05/07, BIOS32 rev. 0 @
0xffea0, SMBIOS rev. 2.5 @ 0xf0450 (80 entries)
bios0: vendor Dell Inc. version "A04" date 11/05/2007
bios0: Dell Inc. OptiPlex 755
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET SLIC
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 265MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 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,EST,TM2,CX16,xTPR
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 GHz
cpu2:
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,EST,TM2,CX16,xTPR
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 GHz
cpu3:
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,EST,TM2,CX16,xTPR
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 8
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 3 (PCI4)
acpiprt1 at acpi0: bus 2 (PCI2)
acpiprt2 at acpi0: bus -1 (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
acpicpu1 at acpi0
acpicpu2 at acpi0
acpicpu3 at acpi0
acpibtn0 at acpi0: VBTN
bios0: ROM list: 0xc/0xb800! 0xcb800/0x2000! 0xcd800/0x2800!
cpu0: Enhanced SpeedStep disabled by BIOS
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
bridge mem address conflict 0xfe80/0x10
mem address conflict 0xfea0/0x8
mem address conflict 0xfeb0/0x10
mem address conflict 0xfea8/0x8
mem address conflict 0xfe9da000/0x1000
mem address conflict 0xfe9e/0x2
mem address conflict 0xfe9db000/0x1000
mem address conflict 0xfe9d9c00/0x400
mem address conflict 0xfe9dc000/0x4000
bridge mem address conflict 0xfe70/0x10
bridge mem address conflict 0xfe50/0x20
mem address conflict 0xfe9d9b00/0x100
pchb0 at pci0 dev 0 function 0 "Intel 82Q35 Host" rev 0x02
ppb0 at pci0 dev 1 function 0 "Intel 82Q35 PCIE" rev 0x02: apic 8 int
16 (irq 11)
pci1 at ppb0 bus 1
vga1 at pci0 dev 2 function 0 "Intel 82Q35 Video" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
Re: Jan 28 snapshot - em0 disappeared
On Mon, Feb 01, 2010 at 11:33:49AM +0100, Rogier Krieger wrote: > On Mon, Feb 1, 2010 at 07:32, Steve Williams > wrote: > > I have downloaded the current cvs code and compiled it. It exhibits the > > same problem, missing em0. > > It seems to nicely detect the hardware, just not liking its EEPROM > contents and stopping initialisation there. While you should take a > developer's word over mine, I suppose it's not surprising that > ifconfig(8) does not show the hardware. > > Seeing a few Google searches seems to indicate it's not necessarily an > OS problem. While some posts mention an Intel utility (IBAUTIL.EXE) to > configure/manage the built-in boot agent, you will probably want to > search for the correct NIC model and see which specific version/tool > you need. > > I included a link [1] to the utility a 5 minute cursory search yielded > me. Use at your own risk, since I can't really be sure it's the > correct one. > I doubt this has todo with the boot rom. The card has a nvrom to store the macaddr etc and it seems that the access to that one is fubar-ed. There were many changes to em(4) to support newer models, some of the changes were quite intrusive and could result in failure of other cards. If possible please try some older kernels to find the commit which has caused the regression. -- :wq Claudio
Re: Jan 28 snapshot - em0 disappeared
On Mon, Feb 1, 2010 at 07:32, Steve Williams wrote: > I have downloaded the current cvs code and compiled it. It exhibits the > same problem, missing em0. It seems to nicely detect the hardware, just not liking its EEPROM contents and stopping initialisation there. While you should take a developer's word over mine, I suppose it's not surprising that ifconfig(8) does not show the hardware. Seeing a few Google searches seems to indicate it's not necessarily an OS problem. While some posts mention an Intel utility (IBAUTIL.EXE) to configure/manage the built-in boot agent, you will probably want to search for the correct NIC model and see which specific version/tool you need. I included a link [1] to the utility a 5 minute cursory search yielded me. Use at your own risk, since I can't really be sure it's the correct one. Regards, Rogier References: 1. Intel Boot Agent BIOS http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=12344&ProdId=2775&lang=eng
Re: Jan 28 snapshot - em0 disappeared
Hi,
Replying to myself, hence the top post :-) lol.
I have downloaded the current cvs code and compiled it. It exhibits the
same problem, missing em0.
I have put a few debug printf's in /usr/src/sys/dev/pci/if_em_hw.c,
recompiled and verified that the messages show up on boot.
So, I'm ready for troubleshooting this, but I'm at a wee bit of a loss
where to go from here. I did try to put the 4.6 if_em* files into the
src tree (with little expectation of success) and was rewarded with the
kernel not compiling. No surprise there.
I'm comfortable poking around kernel level C, but cvs is a whole new
world to me.
What would be the best approach, checking out the entire tree based on a
certain date, compiling & checking if it works?
Thanks,
Steve Williams
Steve Williams wrote:
Hi,
I upgraded my system today. I'm not sure if it was previously a
snapshot or actually 4.6. Regardless, I upgraded it to the snapshot
from January 28. I booted the snapshot iso and did an upgrade. Ran
sysmerge & slowly working my way through all the ports.
I went from:
OpenBSD 4.6 (GENERIC) #58: Thu Jul 9 21:24:42 MDT 2009
to
OpenBSD 4.7-beta (GENERIC.MP) #402: Wed Jan 27 19:29:54 MST 2010
I am getting an error in the dmesg, and em0 no longer appears in
ifconfig:
em0 at pci0 dev 25 function 0 "Intel ICH9 IGP AMT" rev 0x02: apic 8
int 21 (irq 3)em0: The EEPROM Checksum Is Not Valid
em0: Unable to initialize the hardware
This is an onboard NIC, so it's not like I can replace it.
I booted the 4.6 install CD and went into the shell to confirm that it
could still see the em0 post upgrade, and it was there no problem
I have included the following files:
1) dmesg from January 28 snapshot
2) dmesg from 4.6
3) pcidump -v from January 28 snapshot
Does anyone have any ideas?
This isn't life threatening as I have already have another NIC in one
of the slots and additional slots available, but I would like to know
what the problem is and how to go about fixing it. I haven't been
able to find the magic google incantation to provide guidance :-(
Thanks,
Steve Williams
Snapshot dmesg
--
OpenBSD 4.7-beta (GENERIC.MP) #402: Wed Jan 27 19:29:54 MST 2010
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
RTC BIOS diagnostic error 11
cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 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,EST,TM2,CX16,xTPR
real mem = 2101956608 (2004MB)
avail mem = 2027941888 (1933MB)
RTC BIOS diagnostic error 11
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 11/05/07, BIOS32 rev. 0 @
0xffea0, SMBIOS rev. 2.5 @ 0xf0450 (80 entries)
bios0: vendor Dell Inc. version "A04" date 11/05/2007
bios0: Dell Inc. OptiPlex 755
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET SLIC
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 265MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 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,EST,TM2,CX16,xTPR
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 GHz
cpu2:
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,EST,TM2,CX16,xTPR
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 GHz
cpu3:
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,EST,TM2,CX16,xTPR
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 8
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 3 (PCI4)
acpiprt1 at acpi0: bus 2 (PCI2)
acpiprt2 at acpi0: bus -1 (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
acpicpu1 at acpi0
acpicpu2 at acpi0
acpicpu3 at acpi0
acpibtn0 at acpi0: VBTN
bios0: ROM list: 0xc/0xb800! 0xcb800/0x2000! 0xcd800/0x2800!
cpu0: Enhanced SpeedStep disabled by BIOS
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
bridge mem address conflict 0xfe80/0x10
mem
Jan 28 snapshot - em0 disappeared
Hi,
I upgraded my system today. I'm not sure if it was previously a
snapshot or actually 4.6. Regardless, I upgraded it to the snapshot
from January 28. I booted the snapshot iso and did an upgrade. Ran
sysmerge & slowly working my way through all the ports.
I went from:
OpenBSD 4.6 (GENERIC) #58: Thu Jul 9 21:24:42 MDT 2009
to
OpenBSD 4.7-beta (GENERIC.MP) #402: Wed Jan 27 19:29:54 MST 2010
I am getting an error in the dmesg, and em0 no longer appears in ifconfig:
em0 at pci0 dev 25 function 0 "Intel ICH9 IGP AMT" rev 0x02: apic 8 int
21 (irq 3)em0: The EEPROM Checksum Is Not Valid
em0: Unable to initialize the hardware
This is an onboard NIC, so it's not like I can replace it.
I booted the 4.6 install CD and went into the shell to confirm that it
could still see the em0 post upgrade, and it was there no problem
I have included the following files:
1) dmesg from January 28 snapshot
2) dmesg from 4.6
3) pcidump -v from January 28 snapshot
Does anyone have any ideas?
This isn't life threatening as I have already have another NIC in one of
the slots and additional slots available, but I would like to know what
the problem is and how to go about fixing it. I haven't been able to
find the magic google incantation to provide guidance :-(
Thanks,
Steve Williams
Snapshot dmesg
--
OpenBSD 4.7-beta (GENERIC.MP) #402: Wed Jan 27 19:29:54 MST 2010
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
RTC BIOS diagnostic error 11
cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 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,EST,TM2,CX16,xTPR
real mem = 2101956608 (2004MB)
avail mem = 2027941888 (1933MB)
RTC BIOS diagnostic error 11
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 11/05/07, BIOS32 rev. 0 @ 0xffea0,
SMBIOS rev. 2.5 @ 0xf0450 (80 entries)
bios0: vendor Dell Inc. version "A04" date 11/05/2007
bios0: Dell Inc. OptiPlex 755
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET SLIC
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 265MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 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,EST,TM2,CX16,xTPR
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 GHz
cpu2:
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,EST,TM2,CX16,xTPR
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel"
686-class) 2.40 GHz
cpu3:
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,EST,TM2,CX16,xTPR
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 8
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 3 (PCI4)
acpiprt1 at acpi0: bus 2 (PCI2)
acpiprt2 at acpi0: bus -1 (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
acpicpu1 at acpi0
acpicpu2 at acpi0
acpicpu3 at acpi0
acpibtn0 at acpi0: VBTN
bios0: ROM list: 0xc/0xb800! 0xcb800/0x2000! 0xcd800/0x2800!
cpu0: Enhanced SpeedStep disabled by BIOS
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
bridge mem address conflict 0xfe80/0x10
mem address conflict 0xfea0/0x8
mem address conflict 0xfeb0/0x10
mem address conflict 0xfea8/0x8
mem address conflict 0xfe9da000/0x1000
mem address conflict 0xfe9e/0x2
mem address conflict 0xfe9db000/0x1000
mem address conflict 0xfe9d9c00/0x400
mem address conflict 0xfe9dc000/0x4000
bridge mem address conflict 0xfe70/0x10
bridge mem address conflict 0xfe50/0x20
mem address conflict 0xfe9d9b00/0x100
pchb0 at pci0 dev 0 function 0 "Intel 82Q35 Host" rev 0x02
ppb0 at pci0 dev 1 function 0 "Intel 82Q35 PCIE" rev 0x02: apic 8 int 16
(irq 11)
pci1 at ppb0 bus 1
vga1 at pci0 dev 2 function 0 "Intel 82Q35 Video" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
intagp0 at vga1
agp0 at intagp0
20. jan current amd64 stops randomly on hp dl385 g1
Hi! It may be that i have something not set right in bios (although it has default settings set and firmware is updated) but my hp dl385 g1 randomly stops running 20. january current amd64. The same computer worked for a long time with another operating system, i.e. i dont suspect hardware problem. I wrote up these messages from console kernel: machine: machine check trap, code=0 Stopped at hardclock+0x1: movq, %rsp,%rbp ddb> trace hardclock() at hardclock+0x1 Xresume_lapic_ltimer() at Xresume_lapic_ltimer+0x1e ---interrupt--- Bad frame pointer: 0x8000211b5f10 end trace frame: 0x8000211b5f10, count: -2 cpu_idle_cycle+0x13: ddb> show panic the kernel did not panic ddb> ps PID PPID PGRP UID S FLAGS WAIT COMMAND 20513 18063 20513 0 3 0x4082 netio ftp ... ddb> show registers ds 0xf500 acpi_pdirpa+0xb120 es 0xb800 acpi_pdirpa+0x7420 fs 0x5013 acpi_pdirpa+0xc33 gs 0x5dc8 acpi_pdirpa+0x19e8 rdi 0x8000211b5e08 rsi 0x80968360 cpu_info_primary rbp 0x8000211brdf8 rbx 0 rdx 0x80c898c0 sched_idle_cpus rcx 0 rax 0 r8 0 r9 0 r10 0x8000211b5eb0 r110x8 r12 0 r13 0xfe80075c3238 r14 9x80967360 r15 0 rip 0x802834c1 hardclock+0x1 cs 0x8 rflags 0x246 rsp 0x8000211b5de8 ss0x10 hardclock+0x1 movq %rsp,%rbp Hardware is # sysctl hw hw.machine=amd64 hw.model=AMD Opteron(tm) Processor 280 hw.ncpu=1 hw.byteorder=1234 hw.pagesize=4096 hw.disknames=cd0,sd0 hw.diskcount=2 hw.sensors.ciss0.drive0=online (sd0), OK hw.sensors.kate0.temp0=49.00 degC hw.sensors.kate0.temp2=48.00 degC hw.sensors.kate1.temp0=46.00 degC hw.sensors.kate1.temp2=45.00 degC hw.cpuspeed=2405 hw.setperf=100 hw.vendor=HP hw.product=ProLiant DL385 G1 hw.serialno=700445802 hw.uuid=37303034-3435-3730-3034-343538303200 hw.physmem=4117725184 hw.usermem=4117712896 hw.ncpufound=4 and dmesg is OpenBSD 4.6-current (GENERIC) #59: Wed Jan 20 06:45:07 MST 2010 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC real mem = 4117725184 (3926MB) avail mem = 4002447360 (3817MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xec000 (64 entries) bios0: vendor HP version "A05" date 03/01/2006 bios0: HP ProLiant DL385 G1 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP APIC SPCR SRAT acpi0: wakeup devices acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Opteron(tm) Processor 280, 2405.79 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: AMD erratum 89 present, BIOS upgrade may be required cpu0: apic clock running at 200MHz cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 4 pa 0xfec0, version 11, 24 pins ioapic1 at mainbus0: apid 5 pa 0xfec1, version 11, 4 pins ioapic2 at mainbus0: apid 6 pa 0xfec2, version 11, 4 pins ioapic3 at mainbus0: apid 7 pa 0xfdc0, version 11, 4 pins ioapic4 at mainbus0: apid 8 pa 0xfdc1, version 11, 4 pins acpiprt0 at acpi0: bus 1 (PCI0) acpiprt1 at acpi0: bus 2 (PCI1) acpiprt2 at acpi0: bus 3 (PCI2) acpiprt3 at acpi0: bus 0 (CFG0) acpiprt4 at acpi0: bus 5 (PCI3) acpiprt5 at acpi0: bus 6 (PCI4) acpicpu0 at acpi0: PSS cpu0: Cool'n'Quiet K8 2405 MHz: speeds: 2400 2200 2000 1800 MHz pci0 at mainbus0 bus 0 ppb0 at pci0 dev 3 function 0 "AMD 8111 PCI-PCI" rev 0x07 pci1 at ppb0 bus 1 ohci0 at pci1 dev 0 function 0 "AMD 8111 USB" rev 0x0b: apic 4 int 19 (irq 5), version 1.0, legacy support ohci1 at pci1 dev 0 function 1 "AMD 8111 USB" rev 0x0b: apic 4 int 19 (irq 5), version 1.0, legacy support "Compaq iLO" rev 0x01 at pci1 dev 2 function 0 not configured "Compaq iLO" rev 0x01 at pci1 dev 2 function 2 not configured vga1 at pci1 dev 3 function 0 "ATI Rage XL" rev 0x27 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) usb0 at ohci0: USB revision 1.0 uhub0 at usb0 "AMD OHCI root hub" rev 1.00/1.00 addr 1 usb1 at ohci1: USB revision 1.0 uhub1 at usb1 "AMD OHCI root hub" rev 1.00/1.00 addr 1 amdpcib0 at pci0 dev 4 function 0 "AMD 8111 LPC" rev 0x05 pciide0 at pci0 dev 4 function 1 "AMD 8111 IDE" rev 0x03: DMA, channel 0 configured to c
Re: Wrong cksum of base46.tgz set in 20th Jan 2010 snapshot
On Sat, Jan 23, 2010 at 6:43 PM, Marco Peereboom wrote: > This is exactly what was predicted what would happen. > > No benefit to publish the digests minus a bunch of people whining that > the damn digests are off for obvious reasons. i am not sure if i would categorize these as "whinings". Seems more of a concern. Although, I don't understand why someone expecting correct checksum but seeing otherwise would continue on with the installation. It is almost like if you try to ssh to what you expect is a server you log into regularly, but you get the @s warning about the key for the host having changed, yet without further validation you enter your user-id/password. There is a chance that indeed the keys were changed on the host, but maybe you should verify this fact before giving up your "goods". --patrick > On Sun, Jan 24, 2010 at 12:30:35AM +, Mikolaj Kucharski wrote: >> Hi, >> >> On all mirrors and on main openbsd server base46.tgz is giving failed >> cksum error. Not sure is that random error, as I never saw that before. >> File content seems to be fine as reported by gzip, but could someone fix >> that if possible? >> >> >> $ config -ef bsd >> OpenBSD 4.6-current (GENERIC) #511: Wed Jan 20 06:46:42 MST 2010 >> t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC >> >> >> $ cksum -c SHA256 >> (SHA256) INSTALL.i386: OK >> (SHA256) INSTALL.linux: OK >> (SHA256) base46.tgz: FAILED >> (SHA256) bsd: OK >> (SHA256) bsd.mp: OK >> (SHA256) bsd.rd: OK >> (SHA256) cd46.iso: OK >> (SHA256) cdboot: OK >> (SHA256) cdbr: OK >> (SHA256) cdemu46.iso: OK >> (SHA256) comp46.tgz: OK >> (SHA256) etc46.tgz: OK >> (SHA256) floppy46.fs: OK >> (SHA256) floppyB46.fs: OK >> (SHA256) floppyC46.fs: OK >> (SHA256) game46.tgz: OK >> (SHA256) install46.iso: OK >> (SHA256) man46.tgz: OK >> (SHA256) misc46.tgz: OK >> (SHA256) pxeboot: OK >> (SHA256) xbase46.tgz: OK >> (SHA256) xetc46.tgz: OK >> (SHA256) xfont46.tgz: OK >> (SHA256) xserv46.tgz: OK >> (SHA256) xshare46.tgz: OK >> >> >> $ gzip -vt base46.tgz >> base46.tgz: OK >> >> -- >> best regards >> q#
Re: Wrong cksum of base46.tgz set in 20th Jan 2010 snapshot
This is exactly what was predicted what would happen. No benefit to publish the digests minus a bunch of people whining that the damn digests are off for obvious reasons. On Sun, Jan 24, 2010 at 12:30:35AM +, Mikolaj Kucharski wrote: > Hi, > > On all mirrors and on main openbsd server base46.tgz is giving failed > cksum error. Not sure is that random error, as I never saw that before. > File content seems to be fine as reported by gzip, but could someone fix > that if possible? > > > $ config -ef bsd > OpenBSD 4.6-current (GENERIC) #511: Wed Jan 20 06:46:42 MST 2010 > t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC > > > $ cksum -c SHA256 > (SHA256) INSTALL.i386: OK > (SHA256) INSTALL.linux: OK > (SHA256) base46.tgz: FAILED > (SHA256) bsd: OK > (SHA256) bsd.mp: OK > (SHA256) bsd.rd: OK > (SHA256) cd46.iso: OK > (SHA256) cdboot: OK > (SHA256) cdbr: OK > (SHA256) cdemu46.iso: OK > (SHA256) comp46.tgz: OK > (SHA256) etc46.tgz: OK > (SHA256) floppy46.fs: OK > (SHA256) floppyB46.fs: OK > (SHA256) floppyC46.fs: OK > (SHA256) game46.tgz: OK > (SHA256) install46.iso: OK > (SHA256) man46.tgz: OK > (SHA256) misc46.tgz: OK > (SHA256) pxeboot: OK > (SHA256) xbase46.tgz: OK > (SHA256) xetc46.tgz: OK > (SHA256) xfont46.tgz: OK > (SHA256) xserv46.tgz: OK > (SHA256) xshare46.tgz: OK > > > $ gzip -vt base46.tgz > base46.tgz: OK > > -- > best regards > q#
Re: Wrong cksum of base46.tgz set in 20th Jan 2010 snapshot
If you don't have time to search the archives, you could at least check today's mail. On Sat, Jan 23, 2010 at 7:30 PM, Mikolaj Kucharski wrote: > Hi, > > On all mirrors and on main openbsd server base46.tgz is giving failed > cksum error. Not sure is that random error, as I never saw that before. > File content seems to be fine as reported by gzip, but could someone fix > that if possible? > > > $ config -ef bsd > OpenBSD 4.6-current (GENERIC) #511: Wed Jan 20 06:46:42 MST 2010 >t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC > > > $ cksum -c SHA256 > (SHA256) INSTALL.i386: OK > (SHA256) INSTALL.linux: OK > (SHA256) base46.tgz: FAILED > (SHA256) bsd: OK > (SHA256) bsd.mp: OK > (SHA256) bsd.rd: OK > (SHA256) cd46.iso: OK > (SHA256) cdboot: OK > (SHA256) cdbr: OK > (SHA256) cdemu46.iso: OK > (SHA256) comp46.tgz: OK > (SHA256) etc46.tgz: OK > (SHA256) floppy46.fs: OK > (SHA256) floppyB46.fs: OK > (SHA256) floppyC46.fs: OK > (SHA256) game46.tgz: OK > (SHA256) install46.iso: OK > (SHA256) man46.tgz: OK > (SHA256) misc46.tgz: OK > (SHA256) pxeboot: OK > (SHA256) xbase46.tgz: OK > (SHA256) xetc46.tgz: OK > (SHA256) xfont46.tgz: OK > (SHA256) xserv46.tgz: OK > (SHA256) xshare46.tgz: OK > > > $ gzip -vt base46.tgz > base46.tgz: OK > > -- > best regards > q#
Wrong cksum of base46.tgz set in 20th Jan 2010 snapshot
Hi, On all mirrors and on main openbsd server base46.tgz is giving failed cksum error. Not sure is that random error, as I never saw that before. File content seems to be fine as reported by gzip, but could someone fix that if possible? $ config -ef bsd OpenBSD 4.6-current (GENERIC) #511: Wed Jan 20 06:46:42 MST 2010 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC $ cksum -c SHA256 (SHA256) INSTALL.i386: OK (SHA256) INSTALL.linux: OK (SHA256) base46.tgz: FAILED (SHA256) bsd: OK (SHA256) bsd.mp: OK (SHA256) bsd.rd: OK (SHA256) cd46.iso: OK (SHA256) cdboot: OK (SHA256) cdbr: OK (SHA256) cdemu46.iso: OK (SHA256) comp46.tgz: OK (SHA256) etc46.tgz: OK (SHA256) floppy46.fs: OK (SHA256) floppyB46.fs: OK (SHA256) floppyC46.fs: OK (SHA256) game46.tgz: OK (SHA256) install46.iso: OK (SHA256) man46.tgz: OK (SHA256) misc46.tgz: OK (SHA256) pxeboot: OK (SHA256) xbase46.tgz: OK (SHA256) xetc46.tgz: OK (SHA256) xfont46.tgz: OK (SHA256) xserv46.tgz: OK (SHA256) xshare46.tgz: OK $ gzip -vt base46.tgz base46.tgz: OK -- best regards q#
Re: SHA256 mismatch on base46.tgz in 20 Jan i386 snapshot
Julian Leyh wrote: > Am 23.01.10 07:05, schrieb James Hartley: >> A quick search in the misc@ archives& PR database didn't reveal that anyone >> has mentioned this before. >> >> In installing the 20 January (#511) i386 snapshot, I received a SHA256 >> mismatch on base46.tgz. Otherwise, the snapshot installs as expected. > > Why check SHA256, if you still install it? because sometimes things happen in the snapshot world that don't apply to releases. If a file gets left out of a snapshot, rather than re-rolling the entire release (which can take a day or more on a slow platform, and non-trivial time in all cases), perhaps only base46.tgz is re-rolled. Plus, re-rolling the entire release means it takes many times as long to work out to the mirrors (and this is non-trivial, too). Plus, in many cases, people do intentionally use mismatched bsd.rd and file sets. No, not a good idea, but a time saver in some cases, and some people understand the risks and benefits to being able to do so. As the replication time for snapshots is absolutely non-trivial, it is entirely possible one can download bsd.rd, start installing, and get a base46.tgz (or any other file set) from a NEWER snap. Or an older snap. Or maybe something bad happened to that snapshot. But I don't think so in this case. :) Nick.
Re: SHA256 mismatch on base46.tgz in 20 Jan i386 snapshot
On Fri, Jan 22, 2010 at 10:05:13PM -0800, James Hartley wrote: > A quick search in the misc@ archives & PR database didn't reveal that anyone > has mentioned this before. > > In installing the 20 January (#511) i386 snapshot, I received a SHA256 > mismatch on base46.tgz. Otherwise, the snapshot installs as expected. > Me too. Just upgraded current. Right now I'm runnig OpenBSD 4.6-current (GENERIC.MP) #393: Wed Jan 20 06:54:30 MST 2010 Downloaded from ftp.eu.openbsd.org
Re: SHA256 mismatch on base46.tgz in 20 Jan i386 snapshot
Am 23.01.10 07:05, schrieb James Hartley: A quick search in the misc@ archives& PR database didn't reveal that anyone has mentioned this before. In installing the 20 January (#511) i386 snapshot, I received a SHA256 mismatch on base46.tgz. Otherwise, the snapshot installs as expected. Why check SHA256, if you still install it?
Re: SHA256 mismatch on base46.tgz in 20 Jan i386 snapshot
On Fri, Jan 22, 2010 at 10:05:13PM -0800, James Hartley wrote: > A quick search in the misc@ archives & PR database didn't reveal that anyone > has mentioned this before. > > In installing the 20 January (#511) i386 snapshot, I received a SHA256 > mismatch on base46.tgz. Otherwise, the snapshot installs as expected. > > FYI & FWIW. > > Jim > I did get the same mismatch, to be clear, it's on amd64
SHA256 mismatch on base46.tgz in 20 Jan i386 snapshot
A quick search in the misc@ archives & PR database didn't reveal that anyone has mentioned this before. In installing the 20 January (#511) i386 snapshot, I received a SHA256 mismatch on base46.tgz. Otherwise, the snapshot installs as expected. FYI & FWIW. Jim
pkg_add in Jan 19 amd64 snapshot: no OpenBSD/LibSpec.pm
I just installed the newest amd64 snapshot, and pkg_add installs quirks-1.6 and then fails, complaining about not being able to load OpenBSD/LibSpec.pm. Installing pkg_add (only) from /usr/src seems to solve the issue. If this has been reported before, sorry! Joachim
Re: re(4) panic on 13 Jan 2009 snap
On Wed, Jan 21, 2009 at 6:08 AM, Stuart Henderson wrote: > On 2009-01-19, Bryan wrote: >> Greetings, >> >> >> I am still having issues with the re(4) interface on my server. I >> mentioned this on the list, and was told that the re(4) fix was in. I >> am running the 13 Jan 2009 snapshot, and I can still reproduce the >> error on a regular basis. It goes like this... >> >> 1. push the power button >> 2. boot openbsd >> 3. panic >> >> panic: config_detach: forced detach of re0 failed (45) >> Stopped atDebugger+0x4: leave > > This is not what is shown in your pictures. > In noticed that too... I think that I failed to upload that pic. I'll look for it if you really need it. I typed it as I saw it. complete with whitespace... > After enabling javascript to see them (*grumble*) I see the ones > you have look like this: > unfortunately, at work, imageshack, and other pic sharing sites are blocked. So I use what is available to me. > uvm_fault(0xd080c660, 0x12e52000, 0, 3_) -> e > kernel: page fault trap, code=0 > Stopped at apic_vectorset+0x50: movl %esi,apic_maxlevel(,%eax,4) > apic_vectorset(d3f1d800,0,ff,0,0) at apic_vectorset+0x50 > ioapic_enable(d080c660,0,d0965fa0,d034d1a3,d08c1720) at ioapic_enable+0x8f > cpu_configure(d08c1720,1,3,0,2) at cpu_configure+0x42 > main(0,0,0,0,0) at main+0x3a7 > > only process in the table is the swapper. > > >> 4. issue "boot sync" >> 5. system restarts >> 6. re(4) starts with no issues >> >> If someone has any other ideas, please let me know. The dmesg below is >> when the server will come up after a "boot sync" and a warm restart. >> >> I do intend on updating to the latest snapshot (jan 18th) in the next >> few minutes. > > Did that change anything? > > Sometime between the 13th and the 18th, something was fixed and I've not had an issue with the re(4) interface. was going to post a "it got fixed, sorry about the noise, but you beat me to it...
Re: re(4) panic on 13 Jan 2009 snap
On 2009-01-19, Bryan wrote:
> Greetings,
>
>
> I am still having issues with the re(4) interface on my server. I
> mentioned this on the list, and was told that the re(4) fix was in. I
> am running the 13 Jan 2009 snapshot, and I can still reproduce the
> error on a regular basis. It goes like this...
>
> 1. push the power button
> 2. boot openbsd
> 3. panic
>
> panic: config_detach: forced detach of re0 failed (45)
> Stopped atDebugger+0x4: leave
This is not what is shown in your pictures.
After enabling javascript to see them (*grumble*) I see the ones
you have look like this:
uvm_fault(0xd080c660, 0x12e52000, 0, 3_) -> e
kernel: page fault trap, code=0
Stopped at apic_vectorset+0x50: movl %esi,apic_maxlevel(,%eax,4)
apic_vectorset(d3f1d800,0,ff,0,0) at apic_vectorset+0x50
ioapic_enable(d080c660,0,d0965fa0,d034d1a3,d08c1720) at ioapic_enable+0x8f
cpu_configure(d08c1720,1,3,0,2) at cpu_configure+0x42
main(0,0,0,0,0) at main+0x3a7
only process in the table is the swapper.
> 4. issue "boot sync"
> 5. system restarts
> 6. re(4) starts with no issues
>
> if I shutdown, or do a warm reboot, I have to do step 4 and restart the
> system.
>
> I do have a picture of the error I receive when the system is going to
> panic. As I have no console, and puc(4) is useless for console use,
> the picture can be found here:
>
> http://picasaweb.google.com/lh/photo/Das3TsaFIvV1I-zKTHvaog?feat=directlink
>
> I also did a ps, and trace of the system. here is the photo of that.
>
> http://picasaweb.google.com/lh/photo/l7IN31cOVXa1y8yn74aA8w?feat=directlink
>
> If someone has any other ideas, please let me know. The dmesg below is
> when the server will come up after a "boot sync" and a warm restart.
>
> I do intend on updating to the latest snapshot (jan 18th) in the next
> few minutes.
Did that change anything?
> Regards,
> Bryan Brake
>
> OpenBSD 4.4-current (GENERIC.MP) #35: Tue Jan 13 10:19:47 MST 2009
> t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
> cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 1 GHz
> 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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> real mem = 3488833536 (3327MB)
> avail mem = 3384754176 (3227MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 10/23/08, BIOS32 rev. 0 @ 0xf0010,
> SMBIOS
> rev. 2.5 @ 0xf06e0 (54 entries)
> bios0: vendor American Megatrends Inc. version "5.32" date 10/23/2008
> bios0: HP-Pavilion FK484AV-ABA m9400t
> acpi0 at bios0: rev 0
> acpi0: tables DSDT FACP APIC MCFG OEMB HPET GSCI SLIC SSDT
> acpi0: wakeup devices P0P2(S4) P0P1(S4) PS2K(S3) PS2M(S3) USB0(S3) USB1(S3)
> USB2
> (S3) USB5(S3) EUSB(S3) USB3(S3) USB4(S3) USBE(S3) GBE_(S4) P0P4(S4) P0P5(S4)
> P0P
> 6(S4) P0P7(S4) P0P8(S4) P0P9(S4) SLPB(S4)
> 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 266MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 0 GHz
> cpu1:
> 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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> cpu2 at mainbus0: apid 2 (application processor)
> cpu2: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 0 GHz
> cpu2:
> 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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 0 GHz
> cpu3:
> 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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (P0P1)
> acpiprt2 at acpi0: bus 3 (P0P4)
> acpiprt3 at acpi0: bus -1 (P0P5)
> acpiprt4 at acpi0: bus 2 (P0P6)
> acpiprt5 at acpi0: bus -1 (P0P7)
> acpiprt6 at acpi0: bus -1 (P0P8)
> acpiprt7 at acpi0: bus -1 (P0P9)
> acpicpu0 at acpi0
> acpicpu1 at acpi0
> acpicpu2 at acpi0
> acpicpu3 at acpi0
> acpibtn0 at acpi0: SLPB
> acpibtn1 at acpi0: PWRB
> bios0: ROM list: 0xc/0xe200 0xce800/0x1
Re: re(4) panic on 13 Jan 2009 snap
Hi !
I got the same issue, before last revision of src/sys/dev/pci/ppb.c by
Mark (kettenis@). Yet your trace and ps output is rather different
from what I got back then. I am not familiar enough with the kernel
internals to state about the similarity of our situations. The issue
still shows up if I don't disable apm at boot. Have you done so ?
Regards.
hyjial
2009/1/19 Bryan :
> Greetings,
>
>
> I am still having issues with the re(4) interface on my server. I
> mentioned this on the list, and was told that the re(4) fix was in. I
> am running the 13 Jan 2009 snapshot, and I can still reproduce the
> error on a regular basis. It goes like this...
>
> 1. push the power button
> 2. boot openbsd
> 3. panic
>
> panic: config_detach: forced detach of re0 failed (45)
> Stopped atDebugger+0x4: leave
>
> 4. issue "boot sync"
> 5. system restarts
> 6. re(4) starts with no issues
>
> if I shutdown, or do a warm reboot, I have to do step 4 and restart the
> system.
>
> I do have a picture of the error I receive when the system is going to
> panic. As I have no console, and puc(4) is useless for console use,
> the picture can be found here:
>
> http://picasaweb.google.com/lh/photo/Das3TsaFIvV1I-zKTHvaog?feat=directlink
>
> I also did a ps, and trace of the system. here is the photo of that.
>
> http://picasaweb.google.com/lh/photo/l7IN31cOVXa1y8yn74aA8w?feat=directlink
>
> If someone has any other ideas, please let me know. The dmesg below is
> when the server will come up after a "boot sync" and a warm restart.
>
> I do intend on updating to the latest snapshot (jan 18th) in the next
> few minutes.
>
> Regards,
> Bryan Brake
>
> OpenBSD 4.4-current (GENERIC.MP) #35: Tue Jan 13 10:19:47 MST 2009
>t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
> cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 1 GHz
> 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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> real mem = 3488833536 (3327MB)
> avail mem = 3384754176 (3227MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 10/23/08, BIOS32 rev. 0 @ 0xf0010,
> SMBIOS
> rev. 2.5 @ 0xf06e0 (54 entries)
> bios0: vendor American Megatrends Inc. version "5.32" date 10/23/2008
> bios0: HP-Pavilion FK484AV-ABA m9400t
> acpi0 at bios0: rev 0
> acpi0: tables DSDT FACP APIC MCFG OEMB HPET GSCI SLIC SSDT
> acpi0: wakeup devices P0P2(S4) P0P1(S4) PS2K(S3) PS2M(S3) USB0(S3) USB1(S3)
> USB2
> (S3) USB5(S3) EUSB(S3) USB3(S3) USB4(S3) USBE(S3) GBE_(S4) P0P4(S4) P0P5(S4)
> P0P
> 6(S4) P0P7(S4) P0P8(S4) P0P9(S4) SLPB(S4)
> 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 266MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 0 GHz
> cpu1:
> 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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> cpu2 at mainbus0: apid 2 (application processor)
> cpu2: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 0 GHz
> cpu2:
> 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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class)
> 2.4
> 0 GHz
> cpu3:
> 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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
> xTPR
> ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
> acpihpet0 at acpi0: 14318179 Hz
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus 1 (P0P1)
> acpiprt2 at acpi0: bus 3 (P0P4)
> acpiprt3 at acpi0: bus -1 (P0P5)
> acpiprt4 at acpi0: bus 2 (P0P6)
> acpiprt5 at acpi0: bus -1 (P0P7)
> acpiprt6 at acpi0: bus -1 (P0P8)
> acpiprt7 at acpi0: bus -1 (P0P9)
> acpicpu0 at acpi0
> acpicpu1 at acpi0
> acpicpu2 at acpi0
> acpicpu3 at acpi0
> acpibtn0 at acpi0: SLPB
> acpibtn1 at acpi0: PWRB
> bios0: ROM list: 0xc/0xe200 0xce800/0x1000
> pci0 at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x02
> ppb0 at pci0 dev 1 function 0 "Intel 82G33 PCIE" rev 0x0
re(4) panic on 13 Jan 2009 snap
Greetings,
I am still having issues with the re(4) interface on my server. I
mentioned this on the list, and was told that the re(4) fix was in. I
am running the 13 Jan 2009 snapshot, and I can still reproduce the
error on a regular basis. It goes like this...
1. push the power button
2. boot openbsd
3. panic
panic: config_detach: forced detach of re0 failed (45)
Stopped atDebugger+0x4: leave
4. issue "boot sync"
5. system restarts
6. re(4) starts with no issues
if I shutdown, or do a warm reboot, I have to do step 4 and restart the system.
I do have a picture of the error I receive when the system is going to
panic. As I have no console, and puc(4) is useless for console use,
the picture can be found here:
http://picasaweb.google.com/lh/photo/Das3TsaFIvV1I-zKTHvaog?feat=directlink
I also did a ps, and trace of the system. here is the photo of that.
http://picasaweb.google.com/lh/photo/l7IN31cOVXa1y8yn74aA8w?feat=directlink
If someone has any other ideas, please let me know. The dmesg below is
when the server will come up after a "boot sync" and a warm restart.
I do intend on updating to the latest snapshot (jan 18th) in the next
few minutes.
Regards,
Bryan Brake
OpenBSD 4.4-current (GENERIC.MP) #35: Tue Jan 13 10:19:47 MST 2009
t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class) 2.4
1 GHz
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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
xTPR
real mem = 3488833536 (3327MB)
avail mem = 3384754176 (3227MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 10/23/08, BIOS32 rev. 0 @ 0xf0010, SMBIOS
rev. 2.5 @ 0xf06e0 (54 entries)
bios0: vendor American Megatrends Inc. version "5.32" date 10/23/2008
bios0: HP-Pavilion FK484AV-ABA m9400t
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC MCFG OEMB HPET GSCI SLIC SSDT
acpi0: wakeup devices P0P2(S4) P0P1(S4) PS2K(S3) PS2M(S3) USB0(S3) USB1(S3) USB2
(S3) USB5(S3) EUSB(S3) USB3(S3) USB4(S3) USBE(S3) GBE_(S4) P0P4(S4) P0P5(S4) P0P
6(S4) P0P7(S4) P0P8(S4) P0P9(S4) SLPB(S4)
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 266MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class) 2.4
0 GHz
cpu1: 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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
xTPR
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class) 2.4
0 GHz
cpu2: 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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
xTPR
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz ("GenuineIntel" 686-class) 2.4
0 GHz
cpu3: 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,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,
xTPR
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (P0P1)
acpiprt2 at acpi0: bus 3 (P0P4)
acpiprt3 at acpi0: bus -1 (P0P5)
acpiprt4 at acpi0: bus 2 (P0P6)
acpiprt5 at acpi0: bus -1 (P0P7)
acpiprt6 at acpi0: bus -1 (P0P8)
acpiprt7 at acpi0: bus -1 (P0P9)
acpicpu0 at acpi0
acpicpu1 at acpi0
acpicpu2 at acpi0
acpicpu3 at acpi0
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: PWRB
bios0: ROM list: 0xc/0xe200 0xce800/0x1000
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x02
ppb0 at pci0 dev 1 function 0 "Intel 82G33 PCIE" rev 0x02: apic 4 int 16 (irq 5)
pci1 at ppb0 bus 5
vga1 at pci1 dev 0 function 0 "NVIDIA GeForce 9300 GE" rev 0xa1
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
uhci0 at pci0 dev 26 function 0 "Intel 82801I USB" rev 0x02: apic 4 int 16 (irq
5)
uhci1 at pci0 dev 26 function 1 "Intel 82801I USB" rev 0x02: apic 4 int 21 (irq
3)
ehci0 at pci0 dev 26 function 7 "Intel 82801I USB" rev 0x02: apic 4 int 18 (irq
10)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb1 at pci0 dev 28 function 0 "Intel 82801I PCIE" rev 0x02: apic 4 int 17 (irq
11)
pci2 at ppb1 bus 3
ppb2 at pci2 dev 0 function 0 vendor "Creative Labs", unknown product 0x7006 rev
0x00
pci3 at ppb2 bus 4
azalia0 at pci3 dev 0 function 0 vendor "Creative Labs", unknown product 0x0009
rev 0x00: apic 4 int
Re: panic on 08 jan 2009 snapshot. **update**
On Fri, Jan 09, 2009 at 09:26:00PM -0800, Bryan wrote: > On Fri, Jan 9, 2009 at 9:16 PM, Bryan wrote: > > Greetings, > > > > previous snapshots were able to boot with no issues. I'm using > > GENERIC.MP, and the panic occurs when using GENERIC.SP. be sure to sendbug(1) this if you have not yet; remember a few times sendbug in this situation that being specifically requested. some devs don't read m...@. -- jared
Re: panic on 08 jan 2009 snapshot. **update**
On Fri, Jan 9, 2009 at 9:16 PM, Bryan wrote: > Greetings, > > previous snapshots were able to boot with no issues. I'm using > GENERIC.MP, and the panic occurs when using GENERIC.SP. > > here is the panic message: (typed) > > > npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 > uvm_fault(0xd080c660, 0x12e52000, 0, 3) -> e > kernel: page fault trap, code=0 > stopped at apic_vectorset+0x50: movl > %esi,apic_maxlevel(,%eax,4) > apic_vectorset(d3f1d800,0,ff,0,0) at apic_vectorset+0x50 > ioapic_enable(d080c660,0,d0965fa0,d034d1a3,d08c1720) at ioapic_enable+0x8f > cpu_configure(d08c1720,1,3,0,2) at cpu_configure+0x42 > main(0,0,0,0,0) at main+0x3a7 > > > I do not have my pci serial port card yet (comes in Tuesday..., so I > took screenshots of the dmesg, PS and TRACE. > > here is the *typed* output of trace: > > ddb(0)>trace > apic_vectorset(d3f1d800,0,ff,0,0) at apic_vectorset+0x50 > ioapic_enable(d080c660,0,d0965fa0,d034d1a3,d08c1720) at ioapic_enable+0x8f > cpu_configure(d08c1720,1,3,0,2) at cpu_configure+ > > > ps output can be found here: (until I get my serial port card, this > is the best I can do.) > http://picasaweb.google.com/lh/photo/l7IN31cOVXa1y8yn74aA8w?feat=directlink > > link to the dmesg, ps, and trace can be found in this album: > > http://picasaweb.google.com/brakeb/CrashUsing08jan2009Snapshot?feat=directlink > > > please advise. I originally thought that this panic was due to the > re(4) that was not reset. > I can reproduce this. I first received this error right after I did > the 08 jan 2009 snapshot. I did mention this earlier to the list, and > was told by theo that the 06 jan snapshot would fix this, and it did > seem to fix this, and I was able to even use re(4). > > To reproduce the re(4) error, I can boot into Vista, shutdown, and > boot into OpenBSD. > > After the panic, I hold the power button for 4 seconds, and then boot > back up. the error goes away, as you can see at the bottom of picture > number 4. but it still panics, now on something else. I am unable to > get to a login, so I can't do patches. I can wait for snapshots. > > I apologize for the "stream of consciousness", I just want to make > sure that any questions that anyone might have are answered... > > Regards, > Bryan Brake > Greetings, One other thing I found. Don't know if it means anything, but when I rebooted and enabled "verbose" output, the system panics shortly after it scans pcic2: typed as seen: >>> probing for pcic0 >>> probing for pcic0 failed >>> probing for pcic1 >>> probing for pcic1 failed >>> probing for pcic2 >>> probing for pcic2 failed uvm_fault(0xd080c660, 0x12e52000, 0, 3) -> e kernel: page fault trap, code=0 stopped at apic_vectorset+0x50: movl %esi,apic_maxlevel(,%eax,4) apic_vectorset(d3f1d800,0,ff,0,0) at apic_vectorset+0x50 ioapic_enable(d080c660,0,d0965fa0,d034d1a3,d08c1720) at ioapic_enable+0x8f cpu_configure(d08c1720,1,3,0,2) at cpu_configure+0x42 main(0,0,0,0,0) at main+0x3a7 Regards, Bryan Brake
panic on 08 jan 2009 snapshot.
Greetings, previous snapshots were able to boot with no issues. I'm using GENERIC.MP, and the panic occurs when using GENERIC.SP. here is the panic message: (typed) npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 uvm_fault(0xd080c660, 0x12e52000, 0, 3) -> e kernel: page fault trap, code=0 stopped at apic_vectorset+0x50: movl %esi,apic_maxlevel(,%eax,4) apic_vectorset(d3f1d800,0,ff,0,0) at apic_vectorset+0x50 ioapic_enable(d080c660,0,d0965fa0,d034d1a3,d08c1720) at ioapic_enable+0x8f cpu_configure(d08c1720,1,3,0,2) at cpu_configure+0x42 main(0,0,0,0,0) at main+0x3a7 I do not have my pci serial port card yet (comes in Tuesday..., so I took screenshots of the dmesg, PS and TRACE. here is the *typed* output of trace: ddb(0)>trace apic_vectorset(d3f1d800,0,ff,0,0) at apic_vectorset+0x50 ioapic_enable(d080c660,0,d0965fa0,d034d1a3,d08c1720) at ioapic_enable+0x8f cpu_configure(d08c1720,1,3,0,2) at cpu_configure+ ps output can be found here: (until I get my serial port card, this is the best I can do.) http://picasaweb.google.com/lh/photo/l7IN31cOVXa1y8yn74aA8w?feat=directlink link to the dmesg, ps, and trace can be found in this album: http://picasaweb.google.com/brakeb/CrashUsing08jan2009Snapshot?feat=directlink please advise. I originally thought that this panic was due to the re(4) that was not reset. I can reproduce this. I first received this error right after I did the 08 jan 2009 snapshot. I did mention this earlier to the list, and was told by theo that the 06 jan snapshot would fix this, and it did seem to fix this, and I was able to even use re(4). To reproduce the re(4) error, I can boot into Vista, shutdown, and boot into OpenBSD. After the panic, I hold the power button for 4 seconds, and then boot back up. the error goes away, as you can see at the bottom of picture number 4. but it still panics, now on something else. I am unable to get to a login, so I can't do patches. I can wait for snapshots. I apologize for the "stream of consciousness", I just want to make sure that any questions that anyone might have are answered... Regards, Bryan Brake
FYI: USB rum0 + wep [not equal] network (Jan 23 snapshot)
I acquired an old dell laptop a couple of weeks ago which I went ahead
and put OpenBSD on it. I had everything installed and running fine,
and turned to a local available hot-spot with no wep and began
downloading various packages from ftp without issue via a usb 2.0 asus
wl-167g on top of a generic usb 2.0 pcmcia card.
Then I take the laptop home where I have an older openbsd 4.2 pc
serving as my firewall and wireless access point with WEP using the
ral driver. I plugged away on the laptop hard trying to get internet
access through my access point but without success.
I know the access point is configured via pf correctly because my son
is using his ds/psp on it without issue to access the internet/games
from various locations around the house.
Then I stuck on the handy but absolutely no range no-name zydas
wireless adapter and, when I was in the room where the access point
was located I had internet access through my access point. You will
see however at the end of the dmesg that zydas adapter seems to have a
problem of it's own.
I wish I had kept it (and of course being the [l]user I am I didn't),
but from the access point I was doing a tcpdump when I had the
dhclient requesting an ip address via the rum0 driver. It looked to me
that the access point could see the request and attempted to send the
laptop an ip address, but for whatever reason the rum driver wasn't
picking up the response.
Thanks team! Keep up the good work!
OpenBSD 4.2-current (GENERIC) #651: Tue Jan 22 17:34:45 MST 2008
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class) 498 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 536358912 (511MB)
avail mem = 510722048 (487MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 08/16/00, BIOS32 rev. 0 @
0xffe90, SMBIOS rev. 2.3 @ 0xf64d0 (58 entries)
bios0: vendor Dell Computer Corporation version "A07" date 08/16/2000
bios0: Dell Computer Corporation Latitude CPx H500GT
apm0 at bios0: Power Management spec V1.2
apm0: battery life expectancy 73%
apm0: AC off, battery charge high, estimated 2:52 hours
acpi at bios0 function 0x0 not configured
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfbd60/128 (6 entries)
pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371 ISA and IDE" rev 0x00)
pcibios0: PCI bus #3 is the last bus
bios0: ROM list: 0xc/0x1
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
agp0 at pchb0: aperture at 0xf400, size 0x400
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "ATI Mobility 1" rev 0x64
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
cbb0 at pci0 dev 3 function 0 "TI PCI1225 CardBus" rev 0x01: irq 11
cbb1 at pci0 dev 3 function 1 "TI PCI1225 CardBus" rev 0x01: irq 11
piixpcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 19077MB, 39070080 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: SCSI0
5/cdrom removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 7 function 2 "Intel 82371AB USB" rev 0x01: irq 11
piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x03: SMI
iic0 at piixpm0
spdmem0 at iic0 addr 0x50: 256MB SDRAM non-parity PC100CL2
maestro0 at pci0 dev 8 function 0 "ESS Maestro 2E" rev 0x10: irq 5
ac97: codec id 0x83847609 (SigmaTel STAC9721/23)
ac97: codec features 18 bit DAC, 18 bit ADC, SigmaTel 3D
audio0 at maestro0
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 2 device 0 cacheline 0x8, lattimer 0x20
pcmcia0 at cardslot0
cardslot1 at cbb1 slot 1 flags 0
cardbus1 at cardslot1: bus 3 device 0 cacheline 0x8, lattimer 0x20
pcmcia1 at cardslot1
isa0 at piixpcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
biomask ef4d netmask ef4d
Allen Delong, Out of Office-Jan. 02
Many thanks for your note. I am out of the office until Tuesday, January 2. I will be checking email infrequently during this time, but will return your message on my return. best wishes for a happy new year.
CanSecWest 2007 (April 18-20) Call For Papers (Deadline Jan 7th)
CanSecWest 2007 CALL FOR PAPERS VANCOUVER, Canada -- The eighth annual CanSecWest applied technical security conference - where the eminent figures in the international security industry will get together share best practices and technology - will be held in downtown Vancouver at the the Mariott Renaissance Harbourside on April 18-20, 2007. The most significant new discoveries about computer network hack attacks and defenses, commercial security solutions, and pragmatic real world security experience will be presented in a series of informative tutorials. The CanSecWest 2007 meeting provides international researchers a relaxed, comfortable environment to learn from informative tutorials on key developments in security technology, and collaborate and socialize with their peers in one of the world's most scenic cities - a short drive away from one of North America's top skiing areas. The CanSecWest 2007 conference will also feature the availability of the Security Masters Dojo expert network security sensei instructors, and their advanced, and intermediate, hands-on training courses - featuring small class sizes and practical application excercises to maximize information transfer. We would like to announce the opportunity to submit papers, and/or lightning talk proposals, for selection by the CanSecWest technical review committee. Please make your paper proposal submissions before January 7th, 2007. Slides for the papers must be submitted by March 15th, 2007. Some invited papers have been confirmed, but a limited number of speaking slots are still available. The conference is responsible for travel and accomodations for the speakers. If you have a proposal for a tutorial session then please email a synopsis of the material and your biography, papers and, speaking background to [EMAIL PROTECTED] Only slides will be needed for the March paper deadline, full text does not have to be submitted - but will be accepted if available. The CanSecWest 2007 conference consists of tutorials on technical details about current issues, innovative techniques and best practices in the information security realm. The audiences are a multi-national mix of professionals involved on a daily basis with security work: security product vendors, programmers, security officers, and network administrators. We give preference to technical details and new education for a technical audience. The conference itself is a single track series of presentations in a lecture theater environment. The presentations offer speakers the opportunity to showcase on-going research and collaborate with peers while educating and highlighting advancements in security products and techniques. The focus is on innovation, tutorials, and education instead of product pitches. Some commercial content is tolerated, but it needs to be backed up by a technical presenter - either giving a valuable tutorial and best practices instruction or detailing significant new technology in the products. Paper proposals should consist of the following information: 1) Presenter, and geographical location (country of origin/passport) and contact info (e-mail, postal address, phone, fax). 2) Employer and/or affiliations. 3) Brief biography, list of publications and papers. 4) Any significant presentation and educational experience/background. 5) Topic synopsis, Proposed paper title, and a one paragraph description. 6) Reason why this material is innovative or significant or an important tutorial. 7) Optionally, any samples of prepared material or outlines ready. 8) Will you have full text available or only slides? 9) Please list any other publications or conferences where this material has been or will be published/submitted. Please include the plain text version of this information in your email as well as any file, pdf, sxw, ppt, or html attachments. (Some reviewers only look at .txt info.) Multiple submissions are acceptable. Please forward the above information to be considered for placement on the speaker roster, or have your short lightning talk scheduled. Send all conference related correspondence to [EMAIL PROTECTED] thanks, --dr -- World Security Pros. Cutting Edge Training, Tools, and Techniques London, U.K.Feb 28 / Mar 1 - 2007http://eusecwest.com pgpkey http://dragos.com/ kyxpgp
nForce4/amd64 x2: wd/console problems [jan 30 snapshot]
hello, i think i saw something similar on the list a bit earlier. tried nForce4 mobo with amd64 x2 cpu and bsd.mp (jan 30 snapshot). have got lotsa wd problems so serious so the system even drops to ddb (see below). yeah, and there are problems besides wdX - i could not login to the system, since when i entered login/password for root the console locked up hardly and it looked like return key stuck and generates key pressed events. uniprocessor kernel boots and seems to be working okay. bsd.mp i386 (seems to be a jan 24 snapshots), boots and seems to be working okay. i have unlimited access to the box, so i can check whatever version needed. >> OpenBSD/amd64 BOOT 2.11 boot> bsd.mp booting hd0a:bsd.mp: 3730180+693964+598712+0+428752 [80+313992+194403]=0x9b100c entry point at 0x1001e0 [7205c766, 3404, 24448b12, 5e60a304]B*C?[ using 509248 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2006 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 3.9-beta (GENERIC.MP) #710: Mon Jan 30 13:49:52 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1073278976 (1048124K) avail mem = 908484608 (887192K) using 22937 buffers containing 107536384 bytes (105016K) of memory mainbus0 (root) mainbus0: Intel MP Specification (Version 1.4) (OEM0 PROD) cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, 2010.52 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,NXE,MMXX,FFXSR,LONG, 3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 201MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+, 2010.30 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,NXE,MMXX,FFXSR,LONG, 3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mpbios: bus 0 is type PCI mpbios: bus 1 is type PCI mpbios: bus 2 is type PCI mpbios: bus 3 is type PCI mpbios: bus 4 is type PCI mpbios: bus 5 is type PCI mpbios: bus 6 is type ISA ioapic0 at mainbus0 apid 2: pa 0x81ba5f24, version 11, 24 pins ioapic0: misconfigured as apic 0 ioapic0: remapped to apic 2 pci0 at mainbus0 bus 0: configuration mode 1 "Nvidia nForce4 DDR" rev 0xa3 at pci0 dev 0 function 0 not configured pcib0 at pci0 dev 1 function 0 "Nvidia nForce4 ISA" rev 0xa3 nviic0 at pci0 dev 1 function 1 "Nvidia nForce4 SMBus" rev 0xa2 iic0 at nviic0 iic1 at nviic0 lm1 at iic1 addr 0x2f: W83791SD ohci0 at pci0 dev 2 function 0 "Nvidia nForce4 USB" rev 0xa2: apic 2 int 5 (irq 5), version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: Nvidia OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0 at pci0 dev 2 function 1 "Nvidia nForce4 USB" rev 0xa3: apic 2 int 3 (irq 3) usb1 at ehci0: USB revision 2.0 uhub1 at usb1 uhub1: Nvidia EHCI root hub, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered auich0 at pci0 dev 4 function 0 "Nvidia nForce4 AC97" rev 0xa2: apic 2 int 11 (irq 11), nForce4 AC97 ac97: codec id 0x414c4790 (Avance Logic ALC850) audio0 at auich0 pciide0 at pci0 dev 6 function 0 "Nvidia nForce4 IDE" rev 0xf2: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: wd0: 16-sector PIO, LBA, 2014MB, 4124736 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 4 pciide1 at pci0 dev 7 function 0 "Nvidia nForce4 SATA 1" rev 0xf3: DMA pciide1: using apic 2 int 5 (irq 11) for native-PCI interrupt pciide2 at pci0 dev 8 function 0 "Nvidia nForce4 SATA 2" rev 0xf3: DMA pciide2: using apic 2 int 11 (irq 5) for native-PCI interrupt ppb0 at pci0 dev 9 function 0 "Nvidia nForce4 PCI-PCI" rev 0xa2 pci1 at ppb0 bus 5 "Texas Instruments TSB43AB22 FireWire" rev 0x00 at pci1 dev 11 function 0 not configured skc0 at pci1 dev 12 function 0 "Marvell Yukon 88E8001/8003/8010" rev 0x13, Marvell Yukon Lite (0x9): apic 2 int 5 (irq 5) sk0 at skc0 port A, address 00:15:f2:1d:20:34 eephy0 at sk0 phy 0: Marvell 88E1011 Gi
Solutions Linux Paris Jan 30 -> Feb 2
Hi, For those who have time to swing by, have a talk with us or even better help out, for the rest of the week, OpenBSD will be at Solutions Linux in the CNIT, Paris la Defense http://www.solutionslinux.fr/fr/index.php Booth slaves welcome Wim. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= https://kd85.com/notforsale.html --
