On Tue, 9 Mar 2010 20:11:16 -0500
"STeve Andre'" <and...@msu.edu> wrote:

> On Tuesday 09 March 2010 19:44:12 Ben Niccum wrote:
> > On Fri, 5 Mar 2010 15:16:21 -0800
> >
> > Ben Niccum <be...@bendtel.com> wrote:
> > > Hello,
> > >
> > > So I'm currently running OpenBSD 4.6-release for AMD64 as my
> > > desktop workstation and I decided to try to install 4.6-release
> > > for i386 so that I could use the linux emulation.
> > >
> > > I first tried using the i386 4.6-release cd but it died mid-boot.
> > > It seemed to be complaining about a:
> > >
> > >     fatal integer divide fault (8) in supervisor mode
> > >     trap type 8 code 0 eip d049cc94 cs 8 eflags 10246 cr2 f0bed5
> > > cpl 0 panic: trap type 8, code=0, pc=d049cc94
> > >
> > > the next message lines were just the ones that said system halted,
> > > press any key to reboot.
> > >
> > > I took a picture of it here: http://imgur.com/k4aMn.jpg
> > >
> > > I thought that was strange, so I tried downloading the
> > > 4.7-current for i386 release but got the same results with the
> > > exception of:
> > >
> > >     pc=d04bd9ac
> > >
> > > picture: http://imgur.com/QcD8j.jpg
> > >
> > > Just for comparison, I've included my dmesg.boot from my current
> > > AMD64 4.6-release and one I pulled from the AMD64 4.7-current
> > > install cd. All the iso's used for 4.7-current had a build date
> > > of 2010-03-04.
> >
> > No love?
> >
> > I tried searching but I've been unable to find anyone experiencing
> > similar issues.  I pulled an i386 4.5-release cd and tried booting
> > that just to see if a recent change caused the issue and still I
> > got the same thing.
> >
> > pic: http://imgur.com/uBvYx.jpg
> >
> > Does anyone have any suggestions? I'm new to the mailing list, so
> > should I post this question in a different list?
> >
> > -Ben
> 
> I haven't been following this till now, but its rare for i386 stuff
> not to work right.  I'm going to be that you have a hardware issue.
> Have you started taking things out, shifting/removing memory, and
> stuff like that?  Sometimes its the really weird things...
> 
> --STeve Andre'
> 

I've only got 1 stick of memory, so I can't really remove it.  I did
take out my pci sound card, but I still get the same panic.

I tried making a little sense of my dmesg from the working system and
the little output I get from trying to boot the cd.

On the working system, it starts with these first few lines:

----------------------------------------------------------------------
OpenBSD 4.6 (GENERIC.MP) #81: Thu Jul  9 21:26:19 MDT 2009
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2145255424 (2045MB) avail mem = 2070634496 (1974MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf0000 (43 entries)
bios0: vendor Phoenix Technologies, LTD version "6.00 PG" date
02/05/2009 bios0: EVGA GeForce 9300 Series
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP HPET MCFG APIC
acpi0: wakeup devices HUB0(S5) XVR0(S5) XVR1(S5) XVR2(S5) XVR3(S5)
XVR4(S5) XVR5(S5) XVR6(S5) UAR1(S5) USB0(S3) USB1(S3) USBB(S3) USB2(S3)
AZAD(S5) MMAC(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at
acpi0: 25000000 Hz acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Pentium(R) Dual-Core CPU E5200 @ 2.50GHz
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,CX16,xTPR,NXE,LONG
cpu0: 2MB 64b/line 8-way L2 cache cpu0: apic clock running at 200MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Pentium(R) Dual-Core CPU E5200 @ 2.50GHz
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,CX16,xTPR,NXE,LONG
cpu1: 2MB 64b/line 8-way L2 cache
----------------------------------------------------------------------

but what I see on the boot cd from the pictures I've taken (links
above) is that the cd is dying right about the time where it is still
getting cpu information. Most notably (I think) is that the cd dmesg
does not include any information about the cpu cache.

I'm going to boot my regular system using the single core kernel to try
and get a working dmesg that may be more relevant, since this one is
showing both cores on the cpu.

-Ben
-- 
Ben Niccum
be...@bendtel.com
Direct Line: 541-323-9102
Cell: 541-306-9112  

Reply via email to