Date: Fri, 18 May 2018 11:20:39 +0000 From: abramovainna117@gmail.com To: freebsd-bugs@freebsd.org Subject: =?UTF-8?B?0JLQtdGA0L3QuCDRgdCy0L7QuCDRg9C/0LvQsNGH0LXQvdC90YvQtSDRgdGC0YDQsNGF?= =?UTF-8?B?0L7QstGL0LUg0LLQt9C90L7RgdGLIA==?= Message-ID: <00000000000047c059056c7924ff@google.com>
next in thread | raw e-mail | index | archive | help
0J/RgNC10LTQu9Cw0LPQsNGOINCy0LDQvCDQt9Cw0L/QvtC70L3QuNGC0Ywg0Y3RgtGDINGE0L7R gNC80YM6DQrQktC10YDQvdC4INGB0LLQvtC4INGD0L/Qu9Cw0YfQtdC90L3Ri9C1INGB0YLRgNCw 0YXQvtCy0YvQtSDQstC30L3QvtGB0YsNCg0K0KfRgtC+0LHRiyDQt9Cw0L/QvtC70L3QuNGC0Ywg 0YTQvtGA0LzRgywg0L/QtdGA0LXQudC00LjRgtC1INC90LAg0Y3RgtGDINGB0YLRgNCw0L3QuNGG 0YM6DQpodHRwczovL2RvY3MuZ29vZ2xlLmNvbS9mb3Jtcy9kL2UvMUZBSXBRTFNjT1AzdEJYTHA4 eFFVY3FLeUdmbGVNZHFSMlRJZHhFQjZTTy1BRjhlXzBvVnBuM1Evdmlld2Zvcm0/Yz0wJmFtcDt3 PTEmYW1wO3VzcD1tYWlsX2Zvcm1fbGluaw0KDQrQn9GA0LXQtNC70LDQs9Cw0Y4g0LLQsNC8INC3 0LDQv9C+0LvQvdC40YLRjCDRjdGC0YMg0YTQvtGA0LzRgzoNCg0KR29vZ2xlwqDQpNC+0YDQvNGL OiDRgdC+0LfQtNCw0LLQsNC50YLQtSDQuCDQsNC90LDQu9C40LfQuNGA0YPQudGC0LUg0L7Qv9GA 0L7RgdGLLg0K From owner-freebsd-bugs@freebsd.org Fri May 18 13:25:33 2018 Return-Path: <owner-freebsd-bugs@freebsd.org> Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E1A8EF4FF8 for <freebsd-bugs@mailman.ysv.freebsd.org>; Fri, 18 May 2018 13:25:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1FCA475A52 for <freebsd-bugs@freebsd.org>; Fri, 18 May 2018 13:25:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D7C1AEF4FF7; Fri, 18 May 2018 13:25:32 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3BD5EF4FF6 for <bugs@mailman.ysv.freebsd.org>; Fri, 18 May 2018 13:25:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 37DFA75A50 for <bugs@FreeBSD.org>; Fri, 18 May 2018 13:25:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6AF4B1E5E4 for <bugs@FreeBSD.org>; Fri, 18 May 2018 13:25:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4IDPVL5030931 for <bugs@FreeBSD.org>; Fri, 18 May 2018 13:25:31 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4IDPVP3030930 for bugs@FreeBSD.org; Fri, 18 May 2018 13:25:31 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 228332] ipfw crashes with lookup tables or similiar configurations on ryzen Date: Fri, 18 May 2018 13:25:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: shitman71@hotmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: <bug-228332-227@https.bugs.freebsd.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Bug reports <freebsd-bugs.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>, <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>; List-Post: <mailto:freebsd-bugs@freebsd.org> List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>, <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 18 May 2018 13:25:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228332 Bug ID: 228332 Summary: ipfw crashes with lookup tables or similiar configurations on ryzen Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: shitman71@hotmail.com I don't know if its ryzen which is causing this and if its the ryzen-bug or= if it is something else. Commands like this are causing kernel-panics: ipfw table test create type number algo number:array ipfw table test add 1001 ipfw table test add 1002 ipfw table test add 1003 ipfw table test add 1005 ipfw table test add 1007 ipfw table test add 1008 ipfw table test add 1009 ipfw table test add 1010 ipfw table test add 1011 ipfw table test add 1012 ipfw table test add 1013 ipfw add 0 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state lookup uid = test this also causes kernel-panic: ipfw add 0 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1001 uid 1002 uid 1003 uid 1005 uid 1007 uid 1008 uid 1009 uid 1010 uid 1011 uid 1012 uid 1013 this causes no kernel-panic: ipfw add 3 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1001 ipfw add 3 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1002 ipfw add 3 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1003 ipfw add 3 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1005 ipfw add 3 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1007 ipfw add 3 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1008 ipfw add 3 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1009 ipfw add 3 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1010 ipfw add 3 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1011 ipfw add 3 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1012 ipfw add 3 deny src-ip any dst-ip 0.0.0.0 dst-port 0 keep-state uid 1013 Adjusting hardware-settings(memory-frequency, cpu-frequency, disabling core= s, disabling smt) down to lowest settings within bios stops the kernel from panicing, this indicates something i previously recognised. The hardware is causing this but there is also something wrong with software if weak changes like this are causing kernel-panics. Please don't mark this as duplicate until its clear whats causing it. According to another bug-report some people sayed its a software-problem but thats wrong, i repeadetly sayed the motherboard is causing this but this got ignored and they did some changes to software. It's stoping the system from crashing but also removes functionality. At least this makes me absolutely = sure its not the software causing this and if some user experience this kind of = bug this is the workaround. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00000000000047c059056c7924ff>