From owner-freebsd-stable@FreeBSD.ORG Wed Mar 30 15:50:01 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EDC31065678 for ; Wed, 30 Mar 2011 15:50:01 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id F2A6D8FC1A for ; Wed, 30 Mar 2011 15:50:00 +0000 (UTC) Received: by qyk27 with SMTP id 27so1139932qyk.13 for ; Wed, 30 Mar 2011 08:50:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=hGitUu7h7aRA1ZotI4bAoRtzszfbI0/6uJ9FQWBRRLs=; b=MiZ9qsP98uwsVTatEGWAMF2HKY2mNB/c1UZQPdDNkejwOU6bH6HZ0q6ChlpgR/r8z7 zeYN2dj1Ktmu1rWyOPWj7gQTUp+wLESCYWIWLW3MWjDZsyvSN111ISqA37R28qK1T+TF l79gQhFvFUTv2UxvSPatvMmiARXaW8z5enYdk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LmTtpVtR3a99dMTzxFGnzyoYTvGfGUognA1WIUIHc7Al0yZ1Lapq8F+6okePcWYg4/ MCvyYfiD8qHgRwLOgwd6E9R04b9YEPndUjHZTna9WMBHJzQB26lo/4sbcj770jiTWvDn Y2zCuk6GVW4C/N0hkQksGG3q0VaHuQpgRmSPE= MIME-Version: 1.0 Received: by 10.224.219.68 with SMTP id ht4mr1232685qab.217.1301500200050; Wed, 30 Mar 2011 08:50:00 -0700 (PDT) Received: by 10.224.67.21 with HTTP; Wed, 30 Mar 2011 08:50:00 -0700 (PDT) In-Reply-To: <4D932F13.1060105@rsu.ru> References: <4D932F13.1060105@rsu.ru> Date: Wed, 30 Mar 2011 11:50:00 -0400 Message-ID: From: Mehmet Erol Sanliturk To: Alexander Pyhalov Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: boot0 bug? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2011 15:50:01 -0000 On Wed, Mar 30, 2011 at 9:24 AM, Alexander Pyhalov wrote: > Hello. > I have IBM blade, which is connected to EMC Clarion disk storage (2 FC > adapters connected to 2 FC switches, so system sees 4 paths to storage). One > lun is provided to the system. The problem is that FreeBSD doesn't boot > randomly (at least 1 attempt from 5 boots is unsuccessful). The blade stalls > and I see only blank screen. > I've tried other operating systems - OpenIndiana b148 and Ubuntu 10.10 - > each of them has booted perfectly 10 times without any issues. > > I don't see any messages from boot1 stage and system is logged in to EMC > storage with only one path. When the system boots successfully, I can see on > EMC Clarion that it is connected with all paths. I've tried to use boot0 > from CURRENT - results are the same (boot fails randomly). > How can I debug this issue? > > Additional info: > # uname -a > FreeBSD fbsdhost5.xx 8.2-RELEASE FreeBSD 8.2-RELEASE #0 r219027M: Wed Mar > 9 15:12:21 MSK 2011 alp@xx:/usr/obj/usr/src-releng-8.2/sys/ibm-hs-21xm-vnet-amd64.releng-8.2 > amd64 > > # camcontrol devlist -v > scbus0 on isp0 bus 0: > at scbus0 target 0 lun 0 (sg0,pass0,da0) > at scbus0 target 1 lun 0 (sg1,pass1,da1) > <> at scbus0 target -1 lun -1 () > scbus1 on isp1 bus 0: > at scbus1 target 0 lun 0 (sg2,pass2,da2) > at scbus1 target 1 lun 0 (sg3,pass3,da3) > <> at scbus1 target -1 lun -1 () > scbus-1 on xpt0 bus 0: > <> at scbus-1 target -1 lun -1 (xpt0) > > # gmultipath status > Name Status Components > multipath/fbsdhost5tst N/A da0 > da1 > da2 > da3 > # gpart show > => 63 33554367 multipath/fbsdhost5tst MBR (16G) > 63 33543657 1 freebsd [active] (16G) > 33543720 10710 - free - (5.2M) > > => 0 33543657 multipath/fbsdhost5tsts1 BSD (16G) > 0 16 - free - (8.0K) > 16 18863577 1 freebsd-ufs (9.0G) > 18863593 4194304 2 freebsd-swap (2.0G) > 23057897 2097152 4 freebsd-ufs (1.0G) > 25155049 8388608 5 freebsd-ufs (4.0G) > > # boot0cfg -v /dev/multipath/fbsdhost5tst > # flag start chs type end chs offset size > 1 0x80 0: 1: 1 0xa5 39:254:63 63 33543657 > > version=2.0 drive=0x80 mask=0xf ticks=182 bell=# (0x23) > options=packet,update,nosetdrv > volume serial ID 9090-9090 > default_selection=F1 (Slice 1) > > # df > Filesystem 1K-blocks Used Avail Capacity Mounted > on > /dev/multipath/fbsdhost5tsts1a 9129786 4522594 3876810 54% / > devfs 1 1 0 100% /dev > /dev/multipath/fbsdhost5tsts1d 1012974 12 931926 0% /tmp > /dev/multipath/fbsdhost5tsts1e 4058062 141846 3591572 4% /var > > -- > Best regards, > Alexander Pyhalov, > system administrator of Computer Center of Southern Federal University > I will mention the following issue similar to above problem as my observation . The problem is NOT only belong to FreeBSD , all of the BSD based operating systems ( such as PC-BSD , NetBSD , DragonFlyBSD ) independent from version numbers are exhibiting the same behavior . Assume an operating system other than BSD based operating systems is booted on my computer ( Intel DG965WH board ) and then it is shut down . When I start the booting of an BSD based operating system , it is exactly crashing at some point , especially when it becomes necessary to accept a user response . In that point it is unknown whether key board is locked or there is another problem . What ever the reason is , it is necessary to hard reset the computer . The second and subsequent boots are successful . When another operating system is booted , the above crash-successes cycle is starting again . Neither of the other operating systems ( mostly Linux and others ) is exhibiting such a behavior what ever is the previously booted operating system . I can say that this issue is only belong to BSD based operating systems . I do not know the reason , but I suspect that there is a missing part in the booting code , especially within initialization code at the beginning . First , unsuccessful boot is setting some value(s) , but itself is crashing , the subsequent booting is using that previously set value(s) and they are succeeding up to the point where the other operating systems is setting that or those value(s) differently . Thank you very much . Mehmet Erol Sanliturk