[E1000-devel] skb corruption
Hi, I have a Intel(R) Xeon(R) CPU E5-2680 based system with X710 based 10Gbe card. The i40e driver version used is 1.5.16 and firmware version is 5.02. I have observed one crash where the RIP is pointing to secpath_put when the skb->sp is being accessed although there were no IPSec connections established. [844890.055882] task: 88085439b000 ti: 8808543a8000 task.ti: 8808543a8000 [844890.063509] RIP: 0010:[] [] skb_release_head_state+0x31/0xf0 [844890.072559] RSP: 0018:88085fc83dd8 EFLAGS: 00010206 [844890.077991] RAX: RBX: 881011287900 RCX: 0001 [844890.085270] RDX: 0500 RSI: RDI: [844890.092548] RBP: 88085fc83de0 R08: R09: 0001802a0027 [844890.099828] R10: 81378240 R11: ea004044a100 R12: 881011287900 [844890.107108] R13: ff55 R14: 8807ca20f550 R15: 880803e84a00 [844890.114387] FS: () GS:88085fc8() knlGS: [844890.122620] CS: 0010 DS: ES: CR0: 80050033 [844890.128486] CR2: CR3: 01e0d000 CR4: 001407e0 [844890.135765] Stack: [844890.137890] 881011287900 88085fc83df8 816d3632 8810138e6548 [844890.145517] 88085fc83e18 816d3791 8810138e6548 8807ca20f550 [844890.153141] 88085fc83e28 816e4f85 88085fc83eb0 a0075790 [844890.160769] Call Trace: [844890.163328] [844890.165352] [844890.166986] [] skb_release_all+0x12/0x30 [844890.171289] [] consume_skb+0x31/0x80 [844890.176641] [] __dev_kfree_skb_any+0x35/0x40 [844890.182697] [] i40e_napi_poll+0x100/0x1000 [i40e] [844890.189180] [] net_rx_action+0x129/0x220 [844890.194880] [] __do_softirq+0xb7/0x2a0 [844890.200406] [] irq_exit+0x95/0xa0 [844890.205489] [] do_IRQ+0x56/0xe0 [844890.210401] [] common_interrupt+0x6a/0x6a [844890.216185] [844890.218205] [844890.219840] [] ? cpuidle_enter_state+0x46/0xb0 [844890.224663] [] ? cpuidle_enter_state+0x42/0xb0 [844890.230883] [] cpuidle_idle_call+0xbe/0x200 [844890.236839] [] arch_cpu_idle+0xe/0x20 [844890.242277] [] cpu_startup_entry+0xc5/0x260 [844890.248236] [] start_secondary+0x190/0x1e0 [844890.254099] Code: 48 89 e5 53 48 89 fb 48 8b 7f 58 48 85 ff 74 12 40 f6 c7 01 0f 84 a0 00 00 00 48 c7 43 58 00 00 00 00 48 8b 7b 60 48 85 ff 74 05 ff 0f 74 7a 48 8b 83 80 00 00 00 48 85 c0 74 15 65 8b 14 25 [844890.274478] RIP [] skb_release_head_state+0x31/0xf0 [844890.288994] RSP This is probably an indication of double free of skb leading to a skb corruption. Any pointers would be helpful. Thanks, Chandrasekhar ___ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel Ethernet, visit http://communities.intel.com/community/wired
[Qemu-discuss] Multiple queues for macvtap interface
Hi, I have a Dell PowerEdge 730 server with Ubuntu 16.04 and KVM running on it. QEMU version used is 2.5.0. I have a guest OS with linux running on it which does packet processing and forwarding. I have 4 10G interfaces connected to the Dell server and all of them are connected to the guest via macvtap. For improving the throughput of the guest I am using multiple queues on the vhost driver by defining “” in the guest xml file. By using interrupt affinity for the queue interrupts I am able to use multiple VCPUs on the guest. However I am seeing that on the host the macvtap interface is created with only 1 Rx/Tx queue as shown below. lab5@lab5-PowerEdge-R730:~$ ls /sys/class/net/macvtap0/queues/ rx-0 tx-0 Also only 1 tap device is opened per macvtap interface. For lower input rate of around 10Gbps, there are not many issues. However when the input rate starts increasing, I don’t see the guest getting the packets at a very high rate. Can anyone tell me how to create multiple queues for macvtap interface in QEMU? Thanks, Chandrasekhar
telnetd gives problems
Hi, I am using busybox-1.4.2 for a PPC440GX based board. I intend to run the telnetd daemon on the board. The telnetd has been compiled with the Support standalone telnetd (not inetd only) option. Also the LOGIN and FEATURE_SUID features have been enabled in Busybox. But when I try to telnet to this board (after the telnetd daemon has been started) I get the following error #telnet 192.168.1.205 Trying 192.168.1.205... Connected to 192.168.1.205 (192.168.1.205). Escape character is '^]'. Connection closed by foreign host. The kernel has UNIX98_PTYS and DEVPTS_FS enabled. At the RFS end, the /dev/pts directories are created, /dev/ptmx device file is created and also the devpts FS is mounted. Are there any other settings that I am missing? Thanks and Regards Sekhar ___ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
Linux 2.6 sources for MPC852T processor
An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060426/ff429bb5/attachment.htm
Regarding PCIBIOS_MIN_MEM and PCIBIOS_MIN_IO
Hi, I am writing a driver for the PCI controller for the 2.4.17 kernel. I found out that we need to define 2 macros PCIBIOS_MIN_MEM and PCIBIOS_MIN_IO. What does these macros mean? I have a ARM board with Memory space starting at 0x6000_ and IO space starting at 0x7000_. So does this mean that I have to set the above values to these macros? Thanks and Regards Chandrasekhar __ Free antispam, antivirus and 1GB to save all your messages Only in Yahoo! Mail: http://in.mail.yahoo.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Regarding PCIBIOS_MIN_MEM and PCIBIOS_MIN_IO
Hi, I am writing a driver for the PCI controller for the 2.4.17 kernel. I found out that we need to define 2 macros PCIBIOS_MIN_MEM and PCIBIOS_MIN_IO. What does these macros mean? I have a ARM board with Memory space starting at 0x6000_ and IO space starting at 0x7000_. So does this mean that I have to set the above values to these macros? Thanks and Regards Chandrasekhar __ Free antispam, antivirus and 1GB to save all your messages Only in Yahoo! Mail: http://in.mail.yahoo.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
