Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Jan 2002 00:53:25 +0900
From:      mistral@imasy.or.jp (Yoshihiko SARUMARU)
To:        stable@FreeBSD.org
Subject:   miibus.ko was loaded twice and panic on ifconfig
Message-ID:  <020111005325.M0200889@mistral.imasy.or.jp>

next in thread | raw e-mail | index | archive | help
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: <Intel Pro 10/100B/100+ Ethernet> 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: <i82555 10/100 media interface> 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: <Intel Pro 10/100B/100+ Ethernet> 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: <i82555 10/100 media interface> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?020111005325.M0200889>