From owner-freebsd-current@FreeBSD.ORG Wed May 5 23:25:12 2004 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 292B816A4CE for ; Wed, 5 May 2004 23:25:12 -0700 (PDT) Received: from mail-3.zoominternet.net (mail-3.zoominternet.net [63.67.120.3]) by mx1.FreeBSD.org (Postfix) with SMTP id 7563343D2F for ; Wed, 5 May 2004 23:25:11 -0700 (PDT) (envelope-from dmmiller@cvzoom.net) Received: (qmail 1647 invoked from network); 6 May 2004 06:25:08 -0000 Received: from acs-24-239-218-237.zoominternet.net (HELO cvzoom.net) ([24.239.218.237]) (envelope-sender ) by mail-3.zoominternet.net (qmail-ldap-1.03) with SMTP for ; 6 May 2004 06:25:08 -0000 Message-ID: <4099DA46.4000902@cvzoom.net> Date: Thu, 06 May 2004 02:25:10 -0400 From: Donn Miller User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040314 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 06 May 2004 04:59:22 -0700 cc: current@freebsd.org Subject: Re: Panic on boot 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: Thu, 06 May 2004 06:25:12 -0000 Doug White wrote: > On Wed, 28 Apr 2004, Donn Miller wrote: > > >>I've been getting similar panics for the past 2 weeks or so on my HP >>Pavilion laptop (N5440, 850 MHz Pentium III). Sometimes when I attempt >>to boot, like 1 out of 20 times, it doesn't panic for some reason. But >>I do get the same results with every panic, so I know it's not a >>hardware problem. These occur after "vga0" is probed. It's an S3 >>Savage chipset. > > > [...] > > >>stopped at module_lookupbyname+0x24: movl 0x1c(%ebx), %eax >>module_lookupbyname(c06d27e1,0,0,c2bbf300,c06efb78) at >>module_lookupbyname+0x24 >>module_register_init(c0726a8,c1ec00,c1e000,c1ec00,c1e000) at >>module_register_init+0x32 >>mi_startup() at mi_startup+0xb5 >>begin() at begin+0x2c > > > Looks like you might have a bogus or corrupted module. Can you try > booting single-user and disabling any _load directives in boot.conf? If > you can get the system up otherwise, try rebuilding and reinstalling your > kernel. I did try renaming boot.conf to boot.conf.bak so that no modules would load. Did get the same results, i.e., fatal trap, with the module_lookupbyname being the culprit. Oddly enough, after I restored my boot.conf to its proper name, and on the next boot, I escaped to the boot prompt, and did a unload boot all the modules would load, and my system would boot, but I'd keep getting kernel: cbb1: CardBus card activation failed So, I suspect the module_lookupbyname has something to do with the cardbus code clashing with the latest pci commits. BTW, each time I got the "CardBus card activation failed" messages, the system would halt for half a second or so and then resume normally. Strangely enough, the cardbus seems to be initializing properly. There are no PCMCIA cards at all inserted. pcib0: at pcibus 0 on motherboard pci0: on pcib0 $PIR: 0:7 INTD routed to irq 5 $PIR: 0:8 INTA routed to irq 5 $PIR: 0:8 INTA routed to irq 5 $PIR: 0:16 INTA routed to irq 11 agp0: mem 0xec000000-0xefffffff at device 0.0 on pci0 agp0: Reserved 0x4000000 bytes for rid 0x10 type 3 at 0xec000000 pcib1: at device 1.0 on pci0 pci1: on pcib1 $PIR: 1:1 INTA routed to irq 11 pci1: at device 1.0 (no driver attached) cbb0: mem 0x10000000-0x10000fff at device 4.0 on pci0 cbb0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x10000000 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 $PIR: 0:4 INTA routed to irq 11 cbb1: mem 0x10001000-0x10001fff at device 4.1 on pci0 cbb1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x10001000 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 $PIR: 0:4 INTA routed to irq 11