Re: Panic on FreeBSD 6.0BETA1

From: Derrick Edwards (dantavious_at_comcast.net)
Date: 08/04/05

  • Next message: Ben Kaduk: "Re: Panic on FreeBSD 6.0BETA1" 
    To: Ben Kaduk <minimarmot@gmail.com>
Date: Thu, 4 Aug 2005 01:31:34 -0400

    On Thursday 04 August 2005 01:00, Ben Kaduk wrote:
            Thanks for the reply,
    I used the following sequence to upgrade my firewall from 5.4 Stable to 6.0
    BETA1 and all worked well. It is my desktop that is giving me the blues.
    After a successful build and install of the kernel, I reboot and attempt to go
    to single user mode to complete the install. After pressing 4 to go to single
    user mode it panics. Since I have the debugging options turned on is there a
    way I capture the pertinent information that you mentioned, without having to
    manually write it :) If so, point me to the documentation and I will have at
    it. Again, thanks for the reply.

    #!/usr/local/bin/bash
    cd /usr/obj
    chflags -R noschg *
    rm -rf *
    /usr/local/bin/cvsup -g -L2 /root/cvs-supfile
    cd /usr/src/
    make -j2 buildworld
    make -j2 buildkernel KERNCONF=GENERIC
    make -j2 installkernel KERNCONF=GENERIC
    reboot into single user mode
    make installworld
    mergemaster -cv
    reboot..
     

    > On 8/4/05, Derrick Edwards <dantavious@comcast.net> wrote:
    > > Hi all,
    > > I decided to try and help with testing 6-BETA1, after updating sources
    > > and recompiling i get the following during boot up. I am tried booting
    > > without hyperthreading enabled in the bios and I still get the same
    > > panic.
    > >
    > > Fatal trap 12: page fault while in kernel mode
    > > cpuid = 0; apic id =00
    > > fault virtual address = 0x480008
    > > fault code = supervisor read, page not present
    > > instruction pointer = 0x20:0xc06923cc
    > > stack pointer = 0x28:0xc10208ec
    > >
    > > Code segment = base 0x0, limit 0xfffff, type 0x1b
    > > = DPL 0, pres 1, def32 1, gran 1
    > >
    > > processor eflags = interrupt enabled, resyne, IOPL = 0
    > > current process = 0 (swapper)
    > > [thread pid 0tid0]
    > > Stopped at strlen+0x8: cmpb $0,0(%edx)
    > >
    > > I left all the debugging features in the current however, I am not sure
    > > exactly how to trace this problem. If someone could point me to any doc
    > > that would allow to provide more information that would be great. I
    > > updated my pen 400MHZ using the same procedures and all went well. Please
    > > help
    > >
    > > CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (1866.74-MHz 686-class CPU)
    > > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9
    > >
    > > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,
    > >MCA, CMOV,PAT,PSE36,CLFLUSH,D TS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
    > > Hyperthreading: 2 logical CPUs
    > > real memory = 1073676288 (1023 MB)
    > > avail memory = 1036931072 (988 MB)
    > > ACPI APIC Table: <IntelR AWRDACPI>
    > > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
    > > cpu0 (BSP): APIC ID: 0
    > > cpu1 (AP): APIC ID: 1
    > >
    > >
    > >
    > >
    > > Thanks for your assistance
    > > Derrick
    > >
    > >
    > > _______________________________________________
    > > freebsd-current@freebsd.org mailing list
    > > http://lists.freebsd.org/mailman/listinfo/freebsd-current
    > > To unsubscribe, send any mail to
    > > "freebsd-current-unsubscribe@freebsd.org"
    >
    > I presume that you used the standard upgrade sequence:
    > cd /usr/src
    > make buildworld
    > make kernel KERNCONF=mykernconf
    > reboot to single user
    > mergemaster -p
    > make installworld
    > mergemaster -i
    > reboot
    >
    > Also, you checked /usr/src/UPDATING for any issues since your previous
    > install (which you didn't mention what was)?
    >
    > When in this procedure did you get this panic() (the first or second
    > reboot)?
    >
    > If you are at a debugger prompt (db>) the output of 'trace', 'show pcpu',
    > 'show pcpu 0', and 'show pcpu 1' would probably be useful to the
    > kernel hackers who can help you (not myself).
    >
    > Thanks for helping to test the beta, and getting the information that
    > will be needed to debug this.
    >
    > Ben Kaduk
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Ben Kaduk: "Re: Panic on FreeBSD 6.0BETA1"

    Relevant Pages

    • Re: Upgrading fc6 -> f7 with problems
      ... Install FC6-i386 from a DVD, ... Reboot, replace i586 kernel with i686 kernel ... See that I can log in and that yum update ... After the F7 upgrade I still have rpm-python-4.4.2.1-1.fc6 ...
      (Fedora)
    • Re: Uninstalling ZoneAlarm / Problems Upgrading ZoneAlarm
      ... First, downlad and save the file, don't try to run the install remotely. ... Reboot in Safe Mode, and delete all the files in the ... but I can't seem to upgrade. ... remove ZA from the Add/Remove Programs menu, the uninstall process freezes ...
      (comp.security.firewalls)
    • Re: Weirdness with Fedora/XP upgrade -- update
      ... and told XP to reboot. ... All went smoothly, up to the point of installing Tomboy -- which it shouldn't install in an upgrade, since that isn't in my F8. ...
      (Fedora)
    • Re: Help! Office 2000 pro install broke my win2k box
      ... upgrade, I though I might as well put Office 2000 on it. ... Install Office 97, and at the end of the installation "bdrintl.dll ... Reboot, install Office97, reboot, yeah everything ok except... ... Completely uninstall, reboot, reinstall, reboot, no MSAccess.exe. ...
      (microsoft.public.office.setup)
    • SUMMARY: Recommended patch clusters in single user
      ... I've seen multiple recommendations that patches are only ever ... then reboot). ... patches through a single user install. ...
      (SunManagers)