From owner-freebsd-ppc@freebsd.org Sun Feb 19 03:02:51 2017 Return-Path: Delivered-To: freebsd-ppc@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 9AA93CE3871 for ; Sun, 19 Feb 2017 03:02:51 +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 mx1.freebsd.org (Postfix) with ESMTPS id 89734143F for ; Sun, 19 Feb 2017 03:02:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1J32phP029930 for ; Sun, 19 Feb 2017 03:02:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 205458] 11.0-CURRENT/10-STABLE powerpc64: a PowerMac G5 specific sys/powerpc/ofw/ofw_machdep.c change for reliable PowerMac G5 booting (with lots of RAM) Date: Sun, 19 Feb 2017 03:02:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: jhibbits@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Feb 2017 03:02:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205458 --- Comment #15 from Mark Millard --- (In reply to Justin Hibbits from comment #11) Context: PowerMac G5 so-called "Quad Core", full 16 GByte of RAM. (Not the most interesting but the only powerpc64 context I currently have access to.) I've had no problems with the classic boot hangups and crashes since I switched to your code (replacing my hack). That even includes during the kernel version bisection effort that eventually found recent locking changes in the kernel (after -r313266) lead to randomly occurring panics and hangups after booting. It is still unknown when I'll again get access to the other, older type of PowerMac G5 (a dual processor, single core per processor G5). --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Mon Feb 20 16:20:23 2017 Return-Path: Delivered-To: freebsd-ppc@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 EF77FCE6984 for ; Mon, 20 Feb 2017 16:20:23 +0000 (UTC) (envelope-from gabriel.diaz@vgtelecomreports.com) Received: from smtp.vgtelecomreports.com (smtp.vgtelecomreports.com [202.0.103.126]) by mx1.freebsd.org (Postfix) with ESMTP id 3802318E9 for ; Mon, 20 Feb 2017 16:20:17 +0000 (UTC) (envelope-from gabriel.diaz@vgtelecomreports.com) X-SmarterMail-Authenticated-As: admin@vgtelecomreports.com DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; d=vgtelecomreports.com; s=smtp; h=received:from:to:message-id:subject:date:mime-version:reply-to :content-type; b=Kw8f6Op3EGA/2Vfc5HCTcpiRRDzxvAy9W7rWpmDd5xoGwgHLO6CStpe4zWO3zxK29 HtZ9L0l555szNHIq+O+CCgo2wqcIJgx6VjELmP/svw5TdyB3ltmMrM60Y/AfaE1rw ymZXSfwCYRttoV7AxaIYp/NIUJ/p2x5PDyjpNbwIQ= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vgtelecomreports.com; s=smtp; h= content-type:reply-to:mime-version:date:subject:message-id:to:from; bh=cx8LEjVg5smy8+MV7usXwouERCHxPJ5hiNVunB3oZ48=; b=SMRp8fT5eCAXXv42BL1SvnlvQN8+XYlUdgX7Ev7nuw6AJgr5OCfZaF4AF8h0EFECF rimhby2GYTi9UVzG2tkYbpC5E+3wORE9esvo7T1H9uV4cxy4t08e430OlpBoqYeTL pOst5dap+Of0R6EdqkXMCQdhsmL9Gq+CuVsvUexWY= Received: from WIN-ASQ29B6R1EP (WIN-ASQ29B6R1EP [202.0.103.127]) by smtp.vgtelecomreports.com with SMTP; Mon, 20 Feb 2017 13:13:09 +0000 From: Gabriel Diaz To: freebsd-ppc@freebsd.org Message-Id: <20170220131309.1613692441@vgtelecomreports.com> Subject: Smart Airport Technologies Market 2016-2026 Report Date: Mon, 20 Feb 2017 13:13:09 +0000 MIME-Version: 1.0 Reply-To: gabriel.diaz@vgtelecomreports.com Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2017 16:20:24 -0000 Visiongain - Business Report Updates Report this email as Spam Have questions about our reports or the licensing options available? Call us on +44 (0)208 781 6961 Smart Airport Technologies Market 2016-2026 Smart Security Towards Airport 3.0. Forecasts For Operation Solutions (Operations Resource Management, AODB, FIDS, WiFi, Baggage Management) Checkpoint & Border Control Solutions (IATA-ACI Smart Security, Border Control eGate Solutions) Flight Operations & A-CDM Solutions (Airport-Collaborative Decision Making System, Ground Movement Systems) Passenger Processing Solutions (End-to-End PPS Solutions) Plus Analysis of Leading Companies The smart airport technologies sector is set to be worth $2.99bn in 2016. Global air passenger numbers are continually growing at approximately 5% per annum. Airports worldwide, regardless of size, desire to deliver a superior passenger experience, facilitating the increasing demand for air travel. For larger airports, this is demonstrated by particular interest in improving stakeholder collaborations, operational efficiency and technologies. For smaller airports, creating a convenient and seamless terminal experience is fundamental. All of these require advanced end-to-end IT solutions, creating a smart system: Airport 3.0. How This 275 Page Report Delivers: • Global Smart Airport Technologies Market forecasts from 2016-2026 • Regional Smart Airport Technologies Market forecasts from 2016-2026 with detailed tables of contracts for each region - Asia-Pacific - South America - Europe - Middle East and Africa - North America; • Smart Airport Technologies Submarket forecasts from 2016-2026 covering - Operation Solutions - Checkpoint & Border Control Solutions - Flight Operations & A-CDM Solutions - Passenger Processing Solutions • Analysis of the key factors driving growth in the global and regional level Smart Airport Technologies Markets from 2016-2026 • Profiles of the leading 9 Smart Airport Technologies companies in 2016 - Amadeus IT Holding S.A. - CISCO Systems Inc. - Indra Sistemas S.A. - International Business Machines Corporation (IBM) - NEC Corporation - Rockwell Collins Inc. - Siemens AG - SITA - Unisys Corporation. • The report contains 165 tables, charts and graphs that utilise visual representation in order to clarify trends and market projections within the smart airport technologies market. For more information and orders please contact gabriel.diaz@vgtelecomreports.com How to purchase Choose the license you need from the list below and click the button to send your details Licensing options: Single User GBP 1999 Dept. (5 Users) GBP 2999 Site GBP 4999 Global GBP 6999 Table of Contents - Smart Airport Technologies Market 2016-2026 1. Report Overview 2. Introduction to the Smart Airport Technologies Market 2.1 Global Smart Airport Technologies Market Structure Overview 2.2 Smart Airport Technologies Market Definition 3. Global Smart Airport Technologies Market 2016-2026 3.1 Global Smart Airport Technologies Market Forecast 2016-2026 3.2 Global Smart Airport Technologies Market Drivers & Restraints 3.2.1 World’s 100 Major Air Navigation Service Providers 3.2.2 World’s Major Computer Reservation / Passenger Service Systems 4. Global Smart Airport Technologies Submarket 2016-2026 4.1 Global Smart Airport Technologies Submarket Overview 4.2 Smart Airport Operations Technologies Submarket 2016-2026 4.2.1 Smart Airport Operations Technologies Analysis 4.3 Smart Airport Checkpoint & Border Control Technologies Submarket 2016-2026 4.3.1 Smart Airport Checkpoint & Border Control Technologies Analysis 4.4 Smart Airport Flight Operations & A-CDM Technologies Submarket 2016-2026 4.4.1 Smart Airport Flight Operations & A-CDM Technologies Analysis 4.5 Smart Airport Passenger Processing Technologies Submarket 2016-2026 4.5.1 Smart Airport Passenger Processing Technologies Analysis 4.6 Global Smart Airport Technologies Submarkets Cumulative Market Share Forecast 2016-2026 5. Regional Smart Airport Technologies Market Forecasts 2016-2026 5.1 Regional Smart Airport Technologies Market Share Forecast 2016-2026 5.2 North American Smart Airport Technologies Market Forecast 2016-2026 5.2.1 North American Smart Airport Technologies Market Analysis 5.2.2 North American Smart Airport Technologies Market Contracts & Programmes 5.3 European Smart Airport Technologies Market Forecast 2016-2026 5.3.1 European Smart Airport Technologies Market Analysis 5.3.2 European Smart Airport Technologies Market Contracts & Programmes 5.4 Asia Pacific Smart Airport Technologies Market Forecast 2016-2026 5.4.1 Asia Pacific Smart Airport Technologies Market Analysis 5.4.1.1 Chinese Smart Airport Technologies Market Analysis 5.4.1.2 Indian Smart Airport Technologies Market Analysis 5.4.1.3 Rest of the Asia Pacific Smart Airport Technologies Market Analysis 5.4.2 Asia Pacific Smart Airport Technologies Market Contracts & Programmes 5.5 South American Smart Airport Technologies Market Forecast 2016-2026 5.5.1 South American Smart Airport Technologies Market Analysis 5.5.2 South American Smart Airport Technologies Market Contracts & Programmes 5.6 Middle East & African Smart Airport Technologies Market Forecast 2016-2026 5.6.1 Middle East & African Smart Airport Technologies Market Analysis 5.6.2 Middle East & African Smart Airport Technologies Market Contracts & Programmes 5.7 Regional Smart Airport Technologies Markets Cumulative Market Share Forecast 2016-2026 6. SWOT Analysis of the Smart Airport Technologies Market 2016-2026 7. PEST Analysis of the Smart Airport Technologies Market 2016-2026 8. Leading Smart Airport Technologies Companies 8.1 Leading Smart Airport Technologies Companies Analysis 2016 8.2 Amadeus IT Holding S.A. 8.2.1 Amadeus IT Holding S.A. Total Company Sales 2011-2015 8.2.2 Amadeus IT Holding S.A. Net Income 2011-2015 8.2.3 Amadeus IT Holding S.A. Organisational Structure 8.2.4 Amadeus IT Holding S.A. Products / Services 8.2.5 Amadeus IT Holding S.A. Analysis 8.2.6 Amadeus IT Holding S.A. Primary Market Competitors 8.2.7 Amadeus IT Holding S.A. Primary International Operations 2015 8.2.8 Amadeus IT Holding S.A. Major Contracts / Projects / Programmes 8.3 CISCO Systems Inc. 8.3.1 CISCO Systems Inc. Total Company Sales 2011-2015 8.3.2 CISCO Systems Inc. Net Income 2011-2015 8.3.3 CISCO Systems Inc. Organisational Structure 8.3.4 CISCO Systems Inc. Products / Services 8.3.5 CISCO Systems Inc. Analysis 8.3.6 CISCO Systems Inc. Primary Market Competitors 8.3.7 CISCO Systems Inc. Primary International Operations 2015 8.3.8 CISCO Systems Inc. Major Contracts / Projects / Programmes 8.4 Indra Sistemas S.A. 8.4.1 Indra Sistemas S.A. Total Company Sales 2011-2015 8.4.2 Indra Sistemas S.A. Net Income / Loss 2011-2015 8.4.3 Indra Sistemas S.A. Organisational Structure 8.4.4 Indra Sistemas S.A. Products / Services 8.4.5 Indra Sistemas S.A. Analysis 8.4.6 Indra Sistemas S.A. Primary Market Competitors 8.4.7 Indra Sistemas S.A. Primary International Operations 2015 8.4.8 Indra Sistemas S.A. Major Contracts / Projects / Programmes 8.5 International Business Machines Corporation (IBM) 8.5.1 IBM Corporation Total Company Sales 2011-2015 8.5.2 IBM Corporation Net Income 2011-2015 8.5.3 IBM Corporation Organisational Structure 8.5.4 IBM Corporation Products / Services 8.5.5 IBM Corporation Analysis 8.5.6 IBM Corporation Primary Market Competitors 8.5.7 IBM Corporation Primary International Operations 2015 8.5.8 IBM Corporation Major Contracts / Projects / Programmes 8.6 NEC Corporation 8.6.1 NEC Corporation Total Company Revenue 2012-2016 8.6.2 NEC Corporation Net Income / Loss 2012-2016 8.6.3 NEC Corporation Organisational Structure / Subsidiaries 8.6.4 NEC Corporation Products / Services 8.6.5 NEC Corporation Analysis 8.6.6 NEC Corporation Primary Market Competitors 8.6.7 NEC Corporation Primary International Operations 2015 8.6.8 NEC Corporation Major Contracts / Projects / Programmes 8.7 Rockwell Collins Inc. 8.7.1 Rockwell Collins Inc. Total Company Sales 2011-2015 8.7.2 Rockwell Collins Inc. Net Income 2011-2015 8.7.3 Rockwell Collins Inc. Organisational Structure 8.7.4 Rockwell Collins Inc. Products / Services 8.7.5 Rockwell Collins Inc. Analysis 8.7.6 Rockwell Collins Inc. Primary Market Competitors 8.7.7 Rockwell Collins Inc. Primary International Operations 2015 8.7.8 Rockwell Collins Inc. Major Contracts / Projects / Programmes 8.8 Siemens AG 8.8.1 Siemens AG Total Company Sales 2013-2015 8.8.2 Siemens AG Net Income 2013-2015 8.8.3 Siemens AG Organisational Structure / Subsidiaries 8.8.4 Siemens AG Products / Services 8.8.5 Siemens AG Analysis 8.8.6 Siemens AG Primary Market Competitors 8.8.7 Siemens AG Primary International Operations 2015 8.8.8 Siemens AG Major Contracts / Projects / Programmes 8.9 SITA 8.9.1 SITA Total Company Sales 2012-2015 8.9.2 SITA Organisational Structure 8.9.3 SITA Products / Services 8.9.4 SITA Analysis 8.9.5 SITA Primary Market Competitors 8.9.6 SITA Primary International Operations 2015 8.9.7 SITA Major Contracts / Projects / Programmes 8.10 Unisys Corporation 8.10.1 Unisys Corporation Total Company Sales 2011-2015 8.10.2 Unisys Corporation Net Income / Loss 2011-2015 8.10.3 Unisys Corporation Organisational Structure 8.10.4 Unisys Corporation Products / Services 8.10.5 Unisys Corporation Analysis 8.10.6 Unisys Corporation Primary Market Competitors 8.10.7 Unisys Corporation Primary International Operations 2015 8.10.8 Unisys Corporation Major Contracts / Projects / Programmes 8.11 Other Leading Companies in the Smart Airport Technologies Market 9. Conclusions 9.1 Global Smart Airport Technologies Market Outlook & Key Findings 9.2 Drivers & Restraints for the Global Smart Airport Technologies Market 10. Glossary List of Tables Table 3.1 Global Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %, CAGR%, Cumulative) Table 3.2 Global Smart Airport Technologies Market Drivers & Restraints Table 3.3 World’s 100 Major Air Navigation Service Providers (AN Provider, Country) Table 3.4 World’s Major Computer Reservation / Passenger Service Systems Providers (System, Vendor) Table 4.1 Global Smart Airport Technologies Submarket Forecast 2016-2026 ($m, AGR %, Cumulative) Table 4.2 Smart Airport Operations Technologies Submarket Forecast 2016-2026 ($m, AGR %, Cumulative) Table 4.3 Smart Airport Checkpoint & Border Control Technologies Submarket Forecast 2016-2026 ($m, AGR %, Cumulative) Table 4.4 Smart Airport Flight Operations & A-CDM Technologies Submarket Forecast 2016-2026 ($m, AGR %, Cumulative) Table 4.5 Smart Airport Passenger Processing Technologies Submarket Forecast 2016-2026 ($m, AGR %, Cumulative) Table 5.1 Regional Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %, Cumulative) Table 5.2 North American Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %, CAGR%, Cumulative) Table 5.3 North American Smart Airport Technologies Market Major Contracts & Programmes (Date, Company, Details) Table 5.4 European Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %, CAGR%, Cumulative) Table 5.5 European Smart Airport Technologies Market Major Contracts & Programmes (Date, Company, Details) Table 5.6 Asia Pacific Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %, CAGR%, Cumulative) Table 5.7 Asia Pacific Smart Airport Technologies Market Major Contracts & Programmes (Date, Company, Details) Table 5.8 South American Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %, CAGR%, Cumulative) Table 5.9 South American Smart Airport Technologies Market Major Contracts & Programmes (Date, Company, Details) Table 5.10 Middle East & African Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %, CAGR%, Cumulative) Table 5.11 Middle East & African Smart Airport Technologies Market Major Contracts & Programmes (Date, Company, Details) Table 6.1 SWOT Analysis of the Smart Airport Technologies Market 2016-2026 Table 7.1 PEST Analysis of the Smart Airport Technologies Market 2016-2026 Table 8.1 Leading Smart Airport Technologies Companies Analysis 2016 (Company, Headquarters, Total Company Sales $m) Table 8.2 Amadeus IT Holding S.A. Company Overview 2016 (CEO, Total Company Sales $m, Net Income $m, HQ, Ticker, IR Contact, Website) Table 8.3 Amadeus IT Holding S.A. Total Company Sales FY2011-2015 ($m, AGR %) Table 8.4 Amadeus IT Holding S.A. Net Income FY2011-2015 ($m, AGR %) Table 8.5 Amadeus IT Holding S.A. Smart Airport Technologies Products / Services (Company Division, Product, Specification) Table 8.6 Amadeus IT Holding S.A. Major Contracts / Projects / Programmes 2010-2016 (Date, Country, Details) Table 8.7 CISCO Systems Inc. Company Overview 2016 (CEO, Total Company Sales $m, Net Income $m, HQ, Ticker, IR Contact, Website) Table 8.8 CISCO Systems Inc. Total Company Sales FY2011-2015 ($m, AGR %) Table 8.9 CISCO Systems Inc. Net Income FY2011-2015 (US$m, AGR %) Table 8.10 CISCO Systems Inc. Smart Airport Technologies Products / Services (Division, Product, Specification) Table 8.11 CISCO Systems Inc. Major Contracts / Projects / Programmes 2011-2015 (Date, Country, Details) Table 8.12 Indra Sistemas S.A. Company Overview 2016 (CEO, Total Company Sales $m, Net Income $m, HQ, Ticker, IR Contact, Website) Table 8.13 Indra Sistemas S.A. Total Company Sales 2011-2015 (US$m, AGR %) Table 8.14 Indra Sistemas SA Net Income / Loss 2011-2015 (US$m) Table 8.15 Indra Sistemas S.A. Smart Airport Technologies Products / Services (Division, Product, Specification) Table 8.16 Indra Sistemas S.A. Major Contracts / Projects / Programmes 2012-2015 (Date, Country, Details) Table 8.17 IBM Corporation Company Overview 2016 (CEO, Total Company Sales $m, Net Income $m, HQ, Ticker, IR Contact, Website) Table 8.18 IBM Corporation Total Company Sales FY2011-2015 (US$m, AGR %) Table 8.19 IBM Corporation Net Income 2011-2015 (US$m, AGR %) Table 8.20 IBM Corporation Smart Airport Technologies Products / Services (Division, Product, Specification) Table 8.21 IBM Corporation Major Contracts / Projects / Programmes 2010-2015 (Date, Country, Details) Table 8.22 NEC Corporation Company Overview 2016 (CEO, Total Company Sales $m, Net Income $m, HQ, Ticker, IR Contact, Website) Table 8.23 NEC Corporation Total Company Revenue FY2012-2016 ($m, AGR %) Table 8.24 NEC Corporation Net Income / Loss 2012-2016 (US$m, AGR %) Table 8.25 NEC Corporation Subsidiaries 2015 (Subsidiary, Location) Table 8.26 NEC Corporation Smart Airport Technologies Products / Services (Division, Product, Specification) Table 8.27 NEC Corporation Major Contracts / Projects / Programmes 2013-2016 (Date, Country, Details) Table 8.28 Rockwell Collins Inc. Company Overview 2016 (CEO, Total Company Sales $m, Net Income $m, HQ, Ticker, IR Contact, Website) Table 8.29 Rockwell Collins Inc. Total Company Sales 2011-2015 (US$m, AGR %) Table 8.30 Rockwell Collins Inc. Net Income 2011-2015 (US$m, AGR %) Table 8.31 Rockwell Collins Inc. Subsidiaries 2015 (Subsidiary, Location) Table 8.32 Rockwell Collins Inc. Smart Airport Technologies Products / Services (Division, Product, Specification) Table 8.33 Rockwell Collins Inc. Major Contracts / Projects / Programmes 2010-2016 (Date, Country, Details) Table 8.34 Siemens AG Company Overview 2016 (CEO, Total Company Sales $m, Net Income $m, HQ, Ticker, IR Contact, Website) Table 8.35 Siemens AG Total Company Sales FY2013-2015 ($m) Table 8.36 Siemens AG Net Income FY2013-2015 ($m) Table 8.37 Siemens AG Subsidiaries 2015 (Subsidiary, Location) Table 8.38 Siemens AG Smart Airport Technologies Products / Services (Division, Product, Specification) Table 8.39 Siemens AG Major Contracts / Projects / Programmes 2012-2016 (Date, Country, Details) Table 8.40 SITA Company Overview 2016 (CEO, Total Company Sales $m, HQ, IR Contact, Website) Table 8.41 SITA Total Company Sales 2012-2015 (US$m, AGR %) Table 8.42 SITA Smart Airport Technologies Products / Services (Division, Product, Specification) Table 8.43 SITA Major Contracts / Projects / Programmes 2013-2016 (Date, Country, Details) Table 8.44 Unisys Corporation Company Overview 2016 (CEO, Total Company Sales $m, Net Income $m, HQ, Ticker, IR Contact, Website) Table 8.45 Unisys Corporation Total Company Sales 2011-2015 (US$m, AGR %) Table 8.46 Unisys Corporation Net Income / Loss 2011-2015 (US$m) Table 8.47 Unisys Corporation Smart Airport Technologies Products / Services (Division, Product, Specification) Table 8.48 Unisys Corporation Major Contracts / Projects / Programmes 2010-2016 (Date, Country, Details) Table 8.49 Other Leading Companies in the Smart Airport Technologies Market 2015 (Company/Parent Company, Service, Website) Table 9.1 Drivers & Restraints for the Global Smart Airport Technologies Market List of Figures Figure 1.1 Global Smart Airport Technologies Market Segmentation Overview Figure 1.2 World Geographical Region Defined in the Report Figure 1.3 Sample Regional Market Forecast 2016 ($m, AGR%) Figure 1.4 Sample Regional Market Forecast 2016 ($m, AGR %) Figure 2.1 Global Smart Airport Technologies Market Structure Overview Figure 2.2 World Region As Defined in This Report by Geographical Area Figure 3.1 Global Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %) Figure 4.1 Global Smart Airport Technologies Submarket Forecasts 2016-2026 ($m) Figure 4.2 Global Smart Airport Technologies Submarket AGR Forecast 2016-2026 (AGR %) Figure 4.3 Global Smart Airport Technologies Submarkets Share Forecast 2016 (% Share) Figure 4.4 Global Smart Airport Technologies Submarkets Share Forecast 2021 (% Share) Figure 4.5 Global Smart Airport Technologies Submarkets Share Forecast 2026 (% Share) Figure 4.6 Global Smart Airport Technologies Submarket Forecast CAGR 2016-2021 (CAGR %) Figure 4.7 Global Smart Airport Technologies Submarket Forecast CAGR 2021-2026 (CAGR %) Figure 4.8 Global Smart Airport Technologies Submarket Forecast CAGR 2016-2026 (CAGR %) Figure 4.9 Global Smart Airport Technologies Submarkets Percentage Changes in Market Share 2016-2021 (%) Figure 4.10 Global Smart Airport Technologies Submarkets Percentage Changes in Market Share 2021-2026 (%) Figure 4.11 Global Smart Airport Technologies Submarkets Percentage Changes in Market Share 2016-2026 (%) Figure 4.12 Smart Airport Operations Technologies Submarket Forecast 2016-2026 ($m, AGR %) Figure 4.13 Smart Airport Operations Technologies Submarket Share Forecast 2016, 2021 and 2026 (% Share) Figure 4.14 Smart Airport Checkpoint & Border Control Technologies Submarket Forecast 2016-2026 ($m, AGR %) Figure 4.15 Smart Airport Checkpoint & Border Control Technologies Submarket Share Forecast 2016, 2021 and 2026 (% Share) Figure 4.16 Smart Airport Flight Operations & A-CDM Technologies Submarket Forecast 2016-2026 ($m, AGR %) Figure 4.17 Smart Airport Flight Operations & A-CDM Technologies Submarket Share Forecast 2016, 2021 and 2026 (% Share) Figure 4.18 Smart Airport Passenger Processing Technologies Submarket Forecast 2016-2026 ($m, AGR %) Figure 4.19 Smart Airport Passenger Processing Technologies Submarket Share Forecast 2016, 2021 and 2026 (% Share) Figure 4.20 Global Smart Airport Technologies Submarkets Cumulative Market Share Forecast 2016-2026 (% Share) Figure 5.1 Regional Smart Airport Technologies Market Forecasts 2016-2026 ($m) Figure 5.2 Regional Smart Airport Technologies Market Forecast AGR 2016-2026 (AGR %) Figure 5.3 Regional Smart Airport Technologies Market Share Forecast 2016 (% Share) Figure 5.4 Regional Smart Airport Technologies Market Share Forecast 2021 (% Share) Figure 5.5 Regional Smart Airport Technologies Market Share Forecast 2026 (% Share) Figure 5.6 Regional Smart Airport Technologies Markets Forecast CAGR 2016-2021 (CAGR %) Figure 5.7 Regional Smart Airport Technologies Markets Forecast CAGR 2021-2026 (CAGR %) Figure 5.8 Regional Smart Airport Technologies Markets Forecast CAGR 2016-2026 (CAGR %) Figure 5.9 Regional Smart Airport Technologies Markets Percentage Changes in Market Share 2016-2021 (%) Figure 5.10 Regional Smart Airport Technologies Markets Percentage Changes in Market Share 2021-2026 (%) Figure 5.11 Regional Smart Airport Technologies Markets Percentage Changes in Market Share 2016-2026 (%) Figure 5.12 North American Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %) Figure 5.13 North American Smart Airport Technologies Market Share Forecast 2016, 2021 and 2026 (% Share) Figure 5.14 European Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %) Figure 5.15 European Smart Airport Technologies Market Share Forecast 2016, 2021 and 2026 (% Share) Figure 5.16 Asia Pacific Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %) Figure 5.17 Asia Pacific Smart Airport Technologies Market Share Forecast 2016, 2021 and 2026 (% Share) Figure 5.18 China Airport Capacity Expansion Plan by 2020 Figure 5.19 South American Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %) Figure 5.20 South American Smart Airport Technologies Market Share Forecast 2016, 2021 and 2026 (% Share) Figure 5.21 Middle East & African Smart Airport Technologies Market Forecast 2016-2026 ($m, AGR %) Figure 5.22 Middle East & African Smart Airport Technologies Market Share Forecast 2016, 2021 and 2026 (% Share) Figure 5.23 Regional Smart Airport Technologies Markets Cumulative Market Share Forecast 2016-2021, 2021-2026, 2016-2026 (% Share) Figure 8.1 Amadeus IT Holding S.A. Total Company Sales FY2011-2015 (US$m, AGR %) Figure 8.2 Amadeus IT Holding S.A. Net Income FY2011-2015 (US$m, AGR %) Figure 8.3 Amadeus IT Holding S.A. Organisational Structure Figure 8.4 Amadeus IT Holding S.A. Primary Market Competitors Figure 8.5 Amadeus IT Holding S.A. Primary International Operations 2015 Figure 8.6 CISCO Systems Inc. Total Company Sales FY2011-2015 (US$m, AGR %) Figure 8.7 CISCO Systems Inc. Net Income FY2011-2015 (US$m, AGR %) Figure 8.8 CISCO Systems Inc. Organisational Structure Figure 8.9 CISCO Systems Inc. Primary Market Competitors Figure 8.10 CISCO Systems Inc. Primary International Operations 2015 Figure 8.11 Indra Sistemas S.A. Total Company Sales 2011-2015 (US$m, AGR %) Figure 8.12 Indra Sistemas S.A. Net Income / Loss 2011-2015 (US$m) Figure 8.13 Indra Sistemas S.A. Organisational Structure Figure 8.14 Indra Sistemas S.A. Primary Market Competitors Figure 8.15 Indra Sistemas S.A. Primary International Operations 2015 Figure 8.16 IBM Corporation Total Company Sales 2011-2015 (US$m, AGR %) Figure 8.17 IBM Corporation Net Income 2011-2015 (US$m, AGR %) Figure 8.18 IBM Corporation Organisational Structure Figure 8.19 IBM Corporation Primary Market Competitors Figure 8.20 IBM Corporation Primary International Operations 2015 Figure 8.21 NEC Corporation Total Company Revenue FY2012-2016 (US$m, AGR %) Figure 8.22 NEC Corporation Net Income / Loss 2012-2016 (US$m, AGR %) Figure 8.23 NEC Corporation Organisational Structure Figure 8.24 NEC Corporation Primary Market Competitors Figure 8.25 NEC Corporation Primary International Operations 2015 Figure 8.26 Rockwell Collins Inc. Total Company Sales 2011-2015 (US$m, AGR %) Figure 8.27 Rockwell Collins Inc. Net Income 2011-2015 (US$m, AGR %) Figure 8.28 Rockwell Collins Inc. Organisational Structure Figure 8.29 Rockwell Collins Inc. Primary Market Competitors Figure 8.30 Rockwell Collins Inc. Primary International Operations 2015 Figure 8.31 Siemens AG Total Company Sales FY2013-2015 ($m) Figure 8.32 Siemens AG Net Income FY2013-2015 ($m) Figure 8.33 Siemens AG Organisational Structure Figure 8.34 Siemens AG Primary Market Competitors Figure 8.35 Siemens AG Primary International Operations 2015 Figure 8.36 Siemens Postal, Parcel & Airport Logistics GmbH Primary International Operations 2015 Figure 8.37 SITA Total Company Sales 2012-2015 (US$m, AGR %) Figure 8.38 SITA Organisational Structure Figure 8.39 SITA Primary Market Competitors Figure 8.40 SITA Primary International Operations 2015 Figure 8.41 Unisys Corporation Total Company Sales 2011-2015 (US$m, AGR %) Figure 8.42 Unisys Corporation Net Income / Loss 2011-2015 (US$m) Figure 8.43 Unisys Corporation Organisational Structure Figure 8.44 Unisys Corporation Primary Market Competitors Figure 8.45 Unisys Corporation Primary International Operations 2015 Companies Mentioned in this Report 3M Identity Management [3M Company] Abacus International Pte Ltd. ABeam Consulting Ltd. Aberdeen International Airport Abu Dhabi International Airport Abu Simbel Airport AccelAero Accenture Access Ltd. Adam Adolfo Suárez Madrid-Barajas Airport AeroCRS [Enoya-one Ltd.] Aeropuertos Dominicanos Siglo XXI (Aerodom) Aerostar Airport Holdings LLC Air Arabia Air Astana Air Berlin Air Canada Air Dolomiti Air France Air Routing International L.P. Air Routing LP LLC AirIT AirKiosk [Sutra Inc.] Airport 20/20 [Gentrack Ltd.] Airport Information Systems Ltd. (AIS) Airport Systems Division Air-Transport IT Services Inc. Air-Transport IT Services Inc. (AirIT) Al Maktoum International Airport Alcatel-Lucent Alicante Airport Alipay All Nippon Airways (ANA) Allegheny County Airport Authority Amadeus Amadeus Americas Inc. Amadeus IT Group SA Amadeus IT Holding S.A. American Airlines Amorph Systems GmbH Amsterdam Schiphol Airport Analogic Corporation AOC Shared Systems Board AR Group GP L.L.C. ARINC Inc. ARINC International ARINC Managed Services LLC Asiana Airlines Astana International Airport ASUR Aswan Airport Aswan International Atlanta Airport Austin Bergstrom International Airport (AUS) Austrian Airlines Avantik PSS AviancaTaca Aviation Analytics Ltd. Aviation Information Technology (AVIT) Axiomatic Technology Ltd. Azerbaijan Airlines BagDrop Systems BV Bahrain Airport Services Company (BAS) Bahrain International Airport Barcelona Airport Beijing Capital Airlines Beijing Capital International Airport Beirut-Rafic Hariri International Airport (BEY) Bellingham International Airport Belo Horizonte – Tancredo Neves International Airport Bengaluru International Airport Ltd. (BIAL) Berlin Brandenburg Airport Bill and Hillary Clinton National Airport Billund Airport Blue Eye Video Bogota El Dorado Airport (BOG) Borg El Arab Airport Branson Airport (BKG) Brasília – Presidente Juscelino Kubitschek International Airport Bratislava M. R. Štefánika Airport (BTS) Bravo Passenger Solutions Pte Ltd. Brisbane West Wellcamp Airport British Airways Brussels Airport Cambodia Bayon Airlines Campinas – Viracopos International Airport Cancún International Airport Cardiff Airport Caribbean Airlines Casper BV Central Japan International Airport Centrair (CJIAC) CGI Group Inc. Changi Airport Group (CAG) Charles de Gaulle Airport Charlotte Airport Charlotte Douglas International Airport Chengdu Airport Chennai Airport Chhatrapati Shivaji International Airport (CSIA) China Eastern Airlines China Eastern Airlines Group China Southern Airlines China TravelSky China TravelSky Holding Company China UnionPay China United Airlines CISCO Systems Inc. Civil Aviation Cares Technology of Xinjiang Ltd. Collins Aviation Maintenance Services Shanghai Ltd. Collins Radio Company Com-Net Software Computer Sciences Corporation (CSC) Concessionária do Aeroporto Internacional de Guarulhos S.A. Copenhagen Airports A/S Crane PAX [Hitit Computer Services] Customs and Border Protection (CBP) D.I.C.E Ltd. Dallas Airport Damarel Systems International Ltd. De Las Américas (SDQ) Dell DESKO GmbH dnata Doha Hamad International Airport Dubai International Airport Dublin Airport Dublin Airport Authority (DAA) Dulles International Airport Duqum Edinburgh Airport Egyptian Airports Company (EAC) Egyptian Holding Company for Airports and Air Navigation Ellinair Emirates Group Enoya-One Ltd. Ensambladores Electronicos de Mexico S. de R.L. de C.V. Entebbe International Airport Etihad Airways Far Eastern Air Transport FIFA Fiumicino-Leonardo de Vinci International Airport Flight Services de Mexico S. de R.L. de C.V. flydubai flynas Frankfurt Airport Fraport AG Fuzhou Airlines Gdansk Lech Walesa Airport Geneva Airport George Best Belfast City Airport Girona Airport Glasgow Airport Google Grantley Adams International Airport (GAIA) Greenville-Spartanburg International Airport (GSP) Gregorio Luperón (POP) Grupo Aeroportuario del Centro Norte (OMA) Guangzhou Airport GX Airlines Hainan Airlines Hainan Airlines Group Haneda Airport Harris Harry Mwanga Nkumbula International Airport Heathrow AOC Ltd. Hewlett Packard Heydar Aliev International Airport Hilton Philadelphia Airport Hitit Computer Services Honeywell International Inc. Hong Kong International Airport (HKIA) Human Recognition Systems Ltd. Hurghada International Airport Iberia IBM IBM Corporation IBS Software Services Icelandair ICM Airport Technics Holding GmbH iFIDS.com Inc. IFlyRes [IBS Software Services] IIAC (Incheon International Airports Corporation) Incheon International Airport Corporation Indira Gandhi International Airport (IGIA) Indra Navia Indra Sistemas S.A. Infologic Nederland B.V. INFORM GmbH Information Systems Associates FZE Ink Aviation Innovative Contractors for Advanced Dimensions (ICAD) Innsbruck Airport Insero Software A/S Intel InteliSys Aviation Systems International Business Machines Corporation InterSystems (Asia Pacific) Pty Ltd Intertrade Ltd. Irish Naturalisation and Immigration Service (INIS) Izmir Adnan Menderes Airport Jakarta International Airport JetBlue John F Kennedy International Airport Johnson Controls Jomo Kenyatta International Airport Jose Maria Cordoba International Airport Juniper Networks KAA Kaba Gallenschütz GmbH Kaiser Optical Systems SARL Kaiser Optical Systems Inc. Kazan Airport (KZN) Kempegowda International Airport, Bengaluru (KIAB) Killeen-Fort Hood Regional Airport King Abdul-Aziz International Airport KIU System Solutions KLM Kolkata Airport Kuala Lumpur International Airport Kualanamu Airport Kuwait International Airport' L-3 Security & Detection Systems Inc. Las Américas (SDQ) Lebanese Air Transport Company (LAT) Lleida-Alguaire Airport London Gatwick Airport London Heathrow Airport (LHR) London International Airport Los Angeles Airport Lucky Air Lufthansa Luis Muñoz Marín International Airport Luxor Airport Luxor International Mactan Cebu International Airport Madrid Airport Maine Electronics Inc. Malaga Airport Managed Services LLC (AMS) Manila Ninoy Aquino International Airport (NAIA) McCarran International Airport (LAS) Meantime Melbourne Airport Mercator [Emirates Group] Miami International Airport (MIA) Middle East Airlines (MEA) Mihin Lanka Minangkabau Airport Moi (Mombasa) Airport Monterrey Airport Morpho Detection, Inc. Moscow Domodedovo Airport Mumbai International Airport Pvt. Ltd (MIAL) Munich Airport (MUC) Münster-Osnabrück Airport (FMO) Muscat International Airport Myrtle Beach International Airport (MYR) Narita International Airport Corporation Nassau Lynden Pindling International Airport Navitaire LLC NEC NEC Asia Pacific Pte. Ltd. NEC Australia Pty. Ltd. NEC China Company Ltd. NEC Communication Systems Ltd. NEC Corporation of America NEC Display Solutions Ltd. NEC Embedded Products Ltd. NEC Energy Devices Ltd. NEC Energy Solutions Inc. NEC Engineering Ltd. NEC Europe Ltd. NEC Facilities Ltd. NEC Fielding Ltd. NEC Latin America NEC Lighting Ltd. NEC Management Partner Ltd. NEC Mobile Communications Ltd. NEC Network and Sensor Systems Ltd. NEC Network Products Ltd. NEC Networks & System Integration Corporation NEC New Zealand NEC Nexsolutions Ltd. NEC Platforms Ltd. NEC Space Technologies Ltd. NET Display Systems NetCracker Technology Corp. Newmarket International Nippon Avionics Company Ltd. NLX Holding Corporation Norman Manley International Airport Northrop Grumman Corporation Northrop Grumman Denmark NUCHTECH Company Ltd Oakland International Airport OCC Corporation Operadora Aeroportuaria Internacional (OPAIN) Optosecurity Inc. Oracle Corporation Orange Orient Thai Airlines Orlando International Airport Orlando Sanford International Airport (SFB) Palma de Mallorca Park Air Systems Norway Passport, Immigration and Citizenship Agency (PICA) Perth Airport Philadelphia International Airport Pittsburgh International Airport (PIT) Port Moresby International Airport Port of Algeciras Port of Bellingham Port of Oakland Portland International Airport (PWM) Providenciales International Airport (PLS) PSI Logistics GmbH Pune Airport Qantas Qmetrix GmbH Québec City Jean Lesage International Airport (YQB) Radio Holdings Inc. Radixx International Inc. RapiScan Systems Inc. Ras Al Hadd Ras Al Khaimah International Airport Receita Federal (Brazilian National Tax Collection Agency) RESA Reveal Imaging Technologies Inc. Rhode Island Airport Corporation RICOMP Claims Management Corporation Rio de Janeiro Galeão International Airport Rockwell Collins (India) Enterprises Private Ltd. Rockwell Collins (Shanghai) Avionics Trading Company Ltd. Rockwell Collins Asia-PAC Holdings LLC Rockwell Collins Australia Pty Ltd. Rockwell Collins Business Services LLC Rockwell Collins Canada Inc. Rockwell Collins Charitable Corporation Rockwell Collins Control Technologies Inc. Rockwell Collins Deutschland GmbH Rockwell Collins Deutschland Holdings GmbH Rockwell Collins Deutschland Services GmbH Rockwell Collins do Brasil Ltda. Rockwell Collins Employee Disaster Assistance Corporation Rockwell Collins EUMEA Holdings SAS Rockwell Collins European Holdings S.à r.l. Rockwell Collins Flight Services Inc. Rockwell Collins France SAS Rockwell Collins Global Logistics Solutions LLC Rockwell Collins Hong Kong Ltd. Rockwell Collins Inc. Rockwell Collins India Private Ltd. Rockwell Collins In-Flight Network Company Rockwell Collins International Financing S.à r.l. Rockwell Collins International Holdings S.à r.l. Rockwell Collins International Inc. Rockwell Collins Leasing LLC Rockwell Collins Network Enabling Software Inc. Rockwell Collins Optronics Inc. Rockwell Collins Prescription Center Inc. Rockwell Collins Public Safety Solutions Inc. Rockwell Collins Satellite Communications Systems Inc. Rockwell Collins Services Company Rockwell Collins Simulation & Training Solutions LLC Rockwell Collins Southeast Asia Pte. Ltd. Rockwell Collins Support Company Rockwell Collins Sweden AB Rockwell Collins Systems International Inc. Rockwell Collins Technologies LLC Rockwell Collins UK Financing LLP Rockwell Collins UK Ltd. Rockwell Collins Vision Systems Inc. Rotterdam The Hague airport (RTM) Royal Boon Edam International BV RwandAir Sabre Corporation Safran Group Salalah Airport San Juan Luis Munoz Marin International Airport (SJU) Sangster International Airport São Paulo Guarulhos International Airport (GRU) São Paulo/Guarulhos – Governador André Franco Montoro International Airport secunet Security Networks AG ServiceTec Global Services Ltd. Shanghai Airlines Shanghai Pudong Airport Sharjah International Airport Sharm El Sheikh International Siam Air Siemens AG Siemens Industry Software Ltd. Siemens Logistics and Airport Solutions Siemens Mobility and Logistics Siemens Postal & Parcel Logistics Technologies AG Siemens Postal and Parcel Logistics Technologies Private Ltd. Siemens Postal Parcel & Airport Logistics GmbH & Co. KG Siemens Postal Parcel & Airport Logistics LLC Siemens Postal Parcel & Airport Logistics Ltd. Siemens Postal Parcel & Airport Logistics Private Ltd. Siemens Postal Parcel & Airport Logistics S.L. Siemens Postal Parcel & Airport Logistics Verwaltungs GmbH Siemens Technology and Services Private Ltd. Singapore Airlines Sinotec SITA SITA Lab Skyguide SkyVantage Corporation Smiths Detection Sohar Sony South Tenerife Airport Southwest Airlines SriLankan Airlines Star Alliance Sultan Mahmud Badaruddin II Airport Sultan Syarif Kasim II Airport Supadio Airport SUTRA Inc. Swiss International Air Lines Swissport International T.F. Green Airport (PVD) TACA Takeflite Solutions Tampa International Airport Tan Son Nhat Airport TAV Information Technologies Corporation [TAV Airports Holding] TCIAA Thales S.A. The Avinor Group The National Airport of Romania Tianjin Airlines Tianjin Airport Tokyo Haneda Airport Tokyo International Air Terminal Corporation (TIAT) Tokyo Narita Airport Tokyo Narita International Airport Toulouse-Blagnac Airport Travel Technology Interactive Group Travelport TravelSky Technology Ltd. Turkish Airlines UFIS Airport Solutions GmbH Ultra Electronics Airport Systems UnionPay International Unisys Australia Unisys China Unisys Corporation Urumqi Air US Airways Vail/Eagle County Regional Airport Vancouver International Airport (YVR) Vanderlande Industries B.V. Videcom International Inc. Videcom VRS [Videcom International] Vilnius International Airport Virgin Atlantic Vistara Washington Dulles International Airport West Air Wilkens Weather Technologies L.P. WorldTicket Xiamen Airport Xovis AG ZAO Rockwell Collins Zurich Airport Air Navigation Service Providers Government Agencies and Other Organisations Mentioned in This Report Aeronáutica Civil Colombiana (UAEAC) Aeronautical Radio of Thailand (AEROTHAI) Aeroportos de Moçambique (ADM) Agence pour la Securité de la Navigation Aerienne en Afrique et Madagascar (ASECNA) Agjencia Nacionale e Trafikut Ajror (ANTA) Air Navigation and Weather Services (ANWS) Air Navigation Services of the Czech Republic (ANS CR) Air Traffic & Navigation Services (ATNS) AirNav Indonesia Airport & Aviation Services Ltd. (AASL) Airports Authority of India (AAI) Airports Fiji Ltd. (AFL) Airservices Australia Airways New Zealand Armenian Air Traffic Services (ARMATS) Austro Control Avinor AS Azerbaijan Air Navigation Services (AZANS) BELAERONAVIGATSIA BelgoControl Bulgarian Air Traffic Services Authority (BULATSA) Civil Aviation Administration of China (CAAC) Civil Aviation Authority of Bangladesh (CAAB) Civil Aviation Authority of Nepal Civil Aviation Authority of Pakistan Civil Aviation Authority of Singapore (CAAS) Civil Aviation Authority of the Philippines (CAAP) Civil Aviation Authority of Uganda Civil Aviation Department (CAD) Civil Aviation Regulatory Commission (CARC) Corporación Centroamericana de Servicios de Navegación Aérea (COCESNA) Corporación Peruana de Aeropuertos y Aviación Comercial (CORPAC) Croatia Control Ltd. Departamento de Controle do Espaço Aéreo (DECEA) / INFRAERO Department of Civil Aviation Department of Civil Aviation (DCA) Deutsche Flugsicherung GmbH (DFS) / The Tower Company Dirección General de Aeronáutica Civil (DGAC) Dirección General de Control de Tránsito Aéreo (DGCTA) Direction des Services de la Navigation Aérienne (DSNA) Directorate General of Meteorology & Air Navigation Dutch Caribbean Air Navigation Service Provider (DC-ANSP) Empresa Nacional de Exploração de Aeroportos e Navegação Aérea (ENANA-EP) ENAIRE ENAV S.p.A. Estonian Air Navigation Services (EANS) Etablissement National de la Navigation Aérienne (ENNA) EUROCONTROL Federal Aviation Administration (FAA) Finavia Corporation General Authority of Civil Aviation (GACA) General Civil Aviation Authority (GCAA) Hellenic Civil Aviation Authority (HCAA) HungaroControl Pte. Ltd. Instituto de Aeronáutica Civil de Cuba (IACC) Instituto Dominicano de Aviación Civil (IDAC) Instituto Nacional de Aeronáutica Civil (INAC) Iran Airports Company (IAC) Iraqi Air Navigation (ICAA) Irish Aviation Authority (IAA) ISAVIA Ltd. Israel Airports Authority (IIA) Jamaica Civil Aviation Authority (JCAA) Jersey - CICZ Kazaeronavigatsia Kenya Civil Aviation Authority Latvijas Gaisa Satiksme (LGS) Letové prevádzkové služby (LPS) Luchtverkeersleiding Nederland (LVNL) Luftfartsverket (LFV) Luxembourg Air Navigation Administration (ANA) Maldives Airports Company Ltd. (MACL) Malta Air Traffic Services Ltd. (MATS) M-NAV Moldovian Air Traffic Services Authority (MoldATSA) National Air Navigation Services Company (NANSC) National Air Traffic Services (NATS) National Airports Corporation Ltd. (NACL) NAV Canada NAV Portugal Naviair Nigerian Airspace Management Agency (NAMA) Office de l'Aviation Civile et des Aeroports (OACA) Oro Navigacija PNG Air Services Ltd. (PNGASL) Polish Air Navigation Services Agency (PANSA) Prishtina International Airport JSC Romanian Air Traffic Services Administration (ROMATSA) Sakaeronavigatsia Ltd. Serbia and Montenegro Air Traffic Services Agency (SMATSA) Serco Group PLC Servicios a la Navegacion en el Espacio Aereo Mexicano (SENEAM) Seychelles Civil Aviation Authority (SCAA) Skyguide Slovenia Control State Airports Authority (DHMI) State ATM Corporation / Federal Air Navigation Authority (FANA) Tanzania Civil Aviation Authority Trinidad and Tobago Civil Aviation Authority (TTCAA) Ukrainian State Air Traffic Service Enterprise (UkSATSE) Organisations Mentioned in this Report ACI EUROPE Airport Authority Hong Kong (AAHK) Airports Authority of India (AAI) Association of European Airlines Board of Airline Representatives Australia (BARA) City of Austin Aviation Department Civil Air Navigation Services Organisation (CANSO) Civil Aviation Authority [ANAC] Civil Aviation Authority of China (CAAC) Civil Aviation Authority of Nepal COMAR Department of Immigration Directorate General of Civil Aviation Authority (DGCA) Directorate General of Meteorology and Air Navigation European Commission European Union FAA Greater Orlando Aviation Authority (GOAA) Greenville-Spartanburg Airport District IATA IATA’s Common Use Working Group (CUWG) ICAO Indian Ministry of Civil Aviation Kenya Airports Authority Members of the European Low Fares Airline Association NSA Public Authority for Civil Aviation (PACA) Puerto Rico Ports Authority Sultanate's Ministry of Transport and Communications U.S. Customs and Border Protection (CBP) Ugandan Civil Aviation Authority Vancouver Airport Authority For more information and orders please contact gabriel.diaz@vgtelecomreports.com Terms and Conditions By replying to this e-mail submitting your order for this product you have agreed without limitation or qualification to be bound by and to comply with these Terms and Conditions. You agree that you will not fail to complete any transaction after submitting an order to purchase a product or submit any order to purchase a product where you do not intend to complete the transaction. Management Reports will only be sent on receipt of payment. Our mailing address is: Airport House, Purley Way, London, UK. CR0 0XZ As a valued contact or customer, you are receiving this email with information that we believe will be relevant to you. Please add us to your safe senders list to ensure you keep receiving these emails. If you wish to stop future messages you can unsubscribe from this list From owner-freebsd-ppc@freebsd.org Mon Feb 20 19:10:50 2017 Return-Path: Delivered-To: freebsd-ppc@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 2A102CE6F62; Mon, 20 Feb 2017 19:10:50 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C11291ECB; Mon, 20 Feb 2017 19:10:49 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id v77so16016675wmv.0; Mon, 20 Feb 2017 11:10:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=P3L3E9k5+UkHpIiU20ABdVOEIR2ezfhaEqIV8O0aYRs=; b=I2LwoJYyVDFvoBB6S9OjQTZf9lux5VjzXba3r+zYPguDZxyVfW3oBHOW9B/Vm8LkuX DmzfylYBDpQfBl6l+fIfwHj4kMocmsG1VidyOtd7ONyht3R70Tja5W6dQI0junVxRlIR mwQr/C6L6q7S6vC5AQInhUiR6H5ghQ3jdodq/9DQmoVBncCm/RVu3ykoK3GKiC9ZV4Bq h3Z8kUHAgdadoMWfEn9N31dJ0nzUvXlpt9jdChM3IhP/AOD1oO6m0YnSRovHHeuuc25o o2t/HLb2G4FxHlsIaAhzQIMwiSQLH2luFbXcM0PZWROvU/RIKCmhzJSi/XSgYCdQCoQX 0Znw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=P3L3E9k5+UkHpIiU20ABdVOEIR2ezfhaEqIV8O0aYRs=; b=hm2l8veGi0KnJ+FKXwrCKBpJ9D71to8NkueFVyOHnHXSWp4JEoR3TMr/fsRssvRCuH hRHzsAXORpxkpHcTyl62BvK8gi3yX/Y7gToknI54WITOAL9+cLeqzT60L4KXhUWOjrsF pKixBqzj5Outj8LFhkO4L1a0Qc6R/sbBJz99qJv5Rl4GTDY0o4MkQBpSrooYwOKO0rG4 oF0jD2xY7bYerUfy/gFOGtPDuml5/p2HXeQTj4RnbVv+omhsl7alXXbCYPhSNFTbK59k 0dzu8mXEoo8b7mms+iMwFzlc5VsIH97oVM42cv+RZOYyhLnqEiJt6y+YcwTL7kcHFBJL wvyQ== X-Gm-Message-State: AMke39nBxWVc8FA/RRj0/xILraFuA7jUcJy/ZozS1BcUMWjlHhibCL37WtyQkqWE6CHUbA== X-Received: by 10.28.158.74 with SMTP id h71mr12396602wme.59.1487617848059; Mon, 20 Feb 2017 11:10:48 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by smtp.gmail.com with ESMTPSA id w51sm10692040wrc.12.2017.02.20.11.10.46 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Mon, 20 Feb 2017 11:10:47 -0800 (PST) Date: Mon, 20 Feb 2017 20:10:45 +0100 From: Mateusz Guzik To: Mark Millard Cc: mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current , Nathan Whitehorn Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] Message-ID: <20170220191044.GA8526@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Mark Millard , mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current , Nathan Whitehorn References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2017 19:10:50 -0000 On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: > [Note: I experiment with clang based powerpc64 builds, > reporting problems that I find. Justin is familiar > with this, as is Nathan.] > > I tried to update the PowerMac G5 (a so-called "Quad Core") > that I have access to from head -r312761 to -r313864 and > ended up with random panics and hang ups in fairly short > order after booting. > > Some approximate bisecting for the kernel lead to: > (sometimes getting part way into a buildkernel attempt > for a different version before a failure happens) > > -r313266: works (just before use of atomic_fcmpset) > vs. > -r313271: fails (last of the "use atomic_fcmpset" check-ins) > > (I did not try -r313268 through -r313270 as the use was > gradually added.) > > So I'm currently running a -r313864 world with a -r313266 > kernel. > > No kernel that I tried that was from before -r313266 had the > problems. > > Any kernel that I tried that was from after -r313271 had the > problems. > > Of course I did not try them all in other direction. :) > I found that spin mutexes were not properly handling this, fixed in r313996. Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64 fcmpset to simulate failures. Everything works, while it would easily fail without the patch. That said, I hope this concludes the 'missing check for not-reread value of failed fcmpset' saga. -- Mateusz Guzik From owner-freebsd-ppc@freebsd.org Mon Feb 20 22:58:33 2017 Return-Path: Delivered-To: freebsd-ppc@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 D50EACE6D55 for ; Mon, 20 Feb 2017 22:58:33 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-74.reflexion.net [208.70.210.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 833D62B5 for ; Mon, 20 Feb 2017 22:58:32 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 14672 invoked from network); 20 Feb 2017 22:58:26 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 20 Feb 2017 22:58:26 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Mon, 20 Feb 2017 17:58:26 -0500 (EST) Received: (qmail 5815 invoked from network); 20 Feb 2017 22:58:26 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 20 Feb 2017 22:58:26 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id A8D59EC903F; Mon, 20 Feb 2017 14:58:25 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <20170220191044.GA8526@dft-labs.eu> Date: Mon, 20 Feb 2017 14:58:24 -0800 Cc: mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current , Nathan Whitehorn Content-Transfer-Encoding: 7bit Message-Id: <83428304-87BE-413C-BAB9-8FF218E7661C@dsl-only.net> References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2017 22:58:33 -0000 On 2017-Feb-20, at 11:10 AM, Mateusz Guzik wrote: > On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: >> [Note: I experiment with clang based powerpc64 builds, >> reporting problems that I find. Justin is familiar >> with this, as is Nathan.] >> >> I tried to update the PowerMac G5 (a so-called "Quad Core") >> that I have access to from head -r312761 to -r313864 and >> ended up with random panics and hang ups in fairly short >> order after booting. >> >> Some approximate bisecting for the kernel lead to: >> (sometimes getting part way into a buildkernel attempt >> for a different version before a failure happens) >> >> -r313266: works (just before use of atomic_fcmpset) >> vs. >> -r313271: fails (last of the "use atomic_fcmpset" check-ins) >> >> (I did not try -r313268 through -r313270 as the use was >> gradually added.) >> >> So I'm currently running a -r313864 world with a -r313266 >> kernel. >> >> No kernel that I tried that was from before -r313266 had the >> problems. >> >> Any kernel that I tried that was from after -r313271 had the >> problems. >> >> Of course I did not try them all in other direction. :) >> > > I found that spin mutexes were not properly handling this, fixed in > r313996. > > Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64 > fcmpset to simulate failures. Everything works, while it would easily > fail without the patch. > > That said, I hope this concludes the 'missing check for not-reread value > of failed fcmpset' saga. > > -- > Mateusz Guzik I tried to update from -r313864 to -r313999 in my amd64 context (a VirtualBox machine under macOS) but it now crashes late in the boot sequence (after it processes a dump if I make one but before I can log in). This update was via my usual explicit svnlite update; buildworld buildkernel; etc. production style build of world and kernel, including use of MALLOC_PRODUCTION. The window shows: _vm_map_lock+0xf vm_map_wire+0x32 rtROMemObjNativeLockInMap+0x8c rtROMemObjNativeLockUser+0x51 RTR0MemObjLockUserTag+0x231 vbglR0HGCMInternalPreprocessCall+0x65d vbglR0HGCMInternalCall+0x17c vgdrvIoCtl_HGCMCall+0x43f VGDrvCommonIoCtl+0x261 vgdrvFreeBSDIOCtl+0x2cd devfs_ioctl+0xae VOP_IOCTL_APV+0x88 vn_ioctl+0x161 devfs_ioctl_f+0x1f kern_ioctl+0x280 sys_ioctl+0x13f amd64_syscall+0x397 Xfast_syscall+0xfb === Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Mon Feb 20 23:10:53 2017 Return-Path: Delivered-To: freebsd-ppc@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 65842CE633E for ; Mon, 20 Feb 2017 23:10:53 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-76.reflexion.net [208.70.210.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 206C3C48 for ; Mon, 20 Feb 2017 23:10:52 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 22102 invoked from network); 20 Feb 2017 23:10:46 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 20 Feb 2017 23:10:46 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Mon, 20 Feb 2017 18:10:46 -0500 (EST) Received: (qmail 14277 invoked from network); 20 Feb 2017 23:10:46 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 20 Feb 2017 23:10:46 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 8551FEC7B46; Mon, 20 Feb 2017 15:10:45 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <83428304-87BE-413C-BAB9-8FF218E7661C@dsl-only.net> Date: Mon, 20 Feb 2017 15:10:44 -0800 Cc: Justin Hibbits , mjg@freebsd.org, FreeBSD Current , svn-src-head@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <83428304-87BE-413C-BAB9-8FF218E7661C@dsl-only.net> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2017 23:10:53 -0000 On 2017-Feb-20, at 2:58 PM, Mark Millard wrote: > On 2017-Feb-20, at 11:10 AM, Mateusz Guzik = wrote: >=20 >> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: >>> [Note: I experiment with clang based powerpc64 builds, >>> reporting problems that I find. Justin is familiar >>> with this, as is Nathan.] >>>=20 >>> I tried to update the PowerMac G5 (a so-called "Quad Core") >>> that I have access to from head -r312761 to -r313864 and >>> ended up with random panics and hang ups in fairly short >>> order after booting. >>>=20 >>> Some approximate bisecting for the kernel lead to: >>> (sometimes getting part way into a buildkernel attempt >>> for a different version before a failure happens) >>>=20 >>> -r313266: works (just before use of atomic_fcmpset) >>> vs. >>> -r313271: fails (last of the "use atomic_fcmpset" check-ins) >>>=20 >>> (I did not try -r313268 through -r313270 as the use was >>> gradually added.) >>>=20 >>> So I'm currently running a -r313864 world with a -r313266 >>> kernel. >>>=20 >>> No kernel that I tried that was from before -r313266 had the >>> problems. >>>=20 >>> Any kernel that I tried that was from after -r313271 had the >>> problems. >>>=20 >>> Of course I did not try them all in other direction. :) >>>=20 >>=20 >> I found that spin mutexes were not properly handling this, fixed in >> r313996. >>=20 >> Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64 >> fcmpset to simulate failures. Everything works, while it would easily >> fail without the patch. >>=20 >> That said, I hope this concludes the 'missing check for not-reread = value >> of failed fcmpset' saga. >>=20 >> --=20 >> Mateusz Guzik >=20 > I tried to update from -r313864 to -r313999 in my amd64 context > (a VirtualBox machine under macOS) but it now crashes late in > the boot sequence (after it processes a dump if I make one but > before I can log in). >=20 > This update was via my usual explicit svnlite update; buildworld > buildkernel; etc. production style build of world and kernel, > including use of MALLOC_PRODUCTION. >=20 > The window shows: >=20 > _vm_map_lock+0xf > vm_map_wire+0x32 > rtROMemObjNativeLockInMap+0x8c > rtROMemObjNativeLockUser+0x51 > RTR0MemObjLockUserTag+0x231 > vbglR0HGCMInternalPreprocessCall+0x65d > vbglR0HGCMInternalCall+0x17c > vgdrvIoCtl_HGCMCall+0x43f > VGDrvCommonIoCtl+0x261 > vgdrvFreeBSDIOCtl+0x2cd > devfs_ioctl+0xae > VOP_IOCTL_APV+0x88 > vn_ioctl+0x161 > devfs_ioctl_f+0x1f > kern_ioctl+0x280 > sys_ioctl+0x13f > amd64_syscall+0x397 > Xfast_syscall+0xfb More detail from booting with the -r313864 kernel.old and using kgdb on what the dump produced: # kgdb kernel.debug /var/crash/vmcore. /var/crash/vmcore.0 /var/crash/vmcore.last # kgdb kernel.debug /var/crash/vmcore.0 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you = are welcome to change it and/or distribute copies of it under certain = conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for = details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: <118>Starting vboxservice. <118>VBoxService 5.1.14 r112924 (verbosity: 0) freebsd.amd64 (Jan 20 = 2017 18:37:45) release log <118>00:00:00.000120 main Log opened 2017-02-20T22:38:46.348080000Z <118>00:00:00.000162 main OS Product: FreeBSD <118>00:00:00.000171 main OS Release: 12.0-CURRENT <118>00:00:00.000180 main OS Version: FreeBSD 12.0-CURRENT r313999M <118>00:00:00.000192 main Executable: /usr/local/sbin/VBoxService <118>00:00:00.000194 main Process ID: 609 <118>00:00:00.000196 main Package type: BSD_64BITS_GENERIC (OSE) Fatal trap 12: page fault while in kernel mode cpuid =3D 2; apic id =3D 02 fault virtual address =3D 0xd6 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff80d4ebaf stack pointer =3D 0x28:0xfffffe0122e2bef0 frame pointer =3D 0x28:0xfffffe0122e2bf00 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 609 (VBoxService) Reading symbols from /boot/kernel/zfs.ko...Reading symbols from = /usr/lib/debug//boot/kernel/zfs.ko.debug...done. done. Loaded symbols for /boot/kernel/zfs.ko Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from = /usr/lib/debug//boot/kernel/opensolaris.ko.debug...done. done. Loaded symbols for /boot/kernel/opensolaris.ko Reading symbols from /boot/modules/vboxguest.ko...done. Loaded symbols for /boot/modules/vboxguest.ko #0 doadump (textdump=3D0) at pcpu.h:232 232 __asm("movq %%gs:%1,%0" : "=3Dr" (td) (kgdb) bt #0 doadump (textdump=3D0) at pcpu.h:232 #1 0xffffffff8039dd0b in db_dump (dummy=3D, = dummy2=3D, dummy3=3D, = dummy4=3D) at /usr/src/sys/ddb/db_command.c:546 #2 0xffffffff8039db0f in db_command (cmd_table=3D) = at /usr/src/sys/ddb/db_command.c:453 #3 0xffffffff8039d884 in db_command_loop () at = /usr/src/sys/ddb/db_command.c:506 #4 0xffffffff803a0814 in db_trap (type=3D, = code=3D) at /usr/src/sys/ddb/db_main.c:254 #5 0xffffffff80a9c0c3 in kdb_trap (type=3D, = code=3D, tf=3D) at = /usr/src/sys/kern/subr_kdb.c:654 #6 0xffffffff80ed25d2 in trap_fatal (frame=3D0xfffffe0122e2be30, = eva=3D214) at /usr/src/sys/amd64/amd64/trap.c:796 #7 0xffffffff80ed27dc in trap_pfault (frame=3D0xfffffe0122e2be30, = usermode=3D0) at /usr/src/sys/amd64/amd64/trap.c:658 #8 0xffffffff80ed1e90 in trap (frame=3D0xfffffe0122e2be30) at = /usr/src/sys/amd64/amd64/trap.c:421 #9 0xffffffff80eb6be1 in calltrap () at = /usr/src/sys/amd64/amd64/exception.S:236 #10 0xffffffff80d4ebaf in _vm_map_lock (map=3D0x1, file=3D0x0, line=3D0) = at /usr/src/sys/vm/vm_map.c:501 #11 0xffffffff80d51ea2 in vm_map_wire (map=3D, = start=3D4534272, end=3D4538368, flags=3D1) at = /usr/src/sys/vm/vm_map.c:2534 #12 0xffffffff8265291c in rtR0MemObjNativeLockInMap () from = /boot/modules/vboxguest.ko #13 0xffffffff82652881 in rtR0MemObjNativeLockUser () from = /boot/modules/vboxguest.ko #14 0xffffffff8264ec01 in RTR0MemObjLockUserTag () from = /boot/modules/vboxguest.ko #15 0xffffffff82624afd in vbglR0HGCMInternalPreprocessCall () from = /boot/modules/vboxguest.ko #16 0xffffffff8262411a in VbglR0HGCMInternalCall () from = /boot/modules/vboxguest.ko #17 0xffffffff8261ec4f in vgdrvIoCtl_HGCMCall () from = /boot/modules/vboxguest.ko #18 0xffffffff8261d221 in VGDrvCommonIoCtl () from = /boot/modules/vboxguest.ko #19 0xffffffff8262327d in vgdrvFreeBSDIOCtl () from = /boot/modules/vboxguest.ko #20 0xffffffff8092976e in devfs_ioctl (ap=3D) at = /usr/src/sys/fs/devfs/devfs_vnops.c:805 #21 0xffffffff8103ef58 in VOP_IOCTL_APV (vop=3D, = a=3D) at vnode_if.c:1067 #22 0xffffffff80b29431 in vn_ioctl (fp=3D0xfffff80006d37730, com=3D, data=3D0xfffffe0122e2c870, = active_cred=3D0xfffff80006495a00, td=3D) at = vnode_if.h:448 #23 0xffffffff80929d5f in devfs_ioctl_f (fp=3D, = com=3D, data=3D, cred=3D, td=3D0xfffff8001504e000) at = /usr/src/sys/fs/devfs/devfs_vnops.c:763 #24 0xffffffff80ab8bf0 in kern_ioctl (td=3D, fd=3D3, = com=3D, data=3D0xfffffe0122e2c870 "\031\002R\031P") = at file.h:322 #25 0xffffffff80ab88bf in sys_ioctl (td=3D, = uap=3D0xfffffe0122e2ca30) at /usr/src/sys/kern/sys_generic.c:743 #26 0xffffffff80ed2e27 in amd64_syscall (td=3D0xfffff8001504e000, = traced=3D0) at subr_syscall.c:135 #27 0xffffffff80eb6ecb in Xfast_syscall () at = /usr/src/sys/amd64/amd64/exception.S:396 #28 0x0000000800c5317a in ?? () Previous frame inner to this frame (corrupt stack?) Current language: auto; currently minimal =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Mon Feb 20 23:35:42 2017 Return-Path: Delivered-To: freebsd-ppc@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 5872DCE6AC1; Mon, 20 Feb 2017 23:35:42 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CCC131911; Mon, 20 Feb 2017 23:35:41 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id r18so16959131wmd.3; Mon, 20 Feb 2017 15:35:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=y8lxRZiqFE+RaXEozUOQgq+0sg6e+vQmwCfXhNkkwdU=; b=MSbVqeapl9WUwC+0+oswpS9plQEzggq7OZihyhGzROXxdn3pMKIVLCLZX5D2fhKP9w ZZZy4oYgw6wM6lDWrXuyUEdo/Bdh740GORYFBgRibalREgccaTkKl8l6rF4qq2EEAjZm hnaIF6y2CYh7VyAnRNYoqp/6mK2rOPtWCXKkarWtriYihlHxZqosVO/RqrceHivh9mkx 1Tftqdec3axk6R+kpaiREGtwUO7RU1gwJAc00sR+Jo3zvXoxITKmDZRrr1TZJAlWClL0 531kGyOqeOd0ZBeZz9woozygxNOBGAhctNXBGi8LOmKiV5xs4nQrVyQpp8en6Lh/f8pz p15w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=y8lxRZiqFE+RaXEozUOQgq+0sg6e+vQmwCfXhNkkwdU=; b=ey6uH+o/wh+35dA/oMzUIqnUyBO24ovGDMoDBRtJJwm+SrYIoEV4/XYTPSM2GNGUp8 o1+BtUUCa6YKEm7aqPKuWn7PeUEsVOeplCPV8apQEdRVlyCIWCvm8GahFcoJGJ9yDX/W /Rp3SIKmpQwhJs1O41uW8y7RukztJqro6reSNVkQurE9V0PGzN0KEDItbdb5CEcPH7Zv lFt4tgIa9U39eu0u43302kD0Bt6sPqWpQeJhWSoU9+IjUdyunnd8ns5NPAln2obZXue+ GciUhZ+SdhH7w+p8d6SdFNWsSPIVnZ/K0p/4/sPRElAVg9AV8f70YgiwUH/E7bYkIaDL QUOA== X-Gm-Message-State: AMke39nB9Y6nguBBB32IimLos+dnFdED2RitYUxVTb9EEXhgZs91nvRca16iz3wAc/OSGw== X-Received: by 10.28.170.4 with SMTP id t4mr12781610wme.89.1487633740252; Mon, 20 Feb 2017 15:35:40 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by smtp.gmail.com with ESMTPSA id 136sm15311968wms.32.2017.02.20.15.35.39 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Mon, 20 Feb 2017 15:35:39 -0800 (PST) Date: Tue, 21 Feb 2017 00:35:37 +0100 From: Mateusz Guzik To: Mark Millard Cc: Justin Hibbits , mjg@freebsd.org, FreeBSD Current , svn-src-head@freebsd.org, FreeBSD PowerPC ML Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] Message-ID: <20170220233537.GB26759@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Mark Millard , Justin Hibbits , mjg@freebsd.org, FreeBSD Current , svn-src-head@freebsd.org, FreeBSD PowerPC ML References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <83428304-87BE-413C-BAB9-8FF218E7661C@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Feb 2017 23:35:42 -0000 On Mon, Feb 20, 2017 at 03:10:44PM -0800, Mark Millard wrote: > On 2017-Feb-20, at 2:58 PM, Mark Millard wrote: > > > On 2017-Feb-20, at 11:10 AM, Mateusz Guzik wrote: > > > >> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: > >>> [Note: I experiment with clang based powerpc64 builds, > >>> reporting problems that I find. Justin is familiar > >>> with this, as is Nathan.] > >>> > >>> I tried to update the PowerMac G5 (a so-called "Quad Core") > >>> that I have access to from head -r312761 to -r313864 and > >>> ended up with random panics and hang ups in fairly short > >>> order after booting. > >>> > >>> Some approximate bisecting for the kernel lead to: > >>> (sometimes getting part way into a buildkernel attempt > >>> for a different version before a failure happens) > >>> > >>> -r313266: works (just before use of atomic_fcmpset) > >>> vs. > >>> -r313271: fails (last of the "use atomic_fcmpset" check-ins) > >>> > >>> (I did not try -r313268 through -r313270 as the use was > >>> gradually added.) > >>> > >>> So I'm currently running a -r313864 world with a -r313266 > >>> kernel. > >>> > >>> No kernel that I tried that was from before -r313266 had the > >>> problems. > >>> > >>> Any kernel that I tried that was from after -r313271 had the > >>> problems. > >>> > >>> Of course I did not try them all in other direction. :) > >>> > >> > >> I found that spin mutexes were not properly handling this, fixed in > >> r313996. > >> > >> Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64 > >> fcmpset to simulate failures. Everything works, while it would easily > >> fail without the patch. > >> > >> That said, I hope this concludes the 'missing check for not-reread value > >> of failed fcmpset' saga. > >> > >> -- > >> Mateusz Guzik > > > > I tried to update from -r313864 to -r313999 in my amd64 context > > (a VirtualBox machine under macOS) but it now crashes late in > > the boot sequence (after it processes a dump if I make one but > > before I can log in). > > > > This update was via my usual explicit svnlite update; buildworld > > buildkernel; etc. production style build of world and kernel, > > including use of MALLOC_PRODUCTION. > > > > The window shows: > > > > _vm_map_lock+0xf > > vm_map_wire+0x32 > > rtROMemObjNativeLockInMap+0x8c > > rtROMemObjNativeLockUser+0x51 > > RTR0MemObjLockUserTag+0x231 > > vbglR0HGCMInternalPreprocessCall+0x65d > > vbglR0HGCMInternalCall+0x17c > > vgdrvIoCtl_HGCMCall+0x43f > > VGDrvCommonIoCtl+0x261 > > vgdrvFreeBSDIOCtl+0x2cd > > devfs_ioctl+0xae > > VOP_IOCTL_APV+0x88 > > vn_ioctl+0x161 > > devfs_ioctl_f+0x1f > > kern_ioctl+0x280 > > sys_ioctl+0x13f > > amd64_syscall+0x397 > > Xfast_syscall+0xfb > > More detail from booting with the -r313864 kernel.old > and using kgdb on what the dump produced: > > # kgdb kernel.debug /var/crash/vmcore. > /var/crash/vmcore.0 /var/crash/vmcore.last > # kgdb kernel.debug /var/crash/vmcore.0 > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "amd64-marcel-freebsd"... > > Unread portion of the kernel message buffer: > <118>Starting vboxservice. > <118>VBoxService 5.1.14 r112924 (verbosity: 0) freebsd.amd64 (Jan 20 2017 18:37:45) release log > <118>00:00:00.000120 main Log opened 2017-02-20T22:38:46.348080000Z > <118>00:00:00.000162 main OS Product: FreeBSD > <118>00:00:00.000171 main OS Release: 12.0-CURRENT > <118>00:00:00.000180 main OS Version: FreeBSD 12.0-CURRENT r313999M > <118>00:00:00.000192 main Executable: /usr/local/sbin/VBoxService > <118>00:00:00.000194 main Process ID: 609 > <118>00:00:00.000196 main Package type: BSD_64BITS_GENERIC (OSE) > > > Fatal trap 12: page fault while in kernel mode > cpuid = 2; apic id = 02 > fault virtual address = 0xd6 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80d4ebaf > stack pointer = 0x28:0xfffffe0122e2bef0 > frame pointer = 0x28:0xfffffe0122e2bf00 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 609 (VBoxService) > > #9 0xffffffff80eb6be1 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 > #10 0xffffffff80d4ebaf in _vm_map_lock (map=0x1, file=0x0, line=0) at /usr/src/sys/vm/vm_map.c:501 The function is: void _vm_map_lock(vm_map_t map, const char *file, int line) { if (map->system_map) mtx_lock_flags_(&map->system_mtx, 0, file, line); else sx_xlock_(&map->lock, file, line); map->timestamp++; } system_map is at offset 0xd5, thus the faulting address of 0xd6 with map address of 1 looks like the backtrace is corect. But this suggests the bug is unrelated to my changes and there is a chance there is no bug in the first place. Please make sure that the virtualbox module is recompiled against proper source tree. If the problem persists, please bisect. The range is not big. Off hand I don't see what can cause the failure in question (and chances are there is no bug if kbi changed and the module was not recompiled). > #11 0xffffffff80d51ea2 in vm_map_wire (map=, start=4534272, end=4538368, flags=1) at /usr/src/sys/vm/vm_map.c:2534 > #12 0xffffffff8265291c in rtR0MemObjNativeLockInMap () from /boot/modules/vboxguest.ko > #13 0xffffffff82652881 in rtR0MemObjNativeLockUser () from /boot/modules/vboxguest.ko > #14 0xffffffff8264ec01 in RTR0MemObjLockUserTag () from /boot/modules/vboxguest.ko > #15 0xffffffff82624afd in vbglR0HGCMInternalPreprocessCall () from /boot/modules/vboxguest.ko > #16 0xffffffff8262411a in VbglR0HGCMInternalCall () from /boot/modules/vboxguest.ko > #17 0xffffffff8261ec4f in vgdrvIoCtl_HGCMCall () from /boot/modules/vboxguest.ko > #18 0xffffffff8261d221 in VGDrvCommonIoCtl () from /boot/modules/vboxguest.ko > -- Mateusz Guzik From owner-freebsd-ppc@freebsd.org Tue Feb 21 02:36:20 2017 Return-Path: Delivered-To: freebsd-ppc@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 0CB59CE76CD for ; Tue, 21 Feb 2017 02:36:20 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-76.reflexion.net [208.70.210.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C2193AF5 for ; Tue, 21 Feb 2017 02:36:18 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 10966 invoked from network); 21 Feb 2017 02:36:17 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 21 Feb 2017 02:36:17 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Mon, 20 Feb 2017 21:36:17 -0500 (EST) Received: (qmail 22327 invoked from network); 21 Feb 2017 02:36:17 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 21 Feb 2017 02:36:17 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 1F863EC9055; Mon, 20 Feb 2017 18:36:16 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <20170220233537.GB26759@dft-labs.eu> Date: Mon, 20 Feb 2017 18:36:15 -0800 Cc: Justin Hibbits , mjg@freebsd.org, FreeBSD Current , svn-src-head@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <26B93201-D3E9-4443-A60F-FC871EC5C96C@dsl-only.net> References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <83428304-87BE-413C-BAB9-8FF218E7661C@dsl-only.net> <20170220233537.GB26759@dft-labs.eu> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2017 02:36:20 -0000 On 2017-Feb-20, at 3:35 PM, Mateusz Guzik wrote: > On Mon, Feb 20, 2017 at 03:10:44PM -0800, Mark Millard wrote: >> On 2017-Feb-20, at 2:58 PM, Mark Millard = wrote: >>=20 >>> On 2017-Feb-20, at 11:10 AM, Mateusz Guzik = wrote: >>>=20 >>>> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: >>>>> [Note: I experiment with clang based powerpc64 builds, >>>>> reporting problems that I find. Justin is familiar >>>>> with this, as is Nathan.] >>>>>=20 >>>>> I tried to update the PowerMac G5 (a so-called "Quad Core") >>>>> that I have access to from head -r312761 to -r313864 and >>>>> ended up with random panics and hang ups in fairly short >>>>> order after booting. >>>>>=20 >>>>> Some approximate bisecting for the kernel lead to: >>>>> (sometimes getting part way into a buildkernel attempt >>>>> for a different version before a failure happens) >>>>>=20 >>>>> -r313266: works (just before use of atomic_fcmpset) >>>>> vs. >>>>> -r313271: fails (last of the "use atomic_fcmpset" check-ins) >>>>>=20 >>>>> (I did not try -r313268 through -r313270 as the use was >>>>> gradually added.) >>>>>=20 >>>>> So I'm currently running a -r313864 world with a -r313266 >>>>> kernel. >>>>>=20 >>>>> No kernel that I tried that was from before -r313266 had the >>>>> problems. >>>>>=20 >>>>> Any kernel that I tried that was from after -r313271 had the >>>>> problems. >>>>>=20 >>>>> Of course I did not try them all in other direction. :) >>>>>=20 >>>>=20 >>>> I found that spin mutexes were not properly handling this, fixed in >>>> r313996. >>>>=20 >>>> Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64 >>>> fcmpset to simulate failures. Everything works, while it would = easily >>>> fail without the patch. >>>>=20 >>>> That said, I hope this concludes the 'missing check for not-reread = value >>>> of failed fcmpset' saga. >>>>=20 >>>> --=20 >>>> Mateusz Guzik >>>=20 >>> I tried to update from -r313864 to -r313999 in my amd64 context >>> (a VirtualBox machine under macOS) but it now crashes late in >>> the boot sequence (after it processes a dump if I make one but >>> before I can log in). >>>=20 >>> This update was via my usual explicit svnlite update; buildworld >>> buildkernel; etc. production style build of world and kernel, >>> including use of MALLOC_PRODUCTION. >>>=20 >>> The window shows: >>>=20 >>> _vm_map_lock+0xf >>> vm_map_wire+0x32 >>> rtROMemObjNativeLockInMap+0x8c >>> rtROMemObjNativeLockUser+0x51 >>> RTR0MemObjLockUserTag+0x231 >>> vbglR0HGCMInternalPreprocessCall+0x65d >>> vbglR0HGCMInternalCall+0x17c >>> vgdrvIoCtl_HGCMCall+0x43f >>> VGDrvCommonIoCtl+0x261 >>> vgdrvFreeBSDIOCtl+0x2cd >>> devfs_ioctl+0xae >>> VOP_IOCTL_APV+0x88 >>> vn_ioctl+0x161 >>> devfs_ioctl_f+0x1f >>> kern_ioctl+0x280 >>> sys_ioctl+0x13f >>> amd64_syscall+0x397 >>> Xfast_syscall+0xfb >>=20 >> More detail from booting with the -r313864 kernel.old >> and using kgdb on what the dump produced: >>=20 >> # kgdb kernel.debug /var/crash/vmcore. >> /var/crash/vmcore.0 /var/crash/vmcore.last >> # kgdb kernel.debug /var/crash/vmcore.0 >> GNU gdb 6.1.1 [FreeBSD] >> Copyright 2004 Free Software Foundation, Inc. >> GDB is free software, covered by the GNU General Public License, and = you are >> welcome to change it and/or distribute copies of it under certain = conditions. >> Type "show copying" to see the conditions. >> There is absolutely no warranty for GDB. Type "show warranty" for = details. >> This GDB was configured as "amd64-marcel-freebsd"... >>=20 >> Unread portion of the kernel message buffer: >> <118>Starting vboxservice. >> <118>VBoxService 5.1.14 r112924 (verbosity: 0) freebsd.amd64 (Jan 20 = 2017 18:37:45) release log >> <118>00:00:00.000120 main Log opened = 2017-02-20T22:38:46.348080000Z >> <118>00:00:00.000162 main OS Product: FreeBSD >> <118>00:00:00.000171 main OS Release: 12.0-CURRENT >> <118>00:00:00.000180 main OS Version: FreeBSD 12.0-CURRENT = r313999M >> <118>00:00:00.000192 main Executable: /usr/local/sbin/VBoxService >> <118>00:00:00.000194 main Process ID: 609 >> <118>00:00:00.000196 main Package type: BSD_64BITS_GENERIC (OSE) >>=20 >>=20 >> Fatal trap 12: page fault while in kernel mode >> cpuid =3D 2; apic id =3D 02 >> fault virtual address =3D 0xd6 >> fault code =3D supervisor read data, page not present >> instruction pointer =3D 0x20:0xffffffff80d4ebaf >> stack pointer =3D 0x28:0xfffffe0122e2bef0 >> frame pointer =3D 0x28:0xfffffe0122e2bf00 >> code segment =3D base 0x0, limit 0xfffff, type 0x1b >> =3D DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 >> current process =3D 609 (VBoxService) >>=20 >=20 >=20 >=20 >> #9 0xffffffff80eb6be1 in calltrap () at = /usr/src/sys/amd64/amd64/exception.S:236 >> #10 0xffffffff80d4ebaf in _vm_map_lock (map=3D0x1, file=3D0x0, = line=3D0) at /usr/src/sys/vm/vm_map.c:501 >=20 > The function is: > void > _vm_map_lock(vm_map_t map, const char *file, int line) > { >=20 > if (map->system_map) > mtx_lock_flags_(&map->system_mtx, 0, file, line); > else > sx_xlock_(&map->lock, file, line); > map->timestamp++; > } >=20 > system_map is at offset 0xd5, thus the faulting address of 0xd6 with = map > address of 1 looks like the backtrace is corect. But this suggests the > bug is unrelated to my changes and there is a chance there is no bug = in > the first place. >=20 > Please make sure that the virtualbox module is recompiled against = proper > source tree. If the problem persists, please bisect. The range is not > big. >=20 > Off hand I don't see what can cause the failure in question (and = chances > are there is no bug if kbi changed and the module was not recompiled). >=20 >> #11 0xffffffff80d51ea2 in vm_map_wire (map=3D, = start=3D4534272, end=3D4538368, flags=3D1) at = /usr/src/sys/vm/vm_map.c:2534 >> #12 0xffffffff8265291c in rtR0MemObjNativeLockInMap () from = /boot/modules/vboxguest.ko >> #13 0xffffffff82652881 in rtR0MemObjNativeLockUser () from = /boot/modules/vboxguest.ko >> #14 0xffffffff8264ec01 in RTR0MemObjLockUserTag () from = /boot/modules/vboxguest.ko >> #15 0xffffffff82624afd in vbglR0HGCMInternalPreprocessCall () from = /boot/modules/vboxguest.ko >> #16 0xffffffff8262411a in VbglR0HGCMInternalCall () from = /boot/modules/vboxguest.ko >> #17 0xffffffff8261ec4f in vgdrvIoCtl_HGCMCall () from = /boot/modules/vboxguest.ko >> #18 0xffffffff8261d221 in VGDrvCommonIoCtl () from = /boot/modules/vboxguest.ko I do not expect that the kernel binary interface deliberately changed between -r313864 and -r313999. Until the attempted update of amd64 (which I always do first) the amd64 and arm64 were running: . . . 12.0-CURRENT FreeBSD 12.0-CURRENT r313864M . . . 1200021 1200021 I've not noticed an update to 1200022 yet. [It turned out that for powerpc64 I had to use -r313266 for the kernel when I tried to update to -r313864. This does mix 1200020 and 1200021. But 1200021 was removal of support for things I do not have involved --and the combination has seemed okay so far.] I've decided to do a round of port upgrades (to -r434493), although virtualbox client has not been updated. I'll force a rebuild before I'm done. It turns out that llvm39 is now required for what I choose to have and its build ran out of RAM/swap as I had things configured. So I've adjusted to have the VM have more RAM assigned and I'm not starting lumina but just using the console for now. We will see. Note: I always manually start lumina and so it was not involved in the boot problem: it was just a basic console style context at all times for the boot crash. Overall it will be a while before I have a works vs. fails pair that are significantly closer together. --=20 Mateusz Guzik From owner-freebsd-ppc@freebsd.org Tue Feb 21 05:39:36 2017 Return-Path: Delivered-To: freebsd-ppc@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 B1479CE6791 for ; Tue, 21 Feb 2017 05:39:36 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-70.reflexion.net [208.70.210.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 713A210BE for ; Tue, 21 Feb 2017 05:39:35 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 16383 invoked from network); 21 Feb 2017 05:39:34 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 21 Feb 2017 05:39:34 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Tue, 21 Feb 2017 00:39:34 -0500 (EST) Received: (qmail 27892 invoked from network); 21 Feb 2017 05:39:34 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 21 Feb 2017 05:39:34 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 386FDEC7E18; Mon, 20 Feb 2017 21:39:33 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <26B93201-D3E9-4443-A60F-FC871EC5C96C@dsl-only.net> Date: Mon, 20 Feb 2017 21:39:32 -0800 Cc: svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <7089D194-8BB3-4D40-8314-4A15B41986DA@dsl-only.net> References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <83428304-87BE-413C-BAB9-8FF218E7661C@dsl-only.net> <20170220233537.GB26759@dft-labs.eu> <26B93201-D3E9-4443-A60F-FC871EC5C96C@dsl-only.net> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2017 05:39:36 -0000 On 2017-Feb-20, at 6:36 PM, Mark Millard wrote: > On 2017-Feb-20, at 3:35 PM, Mateusz Guzik = wrote: >=20 >> On Mon, Feb 20, 2017 at 03:10:44PM -0800, Mark Millard wrote: >>> On 2017-Feb-20, at 2:58 PM, Mark Millard = wrote: >>>=20 >>>> On 2017-Feb-20, at 11:10 AM, Mateusz Guzik = wrote: >>>>=20 >>>>> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: >>>>>> [Note: I experiment with clang based powerpc64 builds, >>>>>> reporting problems that I find. Justin is familiar >>>>>> with this, as is Nathan.] >>>>>>=20 >>>>>> I tried to update the PowerMac G5 (a so-called "Quad Core") >>>>>> that I have access to from head -r312761 to -r313864 and >>>>>> ended up with random panics and hang ups in fairly short >>>>>> order after booting. >>>>>>=20 >>>>>> Some approximate bisecting for the kernel lead to: >>>>>> (sometimes getting part way into a buildkernel attempt >>>>>> for a different version before a failure happens) >>>>>>=20 >>>>>> -r313266: works (just before use of atomic_fcmpset) >>>>>> vs. >>>>>> -r313271: fails (last of the "use atomic_fcmpset" check-ins) >>>>>>=20 >>>>>> (I did not try -r313268 through -r313270 as the use was >>>>>> gradually added.) >>>>>>=20 >>>>>> So I'm currently running a -r313864 world with a -r313266 >>>>>> kernel. >>>>>>=20 >>>>>> No kernel that I tried that was from before -r313266 had the >>>>>> problems. >>>>>>=20 >>>>>> Any kernel that I tried that was from after -r313271 had the >>>>>> problems. >>>>>>=20 >>>>>> Of course I did not try them all in other direction. :) >>>>>>=20 >>>>>=20 >>>>> I found that spin mutexes were not properly handling this, fixed = in >>>>> r313996. >>>>>=20 >>>>> Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64 >>>>> fcmpset to simulate failures. Everything works, while it would = easily >>>>> fail without the patch. >>>>>=20 >>>>> That said, I hope this concludes the 'missing check for not-reread = value >>>>> of failed fcmpset' saga. >>>>>=20 >>>>> --=20 >>>>> Mateusz Guzik >>>>=20 >>>> I tried to update from -r313864 to -r313999 in my amd64 context >>>> (a VirtualBox machine under macOS) but it now crashes late in >>>> the boot sequence (after it processes a dump if I make one but >>>> before I can log in). >>>>=20 >>>> This update was via my usual explicit svnlite update; buildworld >>>> buildkernel; etc. production style build of world and kernel, >>>> including use of MALLOC_PRODUCTION. >>>>=20 >>>> The window shows: >>>>=20 >>>> _vm_map_lock+0xf >>>> vm_map_wire+0x32 >>>> rtROMemObjNativeLockInMap+0x8c >>>> rtROMemObjNativeLockUser+0x51 >>>> RTR0MemObjLockUserTag+0x231 >>>> vbglR0HGCMInternalPreprocessCall+0x65d >>>> vbglR0HGCMInternalCall+0x17c >>>> vgdrvIoCtl_HGCMCall+0x43f >>>> VGDrvCommonIoCtl+0x261 >>>> vgdrvFreeBSDIOCtl+0x2cd >>>> devfs_ioctl+0xae >>>> VOP_IOCTL_APV+0x88 >>>> vn_ioctl+0x161 >>>> devfs_ioctl_f+0x1f >>>> kern_ioctl+0x280 >>>> sys_ioctl+0x13f >>>> amd64_syscall+0x397 >>>> Xfast_syscall+0xfb >>>=20 >>> More detail from booting with the -r313864 kernel.old >>> and using kgdb on what the dump produced: >>>=20 >>> # kgdb kernel.debug /var/crash/vmcore. >>> /var/crash/vmcore.0 /var/crash/vmcore.last >>> # kgdb kernel.debug /var/crash/vmcore.0 >>> GNU gdb 6.1.1 [FreeBSD] >>> Copyright 2004 Free Software Foundation, Inc. >>> GDB is free software, covered by the GNU General Public License, and = you are >>> welcome to change it and/or distribute copies of it under certain = conditions. >>> Type "show copying" to see the conditions. >>> There is absolutely no warranty for GDB. Type "show warranty" for = details. >>> This GDB was configured as "amd64-marcel-freebsd"... >>>=20 >>> Unread portion of the kernel message buffer: >>> <118>Starting vboxservice. >>> <118>VBoxService 5.1.14 r112924 (verbosity: 0) freebsd.amd64 (Jan 20 = 2017 18:37:45) release log >>> <118>00:00:00.000120 main Log opened = 2017-02-20T22:38:46.348080000Z >>> <118>00:00:00.000162 main OS Product: FreeBSD >>> <118>00:00:00.000171 main OS Release: 12.0-CURRENT >>> <118>00:00:00.000180 main OS Version: FreeBSD 12.0-CURRENT = r313999M >>> <118>00:00:00.000192 main Executable: = /usr/local/sbin/VBoxService >>> <118>00:00:00.000194 main Process ID: 609 >>> <118>00:00:00.000196 main Package type: BSD_64BITS_GENERIC (OSE) >>>=20 >>>=20 >>> Fatal trap 12: page fault while in kernel mode >>> cpuid =3D 2; apic id =3D 02 >>> fault virtual address =3D 0xd6 >>> fault code =3D supervisor read data, page not present >>> instruction pointer =3D 0x20:0xffffffff80d4ebaf >>> stack pointer =3D 0x28:0xfffffe0122e2bef0 >>> frame pointer =3D 0x28:0xfffffe0122e2bf00 >>> code segment =3D base 0x0, limit 0xfffff, type 0x1b >>> =3D DPL 0, pres 1, long 1, def32 0, gran 1 >>> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 >>> current process =3D 609 (VBoxService) >>>=20 >>=20 >>=20 >>=20 >>> #9 0xffffffff80eb6be1 in calltrap () at = /usr/src/sys/amd64/amd64/exception.S:236 >>> #10 0xffffffff80d4ebaf in _vm_map_lock (map=3D0x1, file=3D0x0, = line=3D0) at /usr/src/sys/vm/vm_map.c:501 >>=20 >> The function is: >> void >> _vm_map_lock(vm_map_t map, const char *file, int line) >> { >>=20 >> if (map->system_map) >> mtx_lock_flags_(&map->system_mtx, 0, file, line); >> else >> sx_xlock_(&map->lock, file, line); >> map->timestamp++; >> } >>=20 >> system_map is at offset 0xd5, thus the faulting address of 0xd6 with = map >> address of 1 looks like the backtrace is corect. But this suggests = the >> bug is unrelated to my changes and there is a chance there is no bug = in >> the first place. >>=20 >> Please make sure that the virtualbox module is recompiled against = proper >> source tree. If the problem persists, please bisect. The range is not >> big. >>=20 >> Off hand I don't see what can cause the failure in question (and = chances >> are there is no bug if kbi changed and the module was not = recompiled). >>=20 >>> #11 0xffffffff80d51ea2 in vm_map_wire (map=3D, = start=3D4534272, end=3D4538368, flags=3D1) at = /usr/src/sys/vm/vm_map.c:2534 >>> #12 0xffffffff8265291c in rtR0MemObjNativeLockInMap () from = /boot/modules/vboxguest.ko >>> #13 0xffffffff82652881 in rtR0MemObjNativeLockUser () from = /boot/modules/vboxguest.ko >>> #14 0xffffffff8264ec01 in RTR0MemObjLockUserTag () from = /boot/modules/vboxguest.ko >>> #15 0xffffffff82624afd in vbglR0HGCMInternalPreprocessCall () from = /boot/modules/vboxguest.ko >>> #16 0xffffffff8262411a in VbglR0HGCMInternalCall () from = /boot/modules/vboxguest.ko >>> #17 0xffffffff8261ec4f in vgdrvIoCtl_HGCMCall () from = /boot/modules/vboxguest.ko >>> #18 0xffffffff8261d221 in VGDrvCommonIoCtl () from = /boot/modules/vboxguest.ko >=20 > I do not expect that the kernel binary interface deliberately changed > between -r313864 and -r313999. Until the attempted update of amd64 > (which I always do first) the amd64 and arm64 were running: >=20 > . . . 12.0-CURRENT FreeBSD 12.0-CURRENT r313864M . . . 1200021 = 1200021 >=20 > I've not noticed an update to 1200022 yet. >=20 > [It turned out that for powerpc64 I had to use -r313266 for the > kernel when I tried to update to -r313864. This does mix 1200020 > and 1200021. But 1200021 was removal of support for things I do > not have involved --and the combination has seemed okay so far.] >=20 > I've decided to do a round of port upgrades (to -r434493), > although virtualbox client has not been updated. I'll force a > rebuild before I'm done. >=20 > It turns out that llvm39 is now required for what I choose to > have and its build ran out of RAM/swap as I had things configured. > So I've adjusted to have the VM have more RAM assigned and I'm not > starting lumina but just using the console for now. We will see. >=20 > Note: I always manually start lumina and so it was not > involved in the boot problem: it was just a basic console > style context at all times for the boot crash. >=20 > Overall it will be a while before I have a works vs. fails > pair that are significantly closer together. Looks like some kernel binary interface (as seen by emulators/virtualbox-ose-addition ) has changed: rebuilding emulators/virtualbox-ose-addition removed the booting crash but uname -apKU still lists 1200021 and 2100021 for the kernel and world for -r313999, just like for -r313864. [Unfortunately lumina no longer processes my mouse clicks so now I've got something else to figure out.] =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Tue Feb 21 06:50:07 2017 Return-Path: Delivered-To: freebsd-ppc@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 EF4F5CE7F18; Tue, 21 Feb 2017 06:50:07 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7DBD11897; Tue, 21 Feb 2017 06:50:07 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-wr0-x243.google.com with SMTP id q39so14104811wrb.2; Mon, 20 Feb 2017 22:50:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=7sShgGg8QNxIQ67MNAjR4XjQa/aVRE3oXf+13OLi0dI=; b=FUQQGn+HQnmc6fbf7M8q9GZTtvpeXMyAq1EIWrZlY/rh8TdVet3ben1wskFBYlO6ME baQyTFPZyfXS7QFavVmoSDlERKQ5Dh+X/PFuUDLNgeWgcwnwGXFLP1jFE8O1hL1XmCtk FSRJ17kHOCJBRrQij2mKoPGvWt94+GMzEg1j0HIoMciQiIuMuLHJVLQ0YhdlNGvVpXE4 DOyf/aRsZJ2ObFs+yKhMuHvw6RALOydeLiC2vkyMMexBpYtB28QBycMfbu34gA9D9UQt sLCdgOvTubDDOY8B5DjbSfbLy0O5jk4q1qcV4tMN+YF+8FEXzUlnjk8id2QhmhxLuQpL /d6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=7sShgGg8QNxIQ67MNAjR4XjQa/aVRE3oXf+13OLi0dI=; b=RwiitsF5Ybi6QmsvEXRlwb8J7NmEjavu96SLLNjojrQT1Ti2oHD5iqgTNYPO7st63r LENF0yxN5i+fCRXeIyI5kFbPllucTeM5Qk2LZq55cru9PS4YViLOwTHx1KnW3u7mzicu X5bfL2ZWnQsOWd4CpqLxdlKdRw0eo6c/QaNCgrgs+ZaJBboXq+3sisfcqbEbsFYSCtY5 g0xYlzAzC1dxwnxl/dCwHJVk5leaeyz/EpS0TyxB/o9Z2DRV08YfPk2xnqwMvA/X2A/+ +ALqazMQ66PCy1KQVEquDW52kSUbbvPRNg4+qYLlNPMOsEDAjW4MiQcnEaIWlesZCX+k 84eA== X-Gm-Message-State: AMke39nemBeA8n1bwIlTphVu79uQuol1OlF4h7rJU8sA0whFTwuTYCcmy1NPKAF4+ovEdw== X-Received: by 10.223.150.178 with SMTP id u47mr15319134wrb.200.1487659806097; Mon, 20 Feb 2017 22:50:06 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by smtp.gmail.com with ESMTPSA id b51sm27669934wrd.39.2017.02.20.22.50.04 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Mon, 20 Feb 2017 22:50:05 -0800 (PST) Date: Tue, 21 Feb 2017 07:50:03 +0100 From: Mateusz Guzik To: Mark Millard Cc: svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] Message-ID: <20170221065002.GG26759@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Mark Millard , svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <83428304-87BE-413C-BAB9-8FF218E7661C@dsl-only.net> <20170220233537.GB26759@dft-labs.eu> <26B93201-D3E9-4443-A60F-FC871EC5C96C@dsl-only.net> <7089D194-8BB3-4D40-8314-4A15B41986DA@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <7089D194-8BB3-4D40-8314-4A15B41986DA@dsl-only.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2017 06:50:08 -0000 On Mon, Feb 20, 2017 at 09:39:32PM -0800, Mark Millard wrote: > Looks like some kernel binary interface (as seen by > emulators/virtualbox-ose-addition ) has changed: > rebuilding emulators/virtualbox-ose-addition removed > the booting crash but uname -apKU still lists 1200021 > and 2100021 for the kernel and world for -r313999, > just like for -r313864. > I think this is r313992. I don't see why __FreeBSD_version would be modified for this. You are expected to always recompilel your modules while tracking -current. -- Mateusz Guzik From owner-freebsd-ppc@freebsd.org Tue Feb 21 09:37:29 2017 Return-Path: Delivered-To: freebsd-ppc@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 CC4EECE68A8 for ; Tue, 21 Feb 2017 09:37:29 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-73.reflexion.net [208.70.210.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A5CCF2A for ; Tue, 21 Feb 2017 09:37:28 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 2810 invoked from network); 21 Feb 2017 09:37:27 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 21 Feb 2017 09:37:27 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Tue, 21 Feb 2017 04:37:27 -0500 (EST) Received: (qmail 12940 invoked from network); 21 Feb 2017 09:37:26 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 21 Feb 2017 09:37:26 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 32402EC903F; Tue, 21 Feb 2017 01:37:26 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <20170220191044.GA8526@dft-labs.eu> Date: Tue, 21 Feb 2017 01:37:25 -0800 Cc: mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current , Nathan Whitehorn Content-Transfer-Encoding: 7bit Message-Id: <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2017 09:37:29 -0000 [Back to the powerpc64 context.] On 2017-Feb-20, at 11:10 AM, Mateusz Guzik wrote: > On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: >> [Note: I experiment with clang based powerpc64 builds, >> reporting problems that I find. Justin is familiar >> with this, as is Nathan.] >> >> I tried to update the PowerMac G5 (a so-called "Quad Core") >> that I have access to from head -r312761 to -r313864 and >> ended up with random panics and hang ups in fairly short >> order after booting. >> >> Some approximate bisecting for the kernel lead to: >> (sometimes getting part way into a buildkernel attempt >> for a different version before a failure happens) >> >> -r313266: works (just before use of atomic_fcmpset) >> vs. >> -r313271: fails (last of the "use atomic_fcmpset" check-ins) >> >> (I did not try -r313268 through -r313270 as the use was >> gradually added.) >> >> So I'm currently running a -r313864 world with a -r313266 >> kernel. >> >> No kernel that I tried that was from before -r313266 had the >> problems. >> >> Any kernel that I tried that was from after -r313271 had the >> problems. >> >> Of course I did not try them all in other direction. :) >> > > I found that spin mutexes were not properly handling this, fixed in > r313996. > > Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64 > fcmpset to simulate failures. Everything works, while it would easily > fail without the patch. > > That said, I hope this concludes the 'missing check for not-reread value > of failed fcmpset' saga. > > -- > Mateusz Guzik -r313999 is an improvement for powerpc64: it boots and I can log in on the old PowerMac G5 so-called "Quad Core". But, e.g., buildworld buildkernel eventually hangs and later the powerpc64 panics for "spin lock held too long". === Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Tue Feb 21 15:14:16 2017 Return-Path: Delivered-To: freebsd-ppc@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 BFCF2CE8179 for ; Tue, 21 Feb 2017 15:14:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 93B7E1431 for ; Tue, 21 Feb 2017 15:14:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id E5CF11F6; Tue, 21 Feb 2017 15:14:15 +0000 (UTC) Delivered-To: freebsd-powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id D11AA1F5 for ; Tue, 21 Feb 2017 15:14:15 +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 mx1.freebsd.org (Postfix) with ESMTPS id 8B8601418 for ; Tue, 21 Feb 2017 15:14:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1LFEDL6076706 for ; Tue, 21 Feb 2017 15:14:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-powerpc@FreeBSD.org Subject: [Bug 217275] java/bootstrap-openjdk has incorrect architecture designation Date: Tue, 21 Feb 2017 15:14:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: hamiltcl@verizon.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: jkim@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc flagtypes.name attachments.created Message-ID: 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-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Feb 2017 15:14:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217275 Bug ID: 217275 Summary: java/bootstrap-openjdk has incorrect architecture designation Product: Ports & Packages Version: Latest Hardware: powerpc OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: jkim@FreeBSD.org Reporter: hamiltcl@verizon.net CC: freebsd-powerpc@FreeBSD.org CC: freebsd-powerpc@FreeBSD.org Assignee: jkim@FreeBSD.org Flags: maintainer-feedback?(jkim@FreeBSD.org) Created attachment 180190 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D180190&action= =3Dedit Patch to fix install on powerpc64 The java/bootstrap does not install due to missing "powerpc64" files as the bootstrap uses "powerpc" vice "powerpc64" as the architecture designation. There is also a missing lib dependency. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Wed Feb 22 07:12:03 2017 Return-Path: Delivered-To: freebsd-ppc@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 0B455CE9B0C for ; Wed, 22 Feb 2017 07:12:03 +0000 (UTC) (envelope-from msprvs1=17226XAi9Jo7x=bounces-86592@email.em.andgo.com) Received: from mta406b.sparkpostmail.com (mta406b.sparkpostmail.com [35.165.62.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.sparkpostmail.com", Issuer "RapidSSL SHA256 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7828A63 for ; Wed, 22 Feb 2017 07:12:02 +0000 (UTC) (envelope-from msprvs1=17226XAi9Jo7x=bounces-86592@email.em.andgo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sitaridev.co.za; s=scph1216; t=1487747522; i=@sitaridev.co.za; bh=mU84rj7ndMl4SZ+v2rwROa+cY91Lw6pNiHQIKi0uSKQ=; h=To:Date:List-Id:Subject:From:Reply-To:List-Unsubscribe; b=gj1sprCOzl0V9yY00YL1u3qnGX5hfApagoyrdabQJLbSzIdjPig9GioTtdidauOkQ CYYd7UE1KHD7rik2eWVrnttobXd7DetuokSQnhEbgviRYOu50293vBQh7Yo6xqiB6D QLEeFw8tUlWRPDMJ5XwOZkfrORga1GlutakT6q+s= X-MSFBL: jB3oyh8Bz89GMWi0wB7YWFIpf6SUxzqyzBwZdSDkXyc=|eyJnIjoiMDAwMDA6cGx hY2Vob2xkZXIiLCJtZXNzYWdlX2lkIjoiMDAwM2MyMzlhZDU4ZDdkN2I0MjMiLCJ yY3B0X21ldGEiOnsgInN1YnNjcmliZXJfdWlkIjogIm95NjA4eGtsZzJmYzgiLCA iY2FtcGFpZ25fdWlkIjogIm56ODQ5ZTYyNzliZjUiIH0sImN1c3RvbWVyX2lkIjo iODY1OTIiLCJ0ZW1wbGF0ZV9pZCI6InRlbXBsYXRlXzY2NTIyOTU0MjEwMzMzODE xIiwiaXBfcG9vbCI6ImRlZmF1bHQiLCJ0cmFuc21pc3Npb25faWQiOiI2NjUyMjk 1NDIxMDMzMzgxMSIsImIiOiJpcF8zNS4xNjUuNjIuMTMwIiwiY2FtcGFpZ25faWQ iOiJuejg0OWU2Mjc5YmY1IiwicmNwdF90YWdzIjpbIF0sInRlbmFudF9pZCI6InN wYyIsInN1YmFjY291bnRfaWQiOiIwIiwiaXBfcG9vbF9yYXciOiJkZWZhdWx0Iiw iZnJpZW5kbHlfZnJvbSI6InNpdGFyaUBzaXRhcmlkZXYuY28uemEiLCJzZW5kaW5 nX2lwIjoiMzUuMTY1LjYyLjEzMCIsInIiOiJmcmVlYnNkLXBwY0BmcmVlYnNkLm9 yZyIsInRlbXBsYXRlX3ZlcnNpb24iOiIwIn0= To: "=?utf-8?B?ZnJlZWJzZC1wcGNAZnJlZWJzZC5vcmc=?=" Message-ID: <4B.32.55255.2C93DA85@c.mta1vrest.cc.aws-usw2c.prd.sparkpost> Date: Wed, 22 Feb 2017 07:12:02 +0000 X-Mw-Subscriber-Uid: oy608xklg2fc8 X-Mw-Campaign-Uid: nz849e6279bf5 Precedence: bulk X-Mw-Customer-Gid: 2 X-Mw-Mailer: Sparkpost Web API X-Report-Abuse: Please report abuse for this campaign here: http://www.mmsend.co.za/index.php/campaigns/nz849e6279bf5/report-abuse/vn530js8cj347/oy608xklg2fc8 X-Mw-Customer-Uid: ck943am3f1f2e Feedback-ID: nz849e6279bf5:oy608xklg2fc8:vn530js8cj347:ck943am3f1f2e X-Mw-Delivery-Sid: 11 X-Sender: sitari@sitaridev.co.za Subject: =?utf-8?B?U2l0YXJpIENvdW50cnkgRXN0YXRlIC0gUHJlbWl1bSBQbG90cw==?= From: "=?utf-8?B?U2l0YXJpIENvdW50cnkgRXN0YXRl?=" MIME-Version: 1.0 Reply-To: reply@sitaridev.co.za X-Mw-Tracking-Did: 0 X-Receiver: freebsd-ppc@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2017 07:12:03 -0000 =09=09click here if you're not able to view this mailer=0Ahttp://sitaridev.= co.za/mailers/2016/november/premium_plots/pcpud.html=0A=0A=09=09Sitari Coun= try Estate=0A=09=09Somerset West * Cape Town=0A=0A=09=09 http://www.sitarid= ev.co.za/=0A=0AVoted South Africa's=0A Best Residential Estate=0A=0A=09=09E= STATE MOVIE https://www.youtube.com/watch=3Fv=3DWYd3lBDIm5o | PROGRESS=0AMO= VIE https://www.youtube.com/watch=3Fv=3DV7FYFlLmvtQ=0A=0A=09=09DREAM * DESI= GN * BUILD * LIVE=0A=0A=09=09FROM R895 000=0A=0A=09=094 Simple Steps To Bui= lding Your Dream Home=0A=0A=09=09=E2=98=91=0A=09=09Choose your plot=0A=0A= =09=09=E2=98=91=0A=09=09Design your home through our panel of architects=0A= =0A=09=09=E2=98=91=0A=09=09Build your home through our list of specialist b= uilders=0A=0A=09=09=E2=98=91=0A=09=09Move in and enjoy our award-winning li= festyle estate=0A=0A=09=09LEARN MORE ABOUT PREMIUM COUNTRY PLOTS=0Ahttp://s= itaridev.co.za/country-plots/#form=0A=0APremium Country Plots=0Afrom R895 0= 00=0A=0A=09=09MORE INFORMATION http://sitaridev.co.za/country-plots/#form= =0A=0APremium Apartments=0Afrom R1 035 000=0A=0ATurn-key Village Homes=0Afr= om R2 995 000=0A=0ATurn-key Country Homes=0Afrom R2 990 000=0A=0A=09=09Rece= ive pre-launch notifications.=0A=0A=09=09REGISTER NOW http://sitaridev.co.z= a/country-plots/#map=0A=0A=09=09EMAIL SITARI=0A=0A=09=09CALL SITARI http://= sitaridev.co.za/call-me-back-form=0A=0A=09=09VISIT OUR WEBSITE http://sitar= idev.co.za/country-plots/=0A=0A=09=09"Voted SA's best lifestyle estate" - A= frican Property Awards=0A2016/2017=0A=0A=09=09click here to UNSUBSCRIBE=0AH= TTP://WWW.MMSEND.CO.ZA/INDEX.PHP/LISTS/VN530JS8CJ347/UNSUBSCRIBE/OY608XKLG2= FC8/NZ849E6279BF5=0Aor _REPORT ABUSE=0AHTTP://WWW.MMSEND.CO.ZA/INDEX.PHP/CA= MPAIGNS/NZ849E6279BF5/REPORT-ABUSE/VN530JS8CJ347/OY608XKLG2FC8_=0A=0A From owner-freebsd-ppc@freebsd.org Thu Feb 23 11:51:03 2017 Return-Path: Delivered-To: freebsd-ppc@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 BC648CEA2A4 for ; Thu, 23 Feb 2017 11:51:03 +0000 (UTC) (envelope-from wissem@dottn.com) 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 A514CD23 for ; Thu, 23 Feb 2017 11:51:03 +0000 (UTC) (envelope-from wissem@dottn.com) Received: by mailman.ysv.freebsd.org (Postfix) id A1A6DCEA2A3; Thu, 23 Feb 2017 11:51:03 +0000 (UTC) Delivered-To: ppc@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 9F819CEA2A2 for ; Thu, 23 Feb 2017 11:51:03 +0000 (UTC) (envelope-from wissem@dottn.com) Received: from mailing.dottn.com (extranet.dottn.com [41.228.12.249]) by mx1.freebsd.org (Postfix) with ESMTP id DA081D1F for ; Thu, 23 Feb 2017 11:51:01 +0000 (UTC) (envelope-from wissem@dottn.com) Received: by mailing.dottn.com (Postfix, from userid 48) id 31B14C0F1F; Thu, 23 Feb 2017 12:46:13 +0100 (CET) To: ppc@freebsd.org Subject: Calendrier des Formations Dot TN X-PHP-Originating-Script: 0:class.phpmailer.php Received: from [172.16.1.1] by mailing.dottn.com with HTTP; Thu, 23 Feb 2017 12:46:10 +0100 Date: Thu, 23 Feb 2017 12:46:13 +0100 From: Dot TN Training Message-ID: <5b9edca95ef91c2a9a6b94d8d0ebf0c6@dottn.com> X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer) X-phpList-version: 3.3.1 X-MessageID: 6 X-ListMember: ppc@freebsd.org Precedence: bulk Bounces-To: wissem@dottn.com List-Owner: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 11:51:03 -0000 **Calendrier des Formations Dot TN** **Premier semestre 2017** Dot TN, Red Hat Certified Training Partner et Centre de formation agr=C3= =A9=C3=A9. Nous avons l'honneur de vous envoyer notre calendrier des formations et certifications jusqu'au 30 juin 2017. Voici le lien du calendrier des formations:=0Ahttp://mailing.dottn.com/list= s/lt.php?tid=3DnD8yV58A6Om9JegQKMhV3U2UPunxIJwLv4ozmelAozrfaR0fuctcNIFZ+oMe= MQ14 Voici le lien de l'agr=C3=A9ment de la formation:=0Ahttp://mailing.dottn.co= m/lists/lt.php?tid=3D7Wp8FwP+tFmBBonw/LKQwE2UPunxIGwLv4ozmelAozrfaR0fucs8NI= FZ+oMeMQ14 Pour vos inscriptions, veuillez contacter Mademoiselle Hajer au +216 71 710 849. Point TN S.A.R.L. Centre de Formation: 27 Avenue Taieb Mhiri, immeuble Yasmina 2080 Ariana - Tunisie Phone: +216 71 71 08 49=20 Mobile: +216 29 11 33 17=20 Fax: +216 71 88 54 99. -- This message was sent to ppc@freebsd.org by training@dottn.com To forward this message, please do not use the forward button of your email application, because this message was made specifically for you only. Instead use the forward page=0A in our newsletter system. To change your details and to choose which lists to be subscribed to, visit your personal preferences page=0A Or you can opt-out completely=0A from all future mailings. =20 -- powered by phpList, www.phplist.com -- From owner-freebsd-ppc@freebsd.org Thu Feb 23 17:56:56 2017 Return-Path: Delivered-To: freebsd-ppc@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 D36E1CEB6BB for ; Thu, 23 Feb 2017 17:56:56 +0000 (UTC) (envelope-from wissem@dottn.com) 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 C259FEBE for ; Thu, 23 Feb 2017 17:56:56 +0000 (UTC) (envelope-from wissem@dottn.com) Received: by mailman.ysv.freebsd.org (Postfix) id BED5ECEB6BA; Thu, 23 Feb 2017 17:56:56 +0000 (UTC) Delivered-To: ppc@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 BE053CEB6B9 for ; Thu, 23 Feb 2017 17:56:56 +0000 (UTC) (envelope-from wissem@dottn.com) Received: from mailing.dottn.com (extranet.dottn.com [41.228.12.249]) by mx1.freebsd.org (Postfix) with ESMTP id 7EB13EB5 for ; Thu, 23 Feb 2017 17:56:56 +0000 (UTC) (envelope-from wissem@dottn.com) Received: by mailing.dottn.com (Postfix, from userid 48) id 77876C3A0D; Thu, 23 Feb 2017 18:57:49 +0100 (CET) To: ppc@freebsd.org Subject: Au revoir de notre bulletin d'information X-PHP-Originating-Script: 0:class.phpmailer.php Received: from infra.dottn.com [172.16.32.6] by mailing.dottn.com with HTTP; Thu, 23 Feb 2017 18:57:49 +0100 Date: Thu, 23 Feb 2017 18:57:49 +0100 From: Dot TN Mailing System Message-ID: <7faf7935f26717a7702e3889fe450dec@dottn.com> X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer) X-phpList-version: 3.3.1 X-MessageID: systemmessage X-ListMember: ppc@freebsd.org Precedence: bulk Bounces-To: wissem@dottn.com MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2017 17:56:56 -0000 Goodbye from our Newsletter, sorry to see you go. You have been unsubscribed from our newsletters. This is the last email you will receive from us. Our newsletter system, phpList, will refuse to send you any further messages, without manual intervention by our administrator. If there is an error in this information, you can re-subscribe: please go to http://mailing.dottn.com/lists/?p=subscribe and follow the steps. Thank you From owner-freebsd-ppc@freebsd.org Sat Feb 25 00:23:05 2017 Return-Path: Delivered-To: freebsd-ppc@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 7B068CECC81; Sat, 25 Feb 2017 00:23:05 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09DCDA59; Sat, 25 Feb 2017 00:23:05 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id u63so5200244wmu.2; Fri, 24 Feb 2017 16:23:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Gl0tK/UTK+/FnibmCokRYgh5owFlbr/ae5jF7BCf5Dw=; b=HJuwM4A+1w6wNb/sjsbbJ8U7LcDrRmboU3WP2wt2LB1CLUwQms4sltA+1AMGtaFtrt tB2/iiM72pwyVrHh6Ynrhb6GPqDfID0NJQiQlCj4o0Am8Oib/wfzzOmv2dtBPeiNnmGH t1NvW6rv2DscLQXFbsyT4oj0P0WnV7NBpshpvfa6KDMU3qjoURyUZcMxFEyiaCeFzMSH Tk/SONVrth64iEXR3e3vWJKvvy+oVhv14aOovAz74zNg+KMlnoemUO5msTpSGdeBeR2L 5szcAk6azM6tdXtP8xp3am0zaADO/pohrFz0DSkSCucuvHd07qmc8bFUDvsg5nbHrntA 5xpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=Gl0tK/UTK+/FnibmCokRYgh5owFlbr/ae5jF7BCf5Dw=; b=WX/W8i88Lg4xJhLmp0ULAYdc0l8YirBc9WvRVKGKGQ0PkoIKc7KWTOn8+VVaGNoAEl HGWg3GTHoD27o9GYlBaAfnJow/t0IPnkLm5A/RYPau2jWD2XVOXwRKGu1jdapWkmIMQf Nu1UgoKqd8sLqkNZ8YmRW2OQGeLP7dv2HrV/KLaS6rye0baZeLQVJzQycl1FJhailWAg yRcJyq2mGGhowL2JtT7YtxKED/E/qk/AhqZia4tzj9NBVduyBlF8+aEkufK7MwIqeWri 4cfxL1iVl5Bn1RDlvJ3tQ6CSlzCzLWaIgF8SyCOqcOZy58Aw+nc/v/AgFWvo4U6jJDpn 2zVw== X-Gm-Message-State: AMke39mJw12M4XRupucTpuObR3z0s3HYxpFaAveoVYZgnzoQIiGjUU3e9SDJnYGEMI2+nQ== X-Received: by 10.28.6.210 with SMTP id 201mr4917622wmg.85.1487982183619; Fri, 24 Feb 2017 16:23:03 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by smtp.gmail.com with ESMTPSA id l130sm4233029wmf.0.2017.02.24.16.23.02 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Fri, 24 Feb 2017 16:23:03 -0800 (PST) Date: Sat, 25 Feb 2017 01:23:01 +0100 From: Mateusz Guzik To: Mark Millard Cc: mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current , Nathan Whitehorn Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] Message-ID: <20170225002300.GC19697@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Mark Millard , mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current , Nathan Whitehorn References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 00:23:05 -0000 On Tue, Feb 21, 2017 at 01:37:25AM -0800, Mark Millard wrote: > [Back to the powerpc64 context.] > > On 2017-Feb-20, at 11:10 AM, Mateusz Guzik wrote: > > > On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: > >> [Note: I experiment with clang based powerpc64 builds, > >> reporting problems that I find. Justin is familiar > >> with this, as is Nathan.] > >> > >> I tried to update the PowerMac G5 (a so-called "Quad Core") > >> that I have access to from head -r312761 to -r313864 and > >> ended up with random panics and hang ups in fairly short > >> order after booting. > >> > >> Some approximate bisecting for the kernel lead to: > >> (sometimes getting part way into a buildkernel attempt > >> for a different version before a failure happens) > >> > >> -r313266: works (just before use of atomic_fcmpset) > >> vs. > >> -r313271: fails (last of the "use atomic_fcmpset" check-ins) > >> > >> (I did not try -r313268 through -r313270 as the use was > >> gradually added.) > >> > >> So I'm currently running a -r313864 world with a -r313266 > >> kernel. > >> > >> No kernel that I tried that was from before -r313266 had the > >> problems. > >> > >> Any kernel that I tried that was from after -r313271 had the > >> problems. > >> > >> Of course I did not try them all in other direction. :) > >> > > > > I found that spin mutexes were not properly handling this, fixed in > > r313996. > > > > Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64 > > fcmpset to simulate failures. Everything works, while it would easily > > fail without the patch. > > > > That said, I hope this concludes the 'missing check for not-reread value > > of failed fcmpset' saga. > > > > -- > > Mateusz Guzik > > -r313999 is an improvement for powerpc64: it boots and I can > log in on the old PowerMac G5 so-called "Quad Core". > > But, e.g., buildworld buildkernel eventually hangs and later > the powerpc64 panics for "spin lock held too long". > Allright, play time is over. Can you please: 1. verify r313254 is stable for you 2. apply https://people.freebsd.org/~mjg/patches/complete-locks.diff and https://people.freebsd.org/~mjg/.junk/ppc.diff on top of it and retry the test? This is a workaround which effectively disables the powerpc-specific primitive and makes it use a cmpset wrapper instead. I don't have the hardware to test right now and my attempts to boot in qemu also failed. That said, does not look like there are general fcmpset bugs left and the remaining issue seems powerpc-specific. If this works, I'll commit the workaround for the time being as in few weeks I'd like to start merging the work back to stable/11. -- Mateusz Guzik From owner-freebsd-ppc@freebsd.org Sat Feb 25 04:52:29 2017 Return-Path: Delivered-To: freebsd-ppc@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 D4710CEC423 for ; Sat, 25 Feb 2017 04:52:29 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-93.reflexion.net [208.70.210.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 95515128D for ; Sat, 25 Feb 2017 04:52:29 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 16194 invoked from network); 25 Feb 2017 04:25:48 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 25 Feb 2017 04:25:48 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Fri, 24 Feb 2017 23:25:48 -0500 (EST) Received: (qmail 29692 invoked from network); 25 Feb 2017 04:25:47 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 25 Feb 2017 04:25:47 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id B833AEC8534; Fri, 24 Feb 2017 20:25:46 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <20170225002300.GC19697@dft-labs.eu> Date: Fri, 24 Feb 2017 20:25:46 -0800 Cc: mjg@freebsd.org, Justin Hibbits , svn-src-head@freebsd.org, FreeBSD PowerPC ML , FreeBSD Current , Nathan Whitehorn Content-Transfer-Encoding: 7bit Message-Id: <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> <20170225002300.GC19697@dft-labs.eu> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 04:52:29 -0000 On 2017-Feb-24, at 4:23 PM, Mateusz Guzik wrote: > > On Tue, Feb 21, 2017 at 01:37:25AM -0800, Mark Millard wrote: >> [Back to the powerpc64 context.] >> >> On 2017-Feb-20, at 11:10 AM, Mateusz Guzik wrote: >> >>> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: >>>> [Note: I experiment with clang based powerpc64 builds, >>>> reporting problems that I find. Justin is familiar >>>> with this, as is Nathan.] >>>> >>>> I tried to update the PowerMac G5 (a so-called "Quad Core") >>>> that I have access to from head -r312761 to -r313864 and >>>> ended up with random panics and hang ups in fairly short >>>> order after booting. >>>> >>>> Some approximate bisecting for the kernel lead to: >>>> (sometimes getting part way into a buildkernel attempt >>>> for a different version before a failure happens) >>>> >>>> -r313266: works (just before use of atomic_fcmpset) >>>> vs. >>>> -r313271: fails (last of the "use atomic_fcmpset" check-ins) >>>> >>>> (I did not try -r313268 through -r313270 as the use was >>>> gradually added.) >>>> >>>> So I'm currently running a -r313864 world with a -r313266 >>>> kernel. >>>> >>>> No kernel that I tried that was from before -r313266 had the >>>> problems. >>>> >>>> Any kernel that I tried that was from after -r313271 had the >>>> problems. >>>> >>>> Of course I did not try them all in other direction. :) >>>> >>> >>> I found that spin mutexes were not properly handling this, fixed in >>> r313996. >>> >>> Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64 >>> fcmpset to simulate failures. Everything works, while it would easily >>> fail without the patch. >>> >>> That said, I hope this concludes the 'missing check for not-reread value >>> of failed fcmpset' saga. >>> >>> -- >>> Mateusz Guzik >> >> -r313999 is an improvement for powerpc64: it boots and I can >> log in on the old PowerMac G5 so-called "Quad Core". >> >> But, e.g., buildworld buildkernel eventually hangs and later >> the powerpc64 panics for "spin lock held too long". >> > > Allright, play time is over. > > Can you please: > 1. verify r313254 is stable for you > 2. apply https://people.freebsd.org/~mjg/patches/complete-locks.diff and > https://people.freebsd.org/~mjg/.junk/ppc.diff on top of it and retry > the test? > > This is a workaround which effectively disables the powerpc-specific > primitive and makes it use a cmpset wrapper instead. I don't have the > hardware to test right now and my attempts to boot in qemu also failed. > > That said, does not look like there are general fcmpset bugs left and > the remaining issue seems powerpc-specific. > > If this works, I'll commit the workaround for the time being as in few > weeks I'd like to start merging the work back to stable/11. > > -- > Mateusz Guzik I've started a self-hosted powerpc64 -r313254 build based on running the -r313266 kernel. (The context sometimes do cross builds in is tied up with other things. -r313266 is what my prior bisection came up with as the last appearently-working kernel at the time.) So it will be a while before I have a -r313254 in place to try: the self-hosted build takes longer and so will not be installed for a while. To judge stability I'll probably have -e313254 build the patched update that you want me to test, initially doing a cleanworld. So that too will take a while. (The above wording presumes all goes well.) I'll let you know as I go along if I run into anything interesting. My builds are rebuilding both world and kernel since what turns into /usr/include/sys/* has changes in your patch. The builds are without MALLOC_PRODUCTION but are otherwise not debug builds. I've not seen anything indicating that anyone has been trying TARGET_ARCH=powerpc. I've been trying TARGET_ARCH=powerpc64 . While I do not have access to a true TARGET_ARCH=powerpc machine currently, such a build can be used on a PowerMac G5 so-called "Quad Core". So I could eventually build and try such on the one powerpc family machine that I currently have access to. clang 3.9.1 has a significant code generation problem for TARGET_ARCH=powerpc and so I'd have to use a gcc 4.2.1 based build for that sort of experiment. (There is no xtoolchain for 32-bit powerpc.) I use clang 3.9.1 or xtoolchain for TARGET_ARCH=powerpc64 and have been using clang 3.9.1 in recent times. My primary powerpc family use has been to experiment with building based on the modern libc++ and reporting issues discovered in the attempts. This explains the clang/xtoolchain context. clang 3.9.1 has major problems for C++ exception handling for both powerpc64 and powerpc but a lot of FreeBSD is independent of throwing C++ exceptions. By contrast xtoolchain-based works for C++ exception handling but lib32 fails to operate when built by a xtoolchain build. === Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Feb 25 07:46:09 2017 Return-Path: Delivered-To: freebsd-ppc@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 A1832CEC97B for ; Sat, 25 Feb 2017 07:46:09 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-88.reflexion.net [208.70.210.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 623561932 for ; Sat, 25 Feb 2017 07:46:08 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 31791 invoked from network); 25 Feb 2017 07:46:07 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 25 Feb 2017 07:46:07 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Sat, 25 Feb 2017 02:46:07 -0500 (EST) Received: (qmail 8602 invoked from network); 25 Feb 2017 07:46:07 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 25 Feb 2017 07:46:07 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 3155AEC86E2; Fri, 24 Feb 2017 23:46:06 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> Date: Fri, 24 Feb 2017 23:46:05 -0800 Cc: Justin Hibbits , mjg@freebsd.org, FreeBSD Current , svn-src-head@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: 7bit Message-Id: References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> <20170225002300.GC19697@dft-labs.eu> <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 07:46:09 -0000 On 2017-Feb-24, at 8:25 PM, Mark Millard wrote: > On 2017-Feb-24, at 4:23 PM, Mateusz Guzik wrote: >> >> On Tue, Feb 21, 2017 at 01:37:25AM -0800, Mark Millard wrote: >>> [Back to the powerpc64 context.] >>> >>> On 2017-Feb-20, at 11:10 AM, Mateusz Guzik wrote: >>> >>>> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: >>>>> [Note: I experiment with clang based powerpc64 builds, >>>>> reporting problems that I find. Justin is familiar >>>>> with this, as is Nathan.] >>>>> >>>>> I tried to update the PowerMac G5 (a so-called "Quad Core") >>>>> that I have access to from head -r312761 to -r313864 and >>>>> ended up with random panics and hang ups in fairly short >>>>> order after booting. >>>>> >>>>> Some approximate bisecting for the kernel lead to: >>>>> (sometimes getting part way into a buildkernel attempt >>>>> for a different version before a failure happens) >>>>> >>>>> -r313266: works (just before use of atomic_fcmpset) >>>>> vs. >>>>> -r313271: fails (last of the "use atomic_fcmpset" check-ins) >>>>> >>>>> (I did not try -r313268 through -r313270 as the use was >>>>> gradually added.) >>>>> >>>>> So I'm currently running a -r313864 world with a -r313266 >>>>> kernel. >>>>> >>>>> No kernel that I tried that was from before -r313266 had the >>>>> problems. >>>>> >>>>> Any kernel that I tried that was from after -r313271 had the >>>>> problems. >>>>> >>>>> Of course I did not try them all in other direction. :) >>>>> >>>> >>>> I found that spin mutexes were not properly handling this, fixed in >>>> r313996. >>>> >>>> Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64 >>>> fcmpset to simulate failures. Everything works, while it would easily >>>> fail without the patch. >>>> >>>> That said, I hope this concludes the 'missing check for not-reread value >>>> of failed fcmpset' saga. >>>> >>>> -- >>>> Mateusz Guzik >>> >>> -r313999 is an improvement for powerpc64: it boots and I can >>> log in on the old PowerMac G5 so-called "Quad Core". >>> >>> But, e.g., buildworld buildkernel eventually hangs and later >>> the powerpc64 panics for "spin lock held too long". >>> >> >> Allright, play time is over. >> >> Can you please: >> 1. verify r313254 is stable for you >> 2. apply https://people.freebsd.org/~mjg/patches/complete-locks.diff and >> https://people.freebsd.org/~mjg/.junk/ppc.diff on top of it and retry >> the test? >> >> This is a workaround which effectively disables the powerpc-specific >> primitive and makes it use a cmpset wrapper instead. I don't have the >> hardware to test right now and my attempts to boot in qemu also failed. >> >> That said, does not look like there are general fcmpset bugs left and >> the remaining issue seems powerpc-specific. >> >> If this works, I'll commit the workaround for the time being as in few >> weeks I'd like to start merging the work back to stable/11. >> >> -- >> Mateusz Guzik > > I've started a self-hosted powerpc64 -r313254 build > based on running the -r313266 kernel. (The context > sometimes do cross builds in is tied up with other > things. -r313266 is what my prior bisection came up > with as the last appearently-working kernel at the > time.) > > So it will be a while before I have a -r313254 in > place to try: the self-hosted build takes longer > and so will not be installed for a while. > > To judge stability I'll probably have -e313254 build > the patched update that you want me to test, initially > doing a cleanworld. So that too will take a while. > > (The above wording presumes all goes well.) > > I'll let you know as I go along if I run into anything > interesting. > > > My builds are rebuilding both world and kernel since > what turns into /usr/include/sys/* has changes in your > patch. > > The builds are without MALLOC_PRODUCTION but are > otherwise not debug builds. > > > I've not seen anything indicating that anyone has > been trying TARGET_ARCH=powerpc. I've been trying > TARGET_ARCH=powerpc64 . > > While I do not have access to a true > TARGET_ARCH=powerpc machine currently, such a build > can be used on a PowerMac G5 so-called "Quad Core". > So I could eventually build and try such on the one > powerpc family machine that I currently have access > to. > > clang 3.9.1 has a significant code generation problem > for TARGET_ARCH=powerpc and so I'd have to use > a gcc 4.2.1 based build for that sort of experiment. > (There is no xtoolchain for 32-bit powerpc.) > > I use clang 3.9.1 or xtoolchain for > TARGET_ARCH=powerpc64 and have been using clang 3.9.1 > in recent times. My primary powerpc family use has > been to experiment with building based on the > modern libc++ and reporting issues discovered in the > attempts. This explains the clang/xtoolchain context. > > clang 3.9.1 has major problems for C++ exception > handling for both powerpc64 and powerpc but a > lot of FreeBSD is independent of throwing C++ > exceptions. By contrast xtoolchain-based works > for C++ exception handling but lib32 fails > to operate when built by a xtoolchain build. -r313254 had no trouble booting or building the patched version or anything else involved in getting there or installing. But the patched version failed quickly just attempting cleanworld's recursive remove. (So it did boot and let me log in.) The panic description was: panic: vn_finished_secondary_write: neg cnt The sources that are different from svn's -r313254 are (some tied to arm64 experiments, most everything else tied to powerpc64 and/or powerpc, those not from your patches are long standing from my investigations or from Justin H.): # svnlite status /usr/src | sort . . . (ignoring the ? lines) . . . M /usr/src/bin/sh/jobs.c M /usr/src/bin/sh/miscbltin.c M /usr/src/contrib/llvm/lib/Target/PowerPC/PPCInstrInfo.td M /usr/src/contrib/llvm/tools/lld/ELF/Target.cpp M /usr/src/lib/csu/powerpc64/Makefile M /usr/src/libexec/rtld-elf/Makefile M /usr/src/sys/arm/arm/gic.c M /usr/src/sys/boot/ofw/Makefile.inc M /usr/src/sys/boot/powerpc/Makefile.inc M /usr/src/sys/boot/powerpc/kboot/Makefile M /usr/src/sys/boot/uboot/Makefile.inc M /usr/src/sys/conf/kmod.mk M /usr/src/sys/ddb/db_main.c M /usr/src/sys/ddb/db_script.c M /usr/src/sys/kern/init_main.c M /usr/src/sys/kern/kern_condvar.c M /usr/src/sys/kern/kern_lock.c M /usr/src/sys/kern/kern_lockstat.c M /usr/src/sys/kern/kern_mutex.c M /usr/src/sys/kern/kern_rwlock.c M /usr/src/sys/kern/kern_sx.c M /usr/src/sys/kern/kern_synch.c M /usr/src/sys/kern/kern_thread.c M /usr/src/sys/kern/subr_lock.c M /usr/src/sys/kern/vfs_default.c M /usr/src/sys/kern/vfs_subr.c M /usr/src/sys/powerpc/include/atomic.h M /usr/src/sys/powerpc/ofw/ofw_machdep.c M /usr/src/sys/sys/lock.h M /usr/src/sys/sys/lockmgr.h M /usr/src/sys/sys/lockstat.h M /usr/src/sys/sys/mutex.h M /usr/src/sys/sys/rwlock.h M /usr/src/sys/sys/sdt.h M /usr/src/sys/sys/sx.h M /usr/src/sys/sys/systm.h === Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Feb 25 09:06:03 2017 Return-Path: Delivered-To: freebsd-ppc@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 9BD85CEA701 for ; Sat, 25 Feb 2017 09:06:03 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-85.reflexion.net [208.70.210.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5B93985D for ; Sat, 25 Feb 2017 09:06:02 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29566 invoked from network); 25 Feb 2017 09:06:43 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 25 Feb 2017 09:06:43 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Sat, 25 Feb 2017 04:06:01 -0500 (EST) Received: (qmail 22712 invoked from network); 25 Feb 2017 09:06:01 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 25 Feb 2017 09:06:01 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 66939EC86E2; Sat, 25 Feb 2017 01:06:00 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: Date: Sat, 25 Feb 2017 01:05:59 -0800 Cc: Justin Hibbits , mjg@freebsd.org, FreeBSD Current , svn-src-head@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <477BA631-AB85-4E77-8BA3-CD2AFAD5E405@dsl-only.net> References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> <20170225002300.GC19697@dft-labs.eu> <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 09:06:03 -0000 On 2017-Feb-24, at 11:46 PM, Mark Millard = wrote: > On 2017-Feb-24, at 8:25 PM, Mark Millard = wrote: >=20 >> On 2017-Feb-24, at 4:23 PM, Mateusz Guzik = wrote: >>>=20 >>> On Tue, Feb 21, 2017 at 01:37:25AM -0800, Mark Millard wrote: >>>> [Back to the powerpc64 context.] >>>>=20 >>>> On 2017-Feb-20, at 11:10 AM, Mateusz Guzik = wrote: >>>>=20 >>>>> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: >>>>>> [Note: I experiment with clang based powerpc64 builds, >>>>>> reporting problems that I find. Justin is familiar >>>>>> with this, as is Nathan.] >>>>>>=20 >>>>>> I tried to update the PowerMac G5 (a so-called "Quad Core") >>>>>> that I have access to from head -r312761 to -r313864 and >>>>>> ended up with random panics and hang ups in fairly short >>>>>> order after booting. >>>>>>=20 >>>>>> Some approximate bisecting for the kernel lead to: >>>>>> (sometimes getting part way into a buildkernel attempt >>>>>> for a different version before a failure happens) >>>>>>=20 >>>>>> -r313266: works (just before use of atomic_fcmpset) >>>>>> vs. >>>>>> -r313271: fails (last of the "use atomic_fcmpset" check-ins) >>>>>>=20 >>>>>> (I did not try -r313268 through -r313270 as the use was >>>>>> gradually added.) >>>>>>=20 >>>>>> So I'm currently running a -r313864 world with a -r313266 >>>>>> kernel. >>>>>>=20 >>>>>> No kernel that I tried that was from before -r313266 had the >>>>>> problems. >>>>>>=20 >>>>>> Any kernel that I tried that was from after -r313271 had the >>>>>> problems. >>>>>>=20 >>>>>> Of course I did not try them all in other direction. :) >>>>>>=20 >>>>>=20 >>>>> I found that spin mutexes were not properly handling this, fixed = in >>>>> r313996. >>>>>=20 >>>>> Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64 >>>>> fcmpset to simulate failures. Everything works, while it would = easily >>>>> fail without the patch. >>>>>=20 >>>>> That said, I hope this concludes the 'missing check for not-reread = value >>>>> of failed fcmpset' saga. >>>>>=20 >>>>> --=20 >>>>> Mateusz Guzik >>>>=20 >>>> -r313999 is an improvement for powerpc64: it boots and I can >>>> log in on the old PowerMac G5 so-called "Quad Core". >>>>=20 >>>> But, e.g., buildworld buildkernel eventually hangs and later >>>> the powerpc64 panics for "spin lock held too long". >>>>=20 >>>=20 >>> Allright, play time is over. >>>=20 >>> Can you please: >>> 1. verify r313254 is stable for you >>> 2. apply https://people.freebsd.org/~mjg/patches/complete-locks.diff = and >>> https://people.freebsd.org/~mjg/.junk/ppc.diff on top of it and = retry >>> the test? >>>=20 >>> This is a workaround which effectively disables the powerpc-specific >>> primitive and makes it use a cmpset wrapper instead. I don't have = the >>> hardware to test right now and my attempts to boot in qemu also = failed. >>>=20 >>> That said, does not look like there are general fcmpset bugs left = and >>> the remaining issue seems powerpc-specific. >>>=20 >>> If this works, I'll commit the workaround for the time being as in = few >>> weeks I'd like to start merging the work back to stable/11. >>>=20 >>> --=20 >>> Mateusz Guzik >>=20 >> I've started a self-hosted powerpc64 -r313254 build >> based on running the -r313266 kernel. (The context=20 >> sometimes do cross builds in is tied up with other >> things. -r313266 is what my prior bisection came up >> with as the last appearently-working kernel at the >> time.) >>=20 >> So it will be a while before I have a -r313254 in >> place to try: the self-hosted build takes longer >> and so will not be installed for a while. >>=20 >> To judge stability I'll probably have -e313254 build >> the patched update that you want me to test, initially >> doing a cleanworld. So that too will take a while. >>=20 >> (The above wording presumes all goes well.) >>=20 >> I'll let you know as I go along if I run into anything >> interesting. >>=20 >>=20 >> My builds are rebuilding both world and kernel since >> what turns into /usr/include/sys/* has changes in your >> patch. >>=20 >> The builds are without MALLOC_PRODUCTION but are >> otherwise not debug builds. >>=20 >>=20 >> I've not seen anything indicating that anyone has >> been trying TARGET_ARCH=3Dpowerpc. I've been trying >> TARGET_ARCH=3Dpowerpc64 . >>=20 >> While I do not have access to a true >> TARGET_ARCH=3Dpowerpc machine currently, such a build >> can be used on a PowerMac G5 so-called "Quad Core". >> So I could eventually build and try such on the one >> powerpc family machine that I currently have access >> to. >>=20 >> clang 3.9.1 has a significant code generation problem >> for TARGET_ARCH=3Dpowerpc and so I'd have to use >> a gcc 4.2.1 based build for that sort of experiment. >> (There is no xtoolchain for 32-bit powerpc.) >>=20 >> I use clang 3.9.1 or xtoolchain for >> TARGET_ARCH=3Dpowerpc64 and have been using clang 3.9.1 >> in recent times. My primary powerpc family use has >> been to experiment with building based on the >> modern libc++ and reporting issues discovered in the >> attempts. This explains the clang/xtoolchain context. >>=20 >> clang 3.9.1 has major problems for C++ exception >> handling for both powerpc64 and powerpc but a >> lot of FreeBSD is independent of throwing C++ >> exceptions. By contrast xtoolchain-based works >> for C++ exception handling but lib32 fails >> to operate when built by a xtoolchain build. >=20 > -r313254 had no trouble booting or building > the patched version or anything else involved > in getting there or installing. >=20 > But the patched version failed quickly just > attempting cleanworld's recursive remove. (So > it did boot and let me log in.) The panic > description was: >=20 > panic: vn_finished_secondary_write: neg cnt >=20 >=20 > The sources that are different from svn's -r313254 > are (some tied to arm64 experiments, most everything > else tied to powerpc64 and/or powerpc, those not > from your patches are long standing from my > investigations or from Justin H.): >=20 > # svnlite status /usr/src | sort > . . . (ignoring the ? lines) . . . > M /usr/src/bin/sh/jobs.c > M /usr/src/bin/sh/miscbltin.c > M /usr/src/contrib/llvm/lib/Target/PowerPC/PPCInstrInfo.td > M /usr/src/contrib/llvm/tools/lld/ELF/Target.cpp > M /usr/src/lib/csu/powerpc64/Makefile > M /usr/src/libexec/rtld-elf/Makefile > M /usr/src/sys/arm/arm/gic.c > M /usr/src/sys/boot/ofw/Makefile.inc > M /usr/src/sys/boot/powerpc/Makefile.inc > M /usr/src/sys/boot/powerpc/kboot/Makefile > M /usr/src/sys/boot/uboot/Makefile.inc > M /usr/src/sys/conf/kmod.mk > M /usr/src/sys/ddb/db_main.c > M /usr/src/sys/ddb/db_script.c > M /usr/src/sys/kern/init_main.c > M /usr/src/sys/kern/kern_condvar.c > M /usr/src/sys/kern/kern_lock.c > M /usr/src/sys/kern/kern_lockstat.c > M /usr/src/sys/kern/kern_mutex.c > M /usr/src/sys/kern/kern_rwlock.c > M /usr/src/sys/kern/kern_sx.c > M /usr/src/sys/kern/kern_synch.c > M /usr/src/sys/kern/kern_thread.c > M /usr/src/sys/kern/subr_lock.c > M /usr/src/sys/kern/vfs_default.c > M /usr/src/sys/kern/vfs_subr.c > M /usr/src/sys/powerpc/include/atomic.h > M /usr/src/sys/powerpc/ofw/ofw_machdep.c > M /usr/src/sys/sys/lock.h > M /usr/src/sys/sys/lockmgr.h > M /usr/src/sys/sys/lockstat.h > M /usr/src/sys/sys/mutex.h > M /usr/src/sys/sys/rwlock.h > M /usr/src/sys/sys/sdt.h > M /usr/src/sys/sys/sx.h > M /usr/src/sys/sys/systm.h To recover from the problem and again have a buildworld buildkernel present I've booted based on: A) The -r313254 kernel without your patches (kernel.old). B) The -r313254 world (which had your patches in its build). I've reverted the /usr/src/ to not have your patches (but does have my prior ones from prior activity). I repeated the cleanworld to let it finish after its prior failure (that failed during a SSD trim activity). I've started buildworld buildkernel (with -j 4 as is normal for my context). So far this combination seems to be working fine. This suggests that the sys/sys/*.h files that ended up in /usr/include/sys/ and the sys/powerpc/include/atomic.h that ended up in /usr/include/machine/ were not problems as used in the world code --since those uses are still in place in the binaries being used. Only the kernel binaries seem to be a problem (not necessarily all of them). =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Feb 25 13:49:45 2017 Return-Path: Delivered-To: freebsd-ppc@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 0D18CCEC957 for ; Sat, 25 Feb 2017 13:49:45 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-85.reflexion.net [208.70.210.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C116BC32 for ; Sat, 25 Feb 2017 13:49:43 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 10081 invoked from network); 25 Feb 2017 13:51:53 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 25 Feb 2017 13:51:53 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Sat, 25 Feb 2017 08:49:42 -0500 (EST) Received: (qmail 26312 invoked from network); 25 Feb 2017 13:49:42 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 25 Feb 2017 13:49:42 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 425EAEC86E2; Sat, 25 Feb 2017 05:49:41 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <477BA631-AB85-4E77-8BA3-CD2AFAD5E405@dsl-only.net> Date: Sat, 25 Feb 2017 05:49:40 -0800 Cc: svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> <20170225002300.GC19697@dft-labs.eu> <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> <477BA631-AB85-4E77-8BA3-CD2AFAD5E405@dsl-only.net> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 13:49:45 -0000 On 2017-Feb-25, at 1:05 AM, Mark Millard wrote: > On 2017-Feb-24, at 11:46 PM, Mark Millard = wrote: >=20 >> On 2017-Feb-24, at 8:25 PM, Mark Millard = wrote: >>=20 >>> On 2017-Feb-24, at 4:23 PM, Mateusz Guzik = wrote: >>>>=20 >>>> On Tue, Feb 21, 2017 at 01:37:25AM -0800, Mark Millard wrote: >>>>> [Back to the powerpc64 context.] >>>>>=20 >>>>> On 2017-Feb-20, at 11:10 AM, Mateusz Guzik = wrote: >>>>>=20 >>>>>> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: >>>>>>> [Note: I experiment with clang based powerpc64 builds, >>>>>>> reporting problems that I find. Justin is familiar >>>>>>> with this, as is Nathan.] >>>>>>>=20 >>>>>>> I tried to update the PowerMac G5 (a so-called "Quad Core") >>>>>>> that I have access to from head -r312761 to -r313864 and >>>>>>> ended up with random panics and hang ups in fairly short >>>>>>> order after booting. >>>>>>>=20 >>>>>>> Some approximate bisecting for the kernel lead to: >>>>>>> (sometimes getting part way into a buildkernel attempt >>>>>>> for a different version before a failure happens) >>>>>>>=20 >>>>>>> -r313266: works (just before use of atomic_fcmpset) >>>>>>> vs. >>>>>>> -r313271: fails (last of the "use atomic_fcmpset" check-ins) >>>>>>>=20 >>>>>>> (I did not try -r313268 through -r313270 as the use was >>>>>>> gradually added.) >>>>>>>=20 >>>>>>> So I'm currently running a -r313864 world with a -r313266 >>>>>>> kernel. >>>>>>>=20 >>>>>>> No kernel that I tried that was from before -r313266 had the >>>>>>> problems. >>>>>>>=20 >>>>>>> Any kernel that I tried that was from after -r313271 had the >>>>>>> problems. >>>>>>>=20 >>>>>>> Of course I did not try them all in other direction. :) >>>>>>>=20 >>>>>>=20 >>>>>> I found that spin mutexes were not properly handling this, fixed = in >>>>>> r313996. >>>>>>=20 >>>>>> Locally I added a if (cpu_tick() % 2) return (0); snipped to = amd64 >>>>>> fcmpset to simulate failures. Everything works, while it would = easily >>>>>> fail without the patch. >>>>>>=20 >>>>>> That said, I hope this concludes the 'missing check for = not-reread value >>>>>> of failed fcmpset' saga. >>>>>>=20 >>>>>> --=20 >>>>>> Mateusz Guzik >>>>>=20 >>>>> -r313999 is an improvement for powerpc64: it boots and I can >>>>> log in on the old PowerMac G5 so-called "Quad Core". >>>>>=20 >>>>> But, e.g., buildworld buildkernel eventually hangs and later >>>>> the powerpc64 panics for "spin lock held too long". >>>>>=20 >>>>=20 >>>> Allright, play time is over. >>>>=20 >>>> Can you please: >>>> 1. verify r313254 is stable for you >>>> 2. apply = https://people.freebsd.org/~mjg/patches/complete-locks.diff and >>>> https://people.freebsd.org/~mjg/.junk/ppc.diff on top of it and = retry >>>> the test? >>>>=20 >>>> This is a workaround which effectively disables the = powerpc-specific >>>> primitive and makes it use a cmpset wrapper instead. I don't have = the >>>> hardware to test right now and my attempts to boot in qemu also = failed. >>>>=20 >>>> That said, does not look like there are general fcmpset bugs left = and >>>> the remaining issue seems powerpc-specific. >>>>=20 >>>> If this works, I'll commit the workaround for the time being as in = few >>>> weeks I'd like to start merging the work back to stable/11. >>>>=20 >>>> --=20 >>>> Mateusz Guzik >>>=20 >>> I've started a self-hosted powerpc64 -r313254 build >>> based on running the -r313266 kernel. (The context=20 >>> sometimes do cross builds in is tied up with other >>> things. -r313266 is what my prior bisection came up >>> with as the last appearently-working kernel at the >>> time.) >>>=20 >>> So it will be a while before I have a -r313254 in >>> place to try: the self-hosted build takes longer >>> and so will not be installed for a while. >>>=20 >>> To judge stability I'll probably have -e313254 build >>> the patched update that you want me to test, initially >>> doing a cleanworld. So that too will take a while. >>>=20 >>> (The above wording presumes all goes well.) >>>=20 >>> I'll let you know as I go along if I run into anything >>> interesting. >>>=20 >>>=20 >>> My builds are rebuilding both world and kernel since >>> what turns into /usr/include/sys/* has changes in your >>> patch. >>>=20 >>> The builds are without MALLOC_PRODUCTION but are >>> otherwise not debug builds. >>>=20 >>>=20 >>> I've not seen anything indicating that anyone has >>> been trying TARGET_ARCH=3Dpowerpc. I've been trying >>> TARGET_ARCH=3Dpowerpc64 . >>>=20 >>> While I do not have access to a true >>> TARGET_ARCH=3Dpowerpc machine currently, such a build >>> can be used on a PowerMac G5 so-called "Quad Core". >>> So I could eventually build and try such on the one >>> powerpc family machine that I currently have access >>> to. >>>=20 >>> clang 3.9.1 has a significant code generation problem >>> for TARGET_ARCH=3Dpowerpc and so I'd have to use >>> a gcc 4.2.1 based build for that sort of experiment. >>> (There is no xtoolchain for 32-bit powerpc.) >>>=20 >>> I use clang 3.9.1 or xtoolchain for >>> TARGET_ARCH=3Dpowerpc64 and have been using clang 3.9.1 >>> in recent times. My primary powerpc family use has >>> been to experiment with building based on the >>> modern libc++ and reporting issues discovered in the >>> attempts. This explains the clang/xtoolchain context. >>>=20 >>> clang 3.9.1 has major problems for C++ exception >>> handling for both powerpc64 and powerpc but a >>> lot of FreeBSD is independent of throwing C++ >>> exceptions. By contrast xtoolchain-based works >>> for C++ exception handling but lib32 fails >>> to operate when built by a xtoolchain build. >>=20 >> -r313254 had no trouble booting or building >> the patched version or anything else involved >> in getting there or installing. >>=20 >> But the patched version failed quickly just >> attempting cleanworld's recursive remove. (So >> it did boot and let me log in.) The panic >> description was: >>=20 >> panic: vn_finished_secondary_write: neg cnt >>=20 >>=20 >> The sources that are different from svn's -r313254 >> are (some tied to arm64 experiments, most everything >> else tied to powerpc64 and/or powerpc, those not >> from your patches are long standing from my >> investigations or from Justin H.): >>=20 >> # svnlite status /usr/src | sort >> . . . (ignoring the ? lines) . . . >> M /usr/src/bin/sh/jobs.c >> M /usr/src/bin/sh/miscbltin.c >> M /usr/src/contrib/llvm/lib/Target/PowerPC/PPCInstrInfo.td >> M /usr/src/contrib/llvm/tools/lld/ELF/Target.cpp >> M /usr/src/lib/csu/powerpc64/Makefile >> M /usr/src/libexec/rtld-elf/Makefile >> M /usr/src/sys/arm/arm/gic.c >> M /usr/src/sys/boot/ofw/Makefile.inc >> M /usr/src/sys/boot/powerpc/Makefile.inc >> M /usr/src/sys/boot/powerpc/kboot/Makefile >> M /usr/src/sys/boot/uboot/Makefile.inc >> M /usr/src/sys/conf/kmod.mk >> M /usr/src/sys/ddb/db_main.c >> M /usr/src/sys/ddb/db_script.c >> M /usr/src/sys/kern/init_main.c >> M /usr/src/sys/kern/kern_condvar.c >> M /usr/src/sys/kern/kern_lock.c >> M /usr/src/sys/kern/kern_lockstat.c >> M /usr/src/sys/kern/kern_mutex.c >> M /usr/src/sys/kern/kern_rwlock.c >> M /usr/src/sys/kern/kern_sx.c >> M /usr/src/sys/kern/kern_synch.c >> M /usr/src/sys/kern/kern_thread.c >> M /usr/src/sys/kern/subr_lock.c >> M /usr/src/sys/kern/vfs_default.c >> M /usr/src/sys/kern/vfs_subr.c >> M /usr/src/sys/powerpc/include/atomic.h >> M /usr/src/sys/powerpc/ofw/ofw_machdep.c >> M /usr/src/sys/sys/lock.h >> M /usr/src/sys/sys/lockmgr.h >> M /usr/src/sys/sys/lockstat.h >> M /usr/src/sys/sys/mutex.h >> M /usr/src/sys/sys/rwlock.h >> M /usr/src/sys/sys/sdt.h >> M /usr/src/sys/sys/sx.h >> M /usr/src/sys/sys/systm.h >=20 > To recover from the problem and again have a buildworld > buildkernel present I've booted based on: >=20 > A) The -r313254 kernel without your patches (kernel.old). > B) The -r313254 world (which had your patches in its > build). >=20 > I've reverted the /usr/src/ to not have your patches > (but does have my prior ones from prior activity). >=20 > I repeated the cleanworld to let it finish after its > prior failure (that failed during a SSD trim activity). >=20 > I've started buildworld buildkernel (with -j 4 as is > normal for my context). >=20 > So far this combination seems to be working fine. This > suggests that the sys/sys/*.h files that ended up in > /usr/include/sys/ and the sys/powerpc/include/atomic.h > that ended up in /usr/include/machine/ were not problems > as used in the world code --since those uses are still in > place in the binaries being used. Only the kernel > binaries seem to be a problem (not necessarily all of > them). Unfortunately it eventually got a panic for a Data Storage Interrupt. I may not be unable to do a self hosted build to get things back to normal.=20 =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Feb 25 17:58:43 2017 Return-Path: Delivered-To: freebsd-ppc@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 2577FCED83B for ; Sat, 25 Feb 2017 17:58:43 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-94.reflexion.net [208.70.210.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D77F7EFF for ; Sat, 25 Feb 2017 17:58:42 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 5334 invoked from network); 25 Feb 2017 18:00:51 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 25 Feb 2017 18:00:51 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Sat, 25 Feb 2017 12:58:40 -0500 (EST) Received: (qmail 27737 invoked from network); 25 Feb 2017 17:58:40 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 25 Feb 2017 17:58:40 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id DD2FAEC8534; Sat, 25 Feb 2017 09:58:39 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: Date: Sat, 25 Feb 2017 09:58:39 -0800 Cc: svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <9A63B36E-5F81-4ECD-A2A2-AB442AAC26A6@dsl-only.net> References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> <20170225002300.GC19697@dft-labs.eu> <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> <477BA631-AB85-4E77-8BA3-CD2AFAD5E405@dsl-only.net> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 17:58:43 -0000 On 2017-Feb-25, at 5:49 AM, Mark Millard wrote: > On 2017-Feb-25, at 1:05 AM, Mark Millard wrote: >=20 >> On 2017-Feb-24, at 11:46 PM, Mark Millard = wrote: >>=20 >>> On 2017-Feb-24, at 8:25 PM, Mark Millard = wrote: >>>=20 >>>> On 2017-Feb-24, at 4:23 PM, Mateusz Guzik = wrote: >>>>>=20 >>>>> On Tue, Feb 21, 2017 at 01:37:25AM -0800, Mark Millard wrote: >>>>>> [Back to the powerpc64 context.] >>>>>>=20 >>>>>> On 2017-Feb-20, at 11:10 AM, Mateusz Guzik = wrote: >>>>>>=20 >>>>>>> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote: >>>>>>>> [Note: I experiment with clang based powerpc64 builds, >>>>>>>> reporting problems that I find. Justin is familiar >>>>>>>> with this, as is Nathan.] >>>>>>>>=20 >>>>>>>> I tried to update the PowerMac G5 (a so-called "Quad Core") >>>>>>>> that I have access to from head -r312761 to -r313864 and >>>>>>>> ended up with random panics and hang ups in fairly short >>>>>>>> order after booting. >>>>>>>>=20 >>>>>>>> Some approximate bisecting for the kernel lead to: >>>>>>>> (sometimes getting part way into a buildkernel attempt >>>>>>>> for a different version before a failure happens) >>>>>>>>=20 >>>>>>>> -r313266: works (just before use of atomic_fcmpset) >>>>>>>> vs. >>>>>>>> -r313271: fails (last of the "use atomic_fcmpset" check-ins) >>>>>>>>=20 >>>>>>>> (I did not try -r313268 through -r313270 as the use was >>>>>>>> gradually added.) >>>>>>>>=20 >>>>>>>> So I'm currently running a -r313864 world with a -r313266 >>>>>>>> kernel. >>>>>>>>=20 >>>>>>>> No kernel that I tried that was from before -r313266 had the >>>>>>>> problems. >>>>>>>>=20 >>>>>>>> Any kernel that I tried that was from after -r313271 had the >>>>>>>> problems. >>>>>>>>=20 >>>>>>>> Of course I did not try them all in other direction. :) >>>>>>>>=20 >>>>>>>=20 >>>>>>> I found that spin mutexes were not properly handling this, fixed = in >>>>>>> r313996. >>>>>>>=20 >>>>>>> Locally I added a if (cpu_tick() % 2) return (0); snipped to = amd64 >>>>>>> fcmpset to simulate failures. Everything works, while it would = easily >>>>>>> fail without the patch. >>>>>>>=20 >>>>>>> That said, I hope this concludes the 'missing check for = not-reread value >>>>>>> of failed fcmpset' saga. >>>>>>>=20 >>>>>>> --=20 >>>>>>> Mateusz Guzik >>>>>>=20 >>>>>> -r313999 is an improvement for powerpc64: it boots and I can >>>>>> log in on the old PowerMac G5 so-called "Quad Core". >>>>>>=20 >>>>>> But, e.g., buildworld buildkernel eventually hangs and later >>>>>> the powerpc64 panics for "spin lock held too long". >>>>>>=20 >>>>>=20 >>>>> Allright, play time is over. >>>>>=20 >>>>> Can you please: >>>>> 1. verify r313254 is stable for you >>>>> 2. apply = https://people.freebsd.org/~mjg/patches/complete-locks.diff and >>>>> https://people.freebsd.org/~mjg/.junk/ppc.diff on top of it and = retry >>>>> the test? >>>>>=20 >>>>> This is a workaround which effectively disables the = powerpc-specific >>>>> primitive and makes it use a cmpset wrapper instead. I don't have = the >>>>> hardware to test right now and my attempts to boot in qemu also = failed. >>>>>=20 >>>>> That said, does not look like there are general fcmpset bugs left = and >>>>> the remaining issue seems powerpc-specific. >>>>>=20 >>>>> If this works, I'll commit the workaround for the time being as in = few >>>>> weeks I'd like to start merging the work back to stable/11. >>>>>=20 >>>>> --=20 >>>>> Mateusz Guzik >>>>=20 >>>> I've started a self-hosted powerpc64 -r313254 build >>>> based on running the -r313266 kernel. (The context=20 >>>> sometimes do cross builds in is tied up with other >>>> things. -r313266 is what my prior bisection came up >>>> with as the last appearently-working kernel at the >>>> time.) >>>>=20 >>>> So it will be a while before I have a -r313254 in >>>> place to try: the self-hosted build takes longer >>>> and so will not be installed for a while. >>>>=20 >>>> To judge stability I'll probably have -e313254 build >>>> the patched update that you want me to test, initially >>>> doing a cleanworld. So that too will take a while. >>>>=20 >>>> (The above wording presumes all goes well.) >>>>=20 >>>> I'll let you know as I go along if I run into anything >>>> interesting. >>>>=20 >>>>=20 >>>> My builds are rebuilding both world and kernel since >>>> what turns into /usr/include/sys/* has changes in your >>>> patch. >>>>=20 >>>> The builds are without MALLOC_PRODUCTION but are >>>> otherwise not debug builds. >>>>=20 >>>>=20 >>>> I've not seen anything indicating that anyone has >>>> been trying TARGET_ARCH=3Dpowerpc. I've been trying >>>> TARGET_ARCH=3Dpowerpc64 . >>>>=20 >>>> While I do not have access to a true >>>> TARGET_ARCH=3Dpowerpc machine currently, such a build >>>> can be used on a PowerMac G5 so-called "Quad Core". >>>> So I could eventually build and try such on the one >>>> powerpc family machine that I currently have access >>>> to. >>>>=20 >>>> clang 3.9.1 has a significant code generation problem >>>> for TARGET_ARCH=3Dpowerpc and so I'd have to use >>>> a gcc 4.2.1 based build for that sort of experiment. >>>> (There is no xtoolchain for 32-bit powerpc.) >>>>=20 >>>> I use clang 3.9.1 or xtoolchain for >>>> TARGET_ARCH=3Dpowerpc64 and have been using clang 3.9.1 >>>> in recent times. My primary powerpc family use has >>>> been to experiment with building based on the >>>> modern libc++ and reporting issues discovered in the >>>> attempts. This explains the clang/xtoolchain context. >>>>=20 >>>> clang 3.9.1 has major problems for C++ exception >>>> handling for both powerpc64 and powerpc but a >>>> lot of FreeBSD is independent of throwing C++ >>>> exceptions. By contrast xtoolchain-based works >>>> for C++ exception handling but lib32 fails >>>> to operate when built by a xtoolchain build. >>>=20 >>> -r313254 had no trouble booting or building >>> the patched version or anything else involved >>> in getting there or installing. >>>=20 >>> But the patched version failed quickly just >>> attempting cleanworld's recursive remove. (So >>> it did boot and let me log in.) The panic >>> description was: >>>=20 >>> panic: vn_finished_secondary_write: neg cnt >>>=20 >>>=20 >>> The sources that are different from svn's -r313254 >>> are (some tied to arm64 experiments, most everything >>> else tied to powerpc64 and/or powerpc, those not >>> from your patches are long standing from my >>> investigations or from Justin H.): >>>=20 >>> # svnlite status /usr/src | sort >>> . . . (ignoring the ? lines) . . . >>> M /usr/src/bin/sh/jobs.c >>> M /usr/src/bin/sh/miscbltin.c >>> M /usr/src/contrib/llvm/lib/Target/PowerPC/PPCInstrInfo.td >>> M /usr/src/contrib/llvm/tools/lld/ELF/Target.cpp >>> M /usr/src/lib/csu/powerpc64/Makefile >>> M /usr/src/libexec/rtld-elf/Makefile >>> M /usr/src/sys/arm/arm/gic.c >>> M /usr/src/sys/boot/ofw/Makefile.inc >>> M /usr/src/sys/boot/powerpc/Makefile.inc >>> M /usr/src/sys/boot/powerpc/kboot/Makefile >>> M /usr/src/sys/boot/uboot/Makefile.inc >>> M /usr/src/sys/conf/kmod.mk >>> M /usr/src/sys/ddb/db_main.c >>> M /usr/src/sys/ddb/db_script.c >>> M /usr/src/sys/kern/init_main.c >>> M /usr/src/sys/kern/kern_condvar.c >>> M /usr/src/sys/kern/kern_lock.c >>> M /usr/src/sys/kern/kern_lockstat.c >>> M /usr/src/sys/kern/kern_mutex.c >>> M /usr/src/sys/kern/kern_rwlock.c >>> M /usr/src/sys/kern/kern_sx.c >>> M /usr/src/sys/kern/kern_synch.c >>> M /usr/src/sys/kern/kern_thread.c >>> M /usr/src/sys/kern/subr_lock.c >>> M /usr/src/sys/kern/vfs_default.c >>> M /usr/src/sys/kern/vfs_subr.c >>> M /usr/src/sys/powerpc/include/atomic.h >>> M /usr/src/sys/powerpc/ofw/ofw_machdep.c >>> M /usr/src/sys/sys/lock.h >>> M /usr/src/sys/sys/lockmgr.h >>> M /usr/src/sys/sys/lockstat.h >>> M /usr/src/sys/sys/mutex.h >>> M /usr/src/sys/sys/rwlock.h >>> M /usr/src/sys/sys/sdt.h >>> M /usr/src/sys/sys/sx.h >>> M /usr/src/sys/sys/systm.h >>=20 >> To recover from the problem and again have a buildworld >> buildkernel present I've booted based on: >>=20 >> A) The -r313254 kernel without your patches (kernel.old). >> B) The -r313254 world (which had your patches in its >> build). >>=20 >> I've reverted the /usr/src/ to not have your patches >> (but does have my prior ones from prior activity). >>=20 >> I repeated the cleanworld to let it finish after its >> prior failure (that failed during a SSD trim activity). >>=20 >> I've started buildworld buildkernel (with -j 4 as is >> normal for my context). >>=20 >> So far this combination seems to be working fine. This >> suggests that the sys/sys/*.h files that ended up in >> /usr/include/sys/ and the sys/powerpc/include/atomic.h >> that ended up in /usr/include/machine/ were not problems >> as used in the world code --since those uses are still in >> place in the binaries being used. Only the kernel >> binaries seem to be a problem (not necessarily all of >> them). >=20 > Unfortunately it eventually got a panic for a Data Storage > Interrupt. >=20 > I may not be unable to do a self hosted build to get things > back to normal.=20 I tried simply starting another buildworld buildkernel after booting and it did complete. Installing and rebooting worked fine. So apparently whatever was going on for the Data Storage Interrupt is fairly rare. Thus the PowerMac G5 so-called "Quad Core" is back to -r313254 without your patches. (The "Quad Core" really has two processors, each with 2 cores.) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Feb 25 19:31:14 2017 Return-Path: Delivered-To: freebsd-ppc@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 629A3CED7EC; Sat, 25 Feb 2017 19:31:14 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-pg0-x241.google.com (mail-pg0-x241.google.com [IPv6:2607:f8b0:400e:c05::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2B95A238; Sat, 25 Feb 2017 19:31:14 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-pg0-x241.google.com with SMTP id 5so7489055pgj.0; Sat, 25 Feb 2017 11:31:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=O/RD6/jdqar3/0DiPgm/Tub2w85Ph06+zCtOm2d6aAs=; b=Jea4TnSLNNaK+xA2au5Tp2rsZhJ8dMLkZzwED8Awg4GD2iaO+m4guhwcoyBQToX9wQ xGj8zXP5Uh1lndbnHjUTtkes9REg17NGKtv2eModugU3coocH8wPoQRAehCtKJxPIEfj xJS0cku9+/E1os+dEmcOjt3n97wlkcSlCPdhMOxcHP9H07tzVJP5lEnTkklytTlPBfaN lA5otf1gczd3EbvA6w+Tuedk9EFnGkMip79yX12rqk29zxgw0sScitZS6Aj69GySKVzt 6rssxikdNH7vwxcbkDwyZUkJyPRH3Ra9uX6lMCzQCk6mza3p0p8g5BGvGFrcI9esGZnX TePg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=O/RD6/jdqar3/0DiPgm/Tub2w85Ph06+zCtOm2d6aAs=; b=Za9T8IBlkSIo7LmXcrUaECXG5yF1qDBtmkpmtdCzlgpMUp6tfRFf/Q3xTQPzL38TVS zKPB853IhBz3u5DXUHlvgbbTLi6x1E+oXM6mX/s31ze0iXegmZ5rzGVtN0VQegcqgr+x dMQbkF9H2xP7XL5sGxJqKnmsxsaw98PMwIq3Oq3iIIW7WUkg7TB4Jp0PsrYFaKIWDB3+ yhkXmh96IwoBzV9RTslWzFP2eLyg5VyuMwz1f8A4QcUrHJP/Ybgdf8IORH1SBXaC9yO2 /j+AmTrjkpkPNbP39Q75iphb7Z2shAhtqbgdGVnzzIbFHGWi1UhXXRumLxZX40gv+nvX /wzg== X-Gm-Message-State: AMke39l8YYKXx6oZPjFzW7HDiOLUvY4VkktBL9zDoAYhCwxjZXA1SDuhKo0Ns4YGu9tDzA== X-Received: by 10.84.236.4 with SMTP id q4mr13181084plk.1.1488051073695; Sat, 25 Feb 2017 11:31:13 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by smtp.gmail.com with ESMTPSA id 4sm4708084pfr.124.2017.02.25.11.31.09 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Sat, 25 Feb 2017 11:31:13 -0800 (PST) Date: Sat, 25 Feb 2017 20:31:04 +0100 From: Mateusz Guzik To: Mark Millard Cc: svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] Message-ID: <20170225193103.GA4379@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Mark Millard , svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> <20170225002300.GC19697@dft-labs.eu> <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> <477BA631-AB85-4E77-8BA3-CD2AFAD5E405@dsl-only.net> <9A63B36E-5F81-4ECD-A2A2-AB442AAC26A6@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <9A63B36E-5F81-4ECD-A2A2-AB442AAC26A6@dsl-only.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Feb 2017 19:31:14 -0000 On Sat, Feb 25, 2017 at 09:58:39AM -0800, Mark Millard wrote: > Thus the PowerMac G5 so-called "Quad Core" is back to > -r313254 without your patches. (The "Quad Core" really has > two processors, each with 2 cores.) > Thanks a lot for testing. I'll have to think what to do with it, worst case I'll #ifdef changes with powerpc. -- Mateusz Guzik