From owner-freebsd-current@FreeBSD.ORG Sat Apr 20 18:06:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DAC24497 for ; Sat, 20 Apr 2013 18:06:44 +0000 (UTC) (envelope-from null@pozo.com) Received: from pozo.com (pozo.com [50.197.129.137]) by mx1.freebsd.org (Postfix) with ESMTP id 8E0658A4 for ; Sat, 20 Apr 2013 18:06:44 +0000 (UTC) Received: from T61p.pozo.com (t61p.pozo.com [192.168.0.4]) (authenticated bits=0) by pozo.com (8.14.6/8.14.6) with ESMTP id r3KHfrJe001805 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NOT); Sat, 20 Apr 2013 10:41:54 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <201304201741.r3KHfrJe001805@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sat, 20 Apr 2013 10:41:48 -0700 To: Rainer Hurling , Florian Smeets From: Manfred Antar Subject: Re: Booting an alternative kernel from loader prompt fails the first time only In-Reply-To: <5172CF44.1050309@gwdg.de> References: <625362A8116D4B43AF4912773F478CB9@multiplay.co.uk> <5172C699.8020708@smeets.im> <5172CF44.1050309@gwdg.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, score=-0.9 required=5.0 tests=ALL_TRUSTED,MISSING_MID autolearn=no version=3.3.2, No X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on pozo.com X-pozocom-MailScanner-Information: Please contact the ISP for more information X-pozocom-MailScanner-ID: r3KHfrJe001805 X-pozocom-MailScanner: Found to be clean X-pozocom-MailScanner-From: null@pozo.com Cc: freebsd-current@freebsd.org, Steven Hartland X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Apr 2013 18:06:44 -0000 At 10:24 AM 4/20/2013, Rainer Hurling wrote: >On 20.04.2013 18:47 (UTC+2), Florian Smeets wrote: >> On 20.04.13 18:05, Steven Hartland wrote: >>> When trying to boot an alternative kernel from the loader prompt >>> it fails the first time the command is run but succeeds the second >>> time. >>> >>> Type '?' for a list of commands, 'help' for more detailed help. >>> OK boot kernel.generic >>> Booting... >>> don't know how to load module '/boot/kernel.generic/kernel' >>> OK boot kernel.generic >>> Booting... >>> /boot/kernel.generic/kernel text=0xd21288 data=...... >>> >> >> Yes, I've been seeing the same thing for about 6-12 months maybe more. >> None of the people I asked were able to confirm, so I'm happy that I'm >> not imagining it :) > >I also can confirm this behaviour for month now (on 10.0-CURRENT amd64 >with clang). > >Rainer > >> >> I see this on serial as well as on the normal console in front of a PC. >> >> Florian >> Have you tried: OK boot /boot/kernel.generic/kernel Use full path name always works for me Manfred ======================== || null@pozo.com || || || ======================== -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.