From owner-freebsd-ppc@freebsd.org Tue Aug 2 21:08:01 2016 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 DD857BADC98 for ; Tue, 2 Aug 2016 21:08:01 +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 CD6761D38 for ; Tue, 2 Aug 2016 21:08:01 +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 u72L81mt042697 for ; Tue, 2 Aug 2016 21:08:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 211488] powerpc iso broken / does not burn correctly Date: Tue, 02 Aug 2016 21:08:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-BETA3 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Aug 2016 21:08:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211488 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-ppc@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Thu Aug 4 02:03:38 2016 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 A2C7DBAD4DE for ; Thu, 4 Aug 2016 02:03:38 +0000 (UTC) (envelope-from elena.ivanova@b2bresearchnow.com) Received: from smtp.b2bresearchnow.com (smtp.b2bresearchnow.com [202.0.103.38]) by mx1.freebsd.org (Postfix) with ESMTP id B430D1C5F for ; Thu, 4 Aug 2016 02:03:34 +0000 (UTC) (envelope-from elena.ivanova@b2bresearchnow.com) X-SmarterMail-Authenticated-As: admin@b2bresearchnow.com Received: from WIN-66SK44PGCK8 (WIN-66SK44PGCK8 [202.0.103.217]) by smtp.b2bresearchnow.com with SMTP; Wed, 3 Aug 2016 12:30:08 +0100 From: Elena Ivanova To: freebsd-ppc@freebsd.org Message-Id: <20160803123008.-310531959@b2bresearchnow.com> Subject: Automotive Vehicle to Everything (V2X) Communications Market 2016-2026 Date: Wed, 3 Aug 2016 12:30:08 +0100 MIME-Version: 1.0 Reply-To: elena.ivanova@b2bresearchnow.com Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2016 02:03:38 -0000 B2B ResearchNow Business Reports +44 (0)20 7549 0535 Automotive Vehicle to Everything (V2X) Communications Market 2016-2026 Vehicle to Vehicle (V2V), Vehicle to Infrastructure (V2I), Vehicle to Pedestrian (V2P), Vehicle to Home (V2H), In Vehicle (IN-V), (Embedded, Integrated, Tethered) By Service Provider (OEM, Aftermarket, Telematics, Connectivity) & Technologies: Sensors, Telematics Control Units (TCU), OBU, RSU, DSRC, LTE & GPS For Car-to-X, Connected Car & Intelligent Transportation Systems (ITS) Get Executive Summary Order Report Report Details We break down the most important sector of the automotive industry but also segment it by the key connectivity types, service providers, countries and companies and examine the characteristics that will allow them to lead the V2X market. Now: “NXP V2X Technology Looks To Make Self-Driving Cars A Reality”. This is an example of the business critical headline that you need to know about - and more importantly, you need to read visiongain’s objective analysis of how this will impact your company and the industry more broadly. How are you and your company reacting to this news? Are you sufficiently informed? In this brand new report you find 167 in-depth tables, charts and graphs, and trends – all unavailable elsewhere. The 188 page report provides clear detailed insight into the global V2X communication market. Discover the key drivers and challenges affecting the market. Report Scope • 167 tables, charts and graphs analysing the V2X market • Overview of the global V2X Communications market status in 2016: the Vehicle-to-Vehicle (V2V) and Vehicle-to-Infrastructure (V2I) Communications markets • Analysis of the technologies and applications for V2V, V2I, V2P, V2H, and IN-V communications • Overview of the role of DSRC, LTE, GPS and sensors in the V2X market • Analysis of the penetration of V2V and V2I in new passenger cars from 2016 to 2026 coupled with their drivers and restraints • Global Forecast of the global Vehicle-to-Everything (V2X) Market (in million cars equipped with V2X modules) and its 5 submarkets: - Global Forecast of the passenger cars equipped with V2V modules throughout 2016-2026 and analysis of drivers and restraints. Further segmentation forecast of the V2V Submarket into OEM and Aftermarket V2V Communications submarkets - Forecast of the revenues coming from DSRC-V2V modules for 2016-2026 - Global Forecast of cars equipped with V2I-modules (V2I-Connected Vehicles) for the period 2016-2026 - Global Forecast of DSRC-equipped smartphones which enable Vehicle-to-Pedestrians (V2P) communication - Global Forecast of cars connected with Vehicle-to-Home modules for 2016-2026 - Global Forecast of passenger cars connected with IN-V modules for 2016-2026. Further segmentation of the IN-V submarket into Type of Connectivity (Embedded, Integrated, Tethered) and by Service Provider (OEM, Aftermarket, Telematics, Connectivity) • Regional forecasts of the V2V, V2I, and IN-V Communications Submarket for 2016 to 2026, coupled with regional penetration level forecasts in further detail for the US, UK and japan. • SWOT analysis of the major strengths and weaknesses of the V2V and V2I markets, together with the opportunities available and the key threats faced • Expert opinion from a key-opinion leader in the market, QNX Software Systems • Profiles of 5 leading auto OEMs and 7 leading Tier-1s operating within the V2V-V2I market together with analysis of their role and products - BMW - Daimler - General Motors - Toyota - Volkswagen - Arada - Autotalks - Cohda - Delphi - Denso - eTrans - Kapsch - Qualcomm - Savari • Conclusions & recommendations How will you benefit from this report? • Keep your V2X knowledge base up to speed. Don’t get left behind • Reinforce your strategic decision-making with definitive and reliable V2X market data • Learn how to exploit new V2X Communications technological trends • Realise your company’s full potential within the V2X market • Understand the V2X competitive landscape and identify potential new business opportunities & partnerships Who should read this report? • Anyone within the automotive value chain. • Automotive Manufacturers (OEMs) • Aftermarket Companies for Connected Vehicles • Automotive Safety Systems Companies • Connectivity Solution Companies • Data Transfer & IT Companies • Telematics Solution Companies • Infotainment Companies • Diagnostics Companies • V2X Safety and Security Companies • Road Safety Authorities • Telecommunication Companies • Collision Research Institutes • CEO’s • COO’s • CIO’s • Business Development Managers • Marketing Managers • Technologists • Suppliers • Investors • Banks • Government Agencies • Contractors Visiongain’s study is intended for anyone requiring commercial analyses for the automotive V2X market and leading companies. You find data, trends and predictions. Automotive Vehicle to Everything (V2X) Communications Market 2016-2026 Table of Contents 1. Report Overview 1.1.V2X Communications Market 2016-2026: V2V, V2I, V2P, V2H, IN-V 1.2.V2X Market Segmentation Overview 1.3.Why You Should Read This Report 1.4.How This Report Delivers 1.5.Key Questions Answered by This Analytical Report 1.6.Who is This Report For? 1.7.Methodology 1.8.Frequently Asked Questions (FAQ) 1.9.Associated Visiongain Reports 1.10.About Visiongain 2. Introduction to the V2X Communications Market 2.1.Overview of the Global V2V-V2I Market Status in 2016 2.1.1.The NHTSA Aims to Mandate V2V in All New Cars 2.1.2.The European Commission Announces Europe’s New Connected Car Standards 2.1.3.OEMs & Tier-1s Showcase V2V and V2I Technology 2.2.The Vehicle-to-Everything (V2X) Communications Market 2.3.Learn Which Wireless Communication Technologies Enable V2X 2.3.1.Dedicated Short Range Communication (DSRC) for V2V and V2I 2.3.2.Cellular: LTE-4G for V2V-V2I Communication 2.3.3.GPS for V2V-V2I Communication 2.4.Sensors for V2V-V2I Communication 2.4.1.Overview of the Vehicle-to-Vehicle Applications 2.4.2.V2V Communications Market Segmentation Overview 2.4.2.1.V2V Communication by type 2.4.2.2.V2V Communication by Service Provider 2.5.Vehicle-to-Infrastructure (V2I) Communication 2.5.1.Overview of the V2I Applications 2.5.2.V2I Segmentation Overview 2.5.2.1.Vehicle-to-Grid Communication 2.5.2.2.Convenience Services 2.6.Vehicle-to-Pedestrians (V2P) Communication 2.7.Vehicle-to-Home (V2H) Communication 2.8.In-Vehicle (IN-V) Communication 2.9.Market Definition-The V2X & V2V-V2I Markets 2.10.V2X, V2V & V2I Market Segmentation Overview 3. Global V2X Communications Market Forecast 2016-2026 3.1.Global V2V Communication Market Forecast 2016-2026 3.1.1.Global V2V Market Segmentation Forecast 2016-2026: OEM vs. Aftermarket 3.1.1.1.Revenues from Aftermarket & OEM DSRC Modules 2016-2026 3.1.2.Global V2V Communications Market Status in 2016 3.1.2.1.Aftermarket vendors dominate the V2V Marketplace 3.1.2.2.OEMs showcase V2V pilot programmes with Daimler’s Car-to-X lose to production 3.1.2.3.Government testing, initiatives and the NHTSA mandate 3.1.3.Global V2V Penetration in New Car Sales Forecast 2016-2026 3.1.3.1.Learn Why V2V Penetration in New Car Sales is Low in 2016 3.1.3.1.1.Absence of OEM-based Solutions and Low Consumer Awareness Lead to Low Demand for V2V in 2016 3.1.3.1.2.DSRC-installation cost could disrupt sales 3.1.4.DSRC for Global V2V Communications 3.2.Global V2I Communications Market Forecast 2016-2026 3.2.1.Global V2I Penetration in New Car Sales Forecast 2016-2026 3.2.1.1.Learn What Are the Reasons for a Low V2I Penetration in 2016 and the potentials for growth in US and European Market 3.2.1.1.1.V2I penetration requires a substantial number of V2V-Connected Vehicles 3.2.1.1.2.RSU installation needs substantial investment in new infrastructure 3.2.2.Road Side Units (RSU) Installations Forecast 2016-2026 3.3.Global Vehicle-to-Pedestrians (V2P) Market Forecast 2016-2026 3.3.1.Revenues from DSRC-Enabled Smartphones Forecast 2016-2026 3.3.2.Smartphone Shipments Forecast 2016-2026 3.3.3.DSRC Penetration in New Smartphone Sales Forecast 2016-2026 3.3.4.Drivers & Restraints of the V2P Communications Submarket 3.4.Global V2H Communications Submarket Forecast 2016-2026 3.4.1.Global V2H Penetration in New Vehicle Sales Forecast 2016-2026 3.4.2.Drivers & Restraints of the V2H Communications Submarket 3.5.Global IN-V Communications Submarket Forecast 2016-2026 3.5.1.Revenues Forecast from Cars with IN-V Modules 2016-2026 3.5.2.IN-V Communications Submarket Segmentation Forecast 2016-26 3.5.2.1.IN-V Submarket Forecast 2016-26 by Type of Connectivity 3.5.2.1.1.Status of Embedded Solutions 3.5.2.1.2.Status of Integrated Solutions 3.5.2.1.3.Status of Tethered Solutions 3.5.2.2.IN-V Submarket Forecast 2015-25 by Service Provider 3.5.2.2.1.Status of OEM Hardware Solutions 3.5.2.2.2.Status of Aftermarket Hardware Solutions 3.5.2.2.3.Status of Telematics Hardware Solutions 3.5.2.2.4.Status of Connectivity Hardware Solutions 3.6.Global V2V Material, Commodity and Other Costs and the influence on Consumers’ Demand (modelling approach) 3.6.1.Cost components in Vehicle Manufacture per Category of costs 3.6.2.Cost Components for Each Country and Car Manufacturer Individually 3.7.Global V2V Communication and ADAS Systems 3.7.1.Most Innovative Car Manufacturers in Communication and ADAS Systems and the Number of Suppliers per region 3.8.Global V2X Forecasting for Premium and Volume Manufacturers 3.9.Global V2X Legal Framework Analysis 3.10.Ventures Capitals investing in the Connected Car industry 4.Regional V2X Market Forecast 2016-2026 4.1.Passenger Car Sales Data: Historical 2005-15 & Forecast 2016-26 4.1.1.Historical Regional Passenger Car Sales 2005-2015 4.1.2.Historical Regional Passenger Car Sales Market Shares 2005, 2010, 2015 4.1.3.Regional Passenger Car Sales Forecast 2016-2026 4.1.4.Regional Market Shares Forecast of Passenger Car Sales 2016, 2021, 2026 4.2.Regional V2V Communications Submarket Forecast 2016-2026 4.2.1.Regional V2V Market Share Forecast Summary 2016, 2021, 2026 4.2.2.How Different Motivations behind V2V Communications Will Lead to Different Regional Penetration of V2V 4.2.3.How Differences in Spectrum Allocation among Different Regions Affect the Global Standardization of V2V Communications 4.3.Regional V2I Communications Submarket Forecast 2016-2026 4.3.1.Regional V2I Market Share Forecast Summary 2016, 2021, 2026 4.4.Regional IN-V Connected Car Market Forecast 2016-2026 4.4.1.Regional IN-V Connected Car Market Share Forecast Summary 4.5.US V2V Equipment Cost in New and Old Car Forecast 2016-2026 4.5.1.V2V Data Transfer Cost for Consumers and Profit Margins for Communication Companies 4.6.V2V Market Forecast and Analysis for US Region 4.6.1.US V2V Forecasting In Three Scenarios 4.6.2.US V2X Forecasting for Premium and Volume Manufacturers 4.6.3.Model Approach for the Automotive and V2X Industry in USA Previous year’s car sales 4.7.Legal Framework Analysis for US and UK 4.7.1.US V2X Legal Framework and Standards 4.7.2.European V2X Legal Framework and Standards 4.8.UK V2V Forecasting in Different Levels of Automation 4.9.China V2X Forecasting for Premium and Volume Manufacturers 4.10.Japan V2X Forecasting for Premium and Volume Manufacturers 5. SWOT Analysis of the V2X Market 2016-2026 5.1. SWOT Analysis of the V2V Communications Market 2016-2026 5.2. SWOT Analysis of the V2I Communications Market 2016-2026 6. Expert Opinion 6.1. Expert Opinion – QNX Software Systems, Emil Dautovic, Business Development Manager, EMEA, at QNX 6.1.1 QNX’s Involvement in the Automotive Sector 6.1.2.QNX Opinions of Major Trends in Safety, Autonomous and Connected Cars 6.1.3.What Are QNX’s Views on on Sensor Fusion, Algorithms and R&D? 6.1.4.QNX’s Outlook on Prominent Applications in the Autonomous and Connected Cars 6.1.5.QNX Overview of V2X and Autonomous Driving 6.1.6.What is QNX’s Attitude to Infotainment and Safety? 6.1.7.QNX on Connectivity and Cyber Security 6.1.8.What is QNX’s Perspective on Challenges and Opportunities in Safety, Autonomous and Connected Cars 7.Leading Companies in the V2V & V2I Market 7.1.Leading OEMs in the V2V & V2I Market 7.1.1.BMW AG Company Overview 7.1.1.1.BMW’s Role in the V2V & V2I Market 7.1.2.Daimler AG Company Overview 7.1.2.1.Daimler’s Role in the V2V & V2I Market 7.1.3.General Motors (GM) Company Overview 7.1.3.1.GM’s Role in the V2V & V2I Market 7.1.4.Toyota Motor Company Overview 7.1.4.1.Toyota’s Role in the V2V & V2I Market 7.1.4.2.Toyota on the FCC’s Proposed Rulemaking To Open 5.9 GHz Band 7.1.5.Volkswagen Group AG Company Overview 7.1.5.1.VW’s Role in the V2V & V2I Market 7.2.Leading Suppliers, Tier-1s in the V2V & V2I Market 7.2.1.Arada Systems Company Overview 7.2.1.1.Arada Systems’ Role in the V2V & V2I Market 7.2.2.Autotalks Ltd. Company Overview 7.2.2.1.Autotalks’s Role in the V2V & V2I Market 7.2.3.Cohda Wireless Company Overview 7.2.3.1.Cohda Wireless Role in the V2V & V2I Market 7.2.3.2.Cohda Wireless Products in the V2V & V2I Market 7.2.4.Delphi Automotive PLC Company Overview 7.2.4.1.Delphi’s Role in the V2V & V2I Market 7.2.5.Denso Corporation Company Overview 7.2.5.1.Denso’s Role in the V2V & V2I Market 7.2.5.2.Denso’s Products in the V2V & V2X Market 7.2.6.eTrans Systems Company Overview 7.2.6.1.eTrans Systems’ Role in the V2V & V2I Market 7.2.6.1.1.Software Engineering 7.2.6.1.2.V2X Application Development 7.2.6.1.3.Cyber-Security 7.2.6.1.4.Testing & Simulation 7.2.6.1.5.Connected Vehicle Pilot Support 7.2.7.Kapsch TrafficCom Company Overview 7.2.7.1.Kapsch’s Role in the V2V & V2I Market 7.2.7.2.Kapsch’s Products in the V2V & V2X Market 7.2.7.3.Kapsch’s Acquisitions 7.2.8.Qualcomm Incorporated Company Overview 7.2.8.1.Qualcomm’s Role in the V2V & V2I Market 7.2.8.2.Qualcomm’s Products in the V2V & V2X Market 7.2.9.Savari Inc. Company Overview 7.2.9.1.Savari’s Role in the V2V & V2X Market 7.2.9.2.Savari’s Products in the V2V & V2X Market 7.2.10.Other Leading Companies in the V2V & V2I Market 8. Conclusions 8.1.Key Findings from Our Research 8.2 V2V & V2I Penetration in New Vehicle Sales Forecast 2016-2026 8.3.What Will Drive Demand in the V2X Market from 2016 to 2026? 8.4.Learn Which Connectivity Technology is Most Suitable to Support V2V and V2I: DSRC, Wi-Fi, LTE, or LIDAR? 9. Glossary ------------------------------------------------------------ List of Tables Table 2.1 Cost of Road Accidents and Congestion in Europe and the U.S. in 2014 Table 2.2 European Commission’s Action Plan for the Deployment of ITS in Europe Table 2.3 Definition of Cooperative Intelligent Transportation Systems (ITS) Table 2.4 Car-2-Car Consortium’s Related Projects and Task Forces Table 2.5 Dedicated Short Range Communications (DSRC) Service At a Glance Table 2.6 Benefits of Using DSRC for V2V and V2I Communications Table 2.7 ADAS Sensors Usage in ADAS End-User Applications Table 2.8 Automation Levels Table 2.9 Vehicle-to-Vehicle (V2V) Communication Applications Table 2.10 Vehicle-to-Infrastructure (V2I) Communications Applications Table 2.1 Global Sales of New Passenger Cars Equipped with V2V, V2I, V2H, IN-V Modules Forecast 2016-2026 (Millions, AGR%, CAGR%) Table 3.2 New Passenger Cars Equipped with V2V Modules Sales Forecast 2016-2026 (Ml, AGR%, CAGR%) Table 3.3 Aftermarket & OEM DSRC Modules Revenue Forecast 2016-2026 ($bn, AGR%, CAGR%) Table 3.4 Total DSRC Installations Forecast 2016-2026 (Million Units, AGR%, CAGR%) Table 3.5 Cost of DSRC Installations In New Vehicles for OEMs & Consumers 2016, 2021, 2026 ($) Table 3.6 Passenger Cars Equipped With V2I Modules Sales Forecast 2016-2026 (Millions, AGR%, CAGR%) Table 3.7 Road Side Units (RSU) Installations Forecast 2016-2026 (Ml, AGR%, CAGR%) Table 3.8 Revenues Forecast From DSRC-Equipped Smartphones 2016-26 ($bn, AGR%, CAGR%) Table 3.9 Smartphone Shipments Forecast 2016-2026 (Billion Units, AGR%, CAGR%) Table 3.10 Drivers & Restraints of the V2P Communications Submarket Table 3.11 Passenger Cars Equipped With V2H Modules Forecast 2016-2026 (Ml, AGR%, CAGR%) Table 3.12 Drivers & Restraints of the V2H Communications Submarket Table 3.13 Passenger Cars Equipped With IN-V Modules Sales Forecast 2016-2026 (Ml, AGR%, CAGR%) Table 3.14 Revenue Forecast from Cars With IN-V Modules 2016-2026 ($bn, AGR%, CAGR%) Table 3.15 Global IN-V Connected Vehicles Submarket Drivers & Restraints Table 3.16 IN-V Communications Submarket Forecast by Type of Connectivity 2016-2026 ($bn, AGR) Table 3.17 IN-V Submarket Forecast by Service Provider 2016-2026 ($bn, AGR) Table 3.18 Number of ADAS suppliers across Japan, Europe, USA and new entrant countries Table 4.1 Historical Regional Passenger Car Sales 2005-2015 (Million, AGR%) Table 4.2 Regional Passenger Car Sales Forecast 2016-2026 (Million, AGR%) Table 4.3 Regional V2V Communication Submarket Forecast 2016-2026 (Million, AGR%, CAGR%) Table 4.4 Regional V2I Submarket Forecast 2016-2026 (Million, AGR%, CAGR%) Table 4.5 Regional IN-V Connected Car Markets Forecasts 2016-2026 ($bn, AGR %) Table 4.6 Forecasting of Cost of V2V equipment Per Vehicle in two possible scenarios in US dollars Table 4.7 Forecasting of Cost of V2V equipment Per Old Vehicle in two possible scenarios in US dollars 2020 Table 4.8 Forecasting of Cost of V2V equipment Per New Vehicle in two possible scenarios in US dollars 2020 Table 4.9 Forecasting of Total Cost of V2V equipment in two possible scenarios in billion US dollars 2020-2026 Table 4.10 Data transfer cost for V2V communication for 10, 20, 30 and 40 years, US$ Table 4.11 US Volume Car Sales and Year-to-Year change, 2015, 2016 (%) Change Table 4.12 Comparative Analysis for Premium and Volume Cars Table 4.13 US Demand Forecasting for Premium and Volume Cars Period 2016 - 2026 Table 4.14 Advantages of the Forecasting Model for USA V2X Market 2016-2026 Table 4.15 Advantages of the Forecasting Model for USA V2X Market 2016-2026 Table 4.16 NHTSA Cooperation with the FTC In the Setting of Safety Standards Against hacking for Connected Car and V2V Technology Table 4.17 UK V2X Automation Level Share Forecast 2015-2030 (CCP, L3, L4/5) Table 4.18 UK Total Vehicle Production with Automation Technology 2016-2026 (CCP, L3, L4/5 in ml units) Table 4.19 Top Ten Luxury and Premium cars in China Table 4.20 Three categories of connectivity in Chinese Automotive Industry 2012,2016,2026 Table 4.21 Technical Barriers for the Connected Car industry in China Table 4.22 Japan’s Monthly Motor Vehicle Sales 2013-2015 Table 4.23 Japan’s Monthly Motor Vehicle Production 2013 – 2015 Table 4.24 Japan’s Monthly Vehicle exports globally 2013 – 2015 Table 4.25 Japan’s Volume Cars Automation Level Production Forecast 2016-2026 (L1/2, L3, L4/5 %) Table 5.1 SWOT Analysis of the V2V Communications Market 2016-2026 Table 5.2 SWOT Analysis of the V2I Communications Market 2016-2026 Table 6.1 Overview of the Profiled Companies And their Products in the V2V-V2I Market Table 7.2 BMW AG Overview (Revenue, Car Sales, Market Share in Car Sales, No. of Employees, HQ, Ticker, Contact, Website) Table 7.3 Daimler AG Overview (Revenue, HQ, Car Sales 2014, No. of Employees, Ticker, IR, Website) Table 7.4 Daimler’s Car-To-X Communications Technology Table 7.5 General Motors Company Overview (Revenue, HQ, Employees, Ticker, Contact, Website) Table 7.6 Toyota Overview (Revenue, HQ, Market Cap, Ticker, No. of Employees, IR, Contact, Website) Table 7.7 Strategic Alliances with Sumitomo and SPARX Table 7.8 Volkswagen Company Overview (Revenue, Cars Sold, HQ, Global Car Sales Market Share, Ticker, Website) Table 7.9 Arada Systems Overview 2016 (Products, Services, HQ, Website) Table 7.10 Autotalks Overview 2016 (Products, Services, IR, HQ, Website) Table 7.11 Autotalks Products in the V2V-V2I Market (Description, Features) Table 7.12 Cohda Wireless Overview 2016 (Revenue, Products, HQ, IR, Employees, Website) Table 7.13 Cohda Wireless Products in the V2V-V2I Market (Description, Features) Table 7.14 Delphi Overview 2016 (Revenue, Products, HQ, Ticker, Contact, Website) Table 7.15 Delphi Financials (5-year Revenue, Gross Profit, Operating Income, Net Income, Dilut. EPS) 2010-2015 Table 7.16 Denso Overview 2016 (Revenue, Products, Market Cap, Ticker, HQ, Employees, Website) Table 7.17 Denso’s Financials 2011-2015 (5-year Revenue, Gross Profit, Op. Income, Net income, Diluted EPS), (In $Million Apart from EPS) Table 7.18 Denso’s Products in the V2V-V2I Market (Description, Features) Table 7.19 eTrans Systems Overview 2015 (Products, Services, HQ, Website) Table 7.20 Kapsch 2015 (Revenue, Products, HQ, Employees, Ticker, Website) Table 7.21 Kapsch Financials (5-year Revenue, Gross Profit, Operating & Net Income, Diluted EPS) in million USD 2010-2015 Table 7.22 Kapsch’s Products in the V2V-V2I Market (Description, Modes) Table 7.23 Kapsch’s Products in the V2V-V2I Market (Description, Features) Table 7.24 Qualcomm Overview 2016 (Revenue, Product, HQ, Ticker, Contact, Website) Table 7.25 Qualcomm Financials (5-year Revenue, Gross Profit, Operating Income, Net income, Diluted EPS) 2010-2015 Table 7.26 Qualcomm’s Products in the V2V-V2I Market (Description, Features) Table 7.27 Savari Company 2015 (Revenue, Products, HQ, Contact, Website) Table 7.28 Savari’s Applications for V2V-V2I Overview 2016 Table 7.29 Other Leading Companies in the V2V & V2I Market (Company, Country) Table 8.1 Global Automotive V2X, V2V, V2I, V2P, V2H, IN-V Markets Forecast Summary 2016-2026 (Ml, CAGR%) Table 8.2 Key Findings of Our Research Table 8.3 Drivers & Restraints of the V2X Communications Market 2016-2026 ------------------------------------------------------------ List of Figures Figure 1.1 The V2X Communications Market In the Automotive Sector Figure 1.2 V2V, V2I & V2X Market Segmentation Overview Figure 2.1 Megatrends in the Automotive Sector & the V2V-V2I Market Figure 2.2 The Vehicle-to-Everything (V2X) & the V2V, V2I, V2P, V2H, IN-V Markets Figure 2.3 Contribution of V2V & V2I to Safety, Traffic and Autonomous Driving Figure 2.4 V2V Segmentation Overview: V2M, OEM, Aftermarket Figure 2.5 V2I Segmentation Overview: ETC, EPP, V2G Figure 2.6 Wired & Wireless Broadband Subscriptions by technology in 2015 (%) Figure 2.7 IN-V Communications’ Segmentation Figure 2.8 V2V, V2I & V2X Market Segmentation Overview Figure 3.1 Global Sales of New Passenger Cars Equipped with V2V, V2I, V2H, IN-V Modules Forecast 2016-2026 (Millions, AGR%, CAGR%) Figure 3.2 V2X Submarkets’ Share Forecast Summary 2016, 2021, 2026 (%) Figure 3.3 New Passenger Cars Equipped with V2V Modules Sales Forecast 2016-2026 (Ml, AGR%) Figure 3.4 Aftermarket & OEM DSRC Modules Revenue Forecast 2016-2026 ($bn, AGR%) Figure 3.5 Market Share Forecast of OEM & Aftermarket DSRC-Installations Revenues 2016, 2021, 2026 (%) Figure 3.6 V2V Penetration in New Car Sales (%) & DSRC Installation Cost ($) Forecast 2016-26 Figure 3.7 Total DSRC Installations Forecasts 2016-2026 (Million Units, AGR%) Figure 3.8 Passenger Cars Equipped With V2I Modules Sales Forecast 2016-2026 (Ml, AGR%) Figure 3.9 V2I & V2V Penetration in New Vehicles Sales Forecast 2016-2026 (%) Figure 3.10 Road Side Units (RSU) Installations Forecast 2016-2026 (Millions, AGR%) Figure 3.11 Revenues Forecast From DSRC-Equipped Smartphones 2016-26 ($bn, AGR%) Figure 3.12 Smartphone Shipments Forecast 2016-2026 (Billion Units, AGR%) Figure 3.13 Smartphone Shipments (Mi) & Penetration of DSRC in Smartphones (%) 2016-2026 Figure 3.14 Passenger Cars Equipped With V2H Modules Forecast 2016-2026 (Ml, AGR%) Figure 3.15 V2H Penetration In New Cars Forecast 2016-2026 (%) Figure 3.16 Passenger Cars Equipped With IN-V Modules Sales Forecast 2016-2026 (Ml, AGR%) Figure 3.17 Revenue Forecast from Cars With IN-V Modules 2016-2026 ($bn, AGR%) Figure 3.18 IN-V Communications Submarket Share Forecast 2016, 2021, 2026 by Type of Connectivity (%) Figure 3.19 Global IN-V Submarket Share Forecast 2016, 2026, 2026 by Service Provider (%) Figure 3.20 US Labour Cost for Leading Automakers ($ / hour) 2016 Figure 3.21 Average Annual Change in wage from 2010 to 2015 Figure 3.22 The most innovative car manufacturers for communication systems, Innovation score capped at 100 Figure 3.23 Number of ADAS suppliers across Japan, Europe, USA and new entrant, 1990,1994,2004 Figure 3.24 Most innovative car manufacturers for ADAS, innovation score capped at 100 Figure 3.25 Most innovative manufacturers for R&D of Communications Systems, additive index of Figures 3.23 and 3.21, capped at 100 Figure 3.26 Premium and luxury car market in bn US $, 2010 – 2015 Figure 3.27 Global Luxury and Premium Car Market Sales April 2014 - April 2015 Figure 3.28 Harmonized Index of Consumer Prices: Purchase of Vehicles for Euro Area Forecast 1996-2024 Figure 3.29 Premium Car Manufacturer Vehicles Sold by Country, 2002 (‘000 Units) Figure 3.30 Premium Car Manufacturer Vehicles Sold by Country, 2012 (‘000 Units) Figure 3.31 Premium Car Manufacturer Vehicles Sold by Country, 2022 (‘000 Units) Figure 3.32 Venture Capital Companies in the Automotive Industry Figure 4.1 Historical Regional Market Shares in P. Car Sales 2005, 2010, 2015 (%) Figure 4.2 Regional Market Share Forecast in Passenger Car Sales 2016, 2021, 2026 (%) Figure 4.3 Regional V2V Communication Submarket Forecast 2016-2026 (Million, AGR%) Figure 4.4 Regional Market Share Forecast of the V2V Submarket 2016, 2021, 2026 (%) Figure 4.5 Regional V2I Submarket Forecast 2016-2026 by Region (Million Cars, AGR%) Figure 4.6 Regional Market Share Forecast of the V2I Submarket 2016, 2021, 2026 (%) Figure 4.7 Regional IN-V Connected Car Markets Forecasts 2016-2026 ($bn, AGR %) Figure 4.8 Regional Market Share Forecasts of the IN-V Connected Car Submarket 2016, 2021, 2026 (%) Figure 4.9 Data transfer cost for V2V communication for 10,20,30 and 40 years Figure 4.10 Number of sales of V2V equipment in new vehicles by model year 2016-2026 (Millions of Vehicles) Figure 4.11 Share of Cars Connected on Web in USA 2012 – 2026 (% share) Figure 4.12 Best US Luxury Car Brand Sales, First Half of 2015 Figure 4.13 Comparative Analysis for Premium and Volume Cars, 2015 Figure 4.14 US Total Car Sales/Demand, 1999-2026 (units) Figure 4.15 UK V2X Automation Level Share Forecast 2015-2030 (%) Figure 4.16 Decline Ratio of Level 3 to Level 4&5 2025-2030 Figure 4.17 UK Total Commercial Vehicle and Car Production 2000-2026 (units) Figure 4.18 China’s Premium and Luxury Car Market Sales, first half of 2016 Figure 4.19 China’s Commercial and Passenger Vehicle Sales 2005-2015 (Millions) Figure 4.20 Japan – Passenger Car Sales by Manufacturers 2013-2015 (units) Figure 4.21 Japanese Production Penetration of Automated Technology Forecast 2016-2026 (%) Figure 4.22 Japanese Total Vehicle Exports Forecast 2015-2050 (Billion Yen) Figure 4.23 Japanese Car Exports forecast 2013 – 2021 (million units) Figure 7.1 Ranking of the 16 leading Automotive OEMs by 2015 Revenue ($bn) Figure 7.2 Ranking of the 10 leading Automotive OEMs by Sales (million vehicles) in 2015 Figure 7.3 Market Share in 2015 BMW Group’s Sales in Selected Regions (%) Figure 7.4 BMW Group Car Sales Overview 2011, 2012, 2013, 2014, 2015 (ml) Figure 7.5 Mercedes-Benz Car Sales’ Share Distribution in Selected Regions in 2014 (%) Figure 7.6 Mercedes-Benz Car Sales’ Share Distribution in Selected Regions in 2015 (%) Figure 7.7 GM Car Sales Overview 2011-2015 (Million Units) Figure 7.8 Toyota Car Sales Overview 2010-2015 (Thousand Units) Figure 7.9 Toyota Car Market Share per Region % Figure 7.10 Volkswagen group sales in billion Euros 2006-2015 Figure 7.11 Volkswagen Group Regional Market Share 2015 (%) Figure 7.12 Delphi's Percentage of Net Sales to the Largest Customers 2015 Figure 7.13 Delphi’s 2015 Net Sales by Region (%) Figure 7.14 Delphi’s 2015 Revenue by Segment (%) Figure 8.1 V2V-V2I Penetration Into New Cars Forecast 2016-2026 (%) ------------------------------------------------------------ Companies Mentioned in this report Abalta Technologies, Inc. Adam Opel AG ADASWorks ADT Security Services Aeris Alcatel-Lucent Alibaba Alpine Electronics of Silicon Valley Alpine Technology Fund American Honda Motor Corp. Inc. Amiti Ventures Apple Aptina LLC Arada Systems Arynga AT&T Audi AG Autosense International Autotalks Ltd. Baidu Birds Eye Systems BlackBerry BlackBerry Technology Solutions BlackBerry IoT BMW BMW iVentures Bosch Group Buick Cadillac CarIQ Technologies Certicom Cetecom GmbH Chrysler Group LLC Cisco Internet Business Solutions Group CloudMade Cohda Wireless Connected Vehicles Test Bed Continental AG Covisint CSR CyberAgent Ventures Daihatsu Daimler Financial Services Dash Labs Delphi Automotive LLC Delphi Automotive PLC Denso Corporation DENSO International America, Inc. DGE Inc Dolby Laboratories, Inc. Driverless Transportation dSPACE Eict Elliott Management escrypt GmbH eTrans Systems Fiat Chrysler (FCA) Ford Motor Corporation Garmin Gemini Israel Funds General Motors (GM) Corporation General Motors Financial Company Glympse GM Google Inc GreenRoad Hitachi Ltd Honda Hyundai Motor Company Hyundai Ventures Investment Corporation Iav Innovative Defense Technologies INRIX Intel Intel Capital iOnRoad Isuzu Itseez Jaguar Land Rover Jasper Wireless Jeep JustPark Kapsch Group Kapsch TrafficCom Kia Motors Kia Motors America Inc Lamborghini Lesswire AG Lexus Life360 LOC&ALL Luxoft Magma Venture Partners MAN Group Marben Mazda Mercedes Benz Mercedes-Benz R&D North America Mini Mitsubishi Mitsubishi Motors of North America Inc. Mitsui & Co Global Investment MKI USA, Inc. NEC GmbH Nissan Motor Co. Nokia Oyj Nortel NVIDIA Corporation NXP Semiconductors OmniAir OnStar Panasonic Automotive Systems Paratek Persistent Venture Fund Porsche Prospect Silicon Valley PSA Peugeot Citroen QNX Software Systems Qualcomm Atheros Qualcomm Ventures Renault S.A Renault-Nissan Renesas Electronics America Renesas Electronics Corporation Robert Bosch GmbH Rohde & Schwarz GmbH Rsystems International SAIC Motors Savari Networks Security Innovations Siemens AG Sierra Wireless Silver Point Capital. Smart SPARX Group Co. Ltd Spirent Communications plc Streetline Subaru Subaru of America Inc. Sugar OAK Holdings Sumitomo Mitsui Banking Corporation (SMBC) Suzuki Swarco Traffic Ltd Tass International TATA Consultancy Services (TCS) TE Connectivity Tesla Texas Instruments (TI) TOYOTA InfoTechnology Center USA Toyota Motor Corporation (TMC) Transdyn Inc. Transportation Technology Ventures Twitter UMC Capital Vector Group Verizon Communications Verizon Enterprise Solutions Verizon Ventures Vidder Inc Visteon Corporation Vodafone Volkswagen AG Volvo AB Waze ZMP Zoomsafer Government Agencies & Other Organisations Mentioned in This Report American Association of State Highway and Transportation Officials (AASHTO) Amsterdam Group Car 2 Car Consortium (C2C-CC) Center for Automotive Research (CAR) Conference of European Directors of Roads (CEDR) European Association of Operators of Toll Road Infrastructures (ASECAP) European Commission European Committee for Standardization (CEN) European Telecommunications Standards Institute (ETSI) Federal Communications Commission (FCC) Federal Trade Commission (FTC) Institute of Electrical and Electronics Engineers (IEEE) Insurance Institute for Highway Safety Intelligent Transportation Society of America (ITS America) Intelligent Transportation Systems - Joint Programme Office (ITS JPO) Japan Automobile Dealers Association (JAMA) Michigan Department of Transportation (MDOT) National Electrical Manufacturers Association (NEMA) National Highway Transportation Safety Administration (NHTSA) OmniAir Testing and Certification Consortium Organisation Internationale des Constructeurs d'Automobiles (OICA) Organization for Economic Cooperation and Development (OECD) POLIS Texas A&M Transportation Institute The Amsterdam Group Tongji University U.S. Department of Transportation US Department of Transportation Research and Innovative Technology Administration (US DoT RITA) UCLA Network Research Lab United Automobile Workers (UAW) University of Michigan Transportation Research Institute (UMTRI) Virginia Tech. Institute World Health Organization (WHO) PARC (Palo Alto Research Center) Pricing Single User License - GBP 1999 Access for one user only. The user will not be able to print this license. Departmental License - GBP 2999 Entitles up to 5 users to access the report. The users may print out the report. (Not suitable for library usage) Site License - GBP 4999 Unlimited access for your company at a single location Global License - GBP 6999 Unlimited access for your whole company worldwide 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. You are currently subscribed to this list as freebsd-ppc@freebsd.org . As a valued contact or customer, you are receiving this email with information that we believe will be relevant to you. If however, you wish to stop future messages, please reply to this email typing "UNSUBSCRIBE" in the subject box. Registered Office: 230 City Road, London, EC1V 2QY, U.K. From owner-freebsd-ppc@freebsd.org Thu Aug 4 06:59:07 2016 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 AD9AEBAE160 for ; Thu, 4 Aug 2016 06:59:07 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 365531EA0 for ; Thu, 4 Aug 2016 06:59:07 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id o80so365519677wme.1 for ; Wed, 03 Aug 2016 23:59:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=jm2NpCm1jVtVAoXlODQkwwvciHU23pyPZEty9qs0lFc=; b=WWRdZdMRh2GtW4IkdH3Gpr0JGEtwP0rRwteoOdDpFIjp0XopzQjKHCgTJdMbY+BNRl aLUXi1zHqe00aGmOdMgzl1kCRpAh7orDEYA8zfNgVbB3F0HYztCHn05r0G4VHrP7LHKb 2+0otjj2bQ8/YBvaSlEEGoVHgGQXryk/B4B5b03T7DfJhCR2IetStXgrmKhD2IzYEJIf c7uwV68UfWfo7R8Eiy4NqJQsG7056eH/J7VFXfq8mWZlNyRGzCAFUSHBG6LGjGHXX/5J I4P8FA5p0iU3scUlTSPTXg0KUA+AlD0W/jucizdgQLtIZ8TkNvKGHTNeHdPzg8HJGWu7 kzeg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=jm2NpCm1jVtVAoXlODQkwwvciHU23pyPZEty9qs0lFc=; b=fZDsynM4Q3LTXDbOLvLeflD7E23jE7EruUgYN771Tr4/JMeT4zyk3lBJZTrgVgv0mY uDsimb9RknoXH0sPF3J6mQ7sKum+UJAy8zZo8Dbi3ddkBcokzU5ybXIhJ9JsHJHWkGVk XU1RmXcXi+IXSyvM8abZ+CvwclNsoJ14EavQ7xwoIDstC76N4t5po5RSsZ22TG3dzW8U 0XCrUE/KcTbT05Ip+XK3T2+lu6VDx1p5KsA0QeiL3SGB9zKn5E8qbzbl9HLH5rWUvRNA 2dIf+VVuR7PitptW4+idn2uGwYfzttKrmqPub5i4bAQjQ08GSCxa1ugmPuHBBw1wFonI DRrQ== X-Gm-Message-State: AEkoouubCMpwAwDomkiv+5OZQKIfpsiONGKvIvoaJ0u/t93xu5YHAY/pygqU/z6WyHjG8g== X-Received: by 10.194.104.106 with SMTP id gd10mr33965074wjb.55.1470293944938; Wed, 03 Aug 2016 23:59:04 -0700 (PDT) Received: from [192.168.1.131] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.googlemail.com with ESMTPSA id a2sm11237592wjg.46.2016.08.03.23.59.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Aug 2016 23:59:04 -0700 (PDT) To: FreeBSD PowerPC ML From: "Jukka A. Ukkonen" Subject: 11.0-BETA3 panic on PowerMac G5 during boot autoconfig Message-ID: Date: Thu, 4 Aug 2016 09:59:03 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2016 06:59:07 -0000 Hello all, Has anyone else noticed a similar problem with 11.0-BETA3? My G5 boots just fine with 11-BETA2. When I built the latest BETA3 source yesterday afternoon the system started panicing during the boot. The message shown flashes so quickly past the screen that I have no idea what it is trying to say. Though kern.panic_reboot_wait_time is set to 15 seconds, the system apparently does not obey this delay. It reboots immediately after showing the panic message. --jau From owner-freebsd-ppc@freebsd.org Thu Aug 4 14:31:47 2016 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 2C358BAF2DA for ; Thu, 4 Aug 2016 14:31:47 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (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 DA7BF11BE for ; Thu, 4 Aug 2016 14:31:46 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-vk0-x236.google.com with SMTP id s189so169524423vkh.1 for ; Thu, 04 Aug 2016 07:31:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=5ql0UigHxQ4/vLs4b2pfOeTC+X1yu8GAAH23mOArQO4=; b=AuVi5jXlyYLw2JavlQdanKupNoqmC7HT9vfiLwFyr255l5gCIsfWLdR99L1MpeDKn7 +EzrrT58uUBp2CHU2R/c4G8DFn0pz4ExTPpCpi4QQ8BVt5rfdOAQfRWOrBeJjwqWs2CG Mg77j9c+OvRBHa3k4jWbM6gyXl7EVLlUmj3nyAL2V3UQg00gupckAe8zSNimHhiIvx24 dDPExeTsu5zxVrDpOWnsyvbMqvW0WL6WeBOB+ylAUD7iVyehmO8n769jNmCLsNWUUBkP VdGwwSZiyUcHyucqc4QCdYfWqTUeK6AKfYex/mmVs0XGJ4t4bwmNf7cgIs2Bucok9Rdd TwOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=5ql0UigHxQ4/vLs4b2pfOeTC+X1yu8GAAH23mOArQO4=; b=Z1IKyp9+BGpgcIYb4uFHpQfU7eRvMESptwRj62KPXeYpD7+X6Mr7BAxo3ty5AaXR3R I7p5igdG+BGgXKJwVdAoJBTyCt3NbKFTQQRd6P1nZ+zgPB6JirO0aNW7J/sCPpKQysRz fa1CgtNheTm4TMKIaa2bstVqnAQrQ6G3TSxcoon9ZfCfORjddkF2ynBUGZmtwHt00nol t3gYcjftCswT60wPohH+R9D3/llMBvzFZTPQhXVM2P6ijYgL8WEQACBJjn7GIHxqnF4h 2xaRFpv6oOJvhBWMV35TszdqQKimJByeW+Qz4cbhfU/Yfj19SuvowMroSm13sTsFPLP2 3Gsg== X-Gm-Message-State: AEkoousozsXRk2OBOaKCEmK7U42UdmCgyWfX+f9vgjyRgpEXPsOArmL68ElQ2QTLuZQeemAQyeP+g8YU8spz2g== X-Received: by 10.31.174.141 with SMTP id x135mr36397700vke.25.1470321105881; Thu, 04 Aug 2016 07:31:45 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.103.150.1 with HTTP; Thu, 4 Aug 2016 07:31:45 -0700 (PDT) In-Reply-To: References: From: Justin Hibbits Date: Thu, 4 Aug 2016 09:31:45 -0500 X-Google-Sender-Auth: OAq8y1JSlj_4n3FJbGP8KsQdj2o Message-ID: Subject: Re: 11.0-BETA3 panic on PowerMac G5 during boot autoconfig To: "Jukka A. Ukkonen" Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2016 14:31:47 -0000 On Thu, Aug 4, 2016 at 1:59 AM, Jukka A. Ukkonen wrote: > > Hello all, > > Has anyone else noticed a similar problem with 11.0-BETA3? > My G5 boots just fine with 11-BETA2. When I built the latest > BETA3 source yesterday afternoon the system started panicing > during the boot. The message shown flashes so quickly past > the screen that I have no idea what it is trying to say. > Though kern.panic_reboot_wait_time is set to 15 seconds, > the system apparently does not obey this delay. It reboots > immediately after showing the panic message. > > --jau Can you try setting at the loader 'debug.debugger_on_panic=1'? It *shouldn't* reboot then so you can poke around, and give the panic message. Unfortunately I haven't had time to update my G5, it's still running head from back in October. - Justin From owner-freebsd-ppc@freebsd.org Thu Aug 4 17:50:31 2016 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 CBDEFBAD8E8 for ; Thu, 4 Aug 2016 17:50:31 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id 9407A1BC7 for ; Thu, 4 Aug 2016 17:50:31 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from localhost (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3s4y5N2qX3z1cXL1 for ; Thu, 4 Aug 2016 19:45:28 +0200 (CEST) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by localhost (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id lEhhNU118EnH for ; Thu, 4 Aug 2016 19:45:28 +0200 (CEST) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3s4y5N27LPz1cXL0 for ; Thu, 4 Aug 2016 19:45:28 +0200 (CEST) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id 53FAC1B7580 for ; Thu, 4 Aug 2016 19:45:20 +0200 (CEST) Date: Thu, 4 Aug 2016 19:45:19 +0200 From: Luciano Mannucci To: freebsd-ppc@freebsd.org Subject: Re: PPC64 on IBM KVM saga: 11 CURRENT BETA 1 In-Reply-To: <3rkxKP1cQczRRqR@baobab.bilink.it> References: <3rkxKP1cQczRRqR@baobab.bilink.it> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3s4y5N27LPz1cXL0@baobab.bilink.it> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2016 17:50:31 -0000 On Wed, 6 Jul 2016 12:08:17 +0200 Luciano Mannucci wrote: > Knowing that it might be a sparce cpuids problem, I've assigned just > one to test. It does install (WOW!), though the installed version wont > boot. Wow! The sparse CPU problem is gone! Now I can boot - and install - a multi cpu virtual machine. Tough it won't boot. I think I might try with a BETA 3 and report back the results. Cheers to all, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-ppc@freebsd.org Fri Aug 5 05:02:33 2016 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 3F19DBAEFCA for ; Fri, 5 Aug 2016 05:02:33 +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 2F0091755 for ; Fri, 5 Aug 2016 05:02:33 +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 u7552X8T078193 for ; Fri, 5 Aug 2016 05:02:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 211488] powerpc iso broken / does not burn correctly Date: Fri, 05 Aug 2016 05:02:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-BETA3 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: FreeBSD@rorohiko.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2016 05:02:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211488 sysprint0 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |FreeBSD@rorohiko.net --- Comment #1 from sysprint0 --- I confirm the problem with the 10.3 PPC image Burning the ISO on a Mac creates a bootable but empty disk with a subsequent kernel not found msg when booting. Looking in the mail archives I found https://lists.freebsd.org/pipermail/freebsd-ppc/2015-May/007608.html Is the exact symptom but was answered with a failing capacitor !! On my PPC Mac I managed to get the boot_only_iso to finally work after rebuilding the iso to a dmg I have now run out DVD's to test this further. There is some kind of extra layer in the PPC distribution iso that shouldn'= t be there. Best regards --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Fri Aug 5 09:33:32 2016 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 37B8CBAF888 for ; Fri, 5 Aug 2016 09:33:32 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 CE740113C for ; Fri, 5 Aug 2016 09:33:31 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-wm0-x235.google.com with SMTP id q128so24110250wma.1 for ; Fri, 05 Aug 2016 02:33:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mkJ2N+CxyNorslP7cHY2dANymTub095gaP4whGDLz7Q=; b=USu9lPdV4uiY/8sCbVABJ5WieF/I7Hju1gKUI977n+ZTPXvYATEO/Mt5x3rCQ2ZBhJ Jmyanqo6Io3ldwHeD26aPguA2nYB2VRkUBuRbOVRnEQtBG7uLVshr5bvL31X56ExVSC9 lqFhVHFKPRu/Oe6rRHePapIp+/YhSIe+MeAyYbPL3SgePQwicEMH6ybkB2DSeZTkOe2V SN/T7GJaVCohZn+VTtrOXA1LRc2utCursrWuNJOKWLe+kdzwVbX3TK7hg+/NIEKdUu1/ ePFVvQvb1ueYrZYi4BsKsvjxsWE3fwXNM5HgALo1wF/vZludZbv8uamtb3HiOPJK6V9+ Yiwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mkJ2N+CxyNorslP7cHY2dANymTub095gaP4whGDLz7Q=; b=Js8bazgB4DGkL0tq8SmQnpL+o7xY6oFiV6jgW7l1V2qWJUrgeGgTIPdlB5DBhYcx62 5AVHJoY5GjsW8GjrOW+6VsUs5SGp0nECq6UYg+3JAaUlWqziEnw2rZFdfeV6vW1k7S1y 0Np8GQwUFvgpNiUSTsBzvoPPkcm5PX5oN61OkFRKg4jsgMks+xf6hT/hW680/GxQ5sJI MD1SDJqrcG5SzrPhmpKVQvHOojc4tzbn3CLKPDQ97cUGYdkYka9mVkoC7u/eOJQRxXL1 PLSQJbGSt/M50crnNMfrR3BSO2E/DQil2fjRdOvmyxh/C2SFAWZXOiLBSCANtT+Wvd2X l1ig== X-Gm-Message-State: AEkoouv98RAY0SG5+FMjfvUDhbXDgEw2a4f0K2j0kEFLZnmLGfO0A3fWVlBh/aEU4zBB8Q== X-Received: by 10.194.79.161 with SMTP id k1mr18132615wjx.119.1470389609870; Fri, 05 Aug 2016 02:33:29 -0700 (PDT) Received: from [192.168.1.193] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.gmail.com with ESMTPSA id p23sm7736702wme.8.2016.08.05.02.33.28 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 05 Aug 2016 02:33:29 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: 11.0-BETA3 panic on PowerMac G5 during boot autoconfig From: Jukka Ukkonen X-Mailer: iPad Mail (13G35) In-Reply-To: Date: Fri, 5 Aug 2016 12:33:23 +0300 Cc: FreeBSD PowerPC ML Content-Transfer-Encoding: 7bit Message-Id: <9A2F3AA2-5578-4354-B225-D5CF7EE9AF17@gmail.com> References: To: Justin Hibbits X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2016 09:33:32 -0000 > On 04 Aug 2016, at 17:31, Justin Hibbits wrote: > >> On Thu, Aug 4, 2016 at 1:59 AM, Jukka A. Ukkonen wrote: >> >> Hello all, >> >> Has anyone else noticed a similar problem with 11.0-BETA3? >> My G5 boots just fine with 11-BETA2. When I built the latest >> BETA3 source yesterday afternoon the system started panicing >> during the boot. The message shown flashes so quickly past >> the screen that I have no idea what it is trying to say. >> Though kern.panic_reboot_wait_time is set to 15 seconds, >> the system apparently does not obey this delay. It reboots >> immediately after showing the panic message. >> >> --jau > > Can you try setting at the loader 'debug.debugger_on_panic=1'? It > *shouldn't* reboot then so you can poke around, and give the panic > message. Unfortunately I haven't had time to update my G5, it's still > running head from back in October. > > - Justin I tried this and set also debug.bootverbose=1 to see some additional info. It did not help the debugging, though. The quick flashing of the error message and instant reboot still prevent reading the message. Anyhow I managed to notice that autoconfigure got past reporting atapci0 and atapci1. Right after these there has usually been notes about timecounter, etc. So, I got the idea that maybe it is the timecounter initialization that fails. This could also explain why there is no delay between the error message and reboot. Testing this hypothesis is now on my to do list, but it will take some time. --jau From owner-freebsd-ppc@freebsd.org Fri Aug 5 09:37:43 2016 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 B54D7BAFB21 for ; Fri, 5 Aug 2016 09:37:43 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id AA7D0126C; Fri, 5 Aug 2016 09:37:43 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id A8C1118C4; Fri, 5 Aug 2016 09:37:43 +0000 (UTC) Date: Fri, 5 Aug 2016 09:37:43 +0000 From: Alexey Dokuchaev To: Jukka Ukkonen Cc: Justin Hibbits , FreeBSD PowerPC ML Subject: Re: 11.0-BETA3 panic on PowerMac G5 during boot autoconfig Message-ID: <20160805093743.GA50906@FreeBSD.org> References: <9A2F3AA2-5578-4354-B225-D5CF7EE9AF17@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9A2F3AA2-5578-4354-B225-D5CF7EE9AF17@gmail.com> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2016 09:37:43 -0000 On Fri, Aug 05, 2016 at 12:33:23PM +0300, Jukka Ukkonen wrote: > It did not help the debugging, though. The quick flashing of the error > message and instant reboot still prevent reading the message. It might help to video-record this moment and then play it back frame by by frame; there is non-zero chance that you might be able to read that message on one of them. :) ./danfe From owner-freebsd-ppc@freebsd.org Fri Aug 5 09:56:54 2016 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 B7D24BAF1EE for ; Fri, 5 Aug 2016 09:56:54 +0000 (UTC) (envelope-from objectief@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 4DFE41A56 for ; Fri, 5 Aug 2016 09:56:54 +0000 (UTC) (envelope-from objectief@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id o80so29223653wme.1 for ; Fri, 05 Aug 2016 02:56:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=eUq/fs0tuVtHnfMsnRLquwlvdqqhvNEJoB9tZhTmmTc=; b=vuQ9gQeT4Hgp5Pxo3ih3xk/LRCGIQETfD4JrjNP4bp7Yl4ZZWzsiGLfBnzFTe62U0i zO30og3BzVDBp/1OeYdUT1s+dheh7yei38nDglpGYMn5R6rifo8eJXFz4mVFpgDBn/G8 2iZorQvs7FE5La+QjImoMLhshhUbDzxoDAPz+k7SwoyRwBlccjMQCSqW7ZMgXAVIvTfo cGZhtn7GrVARh2f9Gv/xrs7oOyWEXFVib6y1nGpFWNWHKUvnvBb1H1KjyeRCrebsmtrg y9aFLchfMxJg8TZP3cIu15Fuqg33sLCexZhf70EpBkfS7zlaFpIi+cbOAehlT1Gqoecw /YTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=eUq/fs0tuVtHnfMsnRLquwlvdqqhvNEJoB9tZhTmmTc=; b=j06YBPC8YCpLvKe0lbzFIZoEh4BdrBtmx2LyEgokH7OIcE37B1XBzuXUBbbPtv95eK abi7gbqrDTQC55rcg4IHnzOoiCeZ0FaCP7PP75gVIWSg7Ifm9n3eQErfxhzP54LrvjAj VvBDQAlJbyru6cGGT9XLoET7JpI9cS+lS+8ZAbGftwBumnS7mocti+96fVKfH7vS+wuF PrufTpaTG2ZmbbbHi+CW/OPoRMsBI7WA6AwD30TccDvi1TrxIAM1GazN3eATvfCg9guh DeO+Vm+zRYRugk7QA45pG067n0QKL9H/RTPGGCt2k8QLHAGINNOIpP8pHZqby/bAfjO5 B9SQ== X-Gm-Message-State: AEkoouuI1XHBYF6RFG0EV+27Y+kEUooZEsH6+ma0UnZpHa8YkJNkhglazDF+xLCO6nkPz/TM7sE9u+bYSt42Pw== X-Received: by 10.195.14.11 with SMTP id fc11mr1118273wjd.148.1470391012479; Fri, 05 Aug 2016 02:56:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.109.131 with HTTP; Fri, 5 Aug 2016 02:56:51 -0700 (PDT) In-Reply-To: <20160805093743.GA50906@FreeBSD.org> References: <9A2F3AA2-5578-4354-B225-D5CF7EE9AF17@gmail.com> <20160805093743.GA50906@FreeBSD.org> From: Wim Date: Fri, 5 Aug 2016 11:56:51 +0200 Message-ID: Subject: Re: 11.0-BETA3 panic on PowerMac G5 during boot autoconfig To: freebsd-ppc@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2016 09:56:54 -0000 Hi List, First post, so be gentle. FWIW: I've had the same trouble when burning FreeBSD 13.0 stable to DVD on the G5. I ended up with 3 empty DVD's with a working boot record, but nothing else. Needless to state that these DVD's burned instantly. When I burned the same ISO on the Macbook, it was OK and I could install 13.0. Should I look at the G5's PSU now? Cheers, Wim 2016-08-05 11:37 GMT+02:00 Alexey Dokuchaev : > On Fri, Aug 05, 2016 at 12:33:23PM +0300, Jukka Ukkonen wrote: > > It did not help the debugging, though. The quick flashing of the error > > message and instant reboot still prevent reading the message. > > It might help to video-record this moment and then play it back frame by > by frame; there is non-zero chance that you might be able to read that > message on one of them. :) > > ./danfe > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > From owner-freebsd-ppc@freebsd.org Fri Aug 5 10:30:59 2016 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 D19CABAF8F1 for ; Fri, 5 Aug 2016 10:30:59 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 62B3B183A; Fri, 5 Aug 2016 10:30:59 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id f65so26008563wmi.0; Fri, 05 Aug 2016 03:30:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YSZco9++7/WbZWZu8H2sO5BFEwZf615Yh6G1fARgcFE=; b=EmOzF6D2T0R7CpyKmIp5FVK//CqbywewT63KvGn56HDNJeZZVWrU1H2XA2fWfCUDWx ZmmvMXafg7nd/8K5otS99gybVpPb2rHXGP2msk4953TjEz0dGXypqZYvtAs3qzJEIqDX aQ/Vlzq/KCNKhSYU1A/4xZpuiUFVMK/YjkW5ootbQGqFxt+M30F/nwuKc9SVYJzM/b8I 7lOfwWbl+4pumpHG+avw19BZazrBa2Rrq5kN0GruwABmCKjOGUUKXAYgUtfvDndTwinS zrgeuQGFAh657KypH8+fz081tFsBZORq7NPWs2+bM7z3YrF6/5tYj+JwjbgME+yPKmfK T3OQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YSZco9++7/WbZWZu8H2sO5BFEwZf615Yh6G1fARgcFE=; b=MitpWH7r4C24daWt91kWkJVpMUpgeqsvmHMItDP8s+PNjhy0VNAAnNU7JKLoJuxygW kWimStzeVKJ31TTmd42+M7iafUfieGL3oXHxHQkrKVLGdsFCNScP2St6pPyw54sb4Lu0 Ho6xYDtwVj9ttgFuYlBtqlODbIGFCVb1Zyf3EHbeCcVstShx0qM9YmLCsL5hZqUe3Tgh qhpsBRm4EF0NSFTEtFly6NbC2AdsbrdVcZd19YRGcL5cWS2v8I9N9NRkv646cpnOi5R7 NidB7C68uN62EmuAWqHeOIzVnIEavBzanjb3LAeJz9qjVplWvxsF3IXcnhZtBQvx2AJ7 q+AQ== X-Gm-Message-State: AEkooutz5RjE2Yd2k0bJv8cX9AEM9kNz8b8T4YDmWmoHxNpP2VKRpxKqWlyqDZIQQQSJKw== X-Received: by 10.194.82.164 with SMTP id j4mr21185403wjy.157.1470393056907; Fri, 05 Aug 2016 03:30:56 -0700 (PDT) Received: from [192.168.1.193] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.gmail.com with ESMTPSA id uo4sm17156818wjc.36.2016.08.05.03.30.55 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 05 Aug 2016 03:30:56 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: 11.0-BETA3 panic on PowerMac G5 during boot autoconfig From: Jukka Ukkonen X-Mailer: iPad Mail (13G35) In-Reply-To: <20160805093743.GA50906@FreeBSD.org> Date: Fri, 5 Aug 2016 13:30:54 +0300 Cc: Justin Hibbits , FreeBSD PowerPC ML Content-Transfer-Encoding: 7bit Message-Id: References: <9A2F3AA2-5578-4354-B225-D5CF7EE9AF17@gmail.com> <20160805093743.GA50906@FreeBSD.org> To: Alexey Dokuchaev X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2016 10:30:59 -0000 -- > On 05 Aug 2016, at 12:37, Alexey Dokuchaev wrote: > >> On Fri, Aug 05, 2016 at 12:33:23PM +0300, Jukka Ukkonen wrote: >> It did not help the debugging, though. The quick flashing of the error >> message and instant reboot still prevent reading the message. > > It might help to video-record this moment and then play it back frame by > by frame; there is non-zero chance that you might be able to read that > message on one of them. :) > > ./danfe In fact I also thought of this possibility. The image on the screen rolls forward so quickly that there is also a genuine possibility that the video image will end up blurring multiple lines together over one another. But in case everything else fails I will probably become desperate enough to try this as well. ;-) --jau From owner-freebsd-ppc@freebsd.org Fri Aug 5 14:34:52 2016 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 F2F8FBB0E78 for ; Fri, 5 Aug 2016 14:34:52 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id BA07A1EB4 for ; Fri, 5 Aug 2016 14:34:52 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from localhost (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3s5Tq63Qj8zRRrs for ; Fri, 5 Aug 2016 16:34:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by localhost (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id IKSNmqtOEYSp for ; Fri, 5 Aug 2016 16:34:58 +0200 (CEST) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3s5Tq62T6ZzRRrN for ; Fri, 5 Aug 2016 16:34:58 +0200 (CEST) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id 3E5691B7580 for ; Fri, 5 Aug 2016 16:34:50 +0200 (CEST) Date: Fri, 5 Aug 2016 16:34:50 +0200 From: Luciano Mannucci To: freebsd-ppc@freebsd.org Subject: Re: PPC64 on IBM KVM saga: 11 CURRENT BETA 3 In-Reply-To: <3s4y5N27LPz1cXL0@baobab.bilink.it> References: <3rkxKP1cQczRRqR@baobab.bilink.it> <3s4y5N27LPz1cXL0@baobab.bilink.it> X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3s5Tq62T6ZzRRrN@baobab.bilink.it> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2016 14:34:53 -0000 On Thu, 4 Aug 2016 19:45:19 +0200 Luciano Mannucci wrote: > On Wed, 6 Jul 2016 12:08:17 +0200 > Luciano Mannucci wrote: > The sparse CPU problem is gone! Now I can boot - and install - a multi > cpu virtual machine. Tough it won't boot. > > I think I might try with a BETA 3 and report back the results. Still the same. I'm gettingSLOF ********************************************************************** QEMU Starting Build Date = Oct 12 2015 13:18:48 FW Version = mockbuild@ release 20151012 Press "s" to enter Open Firmware. Populating /vdevice methods Populating /vdevice/v-scsi@2000 SCSI: Looking for devices 8002000000000000 DISK : "QEMU QEMU HARDDISK 2.3." 8001000000000000 CD-ROM : "QEMU QEMU CD-ROM 2.3." Populating /vdevice/vty@30000000 Populating /vdevice/nvram@71000000 Populating /pci@800000020000000 00 1800 (D) : 1af4 1002 unknown-legacy-device* 00 1000 (D) : 106b 003f serial bus [ usb-ohci ] 00 0800 (D) : 8086 100e e1000 [ net ] Scanning USB OHCI: initializing USB Keyboard USB mouse Using default console: /vdevice/vty@30000000 Welcome to Open Firmware Copyright (c) 2004, 2011 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /vdevice/v-scsi@2000/disk@8002000000000000 ... Successfully loaded >> FreeBSD/powerpc Open Firmware boot block Boot path: /vdevice/v-scsi@2000/disk@8002000000000000 Boot loader: /boot/loader domount: can't read superblock panic: domount W3411: Client application returned. E3406: Client application returned an error. I thin I'll open a PR. Cheers, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-ppc@freebsd.org Fri Aug 5 19:00:10 2016 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 904F3BB0CDB for ; Fri, 5 Aug 2016 19:00:10 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7EB9112EF for ; Fri, 5 Aug 2016 19:00:10 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from zeppelin.tachypleus.net (75-101-50-44.static.sonic.net [75.101.50.44]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id u75J02Y6018512 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Fri, 5 Aug 2016 12:00:03 -0700 Subject: Re: PPC64 on IBM KVM saga: 11 CURRENT BETA 3 To: freebsd-ppc@freebsd.org References: <3rkxKP1cQczRRqR@baobab.bilink.it> <3s4y5N27LPz1cXL0@baobab.bilink.it> <3s5Tq62T6ZzRRrN@baobab.bilink.it> From: Nathan Whitehorn Message-ID: <70d56fc0-87f2-873d-5742-0bf6f0962890@freebsd.org> Date: Fri, 5 Aug 2016 12:00:02 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <3s5Tq62T6ZzRRrN@baobab.bilink.it> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVaOj4ZiGYP/rgjxhfxv2rhavAs00CNzJDSShQsxauFDebhJIXIxt7x6mj8hdqWtaQd/LCwEb6ZYJ3PzaHqmpKwYYwHM7xSem00= X-Sonic-ID: C;zPVo0D5b5hGVOKDx2xNB0g== M;QODc0D5b5hGVOKDx2xNB0g== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2016 19:00:10 -0000 On 08/05/16 07:34, Luciano Mannucci wrote: > On Thu, 4 Aug 2016 19:45:19 +0200 > Luciano Mannucci wrote: > >> On Wed, 6 Jul 2016 12:08:17 +0200 >> Luciano Mannucci wrote: >> The sparse CPU problem is gone! Now I can boot - and install - a multi >> cpu virtual machine. Tough it won't boot. >> >> I think I might try with a BETA 3 and report back the results. > Still the same. > I'm gettingSLOF ********************************************************************** > QEMU Starting > Build Date = Oct 12 2015 13:18:48 > FW Version = mockbuild@ release 20151012 > Press "s" to enter Open Firmware. > > Populating /vdevice methods > Populating /vdevice/v-scsi@2000 > SCSI: Looking for devices > 8002000000000000 DISK : "QEMU QEMU HARDDISK 2.3." > 8001000000000000 CD-ROM : "QEMU QEMU CD-ROM 2.3." > Populating /vdevice/vty@30000000 > Populating /vdevice/nvram@71000000 > Populating /pci@800000020000000 > 00 1800 (D) : 1af4 1002 unknown-legacy-device* > 00 1000 (D) : 106b 003f serial bus [ usb-ohci ] > 00 0800 (D) : 8086 100e e1000 [ net ] > Scanning USB > OHCI: initializing > USB Keyboard > USB mouse > Using default console: /vdevice/vty@30000000 > > Welcome to Open Firmware > > Copyright (c) 2004, 2011 IBM Corporation All rights reserved. > This program and the accompanying materials are made available > under the terms of the BSD License available at > http://www.opensource.org/licenses/bsd-license.php > > > Trying to load: from: /vdevice/v-scsi@2000/disk@8002000000000000 ... Successfully loaded > >>> FreeBSD/powerpc Open Firmware boot block > Boot path: /vdevice/v-scsi@2000/disk@8002000000000000 > Boot loader: /boot/loader > domount: can't read superblock > panic: domount > > W3411: Client application returned. > > E3406: Client application returned an error. > > I thin I'll open a PR. > > Cheers, > > Luciano. Please do. I can't reproduce this, so it would be really helpful if you could post (a) your disk image and (b) your VM configuration file (or QEMU command-line) somewhere and reference it from the PR. -Nathan