From owner-freebsd-stable Thu Jan 10 8: 4: 3 2002 Delivered-To: freebsd-stable@freebsd.org Received: from paperboy.epcdirect.co.uk (paperboy.epcdirect.co.uk [195.10.242.11]) by hub.freebsd.org (Postfix) with ESMTP id 6E5DE37B419 for ; Thu, 10 Jan 2002 08:03:54 -0800 (PST) Received: (from root@localhost) by paperboy.epcdirect.co.uk (8.11.6/8.11.1) id g0AG3r583843 for stable@freebsd.org; Thu, 10 Jan 2002 16:03:53 GMT (envelope-from freebsd-net@epcdirect.co.uk) Delivered-To: Received: from lfarr (l-farr.int.epcdirect.co.uk [192.168.6.200]) by paperboy.epcdirect.co.uk (8.11.6/8.11.1av) with ESMTP id g0AG3od83835 for ; Thu, 10 Jan 2002 16:03:50 GMT (envelope-from freebsd-net@epcdirect.co.uk) From: "Lawrence Farr" To: Subject: RE: miibus.ko was loaded twice and panic on ifconfig Date: Thu, 10 Jan 2002 16:03:54 -0000 Message-ID: <001101c199f0$674fac40$c806a8c0@lfarr> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3311 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <020111005325.M0200889@mistral.imasy.or.jp> X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've had exactly the same with the if_lge.ko module and if_lge_load="YES". Lawrence Farr EPC Direct Limited > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of > Yoshihiko SARUMARU > Sent: 10 January 2002 15:53 > To: stable@FreeBSD.ORG > Subject: miibus.ko was loaded twice and panic on ifconfig > > > Hello all, > > I had experienced curious panic with 4.5-RC (or older, maybe). > > - miibus was statically included in /kernel > - fxp was not included in /kernel, and if_fxp_load="YES" was set > in /boot/loader.conf > > Then, I had below message on boot time: > Preloaded elf kernel "kernel" at 0xc0423000. > Preloaded elf module "if_fxp.ko" at 0xc042309c. > Preloaded elf module "miibus.ko" at 0xc042313c. > > The kernel already had miibus, but miibus.ko was loaded by > dependencies of if_fxp.ko. > > > This cause below panic: > > ... > fxp0: port 0xfc40-0xfc7f > mem 0xfec00000-0xfecfffff,0xfedf6000-0xfedf6fff irq 9 at > device 11.0 on pci0 > fxp0: Ethernet address 08:00:46:0f:47:91 > inphy0: on miibus0 > inphy0: no media present > ... > Mounting root from ufs:/dev/ad0s2a > DEPENDENCY NOTE: portmap will be enabled to support amd > swapon: adding /dev/ad0s2b as swap device > Automatic boot in progress... > /dev/ad0s2a: FILESYSTEM CLEAN; SKIPPING CHECKS > /dev/ad0s2a: clean, 2620431 free (111039 frags, 313674 > blocks, 1.5% fragmentation). > Setup PC-CARD: memory beep pccardd. > Doing initial network setup: hostname > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x8 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc03f4980 > stack pointer = 0x10:0xc9dc0b50 > frame pointer = 0x10:0xc9dc0b5c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 62 (ifconfig) > interrupt mask = net > > > I can avoid this panic by including fxp device statically in > kernel too, or load if_fxp after boot sequence was finished > (with miibus was already loaded error). In this manner, fxp0 was > identified as below: > > fxp0: port 0xfc40-0xfc7f > mem 0xfec00000-0xfecfffff,0xfedf6000-0xfedf6fff irq 9 at > device 11.0 on pci0 > fxp0: Ethernet address 08:00:46:0f:47:91 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > > Is there anyone who experienced the same panic? > (You can clearly reboot your system with db> call boot(0) from > this panic. Please try :). > > Thanks, > - Yoshihiko > > -- > Yoshihiko SARUMARU > mail: mistral@imasy.or.jp web: http://www.imasy.or.jp/~mistral/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message