Date: Fri, 4 Aug 2000 19:08:40 -0500 From: "Josh Paetzel" <jpaetzel@hutchtel.net> To: "Patrick Lewis" <pl@teleport.com>, <freebsd-questions@FreeBSD.ORG> Subject: Re: New install - panic Message-ID: <003101bffe71$4fb0a740$40440ace@mark8> References: <20000801225938.A12772@user2.teleport.com> <00de01bffcde$a05cf890$0101a8c0@winbox> <20000802224112.A27746@user2.teleport.com> <20000803210322.A11563@user2.teleport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Patrick Lewis" <pl@teleport.com> To: <freebsd-questions@FreeBSD.ORG> Sent: Thursday, August 03, 2000 11:03 PM Subject: Re: New install - panic > I haven't gotten any further with this problem. Is there some information > I didn't mention that would be helpful? Is there a better list for this > type of question? > > Sorry to pester. RTFM is an appropriate reply; I just don't know which FM > to R. > Have you tried making a new set of floppies using different floppies? The images take up the ENTIRE floppy and sometimes a floppy that is marginal will exhibit unusual and hard to diagnose errors when booting. Josh > -- > Patrick Lewis <pl@teleport.com> > > On Wed, Aug 02, 2000 at 10:41:12PM -0700, Patrick Lewis wrote: > > No luck. I disabled everything but the bare minimum, and I still get the > > same output. > > > > -- > > Patrick Lewis <pl@teleport.com> > > > > On Wed, Aug 02, 2000 at 07:05:40PM -0500, Jeremy Falcon wrote: > > > This has happened to me before on a 4.0 install. It only happened; however, > > > when I didn't do any kernel configuration. Entering the visual kernel > > > editor and not changing anything won't help either. > > > > > > My fix was to remove support for any devices that I didn't have on my > > > computer (i.e. all SCSI devices, etc.). Try that and see if it works. > > > > > > Sincerely, > > > > > > Jeremy Falcon > > > > > > ----- Original Message ----- > > > From: "Patrick Lewis" <pl@teleport.com> > > > To: <freebsd-questions@freebsd.org> > > > Sent: Wednesday, August 02, 2000 12:59 AM > > > Subject: New install - panic > > > > > > > > > > I am trying to install 4.1-RELEASE. Using kern.flp and mfsroot.flp, I get > > > to where I can configure the kernel. > > > > After saving the configuration options, I get the following message: > > > > > > > > avail memory = 10174464 (9936K bytes) > > > > Preloaded elf kernel "kernel" at 0xc063e000. > > > > Preloaded mfs_root "/mfsroot" at 0xc063e084. > > > > Intel Pentium detected, installing workaround for F00F bug > > > > md0: Preloaded image </mfsroot> 2949120 bytes at 0xc036cd98 > > > > md1: Malloc disk > > > > npx0: <math coprocessor> on motherboard > > > > npx0: INT 15 interface > > > > pcib0: <SiS 85c501> on motherboard > > > > pci0: <PCI bus> on pcib0 > > > > isab0: <SiS85c503 PCI-ISA bridge> at device 1.0 on pci0 > > > > isa0: <ISA bus> on isab0 > > > > atapci0: <Generic PCI ATA controller> port > > > 0x3f4-0x3f7,0x374-0x377,0x1f4-0x1f7,0 > > > > x174-0x177 at device 1.1 on pci0 > > > > atapci0: Busmastering DMA not supported > > > > panic: resource_list_alloc: resource entry is busy > > > > Uptime: 0s > > > > Automatic reboot in 15 seconds - press a key on the console to abort > > > > > > > > I am at a loss for what this means. Configuration problem (i.e. operator > > > error), hardware problem, or software bug? > > > > > > > > Please cc: me directly on any replies. Thank you. > > > > > > > > -- > > > > Patrick Lewis <pl@teleport.com> > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003101bffe71$4fb0a740$40440ace>