From owner-freebsd-questions@FreeBSD.ORG Sun May 18 02:49:34 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C76DA37B409 for ; Sun, 18 May 2003 02:49:34 -0700 (PDT) Received: from digiflux.org (43.Red-80-59-151.pooles.rima-tde.net [80.59.151.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A71343FA3 for ; Sun, 18 May 2003 02:49:32 -0700 (PDT) (envelope-from olivas@digiflux.org) Received: from sentinel (sentinel [10.0.2.5]) (authenticated bits=0) by digiflux.org (8.12.9/8.12.9) with ESMTP id h4I9nUuB037836 for ; Sun, 18 May 2003 11:49:31 +0200 (CEST) (envelope-from olivas@digiflux.org) From: Stacy Olivas Date: Sun, 18 May 2003 11:49:30 +0200 User-Agent: KMail/1.5 To: questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305181149.30440.olivas@digiflux.org> Subject: Fwd: MFS and Kernel panics (5.0-RELEASE-p7) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 May 2003 09:49:35 -0000 [forwarded from -hackers] I originally posted this message to -hackers. I'm forwarding it here as well since someone here might have an idea as well. BTW- I found this "problem" while playing with a PicoBSD build of the kernel. TIA. -Stacy ---------- Forwarded Message ---------- Subject: MFS and Kernel panics (5.0-RELEASE-p7) Date: Saturday 17 May 2003 2:21 am From: Stacy Olivas To: hackers@freebsd.org I've been playing with various MFS file sizes in a kernel and have come across some issues. Either I'm doing something wrong, or there possibly is a bug somewhere. Background: OS: FreeBSD 5.0-RELEASE-p7 When building a kernel with an MFS_ROOT size => 8000 bytes (~7.8 megs), after the kernel has successfully loaded, if you subsequently try mounting a floppy disk (to a mount point on the MFS) (doesn't matter if it's fresh floppy or has some files on it) the kernel panics with the following message: panic: isa_dmastart: bad bounce buffer syncing disks, buffers remaining... panic: bwrite: buffer is not busy??? But, for an MFS that is 7000 (~6.8 megs) it works with out a hitch. This behavior has been reproducable on two different systems with more than plenty of memort available. -- dmesg output of kernel that panics (MD_ROOT_SIZE=8000) (thank god dmesg is saved between warm boots): Copyright (c) 1992-2003 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 5.0-RELEASE-p7 #1: Fri May 16 15:18:39 CEST 2003 olivas@thos.digiflux.org:/usr/src/release/picobsd/warbsd/build_dir-warbsd/PIC OBSD-warbsd Preloaded elf kernel "/kernel" at 0xc0f86000. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 360790606 Hz CPU: AMD-K6(tm) 3D+ Processor (360.79-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x591 Stepping = 1 Features=0x8021bf AMD Features=0xffffffff80000800 real memory = 167772160 (160 MB) avail memory = 146579456 (139 MB) Initializing GEOMetry subsystem K6-family MTRR support enabled (2 registers) ACPI-0159: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES ACPI: table load failed: AE_NO_ACPI_TABLES npx0: on motherboard npx0: INT 16 interface Using $PIR table, 4 entries at 0xc00fdf70 pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 cbb0: at device 10.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pci_cfgintr: 0:10 INTA routed to irq 11 cbb1: at device 10.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pci_cfgintr: 0:10 INTB routed to irq 11 pci0: at device 18.0 (no driver attached) ohci0: mem 0xfecff000-0xfecfffff irq 10 at device 19.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: OPTi OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered atapci0: port 0xfcf0-0xfcff at device 20.0 on pci0 atapci0: Busmastering DMA not supported ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 orm0: