On Fri, Oct 07, 2005 at 03:26:25PM +0400, Vitaly wrote: > Panics occured only with ath clients activity. I have attach > backtraces, what should i do else? I'm following up with my own post from a few days ago, only because it looks like the same issue. (To my untrained eyes anyway.) -Snow
attached mail follows:
This is easily reproduceable. Backtrace and kernel config are attached. This only happens when I'm using my ThinkPad as a gateway. If I do the following... kldload ipfw kldload ipdivert sysctl net.inet.ip.forwarding=1 sysctl net.link.ether.ipfw=1 sysctl net.inet.ip.fw.verbose=1 ipfw add 100 divert 8668 ip from any to any via em0 ipfw add 101 allow ip from any to any via em0 ... I will get this panic when I shut down. It may require that traffic be coming or going through the network interfaces when I shut down. The network devices on this laptop are: ath0_at_pci2:2:0: class=0x020000 card=0x057e1014 chip=0x1014168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = '11a/b/g Wireless LAN Mini PCI Adapter' class = network subclass = ethernet em0_at_pci2:1:0: class=0x020000 card=0x055b1014 chip=0x10778086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82547EI Gigabit Ethernet Controller (Mobile)' class = network subclass = ethernet I'm happy to test patches. Please let me know what other information I can provide. -Snow _______________________________________________ freebsd-current_at_freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"Received on Fri Oct 07 2005 - 14:36:35 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:44 UTC