* Re: Reoccuring kern.log events after running xl2tp with ethernet adapter Realtek 8111E [not found] <CANcVnzi2mXKXZLcaAt9rJ9OOdK_2=V8JV9uebVeBcsDu6j+DhQ@mail.gmail.com> @ 2012-06-04 23:10 ` Francois Romieu 2012-06-05 14:56 ` Dustin Schumm 1 sibling, 0 replies; 7+ messages in thread From: Francois Romieu @ 2012-06-04 23:10 UTC (permalink / raw) To: Dustin Schumm; +Cc: netdev Dustin Schumm <shodid@gmail.com> : [...] > I'm more than happy to provide whatever more is needed. It does not look like our usual 816x bug reports... Neither does your setup actually. Which kind of 816x is it (see 'dmesg | grep XID' output) ? -- Ueimor ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Reoccuring kern.log events after running xl2tp with ethernet adapter Realtek 8111E [not found] <CANcVnzi2mXKXZLcaAt9rJ9OOdK_2=V8JV9uebVeBcsDu6j+DhQ@mail.gmail.com> 2012-06-04 23:10 ` Reoccuring kern.log events after running xl2tp with ethernet adapter Realtek 8111E Francois Romieu @ 2012-06-05 14:56 ` Dustin Schumm 2012-06-05 15:37 ` Francois Romieu 1 sibling, 1 reply; 7+ messages in thread From: Dustin Schumm @ 2012-06-05 14:56 UTC (permalink / raw) To: romieu; +Cc: netdev Let me start off by thanking you for helping with this. I'm not that experienced with Linux so as to provide all surrounding information, so let me know if you need more. Forgive me for sending this in plain test as I got a reject from netdev for html. The 816x for Ubuntu on kernel 3.2.0 r8169 0000:0c:00.0: eth0: RTL8168e/8111e at 0xf845e000, bc:5f:f4:10:75:4b, XID 0c200000 IRQ 58 ethtool info driver: r8169 version: 2.3LK-NAPI firmware-version: rtl_nic/rtl8168e-2.fw bus-info: 0000:0c:00.0 I've also tested with Fedora 17 using kernel 3.3.7 http://codepad.org/lxkcRLqp This paste is from Fedora. Like Ubuntu, it starts with "general protection fault: 0000 [#1] SMP" but does not give the other looping messages after as in Ubuntu. The 816x for Fedora is r8169 0000:0c:00.0: eth0: RTL8168e/8111e at 0xf7e78000, bc:5f:f4:10:75:4b, XID 0c200000 IRQ 60 ethtool info driver: r8169 version: 2.3LK-NAPI firmware-version: rtl_nic/rtl8168e-2.fw bus-info: 0000:0c:00.0 and tested again with Cent OS 6.2 using kernel 2.6.32 Everything was functional without error here. I had replaced CentOS by the time I got this mail so I hadn't captured the 816x here and forgot to obtain the kern.log ethtool info driver: r8169 version: 2.3LK-NAPI firmware-version: bus-info: 0000:0c:00.0 > > On Mon, Jun 4, 2012 at 7:10 PM, Francois Romieu <romieu@fr.zoreil.com> wrote: > Dustin Schumm <shodid@gmail.com> : > [...] > > I'm more than happy to provide whatever more is needed. > > It does not look like our usual 816x bug reports... Neither does your > setup actually. > > Which kind of 816x is it (see 'dmesg | grep XID' output) ? > > -- > Ueimor > On Mon, Jun 4, 2012 at 1:39 PM, Dustin Schumm wrote: > > I'm using Ubuntu 12.04 kernel 3.2.0 and trying to set up L2TP over IPSec using openswan and xl2tpd. I've got no problem with the ipsec and I get SAs established. When I start the L2TP connection with xl2tpd, the kernel log starts filling with looping messages and PC becomes unusable. > > I have tested the exact same configuration down to every package in visualization and all is working. I believe it has something to do with my ethernet hardware/driver on this machine or kernel interaction with that device. I'm looking for evidence that points to either the driver or kernel and possible solutions. > > I've tried compiling and installing the drivers from Realtek for the RTL8111E integrated adapter and using that, but it produced the same result. I've also tried a backported kernel 3.4.0 > > I've posted a portion of my kern.log here from where i think the problem starts, http://codepad.org/QFbELkCr > > I'm more than happy to provide whatever more is needed. > > Thank you, > Dustin S. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Reoccuring kern.log events after running xl2tp with ethernet adapter Realtek 8111E 2012-06-05 14:56 ` Dustin Schumm @ 2012-06-05 15:37 ` Francois Romieu 2012-06-05 15:59 ` Dustin Schumm 0 siblings, 1 reply; 7+ messages in thread From: Francois Romieu @ 2012-06-05 15:37 UTC (permalink / raw) To: Dustin Schumm; +Cc: netdev Dustin Schumm <shodid@gmail.com> : [...] > Forgive me for sending this in plain test as I got a reject from > netdev for html. Please: - no full quote - no top answer - no html Thanks. [...] > I've also tested with Fedora 17 using kernel 3.3.7 > http://codepad.org/lxkcRLqp > This paste is from Fedora. Like Ubuntu, it starts with "general > protection fault: 0000 [#1] SMP" but does not give the other looping > messages after as in Ubuntu. This is with an usual 1500 bytes MTU and without TSO (see 'ethtool -k ethX'), right ? -- Ueimor ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Reoccuring kern.log events after running xl2tp with ethernet adapter Realtek 8111E 2012-06-05 15:37 ` Francois Romieu @ 2012-06-05 15:59 ` Dustin Schumm 2012-06-06 19:04 ` Dustin Schumm 0 siblings, 1 reply; 7+ messages in thread From: Dustin Schumm @ 2012-06-05 15:59 UTC (permalink / raw) To: Francois Romieu; +Cc: netdev On Tue, Jun 5, 2012 at 11:37 AM, Francois Romieu <romieu@fr.zoreil.com> wrote: > > This is with an usual 1500 bytes MTU and without TSO (see 'ethtool -k ethX'), > right ? > > -- > Ueimor Yes, MTU:1500 tcp-segmentation-offload: off ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Reoccuring kern.log events after running xl2tp with ethernet adapter Realtek 8111E 2012-06-05 15:59 ` Dustin Schumm @ 2012-06-06 19:04 ` Dustin Schumm 2012-06-06 22:25 ` Francois Romieu 0 siblings, 1 reply; 7+ messages in thread From: Dustin Schumm @ 2012-06-06 19:04 UTC (permalink / raw) To: Francois Romieu; +Cc: netdev On Tue, Jun 5, 2012 at 11:59 AM, Dustin Schumm <shodid@gmail.com> wrote: > On Tue, Jun 5, 2012 at 11:37 AM, Francois Romieu <romieu@fr.zoreil.com> wrote: >> >> This is with an usual 1500 bytes MTU and without TSO (see 'ethtool -k ethX'), >> right ? >> >> -- >> Ueimor > > Yes, > > MTU:1500 > tcp-segmentation-offload: off Do you see any indication if this is a problem with the mainline kernel, distro kernel, driver, or otherwise? It's not definitive, been I've been good using kernels 2.6.x and getting errors on everything 3.x I have tried. I am looking for some direction to pursue. Thanks. -Dustin ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Reoccuring kern.log events after running xl2tp with ethernet adapter Realtek 8111E 2012-06-06 19:04 ` Dustin Schumm @ 2012-06-06 22:25 ` Francois Romieu 2012-06-08 17:56 ` Dustin Schumm 0 siblings, 1 reply; 7+ messages in thread From: Francois Romieu @ 2012-06-06 22:25 UTC (permalink / raw) To: Dustin Schumm; +Cc: netdev Dustin Schumm <shodid@gmail.com> : [...] > Do you see any indication if this is a problem with the mainline > kernel, distro kernel, driver, or otherwise? It's not definitive, been > I've been good using kernels 2.6.x and getting errors on everything > 3.x I have tried. I am looking for some direction to pursue. Thanks. See http://marc.info/?l=linux-kernel&m=133897670115862&w=2 -- Ueimor ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Reoccuring kern.log events after running xl2tp with ethernet adapter Realtek 8111E 2012-06-06 22:25 ` Francois Romieu @ 2012-06-08 17:56 ` Dustin Schumm 0 siblings, 0 replies; 7+ messages in thread From: Dustin Schumm @ 2012-06-08 17:56 UTC (permalink / raw) To: Francois Romieu; +Cc: netdev On Wed, Jun 6, 2012 at 6:25 PM, Francois Romieu <romieu@fr.zoreil.com> wrote: > Dustin Schumm <shodid@gmail.com> : > [...] >> Do you see any indication if this is a problem with the mainline >> kernel, distro kernel, driver, or otherwise? It's not definitive, been >> I've been good using kernels 2.6.x and getting errors on everything >> 3.x I have tried. I am looking for some direction to pursue. Thanks. > > See http://marc.info/?l=linux-kernel&m=133897670115862&w=2 > > -- > Ueimor After further investigation of "EIP is at aesni_cbc_dec" I changed the ipsec encryption to 3des and l2tp is working properly now under kernels 3.x It is strange that the aes module errors do not occur when used with ipsec alone. It is not until l2tp is initiated that the errors start. ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2012-06-08 17:56 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CANcVnzi2mXKXZLcaAt9rJ9OOdK_2=V8JV9uebVeBcsDu6j+DhQ@mail.gmail.com>
2012-06-04 23:10 ` Reoccuring kern.log events after running xl2tp with ethernet adapter Realtek 8111E Francois Romieu
2012-06-05 14:56 ` Dustin Schumm
2012-06-05 15:37 ` Francois Romieu
2012-06-05 15:59 ` Dustin Schumm
2012-06-06 19:04 ` Dustin Schumm
2012-06-06 22:25 ` Francois Romieu
2012-06-08 17:56 ` Dustin Schumm
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox