misc/141470: BTX halted immediatly on selecting any of the boot
options
Sean Johnston
smjohnston at aebc.com
Mon Dec 14 17:10:03 PST 2009
>Number: 141470
>Category: misc
>Synopsis: BTX halted immediatly on selecting any of the boot options
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Dec 15 01:10:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Sean Johnston
>Release: 7.2
>Organization:
AEBC Internet Corp
>Environment:
Unable to install due to this problem.. so
>Description:
I have created a pxe bootable disk image of the freebsd boot only install cd.
I am able to install freebsd on all of my systems, with the exception of my IBM Blade Servers using this method.
When attempting to install FreeBSD 7.2 on my blade systems:
I select FreeBSD 7.2 (i386) from my PXE Boot Menu.
The image is loaded.
I get the message "Welcome to FreeBSD!" followed by the menu
at this point options 1-5 will result in the error shown in the JPG I wish I had an option to attach to this bug report so here it is typed out:
/boot/kernel/acpi.ko text=0x52730 data=0x2400+0x186c syms=[0x4+0x8660+0x4+0xb187]
loading required module 'pci'
ACPI autoload failed - no such file or directory
-
int=00000006 err=00000000 efl=00010046 eip=0004bcb5
eax=00000000 ebx=a0500000 ecx=00000000 edx=004603de
esi=00000000 edi=00000000 ebp=00000000 esp=00029203
cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010
cs:eip=fe fd 03 0f 01 4f 00 0f-01 4f 00 0f 01 4f 00 0f
01 4f 00 0f 01 4f 00 0f-01 4f 00 54 00 00 00 01
ss:esp=83 ec 14 89 5d f4 8b 5d-0c 89 75 f8 8b 75 10 89
7d fc 8b 7d 08 85 db 74-34 80 3b 2f 74 2f c7 44
BTX halted
option 6 allows me to try the various work-arounds I have found on the internet but ultimately I get the same error.
The
>How-To-Repeat:
get an IBM Blade HS20 and try install FreeBSD 7.2
>Fix:
Install FreeBSD on another computer then move the hard drive to the IBM Blade HS20 and turn it on. The system re-configures itself and works fine with the Blade Server. (not really a fix but all I have to offer)
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list