How to determine my ip address (logged in via ssh)
Hi, is there any gentle way how to determine my ip address if I connected via ssh to an openbsd system? who -m shows only my FQDN, but not all providers provide correct RNDS records. any idea? I'm not a c programmer, so a way using bash or perl would be fine. Falk
Re: How to determine my ip address (logged in via ssh)
Hi, On Fri, Jan 09, 2009 at 10:14:19AM +0100, Falk Brockerhoff wrote: Hi, is there any gentle way how to determine my ip address if I connected via ssh to an openbsd system? who -m shows only my FQDN, but not all providers provide correct RNDS records. You could check SSH_CLIENT enviroment any idea? I'm not a c programmer, so a way using bash or perl would be fine. Falk Regards Robert -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: Hey guys you left some holes out there!
Re: How to determine my ip address (logged in via ssh)
Falk Brockerhoff wrote: is there any gentle way how to determine my ip address if I connected via ssh to an openbsd system? echo $SSH_CLIENT | cut -f1 -d' ' -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
i386 kernel panic with 1/9/09 snapshot
Hi This is the first problem I've had with OpenBSD, I think I've attached all relevant information but if i've neglected anything please let me know. I'm getting the following panic at boot time with the latest snapshot dated 1/9/09 uvm_fault(0xd08084a0, 0x12e3e000, 0, 3) - e kernel: page fault trap, code=0 Stopped at apic_vectorset+0x50:movl%esi,apic_maxlevel(,%eax,4) apic_vectorset(d128fb00,0,ff,0,0) at apic_vectorset+0x50 ioapic_enable(d08084a0,0,d0961fa0,d034bc99,d08bd540) at ioapic_enable+0x8f cpu_configure(d08bd540,1,3,0,2) at cpu_configure+0x42 main(0,0,0,0,0) at main+0x399 ddb trace apic_vectorset(d128fb00,0,ff,0,0) at apic_vectorset+0x50 ioapic_enable(d08084a0,0,d0961fa0,d034bc99,d08bd540) at ioapic_enable+0x8f cpu_configure(d08bd540,1,3,0,2) at cpu_configure+0x42 main(0,0,0,0,0) at main+0x399 ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND *0 -1 0 0 7 0x80200swapper ddb show registers ds 0x10 es 0x10 fs 0x58 gs 0 edi 0xff esi0 ebp 0xd0961ef8end+0xa1e54 ebx 0xd12a8800end+0x9e875c edx 0xd12a8800end+0x9e875c ecx 0xd128fb00end+0x9cfa5c eax 0xd0960334end+0xa0290 eip 0xd06256fcapic_vectorset+0x50 cs 0x8 eflags 0x10246 esp 0xd0961ed0end+0xa1e2c ss0xd0960010end+0x9ff6c apic_vectorset+0x50:movl%esi,apic_maxlevel(,%eax,4) ddb Here's the dmesg leading up to the panic Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2009 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.4-current (GENERIC) #1647: Thu Jan 8 15:25:01 MST 2009 t...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) 4 CPU 3.00GHz (GenuineIntel 686-class) 3.01 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,CNXT-ID,xTPR real mem = 535834624 (511MB) avail mem = 509853696 (486MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 06/16/05, BIOS32 rev. 0 @ 0xfd5b6, SMBIOS rev. 2.33 @ 0x1ff77000 (46 entries) bios0: vendor IBM version -[KEE134AUS-1.34]- date 06/16/2005 bios0: IBM CORPORATION -[8482ENY]- acpi0 at bios0: rev 0 acpi0: tables DSDT FACP APIC BOOT ASF! acpi0: wakeup devices CSA_(S4) PCIX(S4) PCIB(S4) COM1(S4) COM2(S4) KBC0(S4) MSE0(S4) USB1(S1) USB2(S1) EUSB(S1) 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 202MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic1 at mainbus0: apid 2 pa 0xfec1, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (CSA_) acpiprt2 at acpi0: bus 3 (PCIX) acpiprt3 at acpi0: bus 4 (PCIB) acpicpu0 at acpi0: C3 acpibtn0 at acpi0: PWRB bios0: ROM list: 0xc/0x9000 0xc9000/0x1000 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82875P Host rev 0x02 ppb0 at pci0 dev 3 function 0 Intel 82875P CSA rev 0x02 pci1 at ppb0 bus 2 em0 at pci1 dev 1 function 0 Intel PRO/1000CT (82547GI) rev 0x00: apic 1 int 18 (irq 5), address 00:11:25:ab:fc:41 ppb1 at pci0 dev 28 function 0 Intel 6300ESB PCIX rev 0x02 pci2 at ppb1 bus 3 uhci0 at pci0 dev 29 function 0 Intel 6300ESB USB rev 0x02: apic 1 int 16 (irq 11) uhci1 at pci0 dev 29 function 1 Intel 6300ESB USB rev 0x02: apic 1 int 19 (irq 5) Intel 6300ESB WDT rev 0x02 at pci0 dev 29 function 4 not configured Intel 6300ESB APIC rev 0x02 at pci0 dev 29 function 5 not configured ehci0 at pci0 dev 29 function 7 Intel 6300ESB USB rev 0x02: apic 1 int 23 (irq 11) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb2 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0x0a pci3 at ppb2 bus 4 vga1 at pci3 dev 2 function 0 ATI Radeon VE rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 1 int 16 (irq 11) drm0 at radeondrm0 ichpcib0 at pci0 dev 31 function 0 Intel 6300ESB LPC rev 0x02 pciide0 at pci0 dev 31 function 2 Intel 6300ESB SATA rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility atapiscsi0 at pciide0 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets, initiator 7 cd0 at scsibus0 targ 0 lun 0: LITE-ON, CD-ROM LTN-489S, 8US5 ATAPI 5/cdrom removable atapiscsi1 at pciide0 channel 0 drive 1 scsibus1 at atapiscsi1: 2 targets, initiator 7 cd1 at scsibus1 targ 0 lun 0: PHILIPS, DVDR1640P, P2.0 ATAPI 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 cd1(pciide0:0:1): using PIO mode 4, Ultra-DMA
Create a bootable usb key?
Hello, I tried to install openbsd on my eeepc 1000H (without external cdrom). I don't have any openbsd system installed. As I don't know how to make a bootable install media on a usb key, I installed a complete openbsd system on my usb key from Linux by using qemu. It worked fine. I modified fstab to be able to run openbsd system from the usb key. I rebooted my eeepc on the USB Key and I have the openbsd that is running... Cool. It's cool but now I'd like to install openbsd from the usb key to the hard disk. I created a 10G OpenBSD partition from Linux so I have a partition available on my disk. Is there an equivalent of the debian debootstrap or is it better to create a bootable key (but how)? Is the only solution is to use disklabel on the hard disk, create partitions (not very easy to know the size of the partition and good offset) and copy files? Is it possible to run the installer from the openbsd that is on my usb key? Thanks for your help, Guillaume
Re: Create a bootable usb key?
On Fri, Jan 9, 2009 at 12:46 PM, Guillaume Thouvenin guillaume.thouve...@polymtl.ca wrote: It's cool but now I'd like to install openbsd from the usb key to the hard disk. I created a 10G OpenBSD partition from Linux so I have a partition available on my disk. Is there an equivalent of the debian debootstrap or is it better to create a bootable key (but how)? Is the only solution is to use disklabel on the hard disk, create partitions (not very easy to know the size of the partition and good offset) and copy files? Is it possible to run the installer from the openbsd that is on my usb key? Put the bsd.rd kernel on your usb key, type bsd.rd at the boot prompt, and install.
Re: Create a bootable usb key?
On Fri, 09 Jan 2009 18:46:04 +0100, Guillaume Thouvenin wrote ...Is it possible to run the installer from the openbsd that is on my usb key? Sure. Assuming you installed the bsd.rd kernel, all you need do is use that kernel instead: boot bsd.rd
Re: Create a bootable usb key?
Guillaume Thouvenin wrote: Is it possible to run the installer from the openbsd that is on my usb key? The way I did it was to boot /bsd.rd and then do an installation to the USB key but installing a single set, bsd.rd, and only that set. Then after booting back to the regular system mounted the stick and added /etc/boot.conf by hand. What I'd like to do eventually is set up grub or something so I have a menu to choose the different options 4.3, 4.4, release, stable, current, i386, amd64, etc. Regards, -Lars
4.4 is getting stuck
Yesterday I upgraded my last production box (remote) from 4.3 to 4.4., without any hitch, rebooted, and so forth. Last night at some innocuous time, it stopped accepting incoming mail (postfix). This morning, it did courier-imap well, until I used an existing ssh-session like this: # pwd /usr/src/usr.sbin/httpd # cd /var/log/ # /usr/local/sbin/post postalias postfix postkick postqueue postcat postfix-disable postlock postsuper postconfpostfix-enable postlog postdroppostfix-install postmap # /usr/local/sbin/postfix status ^C^Z Now it is stuck like this for an hour or so. It still takes keyboard input, though. Courier-imag also does not respond any longer. But nmap is still somewhat okay: $ nmap -sV 172.16.0.4 Starting Nmap 4.68 ( http://nmap.org ) at 2009-01-10 08:58 SGT Interesting ports on 172.16.0.4: Not shown: 1707 closed ports PORTSTATE SERVICE VERSION 13/tcp open daytime 22/tcp open ssh? 25/tcp open smtp? 37/tcp open time (32 bits) 53/tcp open domain? 80/tcp open httpApache httpd 110/tcp open pop3? 993/tcp open imaps? daytime works fine, http works very well, but domain, pop3 and smtp time out; or worse: all get stuck like here: $ telnet 172.16.0.4 25 Trying 172.16.0.4... Connected to 172.16.0.4. Escape character is '^]'. helo mail from:m...@gmail.com quit ^C^Z $ telnet 172.16.0.4 110 Trying 172.16.0.4... Connected to 172.16.0.4. Escape character is '^]'. user udippel Why do I write in: 1. I have no access. It is a remote production server. If I only could stop that 'hanging' postfix, I might be able to issue a 'reboot' 2. Any further trial to ssh into it also get stuck like this: $ ssh -v 172.16.0.4 OpenSSH_5.1, OpenSSL 0.9.7j 04 May 2006 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to 172.16.0.4 [172.16.0.4] port 22. debug1: Connection established. debug1: identity file /home/users/udippel/.ssh/identity type -1 debug1: identity file /home/users/udippel/.ssh/id_rsa type -1 debug1: identity file /home/users/udippel/.ssh/id_dsa type -1 after which I can only leave by killing the session on the client. 3. Even if I went there with a huge effort, and some time delay, how can I debug the problem, so that it won't occur again? Thanks for all ideas, Uwe
Re: Getting the Thinkpad X200 working fully under OpenBSD
On Sat, Jan 3, 2009 at 5:43 AM, Robert rob...@openbsd.pap.st wrote: Everything now works with -current. I've never had much luck with the intel driver, even with somewhat recent snapshots. When I try and use it, it bombs out with an Unable to map mmio range error, then says that the server has segfaulted. I'd like to try and do some X debugging, but it seems like if I try and build X, it then interferes with the currently installed X somehow, which I can't really have on this machine (I could be wrong, however). The vesa driver works, though Xorg.0.log ends up spamming (==) VESA(0): Write-combining range (0x0,0x1000) was already clear (==) VESA(0): Write-combining range (0x0,0x1000) was already clear eventually and continuously. [1] A catch to get the X intel(4) working for me: The X200 reports two outputs/monitors that have to be disabled. (This might mess with the dockingstation, but i don't have one of those.) This didn't help -- same error. Dmesg: (ignore the stuff about sd1, I keep an empty SD-microSD converter in there) OpenBSD 4.4-current (GENERIC.MP) #2050: Sun Jan 4 13:27:04 MST 2009 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3177910272 (3030MB) avail mem = 3069816832 (2927MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (62 entries) bios0: vendor LENOVO version 6DET28WW (1.05 ) date 07/30/2008 bios0: LENOVO 745533M acpi0 at bios0: rev 2 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET SLIC BOOT ASF! SSDT TCPA SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(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) Core(TM)2 Duo CPU P8600 @ 2.40GHz, 2394.34 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,VMX,SMX,EST,TM2,CX16,xTPR,NXE,LONG cpu0: 3MB 64b/line 8-way L2 cache cpu0: apic clock running at 265MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz, 2394.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,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,CX16,xTPR,NXE,LONG cpu1: 3MB 64b/line 8-way L2 cache ioapic0 at mainbus0 apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 5 (EXP3) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpitz0 at acpi0: critical temperature 127 degC acpitz1 at acpi0: critical temperature 104 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4536 serial 458 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock at acpi0 not configured acpivideo at acpi0 not configured acpivideo at acpi0 not configured cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2401, 2400, 1600, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 Intel GM45 Host rev 0x07 vga1 at pci0 dev 2 function 0 Intel GM45 Video rev 0x07 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 0xd000, size 0x1000 inteldrm0 at vga1: apic 1 int 16 (irq 11) drm0 at inteldrm0 Intel GM45 Video rev 0x07 at pci0 dev 2 function 1 not configured Intel GM45 HECI rev 0x07 at pci0 dev 3 function 0 not configured em0 at pci0 dev 25 function 0 Intel ICH9 IGP M AMT rev 0x03: apic 1 int 20 (irq 11), address 00:1f:16:08:ed:7a uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x03: apic 1 int 20 (irq 11) uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x03: apic 1 int 21 (irq 11) uhci2 at pci0 dev 26 function 2 Intel 82801I USB rev 0x03: apic 1 int 22 (irq 11) ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x03: apic 1 int 23 (irq 11) 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 82801I HD Audio rev 0x03: apic 1 int 17 (irq 11) azalia0: codecs: Conexant CX20561 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x03: apic 1 int 20 (irq 11) pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 Intel 82801I PCIE rev 0x03: apic 1 int 21 (irq 11) pci2 at ppb1 bus 3 iwn0 at pci2 dev 0 function 0 Intel WiFi Link 5300AGN rev 0x00: apic 1 int 17 (irq 11), MIMO 3T3R, MoW, address 00:16:ea:e4:8f:b6 ppb2 at pci0 dev 28 function 2 Intel 82801I PCIE rev 0x03: apic 1 int 22 (irq 11) pci3
Re: Getting the Thinkpad X200 working fully under OpenBSD
On Sat, 10 Jan 2009 12:14:59 +1100 Dana impati...@gmail.com wrote: On Sat, Jan 3, 2009 at 5:43 AM, Robert rob...@openbsd.pap.st wrote: Everything now works with -current. Hi, I've never had much luck with the intel driver, even with somewhat recent snapshots. I am using intel(4) exclusivly without any problems. When I try and use it, it bombs out with an Unable to map mmio range error, then says that the server has segfaulted. Never seen that msg before. I'd like to try and do some X debugging, but it seems like if I try and build X, it then interferes with the currently installed X somehow, which I can't really have on this machine (I could be wrong, however). The vesa driver works, though Xorg.0.log ends up spamming (==) VESA(0): Write-combining range (0x0,0x1000) was already clear (==) VESA(0): Write-combining range (0x0,0x1000) was already clear eventually and continuously. That one neither. There should be no need to compile X yourself to get this working. I'm using snapshots on my X200. [1] A catch to get the X intel(4) working for me: The X200 reports two outputs/monitors that have to be disabled. (This might mess with the dockingstation, but i don't have one of those.) This didn't help -- same error. intel(4) worked for me even without those options, but i got a screen stitched together of 1024x768 tiles. Dmesg: (ignore the stuff about sd1, I keep an empty SD-microSD converter in there) OpenBSD 4.4-current (GENERIC.MP) #2050: Sun Jan 4 13:27:04 MST 2009 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP I'm using a newer kernel built from source but an older snapshot. (Yeah yeah, kernel and userland out of sync, i know what i have to do before i cry for help.) To check if there are regressions concerning your problem i'm gonna update to the latest snapshot and report back. Which gets me to a gut feeling: Have you updated/sysmerge'd the coresponding xetc44.tgz? - Robert
Re: Getting the Thinkpad X200 working fully under OpenBSD
On Sat, 10 Jan 2009 02:58:12 +0100 Robert rob...@openbsd.pap.st wrote: To check if there are regressions concerning your problem i'm gonna update to the latest snapshot and report back. intel(4) is still working for me with this snapshot. OpenBSD 4.4-current (GENERIC.MP) #2058: Thu Jan 8 15:39:31 MST 2009 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP - Robert
Re: [PF] IPSEC and PF/RDR rule
Hi,
I have problem on the same field. OpenBSD router with external ip is
redirecting traffic on the port 80:
# router (pf.conf)
rdr pass on ! lo inet proto tcp from any to (self) port = www -
172.16.0.53
but the 172.16.0.53 is connected to the router with ipsec(4):
# router (ipsec.conf)
ike passive esp tunnel \
from { \
172.16.0.0/16 \
192.168.1.0/24 \
192.168.2.0/24 \
192.168.3.0/24 \
} to any \
srcid my-openbsd-router.home.lan
# 172.16.0.53 (ipsec.conf)
ike dynamic esp tunnel \
from egress to 192.168.2.0/24 \
peer my-openbsd-router-external-ip dstid
my-openbsd-router.home.lan
ike dynamic esp tunnel \
from egress to 192.168.3.0/24 \
peer my-openbsd-router-external-ip dstid
my-openbsd-router.home.lan
When I'm in 192.168.2.0/24 network and my laptop has no ipsec configured
I still can reach external ip of my router and traffic is redirected to the
172.16.0.53 web server, but when I'm connecting from outside world I
cannot reach the web server. From my configuration files I can see that
shouldn't work, but I don't know how to alter my configuration to make
it work. Could someone shed some light on this for me please? Thanks.
# router
OpenBSD 4.4-current (GENERIC) #1050: Wed Sep 10 12:18:05 MDT 2008
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
# web server
OpenBSD 4.4-current (GENERIC) #1643: Tue Dec 30 13:50:47 MST 2008
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
--
best regards
q#
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) dmesg output 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
Re: panic on 08 jan 2009 snapshot. **update**
On Fri, Jan 9, 2009 at 9:16 PM, Bryan bra...@gmail.com 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) dmesg output 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
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 bra...@gmail.com 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
