BTX problems

Jung-uk Kim jkim at FreeBSD.org
Mon Aug 22 20:23:07 GMT 2005


On Monday 22 August 2005 03:18 pm, John Baldwin wrote:
> On Monday 22 August 2005 01:19 pm, Jung-uk Kim wrote:
> > On Monday 22 August 2005 12:33 pm, Kenneth D. Merry wrote:
> > > On Mon, Aug 22, 2005 at 12:16:51 -0400, Jung-uk Kim wrote:
> > > > On Monday 22 August 2005 11:57 am, Kenneth D. Merry wrote:
> > > > > On Mon, Aug 22, 2005 at 11:37:25 -0400, Jung-uk Kim wrote:
> > > > > > On Saturday 20 August 2005 01:02 am, Kenneth D. Merry 
wrote:
> > > > > > > On Tue, Aug 16, 2005 at 13:39:48 -0400, John Baldwin 
wrote:
> > > > > > > > There haven't been a whole lot of changes.  My guess
> > > > > > > > would be the recently added smbios support.  You can
> > > > > > > > probably just comment out the call to smbios_detect()
> > > > > > > > in sys/boot/i386/loader/main.c as a simple test for
> > > > > > > > that. It could also possibly be the multiple console
> > > > > > > > support in which case it would be easiest to just
> > > > > > > > step your sys/boot tree back using CVS.  The good
> > > > > > > > news is that sys/boot is largely self-contained so
> > > > > > > > you can step it back while keeping the rest of the
> > > > > > > > tree up to date for testing purposes at least.
> > > > > > >
> > > > > > > Thanks for the tips!
> > > > > > >
> > > > > > > Commenting out smbios_detect() did the trick.  The
> > > > > > > loader works fine after that.
> > > > > > >
> > > > > > > So now what?  Is there a way to fix it so it won't
> > > > > > > crash on my system?
> > > > > >
> > > > > > So, I guess I broke it, then.  Can you install
> > > > > > ports/sysutils/dmidecode and send me dmidecode output?
> > > > >
> > > > > Sure, here it is.
> > > >
> > > > Okay, it looks good so far.  Can you do:
> > > >
> > > > dd if=/dev/mem of=dmi.dat bs=1 count=1534 skip=984640
> > > > dd if=/dev/mem of=smbios.dat bs=1 count=65536 skip=983040
> > > >
> > > > and send me dmi.dat and smbios.dat, please?
> > >
> > > Here they are.
> >
> > It's very strange.  It seems SM entry and DMI structures are all
> > sane. I don't understand why it happens. :-( I just wrote a
> > qucik-and-dirty userland wrapper for smbios.c, which is attached.
> >
> > SMBIOS entry: 0x000f00a0
> > DMI structures: length = 1534, paddr = 0x000f0640, count = 49
> > smbios.bios.vendor="American Megatrends Inc."
> > smbios.bios.version="0700xx "
> > smbios.bios.reldate="11/14/2001"
> > smbios.system.maker="Supermicro"
> > smbios.system.product="P3TDE6"
> > smbios.system.version="1234567890"
> > smbios.planar.maker="Supermicro"
> > smbios.planar.product="P3TDE6"
> > smbios.planar.version="1234567890"
> > smbios.chassis.maker="Supermicro"
> > smbios.chassis.version="P3TDE6"
> >
> > Is it possible that PTOV() is not working somehow???  I need help
> > here.
>
> Perhaps give ken@ a patch with some printf's added to figure out
> how far it gets into smbios_detect() before it dies?

Thanks for the suggestion.

ken,

can you try the attached diff and tell me how far it goes?

Thanks,

Jung-uk Kim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smbios.diff
Type: text/x-diff
Size: 1959 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20050822/96937cce/smbios.bin


More information about the freebsd-current mailing list