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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20141104100910.4f6679b8@uryu.home.lan>
Date:	Tue, 4 Nov 2014 10:09:10 -0800
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	netdev@...r.kernel.org
Subject: Fw: [Bug 87701] New: hard cpu lockup during pppd initialization of
 vpn



Begin forwarded message:

Date: Tue, 4 Nov 2014 08:35:39 -0800
From: "bugzilla-daemon@...zilla.kernel.org" <bugzilla-daemon@...zilla.kernel.org>
To: "stephen@...workplumber.org" <stephen@...workplumber.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@...ux-foundation.org
          Reporter: richcoe2@...il.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html