RE: port-i386/46247: 6.0 Beta boot fails on generic i386 architecture machine

["John Refling" <netbsdrat%gmail.com@localhost>]

The following reply was made to PR port-i386/46247; it has been noted by GNATS.

From: "John Refling" <netbsdrat%gmail.com@localhost>
To: <gnats-bugs%NetBSD.org@localhost>,
        <port-i386-maintainer%netbsd.org@localhost>,
        <gnats-admin%netbsd.org@localhost>,
        <netbsd-bugs%netbsd.org@localhost>
Cc: 
Subject: RE: port-i386/46247: 6.0 Beta boot fails on generic i386 architecture 
machine
Date: Thu, 29 Mar 2012 00:07:37 -0700

 More info on this:
 
 SUSE Linux 10.1 [2006] installs and works on this machine.
 
 Vista Anytime upgrade fails saying APCI is not compatible.
 
 Points to the problem?
 
 John Refling
 
 
 
 -----Original Message-----
 From: David Laight [mailto:david%l8s.co.uk@localhost] 
 Sent: Tuesday, March 27, 2012 12:05 AM
 To: port-i386-maintainer%netbsd.org@localhost; 
gnats-admin%netbsd.org@localhost;
 netbsd-bugs%netbsd.org@localhost; netbsdrat%gmail.com@localhost
 Subject: Re: port-i386/46247: 6.0 Beta boot fails on generic i386
 architecture machine
 
 The following reply was made to PR port-i386/46247; it has been noted by
 GNATS.
 
 From: David Laight <david%l8s.co.uk@localhost>
 To: gnats-bugs%NetBSD.org@localhost
 Cc: 
 Subject: Re: port-i386/46247: 6.0 Beta boot fails on generic i386
 architecture machine
 Date: Tue, 27 Mar 2012 07:57:24 +0100
 
  On Tue, Mar 27, 2012 at 06:50:05AM +0000, John Refling wrote:
  > The following reply was made to PR port-i386/46247; it has been noted by
 GNATS.
  >  How can I help debug this?
  
  Generally at printfs :-)
  I think there is one at the start of /boot (unless someone removed it).
  Since you aren't seeing that, something must be going on in the bootxx
 code.
  bootxx only has access to 'print string' and 'print value' functions,
  but they are usually enough.
  
  I'd make sure there are no 'clear screen' calls, then output somthing
  just before bootxx jumps into /boot, and something right at the top
  of /boot.
  
  Might be a size issue...
  Maybe some of the memory areas used contain bios data (I've NFI how
  to find out which areas are actually usable while you still want
  to make bios calls).
  
  If you suspect bios issues, can be worth using the direct serial
  console versions of stuff - in particular the code can then write
  from 32bit mode without having to switch to 16bit code for the
  bios call.
  
        David
  
  -- 
  David Laight: david%l8s.co.uk@localhost