NetBSD Problem Report #46247

From www@NetBSD.org  Fri Mar 23 00:13:13 2012
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id 910E263E392
	for <gnats-bugs@gnats.NetBSD.org>; Fri, 23 Mar 2012 00:13:13 +0000 (UTC)
Message-Id: <20120323001311.5E97B63B946@www.NetBSD.org>
Date: Fri, 23 Mar 2012 00:13:10 +0000 (UTC)
From: netbsdrat@gmail.com
Reply-To: netbsdrat@gmail.com
To: gnats-bugs@NetBSD.org
Subject: 6.0 Beta boot fails on generic i386 architecture machine
X-Send-Pr-Version: www-1.0

>Number:         46247
>Category:       port-i386
>Synopsis:       6.0 Beta boot fails on generic i386 architecture machine
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    cjep
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 23 00:15:00 +0000 2012
>Closed-Date:    Wed Jun 09 02:19:54 +0000 2021
>Last-Modified:  Wed Jun 09 02:19:54 +0000 2021
>Originator:     John Refling
>Release:        6.0 Beta install
>Organization:
>Environment:
>Description:
I installed 6.0 beta on a rather generic i386 machine:

p4m800pro-m v2.0 by ECS

http://www.ecsusa.com/ECSWebSite/Product/Product_Detail.aspx?DetailID=673&CategoryID=1&DetailName=Feature&MenuID=16&LanID=9

and the install went OK, but it would not successfully boot from hard disk, halting after:

NetBSD MBR boot
NetBSD/x86 ffsv2 Primary Bootstrap
[silence]

The install complained once that the disk geometry could not be uniquely matched:
Bios: 1024/16/63
Prob: 1023/255/63

I tried both the auto and manually entering the c/h/s.

I used the entire disk so no added confusion there.  The dmesg is at the bottom, after other comments.

It did install and boot correctly on this machine with version 5.1, although on one install strange things happened such as creating the main partition past the end of the disk.

How can I help debug this?  It has an AMI bios version 2.59 (latest from manufacturer), Maxtor 40gb hard disk, etc.

----------

On a side note, I did install the beta on my dell poweredge 1850, and it seemed to work, although the long standing problem with the power control has not improved.  Still needs to boot w/o the ACPI. (-1 or -2 on the command line).

----------

I also tried installing 6.0 beta on sun ultra 10 (sparc64) and it seemed to work including 4k disk sectors:

http://mail-index.netbsd.org/netbsd-users/2012/03/01/msg010169.html

----------

