Fw: [Bug 87701] New: hard cpu lockup during pppd initialization of vpn

Fw: [Bug 87701] New: hard cpu lockup during pppd initialization of vpn

[Stephen Hemminger]

Begin forwarded message:

Date: Tue, 4 Nov 2014 08:35:39 -0800
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 87701] New: hard cpu lockup during pppd initialization of vpn


https://bugzilla.kernel.org/show_bug.cgi?id=87701

            Bug ID: 87701
           Summary: hard cpu lockup during pppd initialization of vpn
           Product: Networking
           Version: 2.5
    Kernel Version: 3.18.0-rc3
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: Other
          Assignee: shemminger@linux-foundation.org
          Reporter: richcoe2@gmail.com
        Regression: No

I did not experience this issue in 3.16 or before.
I did not try 3.17.

I moved from kernel-3.15 to 3.16, and then to kernel 3.18.
When I start forticlientsslvpn on 3.18, the system locks up hard.  No mouse and
no keyboard. 

forticlient starts pppd to enable a vpn connection.
Since this is laptop, I don't get a kernel traceback, or OOPS message.

I'm enabling kdump to see if I can get a reliable traceback.
I was first on 3.18.0-rc2, and moved to 3.18.0-rc3 today, and still have the
issue.

-- 
You are receiving this mail because:
You are the assignee for the bug.