From owner-freebsd-current@FreeBSD.ORG Mon Nov 14 23:25:37 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 22693106564A for ; Mon, 14 Nov 2011 23:25:37 +0000 (UTC) (envelope-from chmiels@o2.pl) Received: from tur.go2.pl (tur.go2.pl [193.17.41.50]) by mx1.freebsd.org (Postfix) with ESMTP id A42048FC14 for ; Mon, 14 Nov 2011 23:25:36 +0000 (UTC) Received: from moh1-ve3.go2.pl (moh1-ve3.go2.pl [193.17.41.134]) by tur.go2.pl (Postfix) with ESMTP id 2017C231B17 for ; Tue, 15 Nov 2011 00:00:48 +0100 (CET) Received: from moh1-ve3.go2.pl (unknown [10.0.0.134]) by moh1-ve3.go2.pl (Postfix) with ESMTP id C2361664630 for ; Tue, 15 Nov 2011 00:00:44 +0100 (CET) Received: from unknown (unknown [10.0.0.42]) by moh1-ve3.go2.pl (Postfix) with SMTP for ; Tue, 15 Nov 2011 00:00:44 +0100 (CET) Received: from staticline55990.toya.net.pl [77.237.11.229] by poczta.o2.pl with ESMTP id GlUWlx; Tue, 15 Nov 2011 00:00:44 +0100 Date: Tue, 15 Nov 2011 00:00:55 +0100 From: Sebastian Chmielewski To: Alexander Motin Message-ID: <20111115000055.58b7a103@o2.pl> In-Reply-To: <4EC198B8.1010901@FreeBSD.org> References: <4EC198B8.1010901@FreeBSD.org> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-O2-Trust: 2, 65 X-O2-SPF: neutral Cc: current Subject: Re: Second SATA device lost after ZFS root is mount X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 14 Nov 2011 23:25:37 -0000 On Tue, 15 Nov 2011 00:39:52 +0200 Alexander Motin wrote: > SATA device can be dropped because of error during reset/ probe/ > initialization sequence or because controller reported disconnection. > Verbose boot messages (boot -v from loader prompt) should give more > information about what happened there. Show please full verbose dmesg. Using rc_debug="YES" in rc.conf I've found that my device is dropped during sysctl_start. With empty sysctl.conf my device is not lost. The contents of file seems quite innocent: # Uncomment this to prevent users from seeing information about processes that # are being run under another UID. security.bsd.see_other_uids=1 # Enable/disable coredump kern.coredump=1 # Up the maxfiles to 4x default kern.maxfiles=49312 kern.ipc.shmmax=67108864 kern.ipc.shmall=32768 # Allow users to mount CD's vfs.usermount=1 vfs.hirunningspace=8388608 vfs.lorunningspace=1048576 kern.corefile="/var/coredumps/%U/%N.core" # Do not truncate command line arguments in ps(1) listing kern.ps_arg_cache_limit=10000 # Tune for desktop usage kern.sched.preempt_thresh=224 # Increase default setting - recommended for 2 GB of RAM kern.maxvnodes=400000 dev.acpi_ibm.0.lcd_brightness=6 dev.acpi_ibm.0.lcd_brightness=3 net.link.tap.user_open=1 net.link.tap.up_on_open=1 The device is lost even when sysctl is started with new file when booting finishes (I did service sysctl restart from X session). # sysctl debug.bootverbose=1 # service sysctl restart # dmesg ahcich1: DISCONNECT requested ahcich1: AHCI reset... ahcich1: SATA connect timeout time=10000us status=00000000 ahcich1: AHCI reset: device not found (ada1:ahcich1:0:0:0): lost device (pass1:ahcich1:0:0:0): lost device (pass1:ahcich1:0:0:0): removing device entry Crazy, isn't it? best regards, -- Sebastian Chmielewski * jid:chmielsster@gmail.com * gg:3336919 * icq:224161389