Date: Fri, 15 Mar 2002 19:34:22 -0800 (PST) From: Jeff Kletsky <jeff+freebsd@spotlife.com> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/35950: ACPI missing prevents install from floppies Message-ID: <200203160334.g2G3YMm09873@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 35950
>Category: i386
>Synopsis: ACPI missing prevents install from floppies
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Mar 15 19:40:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Jeff Kletsky
>Release: 5.0-2002031x-CURRENT
>Organization:
SpotLife
>Environment:
(unable to install OS)
>Description:
Unable to install from floppies or bootable CD images from 5.0-2002031x-CURRENT.
Observed on both an Asus (VIA) MB and a Sony VAIO laptop.
>How-To-Repeat:
Create boot floppies or CD from snapshot. Boot, note that BTX loader exits
before booting kernel.
Have tried manually loading acpi.ko (from bin distrubition), as well as
disabling acpi_load and/or acpi from the 'OK' prompt.
Date: Fri, 15 Mar 2002 19:06:58 -0800 (PST)
From: Jeff Kletsky <jeff+freebsd@wagsky.com>
To: Jeff Kletsky <jeff+freebsd@wagsky.com>
Cc: current@FreeBSD.ORG
Subject: Re: ACPI autoload failed -- unable to install
Message-ID: <Pine.BSF.4.21.0203151854140.39257-100000@wildside.wagsky.com>
In-Reply-To: <Pine.BSF.4.21.0203150708330.84877-100000@wildside.wagsky.com>
[...]
I have gotten today's snapshot, 5.0-20020315-CURRENT, created the
kernel and mfsroot 1.44 floppies, and attempted to boot a desktop
machine from them. This is (from my 4.5-STABLE hard drive):
CPU: Pentium III/Pentium III Xeon/Celeron (733.13-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x686 Stepping = 6
Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,
MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory = 402571264 (393136K bytes)
It is an Asus MB with a VIA chipset. Full (4.5) dmesg.boot is attached
at the end of this message.
Once again, the error message is that ACPI cannot be found. BTX then
halts with:
int=00000006 err=00000000 efl=00010006 eip=c0306b40
eax=00000081 ebx=0082fc00 ecx=00000000 edx=00000102
esi=0082f000 edi=009b6000 ebp=00000000 esp=c09b1d98
cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010
cs:eip=ff ff ff ff ff 18 57 56-ff a1 e4 16 37 c0 a3 6c
78 38 c0 a1 e8 16 37 c0-a3 44 79 38 c0 05 a0 1d
ss:esp=04 94 12 c0 00 70 83 00-00 f0 82 00 00 00 00 00
00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
BTX halted
Thanks for your help,
Jeff
On Fri, 15 Mar 2002, Jeff Kletsky wrote:
> Date: Fri, 15 Mar 2002 07:52:17 -0800 (PST)
> From: Jeff Kletsky <jeff+freebsd@wagsky.com>
> To: current@FreeBSD.ORG
> Subject: Re: ACPI autoload failed -- unable to install
>
> With apologies for an incomplete report, I am including the (manually
> transcribed) dump information. I have been able to network boot from a
> combination of the boot.flp and bin distribution (though there are
> problems with getting sysinstall to find disks that prevent that approach
> so far) and confirm that the hw.pcic interrupt routing sysctls *are*
> required. So the report that follows is based on using floppies from
> 5.0-20020314-CURRENT, including the one referred to as 'acpi.ko.flp' in
> the "Failed workaround" description below.
>
> To reproduce, follow the steps 1-7 outlined below. The tail end of the
> process appears as:
>
> OK load acpi.ko
> /boot/kernel/acpi.ko text=0x2b5a0 data=0x1558+0x6cc
> syms=[0x4+0x4ed0+0x4+0x675a]
> OK boot
> /
> int=00000006 err=00000000 efl=00010006 eip=c03069f0
> eax=00000001 ebx=009aec00 ecx=00000000 edx=00000102
> esi=009ae000 edi=009b6000 ebp=00000000 esp=c09b1d98
> cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010
> cs:eip=ff ff ff 83 ec 18 57 ff-ff a1 84 15 37 c0 a3 0c
> 77 38 c0 a1 88 15 37 c0-a3 e4 77 38 c0 05 a0 1d
> ss:esp=04 94 12 c0 00 60 9b 00-00 e0 9a 00 00 00 00 00
> 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00
> BTX halted
>
>
>
> I am willing to try reasonable steps and debugging here. Unfortunately,
> the BIOS driving the USB floppy seems to take about 10 min. to read a
> floppy, so it testing multiple scenarios is somewhat painful. I will be
> working with bootable CD configurations today, though the iLINK
> (IEEE-1394) connection there has its own share of problems (no non-BIOS
> support of the drive). At least with floppies, it *should* be a supported
> configuration. (Note however the reported issues with fixit only being
> mountable from /dev/fd0, not /dev/da0).
>
> Jeff
>
> On Thu, 14 Mar 2002, Jeff Kletsky wrote:
>
> > Date: Thu, 14 Mar 2002 18:49:35 -0800 (PST)
> > From: Jeff Kletsky <jeff+freebsd@wagsky.com>
> > To: current@FreeBSD.ORG
> > Subject: Re: ACPI autoload failed -- unable to install (fwd)
> >
> > Tried the "obvious" -- manually loading acpi.ko -- still fails
> >
> > On Thu, 14 Mar 2002, Jeff Kletsky wrote:
> >
> > > Date: Thu, 14 Mar 2002 17:41:01 -0800 (PST)
> > > From: Jeff Kletsky <jeff+freebsd@wagsky.com>
> > > To: current@FreeBSD.ORG
> > > Subject: ACPI autoload failed -- unable to install
> > >
> > > Having been unable to confirm a complete and proper installation of
> > > 5.0-CURRENT on my Sony PCG-SRX7/EP (similar to SRX77) laptop using the
> > > 4.5-RELEASE installer, I have made a bootable CD from
> > > 5.0-20020313-CURRENT, as well as floppies from 5.0-20020314-CURRENT.
> > > Both exhibit the same set of symptoms.
> >
> > [...]
> >
> > >
> > > Results in:
> > >
> > > ACPI autoload failed - no such file or directory
> > > -
> > > [dump followed]
> >
> > Failed workaround:
> >
> > 1) Create floppies using dd
> > 2) Make another copy of the mfsroot floopy,
> >
> > mount /dev/fd0 /mnt
> > rm -rf /mnt/*
> > mkdir -p /mnt/boot/kernel
> >
> > copy acpi.ko to /mnt/boot/kernel
> >
> > ### Note that copying to root of floppy fails on load attempt ###
> > ### This is inconsistent with the loader (8) manpage in 5.0 ###
> >
> > umount /mnt
> >
> > 3) Boot from kern.flp
> > 4) Load mfsroot.flp
> > 5) Interrupt boot process
> >
> > set hw.pcic.intr_path=1
> > set hw.pcic.irq=0
> >
> > 6) Remove mfsroot.flp, insert 'acpi.ko.flp'
> >
> > load acpi.ko
> >
> > ('boot'ing here causes the BTX to halt if the acpi.ko.flp is still
> > in the drive)
> >
> > 7) Remove acpi.ko.flp, insert mfsroot.flp
> >
> > boot
> >
> > ...and watch the BTX halt
> >
> >
> > Jeff
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
4.5 dmesg.boot to identfy desktop hardware:
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.5-STABLE #0: Fri Mar 15 16:29:39 PST 2002
jeff@jmk64.rubiconproject.com:/usr/obj/usr/src/sys/SMB.20020116
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 733131793 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (733.13-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x686 Stepping = 6
Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PA
T,PSE36,MMX,FXSR,SSE>
real memory = 402571264 (393136K bytes)
config> di pcic0
config> di sn0
No such device: sn0
Invalid command or syntax. Type `?' for help.
config> di lnc0
No such device: lnc0
Invalid command or syntax. Type `?' for help.
config> di ie0
No such device: ie0
Invalid command or syntax. Type `?' for help.
config> di fe0
No such device: fe0
Invalid command or syntax. Type `?' for help.
config> di ed0
No such device: ed0
Invalid command or syntax. Type `?' for help.
config> di cs0
No such device: cs0
Invalid command or syntax. Type `?' for help.
config> di bt0
No such device: bt0
Invalid command or syntax. Type `?' for help.
config> di aic0
No such device: aic0
Invalid command or syntax. Type `?' for help.
config> di aha0
No such device: aha0
Invalid command or syntax. Type `?' for help.
config> di adv0
No such device: adv0
Invalid command or syntax. Type `?' for help.
config> q
avail memory = 387272704 (378196K bytes)
Preloaded elf kernel "kernel" at 0xc040f000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc040f09c.
netsmb_dev: loaded
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 9 entries at 0xc00f12d0
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib2: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib2
pci1: <ATI Mach64-GB graphics accelerator> at 0.0 irq 11
isab0: <VIA 82C686 PCI-ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 82C686 ATA100 controller> port 0xb800-0xb80f at device 4.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: <VIA 83C572 USB controller> port 0xb400-0xb41f irq 10 at device 4.2 on pc
i0
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <VIA 83C572 USB controller> port 0xb000-0xb01f irq 10 at device 4.3 on pc
i0
usb1: <VIA 83C572 USB controller> on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
pci0: <unknown card> (vendor=0x13f6, dev=0x0111) at 5.0 irq 10
fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xa400-0xa43f mem 0xf8800000-0xf88f
ffff,0xf9000000-0xf9000fff irq 11 at device 8.0 on pci0
fxp0: Ethernet address 00:02:b3:08:81:09
inphy0: <i82555 10/100 media interface> on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: <Intel Pro 10/100B/100+ Ethernet> port 0xa000-0xa03f mem 0xf7800000-0xf781
ffff,0xf8000000-0xf8000fff irq 10 at device 10.0 on pci0
fxp1: Ethernet address 00:02:b3:2a:d1:a1
inphy1: <i82555 10/100 media interface> on miibus1
inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pcib1: <Host to PCI bridge> on motherboard
pci2: <PCI bus> on pcib1
orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xd0000-0xd0fff,0xd4000-0xd57ff on
isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
DUMMYNET initialized (011031)
BRIDGE 020214 loaded
IP packet filtering initialized, divert enabled, rule-based forwarding enabled,
default to deny, unlimited logging
IPv6 packet filtering initialized, unlimited logging
ata1-slave: ata_command: timeout waiting for intr
ata1-slave: identify failed
ad0: 9773MB <FUJITSU MPF3102AT> [19857/16/63] at ata0-master UDMA66
ad1: 28629MB <WDC WD300BB-00AUA1> [58168/16/63] at ata0-slave UDMA100
acd0: CDROM <FX4830T> at ata1-master using PIO4
Mounting root from ufs:/dev/ad0s1a
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203160334.g2G3YMm09873>