Re: kernel debugging when booted off install cd
On Sun, 5 Feb 2006, Nick Holland wrote: Charles Sprickman wrote: Hello all, I'm still not able to get OpenBSD 3.4-3.8 loaded on my old firewall box. It either freezes or panics when probing (or creating?) rd0, which I assume is the ramdisk used in the install. It runs 3.3 fine. So rather than just asking some random questions, I'd like to know how to save a dump when booting off of the install CD. I do have a serial console available (set tty com0). If getting a dump isn't possible, I'd then like to know how to get into the kernel debugger. I figure that I can gather information that's more helpful this way. You aren't going to get nor save a dump when booting off the install CD. You really don't want a panicked kernel writing to your good data disks, do you? In this case, I don't mind. I've got another box in it's place so I'm prepared to do anything I need to do to get this running a current version of OBSD. The install kernels don't have all the bells and whistles of the production kernel, that's how they fit on floppies and such. Got it, so there's absolutely no way to dump to a disk? It looks like it tries to... I also don't have another box handy to build a custom 3.8 kernel on. And I also wonder if a non-rd kernel would panic, as the panic happens as it tries to deal with the ramdisk... Use your serial cable to capture the output of the boot process. THAT will tell us much more about your hardware. I've got a thread here: http://marc.theaimsgroup.com/?t=11366659953r=1w=2 I reposted since I just wanted to get the basics on getting a dump in OBSD. I figured once I had that, I could actually file a PR or something. A completely Wild A..ed Guess, based on the symptoms, you may have way too little RAM for the newer kernels (16M will get you running still, but 32M is a practical minimum) and floating point emulation broke after 3.3 on i386 (translation: no more 486sx or 80386 w/o 80387 support). If I were to bet, I'd say you probably have no FPU on your machine. It's old, but not that old. I've got 128MB of RAM. Processor is an AMD K6-2/500 clocked down to 300. VIA chipset. I've had memtest86+ go through about a dozen runs with no errors. 3.3 works flawlessly. Not sure where to go from here... Thanks, Charles Nick.
Re: kernel debugging when booted off install cd
On Fri, 3 Feb 2006, Rogier Krieger wrote: On 2/3/06, Charles Sprickman [EMAIL PROTECTED] wrote: It either freezes or panics when probing (or creating?) rd0, which I assume is the ramdisk used in the install. It runs 3.3 fine. Perhaps you need to look at the FAQ if you're running i386: upgrading/reinstalling OpenBSD/i386 using bsd.rd-a.out [1]. Excellent, I did not know how to boot an ELF kernel from the a.out bootloader. If that doesn't solve your problem, a dmesg would be your best bet. Information from a panic (trace/ps, obtained through the debugger you get dropped into) would also be helpful. Since you mentioned you have a serial console available, I recommend using it to file a report. OK, so I grabbed the 3.5 bsd.rd-a.out and I get the same results. Instant panic, and then a reboot. dump to 1001 dump error 19 How can I go about getting it to crash into the debugger? Thanks, Charles Upon freezes, I usually try to boot into the UKC to set the verbose option. Typically, this gave me a hint in devices to disable. As a sidenote: my own usual culprit is the ahc(4) driver. That said, this only happens with two machines, each having an nVidia nForce2 chipset. Given that you mentioned rd0 as a problem point, I doubt you are having the same underlying problem. Cheers, Rogier References: 1. OpenBSD FAQ - Upgrading/reinstalling OpenBSD/i386 using bsd.rd-a.out http://www.openbsd.org/faq/faq4.html#bsdrdaout -- If you don't know where you're going, any road will get you there.
kernel debugging when booted off install cd
Hello all, I'm still not able to get OpenBSD 3.4-3.8 loaded on my old firewall box. It either freezes or panics when probing (or creating?) rd0, which I assume is the ramdisk used in the install. It runs 3.3 fine. So rather than just asking some random questions, I'd like to know how to save a dump when booting off of the install CD. I do have a serial console available (set tty com0). If getting a dump isn't possible, I'd then like to know how to get into the kernel debugger. I figure that I can gather information that's more helpful this way. Thanks, Charles
Re: 3.8 panic on boot (rd0)
Leaving the history intact, following up below. An offlist reply suggested trying a more recent snapshot of -current. It also paniced in the same place. On Sat, 7 Jan 2006, Kenneth R Westerback wrote: On Sat, Jan 07, 2006 at 03:23:15PM -0500, Charles Sprickman wrote: Hello all, I have an older i386 pc that I've been using as my home firewall for some years now. It currently runs 3.3 and I was hoping to do an upgrade, so I did go ahead and buy the full CD set (impressive packaging, btw) after having trouble with boot floppies (marginal drive) and the boot CD ISO. However, the kernel panics every time I try and boot the 3.8 CD. I've also tried 3.7, 3.6 and 3.5 boot CDs that I downloaded from the OpenBSD ftp server. Hardware seems fine; I ran memtest86+ for a day and it did about 30 passes with no errors, I tried different CD-ROM drives, different IDE cables, removed all network cards, etc., but still it panics in the same place (right after rd0: fixed, 3800 blocks). CPU is an AMD K6-2-500 clocked down to 300 - temperature is fine (about 110F), mainboard is an old Epox. On the suggestion of a bsdforums.org user, I tried downloading bsd.rd and booting that from the 3.3 install, and that failed. I'm guessing it has something to do with the exec format changing; perhaps the old loader doesn't understand the new kernel exec format? rebooting... boot /bsd.rd booting hd0a:/bsd.rd: failed(79). will try /obsd boot ls bsd.rd -rwxr-xr-x 0,0 4658297 hd0a:bsd.rd boot ls obsd -rwxr-xr-x 0,0 2487309 hd0a:obsd boot ...snip... gw# cd / gw# file bsd.rd bsd.rd: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, not stripped gw# file obsd obsd: OpenBSD/i386 demand paged executable not stripped gw# I have this thing hooked up via serial now, so if someone can point me in the right direction (how to get a dump when booting from CD, how to look at that dump, etc.), I will gladly do so. I have also included the 3.3 dmesg below. Thanks, Charles _ I'd suggest trying a 3.8 snapshot as well, to make sure it hasn't already been fixed in -current. I grabbed a snapshot from 1/19 today and burned the mini cd boot iso. Same thing. Where do I go from here to troubleshoot this? It does panic, but I'm not sure how to get a dump when booting off of cd. Thanks, Charles latest boot messages follow, then the older boot messages from 3.8 are still intact below. boot booting cd0a:/3.9/i386/bsd.rd: 4429460+740764 [52+154592+141324]=0x5369c4 entry point at 0x100120 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 (RAMDISK_CD) #1001: Thu Jan 19 12:49:57 MST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: AMD-K6(tm) 3D processor (AuthenticAMD 586-class) 301 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX real mem = 133799936 (130664K) avail mem = 116531200 (113800K) using 1658 buffers containing 6791168 bytes (6632K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(ee) BIOS, date 01/03/00, BIOS32 rev. 0 @ 0xfb390 apm0 at bios0: Power Management spec V1.2 apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xb80c pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdde0/128 (6 entries) pcibios0: PCI Exclusive IRQs: 5 10 11 pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C586 ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x2000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT82C598 PCI rev 0x04 ppb0 at pci0 dev 1 function 0 VIA VT82C598 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Rage Pro rev 0x5c wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) pcib0 at pci0 dev 7 function 0 VIA VT82C586 ISA rev 0x47 pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA33, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: Maxtor 72004 AP wd0: 32-sector PIO, LBA, 1916MB, 3924360 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SAMSUNG, CD-ROM SC-148F, F007 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x02: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered VIA VT82C586 Power rev 0x10 at pci0 dev 7 function 3 not configured sis0 at pci0 dev 17 function 0 NS DP83815 10/100 rev 0x00, DP83816A: irq 10, address 00:09:5b:22:4a:ee nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1 xl0 at pci0 dev 18 function 0 3Com 3c900 10Base-T rev 0x00: irq 5, address 00:a0:24:ce:11:02 isa0 at pcib0
3.8 panic on boot (rd0)
Hello all, I have an older i386 pc that I've been using as my home firewall for some years now. It currently runs 3.3 and I was hoping to do an upgrade, so I did go ahead and buy the full CD set (impressive packaging, btw) after having trouble with boot floppies (marginal drive) and the boot CD ISO. However, the kernel panics every time I try and boot the 3.8 CD. I've also tried 3.7, 3.6 and 3.5 boot CDs that I downloaded from the OpenBSD ftp server. Hardware seems fine; I ran memtest86+ for a day and it did about 30 passes with no errors, I tried different CD-ROM drives, different IDE cables, removed all network cards, etc., but still it panics in the same place (right after rd0: fixed, 3800 blocks). CPU is an AMD K6-2-500 clocked down to 300 - temperature is fine (about 110F), mainboard is an old Epox. On the suggestion of a bsdforums.org user, I tried downloading bsd.rd and booting that from the 3.3 install, and that failed. I'm guessing it has something to do with the exec format changing; perhaps the old loader doesn't understand the new kernel exec format? rebooting... boot /bsd.rd booting hd0a:/bsd.rd: failed(79). will try /obsd boot ls bsd.rd -rwxr-xr-x 0,0 4658297 hd0a:bsd.rd boot ls obsd -rwxr-xr-x 0,0 2487309 hd0a:obsd boot ...snip... gw# cd / gw# file bsd.rd bsd.rd: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, not stripped gw# file obsd obsd: OpenBSD/i386 demand paged executable not stripped gw# I have this thing hooked up via serial now, so if someone can point me in the right direction (how to get a dump when booting from CD, how to look at that dump, etc.), I will gladly do so. I have also included the 3.3 dmesg below. Thanks, Charles _ Here is the partial boot message booting 3.8: OpenBSD/i386 CDBOOT 1.04 boot booting cd0a:/3.8/i386/bsd.rd: 4369156+828044 [52+151072+137381]=0x53b600 entry point at 0x100120 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2005 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 3.8 (RAMDISK_CD) #794: Sat Sep 10 15:58:32 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD cpu0: AMD-K6(tm) 3D processor (AuthenticAMD 586-class) 301 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX real mem = 133799936 (130664K) avail mem = 116502528 (113772K) using 1658 buffers containing 6791168 bytes (6632K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(ee) BIOS, date 01/03/00, BIOS32 rev. 0 @ 0xfb390 apm0 at bios0: Power Management spec V1.2 apm0: flags 70102 dobusy 1 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xf/0xb80c pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdde0/128 (6 entries) pcibios0: PCI Exclusive IRQs: 5 10 11 pcibios0: PCI Interrupt Router at 000:07:0 (VIA VT82C586 ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x2000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 VIA VT82C598 PCI rev 0x04 ppb0 at pci0 dev 1 function 0 VIA VT82C598 AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Rage Pro rev 0x5c wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) pcib0 at pci0 dev 7 function 0 VIA VT82C586 ISA rev 0x47 pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA33, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: Maxtor 72004 AP wd0: 32-sector PIO, LBA, 1916MB, 3924360 sectors wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 atapiscsi0 at pciide0 channel 1 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: SAMSUNG, CD-ROM SC-148F, F007 SCSI0 5/cdrom removable cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2 uhci0 at pci0 dev 7 function 2 VIA VT83C572 USB rev 0x02: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered VIA VT82C586 Power rev 0x10 at pci0 dev 7 function 3 not configured sis0 at pci0 dev 17 function 0 NS DP83815 10/100 rev 0x00: DP83816A, irq 10, address 00:09:5b:22:4a:ee nsphyter0 at sis0 phy 0: DP83815 10/100 PHY, rev. 1 xl0 at pci0 dev 18 function 0 3Com 3c900 10Base-T rev 0x00: irq 5, address 00:a0:24:ce:11:02 isa0 at pcib0 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 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom0: console pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 biomask fbc5 netmask ffe5 ttymask ffe7 rd0: fixed, 3800 blocks fatal page fault in supervisor mode trap type 6 code 2 eip d02b9015 cs 50 eflags 10002 cr2 1ffec1c6 cpl a0 panic: trap type 6, code=2, pc=d02b9015 syncing