From: Martin Zaharinov <micron10@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: netdev <netdev@vger.kernel.org>, Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: Urgent Bug report: PPPoE ioctl(PPPIOCCONNECT): Transport endpoint is not connected
Date: Fri, 6 Aug 2021 08:40:55 +0300 [thread overview]
Message-ID: <FE7AFA47-4EB0-44FB-B0E2-F6877B0B1ABF@gmail.com> (raw)
In-Reply-To: <YQy9JKgo+BE3G7+a@kroah.com>
Hi Greg
Latest kernel 5.13.8.
I try old version from 5.10 to 5.13 and its same error.
Martin
> On 6 Aug 2021, at 7:40, Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Thu, Aug 05, 2021 at 11:53:50PM +0300, Martin Zaharinov wrote:
>> Hi Net dev team
>>
>>
>> Please check this error :
>> Last time I write for this problem : https://www.spinics.net/lists/netdev/msg707513.html
>>
>> But not find any solution.
>>
>> Config of server is : Bonding port channel (LACP) > Accel PPP server > Huawei switch.
>>
>> Server is work fine users is down/up 500+ users .
>> But in one moment server make spike and affect other vlans in same server .
>> And in accel I see many row with this error.
>>
>> Is there options to find and fix this bug.
>>
>> With accel team I discus this problem and they claim it is kernel bug and need to find solution with Kernel dev team.
>>
>>
>> [2021-08-05 13:52:05.294] vlan912: 24b205903d09718e: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:05.298] vlan912: 24b205903d097162: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:05.626] vlan641: 24b205903d09711b: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:11.000] vlan912: 24b205903d097105: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:17.852] vlan912: 24b205903d0971ae: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:21.113] vlan641: 24b205903d09715b: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:27.963] vlan912: 24b205903d09718d: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:30.249] vlan496: 24b205903d097184: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:30.992] vlan420: 24b205903d09718a: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:33.937] vlan640: 24b205903d0971cd: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:40.032] vlan912: 24b205903d097182: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:40.420] vlan912: 24b205903d0971d5: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:42.799] vlan912: 24b205903d09713a: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:42.799] vlan614: 24b205903d0971e5: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:43.102] vlan912: 24b205903d097190: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:43.850] vlan479: 24b205903d097153: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:43.850] vlan479: 24b205903d097141: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:43.852] vlan912: 24b205903d097198: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:43.977] vlan637: 24b205903d097148: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>> [2021-08-05 13:52:44.528] vlan637: 24b205903d0971c3: ioctl(PPPIOCCONNECT): Transport endpoint is not connected
>
> These are userspace error messages, not kernel messages.
>
> What kernel version are you using?
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2021-08-06 5:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 20:53 Urgent Bug report: PPPoE ioctl(PPPIOCCONNECT): Transport endpoint is not connected Martin Zaharinov
2021-08-06 4:40 ` Greg KH
2021-08-06 5:40 ` Martin Zaharinov [this message]
2021-08-08 15:14 ` Martin Zaharinov
2021-08-08 15:23 ` Pali Rohár
2021-08-08 15:29 ` Martin Zaharinov
2021-08-09 15:15 ` Pali Rohár
2021-08-10 18:27 ` Martin Zaharinov
2021-08-11 16:40 ` Guillaume Nault
2021-08-11 11:10 ` Martin Zaharinov
2021-08-11 16:48 ` Guillaume Nault
2021-09-07 6:16 ` Martin Zaharinov
2021-09-07 6:42 ` Martin Zaharinov
2021-09-11 6:26 ` Martin Zaharinov
2021-09-14 6:16 ` Martin Zaharinov
2021-09-14 8:02 ` Guillaume Nault
2021-09-14 9:50 ` Florian Westphal
2021-09-14 10:01 ` Martin Zaharinov
2021-09-14 11:00 ` Florian Westphal
2021-09-15 14:25 ` Martin Zaharinov
2021-09-15 14:37 ` Martin Zaharinov
2021-09-16 20:00 ` Martin Zaharinov
2021-09-14 10:53 ` Martin Zaharinov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FE7AFA47-4EB0-44FB-B0E2-F6877B0B1ABF@gmail.com \
--to=micron10@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).