i386 dmesg on failing machine:

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 6.0_BETA (GENERIC)
total memory = 1023 MB
avail memory = 992 MB
timecounter: Timecounters tick every 10.000 msec
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
ECS P4M800PRO-M (1.0)
mainbus0 (root)
cpu0 at mainbus0 apid 0: Intel(R) Pentium(R) D  CPU 2.66GHz, id 0xf47
cpu1 at mainbus0 apid 1: Intel(R) Pentium(R) D  CPU 2.66GHz, id 0xf47
ioapic0 at mainbus0 apid 2: pa 0xfec00000, version 3, 24 pins
acpi0 at mainbus0: Intel ACPICA 20110623
acpi0: X/RSDT: OemId <AAMMII,OEMRSDT ,08000730>, AslId <MSFT,00000097>
acpi0: SCI interrupting at int 9
timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
attimer1 at acpi0 (TMR, PNP0100): io 0x40-0x43 irq 0
pckbc1 at acpi0 (PS2K, PNP0303) (kbd port): io 0x60,0x64 irq 1
pcppi1 at acpi0 (SPKR, PNP0800): io 0x61
midi0 at pcppi1: PC speaker
sysbeep0 at pcppi1
npx1 at acpi0 (COPR, PNP0C04): io 0xf0-0xff irq 13
npx1: reported by CPUID; using exception 16
UAR1 (PNP0501) at acpi0 not configured
FDC (PNP0700) at acpi0 not configured
LPTE (PNP0401) at acpi0 not configured
SIOR (PNP0C02) at acpi0 not configured
RMSC (PNP0C02) at acpi0 not configured
OMSC (PNP0C02) at acpi0 not configured
acpibut0 at acpi0 (SLPB, PNP0C0E): ACPI Sleep Button
RMEM (PNP0C01) at acpi0 not configured
acpibut1 at acpi0 (PWRB, PNP0C0C-170): ACPI Power Button
acpitz0 at acpi0 (THRM)
acpitz0: levels: critical 110.0 C, passive cooling
apm0 at acpi0: Power Management spec V1.2
pckbd0 at pckbc1 (kbd slot)
pckbc1: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
attimer1: attached to pcppi1
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0: vendor 0x1106 product 0x0314 (rev. 0x00)
agp0 at pchb0: aperture at 0xf8000000, size 0x4000000
pchb1 at pci0 dev 0 function 1: vendor 0x1106 product 0x1314 (rev. 0x00)
pchb2 at pci0 dev 0 function 2: vendor 0x1106 product 0x2314 (rev. 0x00)
pchb3 at pci0 dev 0 function 3: vendor 0x1106 product 0x3208 (rev. 0x00)
pchb4 at pci0 dev 0 function 4: vendor 0x1106 product 0x4314 (rev. 0x00)
pchb5 at pci0 dev 0 function 7: vendor 0x1106 product 0x7314 (rev. 0x00)
ppb0 at pci0 dev 1 function 0: vendor 0x1106 product 0xb198 (rev. 0x00)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
vga1 at pci1 dev 0 function 0: vendor 0x10de product 0x0322 (rev. 0xa1)
wsdisplay0 at vga1 kbdmux 1: console (80x25, vt100 emulation), using wskbd0
wsmux1: connecting to wsdisplay0
drm at vga1 not configured
ex0 at pci0 dev 9 function 0: 3Com 3c905C-TX 10/100 Ethernet with mngmt (rev. 0x78)
ex0: interrupting at ioapic0 pin 17
ex0: MAC address 00:04:75:ce:dc:30
exphy0 at ex0 phy 24: 3Com internal media interface
exphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
viaide0 at pci0 dev 15 function 0: VIA Technologies VT8237 SATA Controller (rev. 0x80)
viaide0: bus-master DMA support present
viaide0: primary channel configured to native-PCI mode
viaide0: using ioapic0 pin 20 for native-PCI interrupt
atabus0 at viaide0 channel 0
viaide0: secondary channel configured to native-PCI mode
atabus1 at viaide0 channel 1
viaide1 at pci0 dev 15 function 1
viaide1: VIA Technologies VT8237 ATA133 controller
viaide1: bus-master DMA support present
viaide1: primary channel configured to compatibility mode
viaide1: primary channel interrupting at ioapic0 pin 14
atabus2 at viaide1 channel 0
viaide1: secondary channel configured to compatibility mode
viaide1: secondary channel interrupting at ioapic0 pin 15
atabus3 at viaide1 channel 1
uhci0 at pci0 dev 16 function 0: vendor 0x1106 product 0x3038 (rev. 0x81)
uhci0: interrupting at ioapic0 pin 21
usb0 at uhci0: USB revision 1.0
uhci1 at pci0 dev 16 function 1: vendor 0x1106 product 0x3038 (rev. 0x81)
uhci1: interrupting at ioapic0 pin 21
usb1 at uhci1: USB revision 1.0
uhci2 at pci0 dev 16 function 2: vendor 0x1106 product 0x3038 (rev. 0x81)
uhci2: interrupting at ioapic0 pin 21
usb2 at uhci2: USB revision 1.0
uhci3 at pci0 dev 16 function 3: vendor 0x1106 product 0x3038 (rev. 0x81)
uhci3: interrupting at ioapic0 pin 21
usb3 at uhci3: USB revision 1.0
ehci0 at pci0 dev 16 function 4: vendor 0x1106 product 0x3104 (rev. 0x86)
ehci0: interrupting at ioapic0 pin 21
ehci0: dropped intr workaround enabled
ehci0: EHCI version 1.0
ehci0: companion controllers, 2 ports each: uhci0 uhci1 uhci2 uhci3
usb4 at ehci0: USB revision 2.0
viapcib0 at pci0 dev 17 function 0: vendor 0x1106 product 0x3227 (rev. 0x00)
viapcib0: SMBus found at 0x400 (revision 0x0)
iic0 at viapcib0: I2C bus
auvia0 at pci0 dev 17 function 5: VIA Technologies VT8237 AC'97 Audio (rev 0x60)
auvia0: interrupting at ioapic0 pin 22
auvia0: ac97: Avance Logic ALC655 codec; no 3D stereo
auvia0: ac97: ext id 0x9c4<AC97_23,LDAC,SDAC,CDAC,SPDIF>
audio0 at auvia0: full duplex, playback, capture, independent
vr0 at pci0 dev 18 function 0: vendor 0x1106 product 0x3065 (rev. 0x78)
vr0: interrupting at ioapic0 pin 23
vr0: Ethernet address: 00:19:21:3c:12:fa
ukphy0 at vr0 phy 1: OUI 0x0002c6, model 0x0032, rev. 10
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isa0 at viapcib0
lpt0 at isa0 port 0x378-0x37b irq 7
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
acpicpu0 at cpu0: ACPI CPU
acpicpu0: C1: HLT, lat   0 us, pow     0 mW
acpicpu1 at cpu1: ACPI CPU
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
timecounter: Timecounter "TSC" frequency 2661693100 Hz quality 3000
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
uhub0 at usb0: vendor 0x1106 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhub1 at usb1: vendor 0x1106 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhub2 at usb2: vendor 0x1106 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhub3 at usb3: vendor 0x1106 UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
uhub4 at usb4: vendor 0x1106 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
wd0 at atabus2 drive 0
wd0: <Maxtor 6E040L0>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 39205 MB, 79656 cyl, 16 head, 63 sec, 512 bytes/sect x 80293248 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
wd0(viaide1:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)
atapibus0 at atabus3: 2 targets
cd0 at atapibus0 drive 0: <PIONEER DVD-RW  DVR-107D, DCDL062297WL, 1.22> cdrom removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
cd0(viaide1:1:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA)
Kernelized RAIDframe activated
boot device: cd0
root on cd0a dumps on cd0b
root file system type: cd9660
warning: no /dev/console





