Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp2937012pxf; Sun, 28 Mar 2021 06:40:41 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxj8tOGWcHvx3nfNOLbgw8XUzFt2exLKIDLb2hchTZKioQ/QvjRc7UEtPk1Tlk/rZsGs17f X-Received: by 2002:a17:906:934c:: with SMTP id p12mr24166785ejw.131.1616938841752; Sun, 28 Mar 2021 06:40:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616938841; cv=none; d=google.com; s=arc-20160816; b=Z2IItoSLdIZ00Qvs8Q12YzNm1Cw559uEm1JKfkNN4UsQ+jKIIYQa26iKeXNefTve9i emjhAqTZXn6uPZsQKjNpMQ6HCBue81nYnxqGNBD+NoDIfNOknCjpMNlFwBEh2ezt0I/b WO7dNcpi2shWlaiKxEmd8JCoZ6/R4FbOKlBO29EpZT20zEDIL3o/yO1VPn8uqT9JcC+g Wirfta84cljss9LbTAbKirfnbSkIuZF27NFKVYJllyn22dQc2NVIlchM5A3uL962cQkR 201yt/hw6E1gWSWQ0wMA8EibgBtkisO+EA+pjLvDS5dwefjLbRqxbqbTmM7Pm1zSNHJa 9Giw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=t4AQ8afiLAK91Mtutrf44uK17xD7kJOYQ7Y2rmgyYEY=; b=eCWtoZDuwuY62QuKb+Juwm/L1pPMCN2wbrrQKhbF4/cHsHN4GcsMqekvMsfnaCzNUC lC8Ak7m8Repo+/JgmBN9B7rvpRf5CVwPQJlIX2RRFw/mq+gC47ipuIdOvqsA9r7S/iJv ZPaI5glO5vt8q4lyWYE7d5s2u4CComTgv3vb4vW+ydQ3DNBh+9OXL2SOFgt7OwihWOP8 TgT+X0a6XpdGFiwzBlaL2ZYYn7FWTMYKKeGZRmoWr5/2anBQe7aNov5L3al2BSbCl8fm cI7NKiSsXXTs+ULRgy0F+FgOyrW9dIxtKwIMTg46pVyr/26zYBa9mx6XXN+xBBvoHLBy eBYA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id da5si12161672edb.464.2021.03.28.06.40.03; Sun, 28 Mar 2021 06:40:41 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230144AbhC1Naf (ORCPT + 99 others); Sun, 28 Mar 2021 09:30:35 -0400 Received: from wtarreau.pck.nerim.net ([62.212.114.60]:50963 "EHLO 1wt.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229503AbhC1Nad (ORCPT ); Sun, 28 Mar 2021 09:30:33 -0400 Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 12SDUTWw024444; Sun, 28 Mar 2021 15:30:29 +0200 Date: Sun, 28 Mar 2021 15:30:29 +0200 From: Willy Tarreau To: Mateusz Jonczyk Cc: Thomas Gleixner , linux-kernel@vger.kernel.org Subject: Re: Testers wanted: Atom netbooks with x86_64 disabled by BIOS Message-ID: <20210328133029.GA24429@1wt.eu> References: <20210327203218.119372-1-mat.jonczyk@o2.pl> <20210327211322.121708-1-mat.jonczyk@o2.pl> <20210327232551.GA20783@1wt.eu> <87lfa8cchf.ffs@nanos.tec.linutronix.de> <059b4775-e130-27c4-26fc-3a0eca07ddae@o2.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <059b4775-e130-27c4-26fc-3a0eca07ddae@o2.pl> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Mar 28, 2021 at 02:37:55PM +0200, Mateusz Jonczyk wrote: > W dniu 28.03.2021 o?00:25, Willy Tarreau pisze: > > FWIW I tested on my ASUS 1025C which runs on an Atom N2600 forced to > > 32-bit. I had already tried in the past but wanted to give it a try > > again in case I'd have missed anything. Sadly it didn't work, I'm > > still getting the "requires an x86-64 CPU" message. > > Thank you. It looks like your bootloader uses the 16-bit kernel boot > protocol. The 16-bit kernel boot code checks for x86_64 presence with a > similar message ( inside arch/x86/boot/cpu.c ), which I did not patch out. > If you would like to test again, use the same patched kernel, but change in > GRUB: "linux16" to "linux" and "initrd16" to "initrd" to use the 32-bit boot > protocol. Which distribution and bootloader do you use? I'm using Lilo on an old Slackware. I can patch the 16-bit code myself, it's no big deal. > Of course, force enabling x86_64 would require passing a kernel command line > parameter with a prominent warning in documentation, just like with > "forcepae". Sure, but I mean, I suspect that the risk could be higher with very low priced laptops were crappy chips are to be expected by definition based on contracts neither you nor me have seen. I'll try again after patching the 16-bit code, thanks for the suggestion. Willy