I disabled wpi0 for test, about 12 hours, it did't freeze or hangup. I guess maybe there is something wrong with firmware or wpi driver.
Just guess... 2006/8/8, Bibby Michael <[EMAIL PROTECTED]>: > > I will disable wpi0 for test later, thanks :) > > >Do you have the right firmware loaded? > > I downloaded and installed the firmware which noticed in OpenBSD's > manual: wpi: > //http://damien.bergamini.free.fr/packages/openbsd/wpi- firmware-1.13.tgz > > $ man wpi > ------skip---- > // > > The driver needs at least version 1.13 of the following firmware file, > which is loaded when an interface is brought up: > > /etc/firmware/wpi-ucode > > This firmware file is not free because Intel refuses to grant > distribu- > tion rights without contractual obligations. As a result, even though > OpenBSD includes the driver, the firmware file cannot be included and > users have to download this file on their own. The official person to > state your views to about this issue is [EMAIL PROTECTED]<mailto:[EMAIL > PROTECTED]> > at > (858) 391 1857. > > A prepackaged version of the firmware, designed to be used with > pkg_add(1) > <http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&arch=i386&apropos=0&manpath=OpenBSD+Current>, > can be found at: > > /http://damien.bergamini.free.fr/packages/openbsd/wpi- > firmware-1.13.tgz / > > ---- skip ----- > // > //Tobias Ulmer wrote: > > > On Mon, Aug 07, 2006 at 03:02:22PM +0800, Bibby Michael wrote: > > > >> Kernel panic: > >> > >> I use OpenBSD 4.0-beta(snapshots). > >> > >> --------------------------- > >> anic: pool_get(mclpl): free list modified; magic=a4153cb5; page > 0xd8038000; > >> item addr 0xd8038800 > >> Stopped at Debugger+0x4: leave > >> > >> RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS > PANIC! > >> DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! > >> > >> ddb{0}> trace > >> Debuuger (c,d1b0a25e,6c,d8038800,d074d5e0 at Debugger+0x4 > >> panic (d0653e40, d0655d09, a4153c65, d803800, d8038800) at panic+0x63 > >> pool_get(d074d5e0,0,e910fce0,d802ab36, d1963406) at pool_get+0x2f9 > >> ieee80211_wep_crypt(d1b0a030, d8033f00, 0,4) at > ieee80211_wep_crypt+0x56) > >> ieee80211_input(d1b0a030, d8033f00, d1ae9a00, 23, 0, d8028818) at > >> ieee80211_input+0x3e4 > >> wpi_rx_intr(d1b0a000,d8028800, d1b0afa4, 16, 0) at wpi_rx_intr+0x3c9 > >> wpi_notif_intr(d1b0a000, d0459f0d, e910ff18, d0459db6) at > >> wpi_notif_intr+0xee > >> wpi_intr(d1b0a000) at wpi_intr+0xca > >> Xintr_ioapic4() at Xintr_ioapic4+0x74 > >> ----------interrupt------------- > >> apm_cpu_idle(0,0,0,0,0) at apm_cpu_idle+0x4a > >> > >> ddb{0}> ps > >> COMMAND only: > >> wget, ksh, dhclient, update, inted, cron, getty, sendmail, syslogd, > crypto, > >> aiodoned, reaper, usbtask, usb[0-4], cardslot0, cleaner, wskbd_hotkey, > >> pfpurge, pagedaemon, kmthread, init, swapper > >> > >> I only use wget in console, without any X-window application running. > >> sendmail/cron/syslogd are system services which bringed up by rc.conf. > >> > >> > >> > > Try to disable wpi(4) and see if it still crashes. > > > > Do you have the right firmware loaded? I don't own such a card but i > > remember people having problems with it because they used firmware for > > -stable and run a -current OS. > > > > Just guessing... > > > > Tobias > > > > > > > > > > > > -- http://www.bsdlife.org #:NRCG5DLINUX/BSDIz;n#!