>How-To-Repeat:

>Fix:

>Release-Note:

>Audit-Trail:
From: David Laight <david@l8s.co.uk>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-i386/46247: 6.0 Beta boot fails on generic i386 architecture machine
Date: Fri, 23 Mar 2012 07:52:38 +0000

 On Fri, Mar 23, 2012 at 12:15:00AM +0000, netbsdrat@gmail.com wrote:
 > >Number:         46247
 > >Category:       port-i386
 > >Synopsis:       6.0 Beta boot fails on generic i386 architecture machine
 ...
 > I installed 6.0 beta on a rather generic i386 machine:
 > 
 > p4m800pro-m v2.0 by ECS
 > 
 > http://www.ecsusa.com/ECSWebSite/Product/Product_Detail.aspx?DetailID=673&CategoryID=1&DetailName=Feature&MenuID=16&LanID=9
 > 
 > and the install went OK, but it would not successfully boot from hard disk, halting after:
 > 
 > NetBSD MBR boot
 > NetBSD/x86 ffsv2 Primary Bootstrap
 > [silence]
 > 
 > The install complained once that the disk geometry could not be uniquely matched:
 > Bios: 1024/16/63
 > Prob: 1023/255/63

 If it got as far as showing the ffs2 message then the chs values won't matter.

 I had an issue booting via grub where the console was getting set to
 com0 instead pc by default.

 Try booting from the install cd, and exit to shell (^C will do).
 Then run 'installboot -e -v wd0' to look at the options, and maybe
 force the console with '-o console-pc'.
 (Commands from memory).
 You might need to mount the root fs and chroot into it.

 	David

 -- 
 David Laight: david@l8s.co.uk

From: "John Refling" <netbsdrat@gmail.com>
To: <gnats-bugs@NetBSD.org>,
	<port-i386-maintainer@netbsd.org>,
	<gnats-admin@netbsd.org>,
	<netbsd-bugs@netbsd.org>
