From owner-freebsd-current@FreeBSD.ORG Sat Aug 23 05:05:11 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF2F116A4BF for ; Sat, 23 Aug 2003 05:05:11 -0700 (PDT) Received: from web14802.mail.yahoo.com (web14802.mail.yahoo.com [216.136.224.218]) by mx1.FreeBSD.org (Postfix) with SMTP id 8646143FBF for ; Sat, 23 Aug 2003 05:05:11 -0700 (PDT) (envelope-from rosti_bsd@yahoo.com) Message-ID: <20030823120511.3203.qmail@web14802.mail.yahoo.com> Received: from [192.114.47.54] by web14802.mail.yahoo.com via HTTP; Sat, 23 Aug 2003 05:05:11 PDT Date: Sat, 23 Aug 2003 05:05:11 -0700 (PDT) From: Rostislav Krasny To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: When this panic will be fixed? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2003 12:05:11 -0000 When FreeBSD 5.0-RELEASE had been released I tried to install it from floppies. I got system panic and then reported this problem into freebsd-stable@freebsd.org mailing list. You can find this report in http://www.atm.tut.fi/list-archive/freebsd-stable/msg08385.html or in http://docs.freebsd.org/cgi/getmsg.cgi?fetch=297316+0+archive/2003/freebsd-stable/20030126.freebsd-stable This is definitely not a hardware problem. Any Windows and FreeBSD 4.x works fine here. Actually FreeBSD 4.x works not so fine but it works; look at following chunk of FreeBSD 4.7 boot log: isa_probe_children: probing PnP devices ed0: at port 0x200-0x21f irq 5 on isa0 bpf: ed0 attached ed0: address 00:00:21:82:25:03, type NE2000 (16 bit) sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 10 drq 0,1 on isa0 sbc0: setting card to irq 10, drq 0, 1 pcm0: on sbc0 pcm0: sndbuf_setmap a000, 1000; 0xcc20d000 -> a000 pcm0: sndbuf_setmap b000, 1000; 0xcc20e000 -> b000 unknown: can't assign resources unknown: at port 0x20f on isa0 I configured the BIOS with "PnP OS = No" option, so the BIOS configures all my PnP devices before even MBR is loading. This is how the BIOS configures my PnP devices: NIC: irq = 10; ports range = 0x0240 - 0x025F SB: irq = 5; DMA = 0, 1; ports ranges = 0x0220 - 0x022F; 0x0300 - 0x0301; 0x0388 - 0x38B Gameport(SB): ports range = 0x0201 - 0x0201 Compare it with my FreeBSD 4.7 boot log above and with my FreeBSD 5.0 boot log (can be found in http://www.atm.tut.fi/list-archive/freebsd-stable/zip00000.zip). Windows (Win98) doesn't reconfigure PnP devices those were already configured by BIOS. I think that FreeBSD should have the same behaviour. At least FreeBSD 5.x will not panic when BIOS is configured with "PnP OS = No" option. The NIC is ISA PnP NE-12 card (NE2000 compatable) based on UMC UM9008/F chip. The SB is ISA PnP Creative SoundBlaster 16 based on ViBRA-16 chip. The Gameport is part of the SB. There is no PCI cards. I tried to install FreeBSD 5.1-RELEASE from floppies but got the same panic. Set BIOS option "PnP OS = Yes" doesn't resolve FreeBSD 5.x panic. Are you going to fix this panic somewhen? Thanks. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com