From owner-freebsd-hackers@freebsd.org Tue Jul 14 20:32:49 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A73179A1262 for ; Tue, 14 Jul 2015 20:32:49 +0000 (UTC) (envelope-from rdarbha@juniper.net) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bn0109.outbound.protection.outlook.com [157.56.110.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D92F1EFE for ; Tue, 14 Jul 2015 20:32:49 +0000 (UTC) (envelope-from rdarbha@juniper.net) Received: from DM2PR0501MB1150.namprd05.prod.outlook.com (10.160.245.152) by DM2PR0501MB1151.namprd05.prod.outlook.com (10.160.245.153) with Microsoft SMTP Server (TLS) id 15.1.213.14; Tue, 14 Jul 2015 19:59:06 +0000 Received: from DM2PR0501MB1150.namprd05.prod.outlook.com ([10.160.245.152]) by DM2PR0501MB1150.namprd05.prod.outlook.com ([10.160.245.152]) with mapi id 15.01.0213.000; Tue, 14 Jul 2015 19:59:06 +0000 From: Raviprakash Darbha To: freebsd-hackers , "freebsd-hackers@freebsd.org" Subject: vm.kmem_size setting for kstack allocation failure Thread-Topic: vm.kmem_size setting for kstack allocation failure Thread-Index: AQHQvm+JmQ631KgkqE6uQLJvRGMtLA== Date: Tue, 14 Jul 2015 19:59:05 +0000 Message-ID: <9956D08B-2609-4AA2-AD62-721B753F6BFA@juniper.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: juniper.net; dkim=none (message not signed) header.d=none; x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [66.129.239.13] x-microsoft-exchange-diagnostics: 1; DM2PR0501MB1151; 5:111cYEpuy105HPv568rQ6z3o1GS3u7XwvPXO9vQtGFZxh/EFram0EbEITq19kZ/7BX2QwErh/IMD8RVcEiWmnu7pYG1bcdSu+mYUFzAhzfDXbIY7LIXKCZmR60+fjy5ok4fH+JfurHdYYe2l0yuULQ==; 24:QaqtB50e8QvQJM2nBA/aHeg+OWzRbW9dC0oO9jSumwZGMoLn+91S9rMHDhv6aOpS0C9GoqOQW2NBqwiiFBGAlS98kxgCSc9j4e/yFeCoSfM=; 20:lLXBEvItH56iZvWdvwvEP4W8MgJayqIzGwWWXRGcKlKSGj7+An0UsbtvCagLVoYHnnYKvB1ZH9p02llKdxhhkA== x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0501MB1151; dm2pr0501mb1151: X-MS-Exchange-Organization-RulesExecuted x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:DM2PR0501MB1151; BCL:0; PCL:0; RULEID:; SRVR:DM2PR0501MB1151; x-forefront-prvs: 0637FCE711 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(53754006)(107886002)(77096005)(5001960100002)(33656002)(2656002)(5001770100001)(5002640100001)(558084003)(87936001)(99286002)(46102003)(189998001)(92566002)(102836002)(36756003)(40100003)(2900100001)(83716003)(2501003)(66066001)(122556002)(82746002)(450100001)(50986999)(106116001)(54356999)(229853001)(77156002)(16236675004)(62966003)(86362001)(104396002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0501MB1151; H:DM2PR0501MB1150.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jul 2015 19:59:05.8404 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0501MB1151 X-Mailman-Approved-At: Tue, 14 Jul 2015 20:43:20 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 20:32:49 -0000 Hello All I have been working on a panic due to kernel stack allocation failure. vm_t= hread_new: kstack allocation failed I understand that this could be a kmem_size setting problem where too less = space is left for the stack. Any thoughts on setting vm.kmem_size to a lesser value ? Thanks Ravi