Cc: <david@l8s.co.uk>
Subject: RE: port-i386/46247: 6.0 Beta boot fails on generic i386 architecture machine
Date: Fri, 23 Mar 2012 23:43:15 -0700

 I had a look at the boot console using the command you mentioned
 and nothing was unusual:

 File system:         /dev/wd0a
 Boot options:        timeout 5, flags 0, speed 9600, ioaddr 0, console pc

 I also hooked up an rs-232 cable and terminal to com0 to see if anything
 was output.  It was silent.

 Also, hooked up the HDD LED and there was absolutely no disk activity
 after:

  NetBSD MBR boot
  NetBSD/x86 ffsv2 Primary Bootstrap
  [silence]

 I'm wondering if bootstrap being confused by the SATA channels (which have
 no disks).  Maybe starting off with the PATA interface (where the disk is)
 then thinking to use the SATA later in the boot process ???

 John Refling


 -----Original Message-----
 From: David Laight [mailto:david@l8s.co.uk] 
 Sent: Friday, March 23, 2012 1:00 AM
 To: port-i386-maintainer@netbsd.org; gnats-admin@netbsd.org;
 netbsd-bugs@netbsd.org; netbsdrat@gmail.com
 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>
 To: gnats-bugs@NetBSD.org
 Cc: 
 Subject: Re: port-i386/46247: 6.0 Beta boot fails on generic i386
 architecture machine
 Date: Fri, 23 Mar 2012 07:52:38 +0000

  On Fri, Mar 23, 2012 at 12:15:00AM +0000, netbsdrat@gmail.com wrote:
  > >Number:         46247
  > >Category:       port-i386
  > >Synopsis:       6.0 Beta boot fails on generic i386 architecture machine
  ...
  > I installed 6.0 beta on a rather generic i386 machine:
  > 
  > p4m800pro-m v2.0 by ECS
  > 
  >
 http://www.ecsusa.com/ECSWebSite/Product/Product_Detail.aspx?DetailID=673&Ca
 tegoryID=1&DetailName=Feature&MenuID=16&LanID=9
  > 
  > and the install went OK, but it would not successfully boot from hard
 disk, halting after:
  > 
  > NetBSD MBR boot
  > NetBSD/x86 ffsv2 Primary Bootstrap
  > [silence]
  > 
  > The install complained once that the disk geometry could not be uniquely
 matched:
  > Bios: 1024/16/63
  > Prob: 1023/255/63

  If it got as far as showing the ffs2 message then the chs values won't
 matter.

  I had an issue booting via grub where the console was getting set to
  com0 instead pc by default.

  Try booting from the install cd, and exit to shell (^C will do).
  Then run 'installboot -e -v wd0' to look at the options, and maybe
  force the console with '-o console-pc'.
  (Commands from memory).
  You might need to mount the root fs and chroot into it.

  	David

  -- 
  David Laight: david@l8s.co.uk


From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-i386/46247: 6.0 Beta boot fails on generic i386
 architecture machine
Date: Mon, 26 Mar 2012 17:35:42 +0000

 On Fri, Mar 23, 2012 at 08:00:07AM +0000, David Laight wrote:
  >  > NetBSD MBR boot
  >  > NetBSD/x86 ffsv2 Primary Bootstrap
  >  > [silence]
  >  > 
  >  > The install complained once that the disk geometry could not be uniquely matched:
  >  > Bios: 1024/16/63
  >  > Prob: 1023/255/63
  >  
  > If it got as far as showing the ffs2 message then the chs values
  > won't matter.

 Are you sure of that? It is still doing I/O via the BIOS until the
 kernel gets started; while I'd expect it to be using LBA for that, the
 entire problem could be that it isn't.

 -- 
 David A. Holland
 dholland@netbsd.org

From: David Laight <david@l8s.co.uk>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-i386/46247: 6.0 Beta boot fails on generic i386 architecture machine
Date: Mon, 26 Mar 2012 19:27:07 +0100

 On Mon, Mar 26, 2012 at 05:40:04PM +0000, David Holland wrote:
 > The following reply was made to PR port-i386/46247; it has been noted by GNATS.
 > 
 > From: David Holland <dholland-bugs@netbsd.org>
 > To: gnats-bugs@NetBSD.org
 > Cc: 
 > Subject: Re: port-i386/46247: 6.0 Beta boot fails on generic i386
 >  architecture machine
 > Date: Mon, 26 Mar 2012 17:35:42 +0000
 > 
 >  On Fri, Mar 23, 2012 at 08:00:07AM +0000, David Laight wrote:
 >   >  > NetBSD MBR boot
 >   >  > NetBSD/x86 ffsv2 Primary Bootstrap
 >   >  > [silence]
 >   >  > 
 >   >  > The install complained once that the disk geometry could not be uniquely matched:
 >   >  > Bios: 1024/16/63
 >   >  > Prob: 1023/255/63
 >   >  
 >   > If it got as far as showing the ffs2 message then the chs values
 >   > won't matter.
 >  
 >  Are you sure of that? It is still doing I/O via the BIOS until the
 >  kernel gets started; while I'd expect it to be using LBA for that, the
 >  entire problem could be that it isn't.

 It will be doing bios requests - probably as CHS requests, but the
 data it has requests a logical sector number which is converted
 to CHS using the parameters obtained from the bios that boot.
 Those ought to match!
 'sysctl machdep.diskinfo' will show the bios geometries.

 The mbr will read the pbr using the CHS values saved by fdisk.
 If fdisk were run on a different system they are very likely to
 be wrong - which is when mbr_lba can help somewhat.

 	David

 -- 
 David Laight: david@l8s.co.uk

