Re: iwn firmware instability with an up-to-date stable kernel
On Fri, Apr 23, 2010 at 10:08 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Sat, Apr 24, 2010 at 4:59 AM, Garrett Cooper yanef...@gmail.com wrote: On Fri, Apr 23, 2010 at 9:42 PM, Garrett Cooper yanef...@gmail.com wrote: On Fri, Apr 23, 2010 at 8:05 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: 2010/4/23 Garrett Cooper yanef...@gmail.com: 2010/4/23 Garrett Cooper yanef...@gmail.com: 2010/4/18 Olivier Cochard-Labbé oliv...@cochard.me: 2010/4/18 Bernhard Schmidt bschm...@techwires.net: Are you able to reproduce this on demand? As in type a few commands and the firmware error occurs? No, I'm not able to reproduce on demand this problem. I'm seeing similar issues on occasion with my Lenovo as well: Apr 23 19:25:24 garrcoop-fbsd kernel: firmware error log: Apr 23 19:25:24 garrcoop-fbsd kernel: error type = NMI_INTERRUPT_WDG (0x0004) Apr 23 19:25:24 garrcoop-fbsd kernel: program counter = 0x046C Apr 23 19:25:24 garrcoop-fbsd kernel: source line = 0x00D0 Apr 23 19:25:24 garrcoop-fbsd kernel: error data = 0x00020703 Apr 23 19:25:24 garrcoop-fbsd kernel: branch link = 0x837004C2 Apr 23 19:25:24 garrcoop-fbsd kernel: interrupt link = 0x06DA18B8 Apr 23 19:25:24 garrcoop-fbsd kernel: time = 4287402440 Apr 23 19:25:24 garrcoop-fbsd kernel: driver status: Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 0: qid=0 cur=1 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 1: qid=1 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 2: qid=2 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 3: qid=3 cur=36 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 4: qid=4 cur=123 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 5: qid=5 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 6: qid=6 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 7: qid=7 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 8: qid=8 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 9: qid=9 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 10: qid=10 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 11: qid=11 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 12: qid=12 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 13: qid=13 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 14: qid=14 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 15: qid=15 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: rx ring: cur=8 This may be because the system was under load (I was installing a port shortly before the connection dropped). I'll try poking at this further because it's going to be an annoying productivity loss :/. Sorry... should have included more helpful details. Thanks, -Garrett dmesg: iwn0: Intel(R) PRO/Wireless 4965BGN mem 0xdf2fe000-0xdf2f irq 17 at device 0.0 on pci3 iwn0: MIMO 2T3R, MoW1, address 00:1d:e0:7d:9f:c7 iwn0: [ITHREAD] iwn0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps pciconf -lv snippet: i...@pci0:3:0:0: class=0x028000 card=0x11108086 chip=0x42308086 rev=0x61 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Wireless WiFi Link 4965AGN (Intel 4965AGN)' class = network c...@pci0:21:0:0: class=0x060700 card=0x20c617aa chip=0x04761180 rev=0xba hdr=0x02 uname -a: $ uname -a FreeBSD garrcoop-fbsd.cisco.com 8.0-STABLE FreeBSD 8.0-STABLE #0 r207006: Wed Apr 21 13:18:44 PDT 2010 r...@garrcoop-fbsd.cisco.com:/usr/obj/usr/src/sys/LAPPY_X86 i386 I'm actually looking at this right now. For me, it's actually happening when my machine stays on overnight (or for long periods of time, idle). Also, it seems to be causing the kernel to panic, although I'm now wondering if the Machine Check Architecture is somehow catching this device error and causing an exception (hw.mca.enabled=1)(?) -- not possible, right ??? Whatever the case, I can't seem to get the firmware error to occur with iwn(4) debugging or wlandebug options enabled, so who knows exactly what leads to this. I know Bernhard has worked hard on this driver, it's a shame that this freaky bug has bit us all now, without leaving many clues :( I've attached a textdump for posterity if nothing else :) Connectivity appears to be shoddy in my neck of the woods (kind of ironic... but meh). Just running buildworld, buildkernel, then doing a tcpdump in parallel causes the pseudo device to go up and down a lot. I assume this isn't standard behavior? Just for reference buildworld was started shortly after 19:39:05, and it finished at 21:29. The interface has also gone up and down once since then while the system's
Re: kernel: arpresolve: can't allocate llinfo
I am upgraded to FreeBSD vpn3 8.0-STABLE FreeBSD 8.0-STABLE #2 r207058M: Thu Apr 22 15:40:40 EEST 2010 ad...@vpn3:/usr/obj/usr/src/sys/GENERICVPN i386 but memory still leak: after 1 day uptime: vmstat -m | grep lltable lltable 24966 3158K -57483 128,256 mpd5.5 provide real IP address, may be create script if-down.sh to clear link in arp lltable? 2010/4/21 Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net On Wed, 21 Apr 2010, Bjoern A. Zeeb wrote: On Wed, 21 Apr 2010, Denis Lamanov wrote: Hi, vmstat -m | grep lltable every 3 minutes increases :( lltable 16938 2149K -17779 128,256 I'll MFC the patches to fix that the next couple of days, maybe tommorow morning. In case you want to try them, you'd need SVN r206469,206470,206481 applied to 8-STABLE. Actually I just merged them. If you wait an hour or two for the changes to show up on your local mirror 8-STABLE should be fine. Please note that if you are using option FLOWTABLE you will still see the leak. I haven't gotten around to update my patches for that. I'll try to remember to post them once done. /bz -- Bjoern A. Zeeb It will not break if you know what you are doing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: iwn firmware instability with an up-to-date stable kernel
On Fri, Apr 23, 2010 at 11:27:32PM -0700, Garrett Cooper wrote: On Fri, Apr 23, 2010 at 10:08 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Sat, Apr 24, 2010 at 4:59 AM, Garrett Cooper yanef...@gmail.com wrote: On Fri, Apr 23, 2010 at 9:42 PM, Garrett Cooper yanef...@gmail.com wrote: On Fri, Apr 23, 2010 at 8:05 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: 2010/4/23 Garrett Cooper yanef...@gmail.com: 2010/4/23 Garrett Cooper yanef...@gmail.com: 2010/4/18 Olivier Cochard-Labbé oliv...@cochard.me: 2010/4/18 Bernhard Schmidt bschm...@techwires.net: Are you able to reproduce this on demand? As in type a few commands and the firmware error occurs? No, I'm not able to reproduce on demand this problem. I'm seeing similar issues on occasion with my Lenovo as well: Apr 23 19:25:24 garrcoop-fbsd kernel: firmware error log: Apr 23 19:25:24 garrcoop-fbsd kernel: error type = NMI_INTERRUPT_WDG (0x0004) Apr 23 19:25:24 garrcoop-fbsd kernel: program counter = 0x046C Apr 23 19:25:24 garrcoop-fbsd kernel: source line = 0x00D0 Apr 23 19:25:24 garrcoop-fbsd kernel: error data = 0x00020703 Apr 23 19:25:24 garrcoop-fbsd kernel: branch link = 0x837004C2 Apr 23 19:25:24 garrcoop-fbsd kernel: interrupt link = 0x06DA18B8 Apr 23 19:25:24 garrcoop-fbsd kernel: time = 4287402440 Apr 23 19:25:24 garrcoop-fbsd kernel: driver status: Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 0: qid=0 cur=1 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 1: qid=1 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 2: qid=2 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 3: qid=3 cur=36 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 4: qid=4 cur=123 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 5: qid=5 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 6: qid=6 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 7: qid=7 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 8: qid=8 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 9: qid=9 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 10: qid=10 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 11: qid=11 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 12: qid=12 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 13: qid=13 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 14: qid=14 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 15: qid=15 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: rx ring: cur=8 This may be because the system was under load (I was installing a port shortly before the connection dropped). I'll try poking at this further because it's going to be an annoying productivity loss :/. Sorry... should have included more helpful details. Thanks, -Garrett dmesg: iwn0: Intel(R) PRO/Wireless 4965BGN mem 0xdf2fe000-0xdf2f irq 17 at device 0.0 on pci3 iwn0: MIMO 2T3R, MoW1, address 00:1d:e0:7d:9f:c7 iwn0: [ITHREAD] iwn0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps pciconf -lv snippet: i...@pci0:3:0:0: class=0x028000 card=0x11108086 chip=0x42308086 rev=0x61 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Wireless WiFi Link 4965AGN (Intel 4965AGN)' class = network c...@pci0:21:0:0: class=0x060700 card=0x20c617aa chip=0x04761180 rev=0xba hdr=0x02 uname -a: $ uname -a FreeBSD garrcoop-fbsd.cisco.com 8.0-STABLE FreeBSD 8.0-STABLE #0 r207006: Wed Apr 21 13:18:44 PDT 2010 r...@garrcoop-fbsd.cisco.com:/usr/obj/usr/src/sys/LAPPY_X86 i386 I'm actually looking at this right now. For me, it's actually happening when my machine stays on overnight (or for long periods of time, idle). Also, it seems to be causing the kernel to panic, although I'm now wondering if the Machine Check Architecture is somehow catching this device error and causing an exception (hw.mca.enabled=1)(?) -- not possible, right ??? Whatever the case, I can't seem to get the firmware error to occur with iwn(4) debugging or wlandebug options enabled, so who knows exactly what leads to this. I know Bernhard has worked hard on this driver, it's a shame that this freaky bug has bit us all now, without leaving many clues :( I've attached a textdump for posterity if nothing else :) Connectivity appears to be shoddy in my neck of the woods (kind of ironic... but meh). Just running buildworld, buildkernel, then doing a tcpdump in parallel causes the pseudo device to go up and down a
Re: iwn firmware instability with an up-to-date stable kernel
On Sat, Apr 24, 2010 at 12:34 AM, Bernhard Schmidt bschm...@techwires.net wrote: On Fri, Apr 23, 2010 at 11:27:32PM -0700, Garrett Cooper wrote: On Fri, Apr 23, 2010 at 10:08 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Sat, Apr 24, 2010 at 4:59 AM, Garrett Cooper yanef...@gmail.com wrote: On Fri, Apr 23, 2010 at 9:42 PM, Garrett Cooper yanef...@gmail.com wrote: On Fri, Apr 23, 2010 at 8:05 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: 2010/4/23 Garrett Cooper yanef...@gmail.com: 2010/4/23 Garrett Cooper yanef...@gmail.com: 2010/4/18 Olivier Cochard-Labbé oliv...@cochard.me: 2010/4/18 Bernhard Schmidt bschm...@techwires.net: Are you able to reproduce this on demand? As in type a few commands and the firmware error occurs? No, I'm not able to reproduce on demand this problem. I'm seeing similar issues on occasion with my Lenovo as well: Apr 23 19:25:24 garrcoop-fbsd kernel: firmware error log: Apr 23 19:25:24 garrcoop-fbsd kernel: error type = NMI_INTERRUPT_WDG (0x0004) Apr 23 19:25:24 garrcoop-fbsd kernel: program counter = 0x046C Apr 23 19:25:24 garrcoop-fbsd kernel: source line = 0x00D0 Apr 23 19:25:24 garrcoop-fbsd kernel: error data = 0x00020703 Apr 23 19:25:24 garrcoop-fbsd kernel: branch link = 0x837004C2 Apr 23 19:25:24 garrcoop-fbsd kernel: interrupt link = 0x06DA18B8 Apr 23 19:25:24 garrcoop-fbsd kernel: time = 4287402440 Apr 23 19:25:24 garrcoop-fbsd kernel: driver status: Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 0: qid=0 cur=1 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 1: qid=1 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 2: qid=2 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 3: qid=3 cur=36 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 4: qid=4 cur=123 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 5: qid=5 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 6: qid=6 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 7: qid=7 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 8: qid=8 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 9: qid=9 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 10: qid=10 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 11: qid=11 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 12: qid=12 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 13: qid=13 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 14: qid=14 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 15: qid=15 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: rx ring: cur=8 This may be because the system was under load (I was installing a port shortly before the connection dropped). I'll try poking at this further because it's going to be an annoying productivity loss :/. Sorry... should have included more helpful details. Thanks, -Garrett dmesg: iwn0: Intel(R) PRO/Wireless 4965BGN mem 0xdf2fe000-0xdf2f irq 17 at device 0.0 on pci3 iwn0: MIMO 2T3R, MoW1, address 00:1d:e0:7d:9f:c7 iwn0: [ITHREAD] iwn0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps pciconf -lv snippet: i...@pci0:3:0:0: class=0x028000 card=0x11108086 chip=0x42308086 rev=0x61 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Wireless WiFi Link 4965AGN (Intel 4965AGN)' class = network c...@pci0:21:0:0: class=0x060700 card=0x20c617aa chip=0x04761180 rev=0xba hdr=0x02 uname -a: $ uname -a FreeBSD garrcoop-fbsd.cisco.com 8.0-STABLE FreeBSD 8.0-STABLE #0 r207006: Wed Apr 21 13:18:44 PDT 2010 r...@garrcoop-fbsd.cisco.com:/usr/obj/usr/src/sys/LAPPY_X86 i386 I'm actually looking at this right now. For me, it's actually happening when my machine stays on overnight (or for long periods of time, idle). Also, it seems to be causing the kernel to panic, although I'm now wondering if the Machine Check Architecture is somehow catching this device error and causing an exception (hw.mca.enabled=1)(?) -- not possible, right ??? Whatever the case, I can't seem to get the firmware error to occur with iwn(4) debugging or wlandebug options enabled, so who knows exactly what leads to this. I know Bernhard has worked hard on this driver, it's a shame that this freaky bug has bit us all now, without leaving many clues :( I've attached a textdump for posterity if nothing else :) Connectivity appears to be shoddy in my neck of the woods (kind of ironic... but meh). Just running buildworld,
Re: iwn firmware instability with an up-to-date stable kernel
On Sat, Apr 24, 2010 at 12:45:14AM -0700, Garrett Cooper wrote: On Sat, Apr 24, 2010 at 12:34 AM, Bernhard Schmidt bschm...@techwires.net wrote: On Fri, Apr 23, 2010 at 11:27:32PM -0700, Garrett Cooper wrote: On Fri, Apr 23, 2010 at 10:08 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: On Sat, Apr 24, 2010 at 4:59 AM, Garrett Cooper yanef...@gmail.com wrote: On Fri, Apr 23, 2010 at 9:42 PM, Garrett Cooper yanef...@gmail.com wrote: On Fri, Apr 23, 2010 at 8:05 PM, Brandon Gooch jamesbrandongo...@gmail.com wrote: 2010/4/23 Garrett Cooper yanef...@gmail.com: 2010/4/23 Garrett Cooper yanef...@gmail.com: 2010/4/18 Olivier Cochard-Labbé oliv...@cochard.me: 2010/4/18 Bernhard Schmidt bschm...@techwires.net: Are you able to reproduce this on demand? As in type a few commands and the firmware error occurs? No, I'm not able to reproduce on demand this problem. I'm seeing similar issues on occasion with my Lenovo as well: Apr 23 19:25:24 garrcoop-fbsd kernel: firmware error log: Apr 23 19:25:24 garrcoop-fbsd kernel: error type = NMI_INTERRUPT_WDG (0x0004) Apr 23 19:25:24 garrcoop-fbsd kernel: program counter = 0x046C Apr 23 19:25:24 garrcoop-fbsd kernel: source line = 0x00D0 Apr 23 19:25:24 garrcoop-fbsd kernel: error data = 0x00020703 Apr 23 19:25:24 garrcoop-fbsd kernel: branch link = 0x837004C2 Apr 23 19:25:24 garrcoop-fbsd kernel: interrupt link = 0x06DA18B8 Apr 23 19:25:24 garrcoop-fbsd kernel: time = 4287402440 Apr 23 19:25:24 garrcoop-fbsd kernel: driver status: Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 0: qid=0 cur=1 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 1: qid=1 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 2: qid=2 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 3: qid=3 cur=36 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 4: qid=4 cur=123 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 5: qid=5 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 6: qid=6 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 7: qid=7 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 8: qid=8 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 9: qid=9 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 10: qid=10 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 11: qid=11 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 12: qid=12 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 13: qid=13 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 14: qid=14 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: tx ring 15: qid=15 cur=0 queued=0 Apr 23 19:25:24 garrcoop-fbsd kernel: rx ring: cur=8 This may be because the system was under load (I was installing a port shortly before the connection dropped). I'll try poking at this further because it's going to be an annoying productivity loss :/. Sorry... should have included more helpful details. Thanks, -Garrett dmesg: iwn0: Intel(R) PRO/Wireless 4965BGN mem 0xdf2fe000-0xdf2f irq 17 at device 0.0 on pci3 iwn0: MIMO 2T3R, MoW1, address 00:1d:e0:7d:9f:c7 iwn0: [ITHREAD] iwn0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps pciconf -lv snippet: i...@pci0:3:0:0: class=0x028000 card=0x11108086 chip=0x42308086 rev=0x61 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Wireless WiFi Link 4965AGN (Intel 4965AGN)' class = network c...@pci0:21:0:0: class=0x060700 card=0x20c617aa chip=0x04761180 rev=0xba hdr=0x02 uname -a: $ uname -a FreeBSD garrcoop-fbsd.cisco.com 8.0-STABLE FreeBSD 8.0-STABLE #0 r207006: Wed Apr 21 13:18:44 PDT 2010 r...@garrcoop-fbsd.cisco.com:/usr/obj/usr/src/sys/LAPPY_X86 i386 I'm actually looking at this right now. For me, it's actually happening when my machine stays on overnight (or for long periods of time, idle). Also, it seems to be causing the kernel to panic, although I'm now wondering if the Machine Check Architecture is somehow catching this device error and causing an exception (hw.mca.enabled=1)(?) -- not possible, right ??? Whatever the case, I can't seem to get the firmware error to occur with iwn(4) debugging or wlandebug options enabled, so who knows exactly what leads to this. I know Bernhard has worked hard on this driver, it's a shame that this freaky bug has bit us all now, without
Re: FreeBSD on MacBook Pro.
Le Fri, 23 Apr 2010 23:42:37 +0200, Peter Ankerstål pe...@pean.org a écrit : Im trying to install FreeBSD on a macbook with dualboot. Everyting works out fine but the keymap doesnt work at all. I've tried alot of keymaps but everyting it produces is mumbojumbo. What keymap should I use to get the macbook working in console? -- There is a french keymap fr.macbook.acc.kbd. May be you can adapt it? This it not very hard to do. There is a new and small utility to get the scancode (use it in a console, not under X): http://hack.org/mc/hacks/kbdscan/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD on MacBook Pro.
Actuall it seems to work with US ISO och US UNIX too but only with the fixit cd. In the FreeBSD boot-meny I also can use the keyboard properly, but when Im trying to log in on the booted system no keys work properly. It almost seems like the ctrl-key is constantly pressed. (pressing say F gives me ^F on the screen and L clears it like ctrl+L does) -- Peter Ankerstål pe...@pean.org http://www.pean.org/ On 24 apr 2010, at 13.34, Patrick Lamaiziere wrote: Le Fri, 23 Apr 2010 23:42:37 +0200, Peter Ankerstål pe...@pean.org a écrit : Im trying to install FreeBSD on a macbook with dualboot. Everyting works out fine but the keymap doesnt work at all. I've tried alot of keymaps but everyting it produces is mumbojumbo. What keymap should I use to get the macbook working in console? -- There is a french keymap fr.macbook.acc.kbd. May be you can adapt it? This it not very hard to do. There is a new and small utility to get the scancode (use it in a console, not under X): http://hack.org/mc/hacks/kbdscan/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
display r number
I recently saw the following in a post to the list, 8.0-STABLE FreeBSD 8.0-STABLE #2 r207058M:. My question is how do you get the r number to display? My uname -a says:8.0-STABLE FreeBSD 8.0-STABLE #2: Sat Apr 17 20:56:53. Is there a command line option, or a configuration setting somewhere? tia ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: display r number
In message alpine.bsf.1.10.1004241455590@neu.net, AN (a...@neu.net) wrote: I recently saw the following in a post to the list, 8.0-STABLE FreeBSD 8.0-STABLE #2 r207058M:. My question is how do you get the r number to display? My uname -a says:8.0-STABLE FreeBSD 8.0-STABLE #2: Sat Apr 17 20:56:53. Is there a command line option, or a configuration setting somewhere? You use SVN instead of CVSup or CVS to update your source tree. Cheers, Nick. -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: display r number
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/24/10 11:02, AN wrote: I recently saw the following in a post to the list, 8.0-STABLE FreeBSD 8.0-STABLE #2 r207058M:. My question is how do you get the r number to display? My uname -a says:8.0-STABLE FreeBSD 8.0-STABLE #2: Sat Apr 17 20:56:53. Is there a command line option, or a configuration setting somewhere? This indicates the type of source-code repository in use. If you use cvsup or csup, you get the result you see. If you use a subversion repository from which to build, you get the revision number (plus an 'M', if there are local changes applied), imb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkvTEx4ACgkQQv9rrgRC1JL0kACdFP/dF6J3LQzQZKWAeDQIqsTJ 8f0AmgNnKFyCZmfb74Fm9W3IyMoRFWXm =rEK/ -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: display r number
On Sat, Apr 24, 2010 at 03:02:49PM +, AN wrote: I recently saw the following in a post to the list, 8.0-STABLE FreeBSD 8.0-STABLE #2 r207058M:. My question is how do you get the r number to display? My uname -a says:8.0-STABLE FreeBSD 8.0-STABLE #2: Sat Apr 17 20:56:53. Is there a command line option, or a configuration setting somewhere? Those people are using freebsd-update(8). You're not. Don't worry about it. :-) -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: display r number
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/04/2010 16:02:49, AN wrote: I recently saw the following in a post to the list, 8.0-STABLE FreeBSD 8.0-STABLE #2 r207058M:. My question is how do you get the r number to display? My uname -a says:8.0-STABLE FreeBSD 8.0-STABLE #2: Sat Apr 17 20:56:53. Is there a command line option, or a configuration setting somewhere? If you get your kernel+system sources via cvsup then you won't be able to see the Subversion revision number -- CVS overwrites the $FreeBSD$ and similar tags in the source code when sources are imported from SVN to CVS. I believe the same applies to freebsd-update, although in that case, you can only get the -RELEASE branches. Presumably if you were to check out 8-Stable directly from a SVN server, you would see the global version. However, unless you are a FreeBSD committer, checking sources out of SVN is (I believe) discouraged in order to reduce the load on the SVN servers. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvTE5UACgkQ8Mjk52CukIzu7wCeKdHtnqVRs7mKfnYBZuu8lLFs hgUAnin6jzpuKH5baOFlcq5gaqinm0F6 =+UNZ -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: display r number
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/04/2010 16:49:53, Jeremy Chadwick wrote: On Sat, Apr 24, 2010 at 03:02:49PM +, AN wrote: I recently saw the following in a post to the list, 8.0-STABLE FreeBSD 8.0-STABLE #2 r207058M:. My question is how do you get the r number to display? My uname -a says:8.0-STABLE FreeBSD 8.0-STABLE #2: Sat Apr 17 20:56:53. Is there a command line option, or a configuration setting somewhere? Those people are using freebsd-update(8). You're not. Don't worry about it. :-) Not to get 8-Stable they aren't. freebsd-update(8) will get you 8.0-RELEASE. Checking out of subversion causes the observed effect. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvTFCMACgkQ8Mjk52CukIxYYwCgi1DlCwQFBqdYmiVkkCllF/hr 8doAnixQk5u57xEoDLQppWGH/0uKti9r =90dQ -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Conheça nossos preços e ofertas.
Krapeta Moda Iacute;ntima Krapeta Moda Iacute;ntima Confira nossos Preccedil;os. http://www.krapeta.com Tabela de Preccedil;os - Krapeta - Moda Iacute;ntima. Conjunto Sutiatilde;n Bojo Poliester Renda R$ 10,00 Sutiatilde;n Bojo Poliester Renda R$ 8,00 Sutiatilde;n Simples de Cotton R$ 3,50 Calcinha Renda Poliester R$ 2,50 Calcinha Fio Dental R$ 2,50 Calcinha Cotton Lisa R$ 2,00 Calcinha Cotton Estampada R$ 2,50 Descontos Para Revenda. Email e MSN: krap...@hotmail.com Krapeta A Moda da Mulher Brasileira. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: iwn firmware instability with an up-to-date stable kernel
On Sat, Apr 24, 2010 at 12:50 AM, Bernhard Schmidt bschm...@techwires.net wrote: On Sat, Apr 24, 2010 at 12:45:14AM -0700, Garrett Cooper wrote: On Sat, Apr 24, 2010 at 12:34 AM, Bernhard Schmidt bschm...@techwires.net wrote: How did you do that? Reloading the module, or with ifconfig? /etc/rc.d/netif restart , which does the ifconfig operations (no module change occurred AFAIK, but wlan0 did of course do some device_printf's when it was associating itself with iwn(4)). Can you do ps xa | grep wpa? Just wondering if wpa_supplicant gets started twice. Some more interesting data. Open authentication at home works out of the box via wpa_supplicant with ifconfig_wlan0=WPA DHCP whereas it flaked out and died at work. There are two instances of wpa_supplicant started up on the laptop. Here's a snippet from pstree that shows that both processes are standalone: -+= 1 root /sbin/init -- |--= 00121 root adjkerntz -i |--= 00559 root /sbin/devd |--= 00711 root /usr/sbin/syslogd -s |--= 00735 root /usr/sbin/rpcbind |--= 00879 root /usr/sbin/moused -p /dev/psm0 -t auto |--= 00903 messagebus /usr/local/bin/dbus-daemon --system |--= 01073 root /usr/sbin/sshd |--= 01081 root sendmail: accepting connections (sendmail) |--= 01085 smmsp sendmail: Queue run...@00:30:00 for /var/spool/clientmqueue (sendmail) |--= 01093 root /usr/sbin/cron -s |-+= 01176 haldaemon /usr/local/sbin/hald | \-+- 01180 root hald-runner | |--- 01185 root hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy) | \--- 01205 root hald-addon-storage: /dev/acd0 (hald-addon-storage) |--= 01179 root /usr/local/sbin/console-kit-daemon |--= 01727 root /usr/sbin/wpa_supplicant -s -B -i wlan0 -c /etc/wpa_supplicant.conf -D bsd -P /var/run/wpa_supplicant/wlan0.pid |--= 01783 root /usr/sbin/wpa_supplicant -s -B -i wlan0 -c /etc/wpa_supplicant.conf -D bsd -P /var/run/wpa_supplicant/wlan0.pid |--= 01866 root dhclient: wlan0 [priv] (dhclient) |--= 01902 _dhcp dhclient: wlan0 (dhclient) Thanks, -Garrett ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org