Bug 17870
| Summary: | 4.0-release consistently crashes a couple seconds into the MFSROOT floppy boot process (kern.flp seems OK) | ||
|---|---|---|---|
| Product: | Base System | Reporter: | fbibsd <fbibsd> |
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
Nope, it wasn't a media problem, but thanks for the suggestion --
I've had that type of thing happen before.
I remade the diskettes about three times and checked them vs. the CDROM images
with MD5.
I did track the problem down to what seems to be a kernel problem on the
boot floppies which make it incompatible with the hardware when a particular
BIOS setting is ON ("USB Function Enable").
Interestingly, once I finished the install, (and built a custom kernel,
though perhaps that wasn't necessary to make it not crash -- perhaps I should
try GENERIC again), I was able to reenable "USB Function Enable" and use USBD
usm just fine with the same system's motherboard and USB hub/trackball.
So it seems like BSD 'can' deal with the platform just fine, but that something
is just wrong with the kernel / driver / probe configuration in the boot
floppy. It should have better error handling at least, and ideally it'd just
work perfectly since the USB driver et. al. does work on this platform.
Under ordinary circumstances I'd likely want to be able to install using
a USB keyboard, though I'd prefer BSD to just turn off USB entirely if it has
to (or maybe just temporarily when probing other stuff?)
rather than crash on install boot.
Since the USB controller is PCI and part of a recognized chipset it should
be trivial to account for whatever needs to be done to keep it happy.
Here's what I sent to freebsd-bugs:
Date: Sun, 9 Apr 2000 16:43:49 -0700 (PDT)
From: x <fbibsd@yahoo.com>
To: freebsd-bugs@freebsd.org
Cc: fbibsd@yahoo.com
Subject: kern/17870 mfsroot.flp boot bug: "BIOS USB Function Enable" Off = no problem, On = bug.
Message-ID: <20000409234349.15406.qmail@web2004.mail.yahoo.com>
------------------------------------------------------------------------
Next in thread | Raw E-Mail | Index | Archive | Help
------------------------------------------------------------------------
I've tracked the problem down to the setting of the
BIOS "USB Function Enable" setting.
When "USB Function Enable" is On the bug persists.
When the setting is changed to Off, installation proceeds normally.
The only USB devices are a four port hub, and attached to the first
port of the USB Hub is a Qtronix trackball. Normally I'd use a USB
keyboard, but presently a PS/2 keyboard is in use.
USB Legacy Support option is also set in the BIOS.
3.4-RELEASE floppies worked well desipte the USB Function Enable On.
The USB function is just from the VIA VP2 chipset in the FIC PA2011
motherboard, and it works well under Win98 with my peripherals.
I'll probably test an install under a TMC MI5-VP4 (VIA VP4 chipset)
motherboard soon; I'll see if the crash also happens with it.
--- Sheldon Hearn <sheldonh@uunet.co.za> wrote:
>
>
> On Sat, 08 Apr 2000 18:11:39 MST, fbibsd@yahoo.com wrote:
>
> > * floppies were first made via fdimage, then remade with dd after
> > the first failure, so a floppy disk image error is probably not
> > the cause of the floppy boot failures.
>
> My first guess is media failure. Try putting the mfsroot.flp image on the
> floppy you're using for the kernel floppy and the kern.flp image on the
> floppy you're using for the mfsroot floppy. In other words, swap the
> floppies. :-)
>
> I'll bet the crash happens on the kernel floppy now, right? If so,
> you've got a bad diskette. :-)
>
> Ciao,
> Sheldon.
__________________________________________________
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
http://invites.yahoo.com
Responsible Changed From-To: freebsd-bugs->n_hibma Nick, the originator's feedback makes this look like a USB problem at install-time. Can you take a look? Responsible Changed From-To: n_hibma->freebdsd-bugs iThis can only be a USB problem if there is a problem with interrupt sharing. USB legacy is on, hence the trackball probably is virtualised as a mouse, but this type of device is not used till later on. Responsible Changed From-To: freebdsd-bugs->freebsd-bugs ECANTSPELL State Changed From-To: open->feedback Is this still a problem in more recent releases? State Changed From-To: feedback->closed Mail to submitter bounces. |
Summary: 4.0-Release consistently crashes a couple seconds into the floppy boot of MFSROOT diskette. * Booting not recognized from CDROM #1 (presumably a local BIOS limitation, though I seem to recall that 3.0 could CD boot though then later releases don't, but this isn't the issue) * So: 'dd' used to make /floppies/kern.flp and /floppies/mfsroot.flp from 4.0 release CD set. * kern.flp boots normally and prompts for mfsroot.flp * mfsroot.flp inserted, <ENTER> pressed, system crashes within a few seconds (details/log below) * Problem is repeatable after cold boot / reset; first warm boot retry gave a crash register dump (not inspected); second retry (cold boot) made the system reboot shortly after MFSROOT disk usage started; third retry (cold boot) gave a somewhat differing register dump as that reported below. * floppies were first made via fdimage, then remade with dd after the first failure, so a floppy disk image error is probably not the cause of the floppy boot failures. Motherboard: FIC PA-2011 (VIA VP2 chipset) BIOS: AMI (C) 1996 626CC12 CPU: AMD K6; 233MHz SDRAM: 128 MBy in one DIMM Video: ATI MACH64 SCSI: Diamond Fireport 40UW (NCR 875 type chip) Ethernet: WD 3c905TX-B 10/100 parallel tasking, connected to 100Mbit hub port Sound: SoundBlaster 32 PnP ISA USB devices: HUB, Qtronix trackball Auto-Detecting Primary Master: IDE Hard Disk Auto-Detecting Secondary Master: ATAPI CDROM Auto-Detecting Secondary Slave: Not Detected {None} Primary Master: FA570480 Maxtor 91741U4 Ultra DMA Mode-2 S.M.A.R.T capable and status OK {17 GBy, non UDMA cable, PIO 4 selected in BIOS} Secondary Master: 1R10 Toshiba DVD-ROM SD-M1212 {non UDMA cable, PIO 4 selected in BIOS} Primary Slave: None Secondary Slave: None PCI System BIOS revision 2.10 detected. 51-0606-000000-00111111-071595-VP2-PA2011-T99-F Floppy Drive A: 1.44MB 3.5" Floppy Drive B: None Serial Ports: 3f8 Parallel Ports: 378 External Cache: 512kB, Enabled AMIBIOS Date: 7/15/95 Power Management: Disabled Processor Clock: 233 MHz Display Type: EGA/VGA Hard Disks Cyl Head Sector Size LBA-Mode 32-bit-mode block-mode pio-mode Pri Master 16383 16 63 8064MB LBA On 16Sec 4 Sec Master CDROM 4 Plug And Play ISA Devices: Creative SB32 Pnp PCI Devices: Onboard PCI USB Controller Onboard PCI IDE Controller Slot 1: SCSI, IRQ 10 Slot 2: Ethernet, IRQ 9 Slot 3: VGA Bank 0-1 DRAM type: SDRAM Bank 2-3 DRAM type: None Bank 4-5 DRAM type: None ---------------------------------------------------------------------- {FreeBSD 4.0 Release CDROM set commences booting kern.flp} /boot.config: -P Keyboard: yes BTX loader 1.00 BTX version is 1.01 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/130048kB available memory FreeBSD/i386 bootstrap loader, Revision 0.7 (root@monster.cdrom.com, Mon Mar 20 21:05:31 GMT 2000) /kernel text=0x1d581e data=0x24c60+0x1a718 | Please insert MFS root floppy and press enter: [MFS root diskette inserted, ENTER pressed, then a couple seconds after MFSROOT diskette use begins:] - int=00000006 err=00000000 efl=00010202 eip=00001b68 eax=0000005c ebx=0002eab4 ecx=00000003 edx=000944c4 esi=0002e9dc edi=00001000 ebp=00094498 esp=0009447c cs=002b ds=0033 es=0033 fs=0033 gs=0033 ss=0033 cs:eip=ff bf a5 bb 8c f5 fd ff-6b 9f 64 63 5d 7f 2b 49 ss:esp=08 30 01 00 5c 00 00 00-b4 ea 02 00 c8 44 09 00 System halted ---------------------------------------------------------------------- Fix: no fix discovered. How-To-Repeat: Make kern.flp and mfsroot.flp from 4.0 release CD set Insert kern.flp boot from kern.flp, until it requests mfsroot floppy insert mfsroot floppy hit enter system will crash with register dump or reboot within a few seconds