DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082007-07-27T02:46:01ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #742 (In Progress): umount problems with multiple mountshttps://bugs.dragonflybsd.org/issues/7422007-07-27T02:46:01Zcorecode
<p>hey,</p>
<p>yes, my fault, but:</p>
<pre>
%mount
/dev/ad6s1a on / (ufs, local, soft-updates)
/dev/ad6s1b on /pbulk (ufs, local, soft-updates)
/ on /pbulk/clients/labospc67_1/root (null, local, read-only)
/pbulk/clients/labospc67_1/var on /pbulk/clients/labospc67_1/root/var (null, local)
/pbulk/clients/labospc67_1/tmp on /pbulk/clients/labospc67_1/root/tmp (null, local)
/pbulk/clients/labospc67_1/dev on /pbulk/clients/labospc67_1/root/dev (null, local)
/ on /pbulk/clients/labospc67_1/root (null, local, read-only)
%umount labospc67_1/root
umount: unmount of /pbulk/clients/labospc67_1/root failed: Device busy
%umount /pbulk/clients/labospc67_1/root/var
umount: unmount of /pbulk/clients/labospc67_1/root/var failed: Invalid argument
</pre>
<p>something is wrong here. i guess I can't umount the "upper" root mount, because it takes the "lower" root mount first. dito for the subdirs.</p>
<p>cheers<br /> simon</p> DragonFlyBSD - Bug #731 (New): system freeze on "slice too large"https://bugs.dragonflybsd.org/issues/7312007-07-15T20:11:05Zcorecode
<p>hey,</p>
<p>i've now had twice a nasty freeze (kind of) with something like this (hand transcribed):</p>
<p><code>dscheck(#ad/0x20021): slice too large 2/2</code><br />..</p>
<p>then vinum tells me that it put "build" down and continues:</p>
<p>fatal: build.p0.s0 read error, offset 33831591936 for 4096 bytes<br />build.p0.s0: user buffer offset 10209280000 for 4096 bytes</p>
<p>(more slice too large follow)</p>
<p>then, the namecache does</p>
<p>blocked on 0xd4fb7b58 "corecode"</p>
<p>and repeats it every 30 seconds or so. system is unoperable at this point.</p>
<p>breaking to the debugger works, but dumpsys does not work:</p>
<pre>
dumping to dev #ad/0x20023, blockno 2130432
dump failed, reason: area improper
</pre>
<p>i'm running:<br /><pre>
DragonFly sweatshorts.home.corecode.ath.cx 1.9.0-DEVELOPMENT DragonFly 1.9.0-DEVELOPMENT #14: Sun Jun 17 11:03:58 CEST 2007 corecode@sweatshorts.home.corecode.ath.cx:/usr/build/obj/usr/build/src/sys/SWEATSHORTS i386
</pre></p>
<p>i've attached relevant outputs.</p>
<p>thanks,<br /> simon</p> DragonFlyBSD - Bug #725 (In Progress): 'make distribution' fails w/'ro' /usr/objhttps://bugs.dragonflybsd.org/issues/7252007-07-10T09:42:05Zc.turner
<p>This seems to choke on sendmail from a ~1wk build<br />(no code changes on this part of the tree it seems)</p>
<p>not sure if it is 'supposed to work' or<br />for how long it has been broken, so I didn't investigate further..</p>
<p>basically, trying to use a -HEAD machine to build out jail<br />images from a release machine over ro nfs..</p>
<p>Thanks,</p>
<p>- Chris</p> DragonFlyBSD - Bug #679 (New): Netgraph backward compatibility for old *LEN constantshttps://bugs.dragonflybsd.org/issues/6792007-06-05T07:56:01Znant
<p>Maintain the old *LEN netgraph constants around for some time to allow<br />the building of earlier mpd (Multi-link PPP Daemon).</p>
<p>Pointed out by: Alexander Motin <<a class="email" href="mailto:mav@freebsd.org">mav@freebsd.org</a>><br />Obtained from: FreeBSD</p>
<p>BTW: Do we need a BURN_BRIDGES kernel option?</p>
<p>Thanks,<br />Nuno</p> DragonFlyBSD - Bug #604 (In Progress): 1.8.1-RELEASE - clock runs fast on mainboard ASUS P5A-Bhttps://bugs.dragonflybsd.org/issues/6042007-04-18T18:55:03Zyeti
<p>After a fresh install of 1.8.1-RELEASE on a system with ASUS P5A-B<br />mainboard (ALI chipset), the clock runs twice as fast as normal.</p>
<p>Booting with ACPI disabled solved this problem.</p>
<p>The clock problem on some ATI chipsets was a problem in Linux some<br />kernels ago too. The solution was triggered by clock=pit as bootarg if I<br />remember right... maybe having a peek into Linux's code helps.</p> DragonFlyBSD - Bug #600 (New): /sys/libkern/karc4randomhttps://bugs.dragonflybsd.org/issues/6002007-04-11T17:14:04Zrobin_carey5
<p>What is the point of keeping/using the in-kernel arc4<br />random number generator when you already have a very<br />good/superior IBAA/L15 random number generator.</p>
<p>If you need a u_int32_t quantity then simply add a<br />function to /sys/kern/kern_nrandom.c to produce a<br />u_int32_t.</p>
<p>--</p>
<p>Some issues with /sys/libkern/karc4random.c :</p>
<p>(a) If you intend to keep /sys/libkern/karc4random.c I<br />recommend you make a modification to it to improve<br />performance: Every time the karc4_random() function is<br />called it calls getmicrotime(), to check the time, and<br />it also checks the number of runs made, to see if it<br />should reseed itself. You can make a big performance<br />improvement by removing this call to getmicrotime()<br />and instead simply checking the number of runs to<br />determine when it should reseed itself.</p>
<p>(b) The karc4random.c file uses u_int8_t types for<br />arc4_i, arc4_j and arc4_t so there is no need for the<br />% 256 operation - another performance improvement.</p>
<p>(c) In arc4_init() you are throwing away 256*4 bytes<br />of output, when you only need to throw away the first<br />256 bytes of output.</p>
<p>Sincerely,<br />R Carey.</p>
<pre><code>_<em><i></em></i>__<em>_</em>_______________________________________________<br />Yahoo! Answers - Got a question? Someone out there knows the answer. Try it<br />now.<br /><a class="external" href="http://uk.answers.yahoo.com/">http://uk.answers.yahoo.com/</a></code></pre> DragonFlyBSD - Bug #599 (New): 1.9.0 reproducable panichttps://bugs.dragonflybsd.org/issues/5992007-04-11T10:24:26Zpavalos
<p>Here's a panic I'm getting with some pretty serious network (www) load, then <br />doing a netstat -an:</p>
<p>Unread portion of the kernel message buffer:<br />panic: m_copydata, negative off -1<br />mp_lock = 00000000; cpuid = 0; lapic.id = 00000000<br />boot() called on cpu#0</p>
<p>syncing disks... 5<br />done<br />Uptime: 12d22h0m32s</p>
<p>(kgdb) bt<br />#0 dumpsys () at thread.h:83<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> 0xc01954bb in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:370<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: K&R -> ANSI cleanup status (Closed)" href="https://bugs.dragonflybsd.org/issues/2">#2</a> 0xc01957c0 in panic (fmt=Variable "fmt" is not available.<br />) at /usr/src/sys/kern/kern_shutdown.c:767<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: freebsds pipe-reverse test fails on dfly (Closed)" href="https://bugs.dragonflybsd.org/issues/3">#3</a> 0xc01c3a32 in m_copydata (m=0x0, off=0, len=0, cp=0xee9534b0 "\001\001<br />\b\n\006¦*$\035\bͬ") at /usr/src/sys/kern/uipc_mbuf.c:1014<br /><a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: Rework of nrelease (Closed)" href="https://bugs.dragonflybsd.org/issues/4">#4</a> 0xc020fc25 in tcp_output (tp=0xdae0c720) <br />at /usr/src/sys/netinet/tcp_output.c:690<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/dev cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/5">#5</a> 0xc02152bf in tcp_timer_persist (xtp=0xdae0c720) <br />at /usr/src/sys/netinet/tcp_timer.c:363<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: sys/emulation cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/6">#6</a> 0xc01a6423 in softclock_handler (arg=0xc0386a80) <br />at /usr/src/sys/kern/kern_timeout.c:307<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: /sys/boot cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/7">#7</a> 0xc019d037 in lwkt_deschedule_self (td=Variable "td" is not available.<br />) at /usr/src/sys/kern/lwkt_thread.c:207<br />Previous frame inner to this frame (corrupt stack?)</p>
<p>The kernel and vmcore is being uploaded to leaf. The source is from March 28.</p>
<p>--Peter</p> DragonFlyBSD - Bug #570 (Feedback): 1.8.x: ACPI problemshttps://bugs.dragonflybsd.org/issues/5702007-03-03T11:46:01Zqhwt+dfly
<p>So if you enable ACPI and boot, it won't respond to keyboard no matter<br />whether you choose to boot into single- or multi-user mode?</p>
<p>So ... your keyboard does not work when you boot straight into the<br />single user mode, whether with or without ACPI driver enabled, right?<br />If not, I have no idea what this part really means:<br /> > But If I boot to non-ACPI-mode, everything works<br /> > just fine, but I can't get to sigle user mode, because prompt freezes<br /> > there too...</p>
<p>If the message buffer(which dmesg command shows you) survives across<br />reboot, I'd like to look at it after you boot with ACPI driver enabled<br />and booted with `boot -v' from the boot loader prompt (did I ask if<br />keyboard works when you go into the boot loader prompt?).</p>
<p>Cheers.</p> DragonFlyBSD - Bug #385 (Feedback): Mail archive address removalhttps://bugs.dragonflybsd.org/issues/3852006-11-22T22:22:03Zjustin
<p>Here's a question for everyone: I had originally the mail archive to<br />completely remove mail addresses, but it seems to mostly be annoying -<br />contacting someone from an archived email would be a dead end unless you<br />happened to already know the person's email address. Meanwhile, the<br />DragonFly lists are archived other places like MARC and Gmane, and<br />addresses are at best mildly obfusticated there.</p>
<p>Opinions? If anyone is significantly bothered by this, I'll keep the<br />addresses completely hidden.</p> DragonFlyBSD - Bug #341 (New): Vinum erroneously repors devices as busyhttps://bugs.dragonflybsd.org/issues/3412006-10-05T22:58:36Zcorecode
<p>Most of the time vinum reports devices as busy when they are not. At least I<br />can't find a different way than to use stop -f.</p> DragonFlyBSD - Bug #331 (In Progress): ftpsesame (aka Bridging S01E03)https://bugs.dragonflybsd.org/issues/3312006-09-27T05:59:03Zbastyaelvtars
ftpsesame cannot allow ftp active filetransfers. Built it with debug <br />(from wip/ftpsesame) and running:<br />---------------------------------------------------------------------------
<ol>
<li>gdb ftpsesame<br />..<br />(gdb) set args -d -D7 -isk1<br />(gdb) b filter_allow<br />Breakpoint 1 at 0x80493c0: file filter.c, line 104.<br />(gdb) run<br />Starting program: <br />/usr/obj/pkgsrc/wip/ftpsesame/work/ftpsesame-0.95/ftpsesame -d -D7 -isk1<br />listening on sk1, filter 'tcp and port 21', snaplen 500<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> session init: client 160.114.118.95:1875, server 193.6.210.44:21<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> client: USER anonymous<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> server: 331 Please specify the password.<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> client: PASS -wget@<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> server: 230 Login successful.<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> client: SYST<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> server: 215 UNIX Type: L8<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> client: PWD<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> server: 257 "/" <br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> client: TYPE I<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> server: 200 Switching to Binary mode.<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> client: CWD /pub/mirrors/knoppix<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> server: 250-Check KNOPPIX-CHANGELOG.txt for the recent changes in <br />KNOPPIX.<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> client: PORT 160,114,118,95,7,84<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> server: 200 PORT command successful. Consider using PASV.<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> active: PORT 160,114,118,95,7,84<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> allowing 193.6.210.44 to 160.114.118.95 port 1876</li>
</ol>
<p>Breakpoint 1, filter_allow (id=1, src=0x281619e8, src2=0x281270ab, <br />dst=0xbfbff268, d_port=1860) at filter.c:104<br />104 {<br />(gdb) n<br />109 snprintf(an, PF_ANCHOR_NAME_SIZE, "%s/%d.%d", <br />FTPSESAME_ANCHOR,<br />(gdb) n<br />111 strlcpy(pfp.anchor, an, PF_ANCHOR_NAME_SIZE);<br />(gdb) n<br />112 strlcpy(pfr.anchor, an, PF_ANCHOR_NAME_SIZE);<br />(gdb) n<br />113 strlcpy(pfte.anchor, an, PF_ANCHOR_NAME_SIZE);<br />(gdb) n<br />115 if (ioctl(dev, DIOCXBEGIN, &pft) <del>1)<br />(gdb) n<br />116 return (0);<br />(gdb) n<br />115 if (ioctl(dev, DIOCXBEGIN, &pft) -1)<br />(gdb) n<br />141 }<br />(gdb) n<br />servertalk (s=0x28169000, sbuf=0x281619e8 "200 PORT command successful. <br />Consider using PASV.") at errno.h:52<br />52 return (&errno);<br />(gdb) n<br />51 {<br />(gdb) n<br /><a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: lib/libcr/sys/ cleanup (Closed)" href="https://bugs.dragonflybsd.org/issues/1">#1</a> filter_allow failed: Invalid argument<br />201 }<br />(gdb) n<br />process_pkt (notused=0x0, h=0xa, p=0x281619c8 "") at ftpsesame.c:438<br />438 s</del>>clientbuf<sup><a href="#fn0">0</a></sup> = '\0';<br />(gdb) n<br />439 }<br />(gdb) n<br />0x2808bf73 in pcap_lookupnet () from /usr/lib/libpcap.so.3<br />(gdb) n<br />Single stepping until exit from function pcap_lookupnet,<br />which has no line number information.<br /><a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: freebsds pipe-reverse test fails on dfly (Closed)" href="https://bugs.dragonflybsd.org/issues/3">#3</a> client: RETR KNOPPIX_V4.0.2CD-2005-09-23-DE.iso<br />0x2808ce00 in pcap_dispatch () from /usr/lib/libpcap.so.3<br />---------------------------------------------------------------------------</p>
<p>On the client machine (also DragonFly :-D):<br />---------------------------------------------------------------------------<br /> > wget --no-passive-ftp <br /><a class="external" href="ftp://xenia.sote.hu/pub/mirrors/knoppix/KNOPPIX_V4.0.2CD-2005-09-23-DE.iso">ftp://xenia.sote.hu/pub/mirrors/knoppix/KNOPPIX_V4.0.2CD-2005-09-23-DE.iso</a><br />--23:39:17-- <br /><a class="external" href="ftp://xenia.sote.hu/pub/mirrors/knoppix/KNOPPIX_V4.0.2CD-2005-09-23-DE.iso">ftp://xenia.sote.hu/pub/mirrors/knoppix/KNOPPIX_V4.0.2CD-2005-09-23-DE.iso</a><br /> => `KNOPPIX_V4.0.2CD-2005-09-23-DE.iso'<br />Resolving xenia.sote.hu... 193.6.210.44<br />Connecting to xenia.sote.hu|193.6.210.44|:21... connected.<br />Logging in as anonymous ... Logged in!<br />> SYST ... done. > PWD ... done.<br />> TYPE I ... done. > CWD /pub/mirrors/knoppix ... done.<br />> PORT ... done. > RETR KNOPPIX_V4.0.2CD-2005-09-23-DE.iso ...<br />Error in server response, closing control connection.<br />Retrying.</p>
<p>--23:40:18-- <br /><a class="external" href="ftp://xenia.sote.hu/pub/mirrors/knoppix/KNOPPIX_V4.0.2CD-2005-09-23-DE.iso">ftp://xenia.sote.hu/pub/mirrors/knoppix/KNOPPIX_V4.0.2CD-2005-09-23-DE.iso</a><br /> (try: 2) => `KNOPPIX_V4.0.2CD-2005-09-23-DE.iso'<br />Connecting to xenia.sote.hu|193.6.210.44|:21... connected.<br />Logging in as anonymous ... Logged in!<br />> SYST ... done. > PWD ... done.<br />> TYPE I ... done. > CWD /pub/mirrors/knoppix ... done.<br />> PORT ... done. > RETR KNOPPIX_V4.0.2CD-2005-09-23-DE.iso ...<br />---------------------------------------------------------------------------</p>
<p>We tried to debug with Joerg off-list (cause the list was offline) but <br />it somehow got suspended. I know I am getting on the list members' <br />nerves, but this is the very last thing I need to complete my mission <br />(kinda funny thing: everything that I need does not work :-P).</p> DragonFlyBSD - Bug #293 (Feedback): Various updates to the handbookhttps://bugs.dragonflybsd.org/issues/2932006-08-11T04:26:06Zvictor
<p>Hi,</p>
<p>there are 3 patches attached:</p>
<p>book.diff - Updates the copyright info relating to FreeBSD at the header<br /> of the handbook.</p>
<p>dfbsd-updating - Update cvsup port path to the current pkgsrc version in<br /> the chapter "Updating DragonFly".</p>
<p>basics.diff - Update various paths relating to pkgsrc and hier(7). Also<br /> make it use the new entity for pkgsrc <br /> tree/collection/framework.</p> DragonFlyBSD - Bug #285 (Feedback): interrupt latency with re without ip address configuredhttps://bugs.dragonflybsd.org/issues/2852006-08-07T06:00:07Zthomas.nikolajsen
<p>Playing sound using pcm(4)/snd(4) gives bad quality: hiss and hops, like sound isn't playing for very short time periods.</p>
<p>This is experienced:<br /> - not having SMP in kernel config (eg GENERIC)<br /> - from dfly-1.5 26th December '05 (24th is ok using kernels from chlamydia);<br />including HEAD.</p>
<p>dfly-1.4 is ok, including 1.4.4.</p>
<p>Using audio/mpg123 for MP3, 'cp test.raw /dev/dspW' or pcmplay for decoded sound.<br />Buffering audio data with mpg123 -b doesn't sound like making any difference.</p>
<p>CPU load doesn't sound like making any difference.<br />Problem experienced on several systems, using snd_via8233 and snd_ich.</p>
<p>No X11 used.</p>
<pre><code>-thomas</code></pre> DragonFlyBSD - Bug #243 (Feedback): weird behavior in the shellhttps://bugs.dragonflybsd.org/issues/2432006-07-15T14:49:02Zswildner
<p>Hi,</p>
<p>I'm not sure if this is a 'real' bug but I'm curious if anyone knows the <br />cause. Check this:</p>
<p>zoot# echo $PATH<br />/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/pkg/bin:/usr/pkg/sbin:/usr/pkg/xorg/bin:/home/s/bin<br />zoot# pwd<br />/usr/src/sys/dev/disk/md<br />zoot# .<br />/usr/sbin/.: Permission denied.<br />zoot# cd /<br />zoot# .<br />/usr/sbin/.: Permission denied.</p>
<p>In other words: The strange thing is that whereever I type . on the csh <br />prompt, I get the /usr/sbin/.: message regardless of what my current <br />directory is.</p>
<p>On a Solaris system I get ".: Permission denied." which is what I'd <br />expect rather.</p>
<p>So, can anyone enlighten me why DragonFly behaves like that?</p>
<p>Sascha</p> DragonFlyBSD - Bug #168 (In Progress): Livelocked limit engaged while trying to setup IPW wirelesshttps://bugs.dragonflybsd.org/issues/1682006-05-05T16:20:50Zmschacht
<p>Dear all,</p>
<p>A few days ago I wanted to try Sephe's 80211 patch to get wpa<br />working under DF. However, I can't load the firmware (neither with<br />nor without the patch). After ipwcontrol and ifconfig I get the<br />following error messages:</p>
<p>intr 5 at 50001 > 50000 hz, livelocked limit engaged!<br />ipw0: timeout waiting for firmware initialization to complete<br />ipw0: could not load firmware<br />intr 5 at 7399 < 20000 hz, livelock removed</p>
<p>ACPI turned on or off doesn't seem to make a difference.<br />I attached a verbose dmesg and vmstat -i before and after</p>
<p>ipwcontrol ipw0 -f....</p>
<p>and after</p>
<p>ifconfig ipw0 inet ... netmask ...</p>
<p>Best regards,<br />Mathias</p>
<p>PS: wep worked under FBSD60 and under WinXP</p>