From: "John Refling" <netbsdrat@gmail.com>
To: <gnats-bugs@NetBSD.org>,
	<port-i386-maintainer@netbsd.org>,
	<gnats-admin@netbsd.org>,
	<netbsd-bugs@netbsd.org>
Cc: 
Subject: RE: port-i386/46247: 6.0 Beta boot fails on generic i386 architecture machine
Date: Mon, 26 Mar 2012 23:45:58 -0700

 How can I help debug this?

 John Refling


 -----Original Message-----
 From: David Laight [mailto:david@l8s.co.uk] 
 Sent: Monday, March 26, 2012 11:35 AM
 To: port-i386-maintainer@netbsd.org; gnats-admin@netbsd.org;
 netbsd-bugs@netbsd.org; netbsdrat@gmail.com
 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>
 To: gnats-bugs@NetBSD.org
 Cc: 
 Subject: Re: port-i386/46247: 6.0 Beta boot fails on generic i386
 architecture machine
 Date: Mon, 26 Mar 2012 19:27:07 +0100

  On Mon, Mar 26, 2012 at 05:40:04PM +0000, David Holland wrote:
  > The following reply was made to PR port-i386/46247; it has been noted by
 GNATS.
  > 
  > From: David Holland <dholland-bugs@netbsd.org>
  > To: gnats-bugs@NetBSD.org
  > Cc: 
  > Subject: Re: port-i386/46247: 6.0 Beta boot fails on generic i386
  >  architecture machine
  > Date: Mon, 26 Mar 2012 17:35:42 +0000
  > 
  >  On Fri, Mar 23, 2012 at 08:00:07AM +0000, David Laight wrote:
  >   >  > NetBSD MBR boot
  >   >  > NetBSD/x86 ffsv2 Primary Bootstrap
  >   >  > [silence]
  >   >  > 
  >   >  > The install complained once that the disk geometry could not be
 uniquely matched:
  >   >  > Bios: 1024/16/63
  >   >  > Prob: 1023/255/63
  >   >  
  >   > If it got as far as showing the ffs2 message then the chs values
  >   > won't matter.
  >  
  >  Are you sure of that? It is still doing I/O via the BIOS until the
  >  kernel gets started; while I'd expect it to be using LBA for that, the
  >  entire problem could be that it isn't.

  It will be doing bios requests - probably as CHS requests, but the
  data it has requests a logical sector number which is converted
  to CHS using the parameters obtained from the bios that boot.
  Those ought to match!
  'sysctl machdep.diskinfo' will show the bios geometries.

  The mbr will read the pbr using the CHS values saved by fdisk.
  If fdisk were run on a different system they are very likely to
  be wrong - which is when mbr_lba can help somewhat.

  	David

  -- 
  David Laight: david@l8s.co.uk


From: David Laight <david@l8s.co.uk>
To: gnats-bugs@NetBSD.org
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

From: "John Refling" <netbsdrat@gmail.com>
To: <gnats-bugs@NetBSD.org>,
	<port-i386-maintainer@netbsd.org>,
	<gnats-admin@netbsd.org>,
	<netbsd-bugs@netbsd.org>
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] 
 Sent: Tuesday, March 27, 2012 12:05 AM
 To: port-i386-maintainer@netbsd.org; gnats-admin@netbsd.org;
 netbsd-bugs@netbsd.org; netbsdrat@gmail.com
 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>
 To: gnats-bugs@NetBSD.org
 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


State-Changed-From-To: open->feedback
State-Changed-By: cjep@NetBSD.org
State-Changed-When: Sat, 08 May 2021 17:23:11 +0000
State-Changed-Why:
The boot code has changed since 6.0 and we can definitely boot on most
machines on this arch. Are you happy to shut this PR?


Responsible-Changed-From-To: port-i386-maintainer->cjep
Responsible-Changed-By: cjep@NetBSD.org
Responsible-Changed-When: Sat, 08 May 2021 17:23:33 +0000
Responsible-Changed-Why:
Swatting old bugs


State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Wed, 09 Jun 2021 02:19:54 +0000
State-Changed-Why:
Submitter wrote to the gnats administrator address to say it could be closed.


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.46 2020/01/03 16:35:01 leot Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2020 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.