From owner-freebsd-current@FreeBSD.ORG Wed Apr 28 23:28:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B18916A4CE for ; Wed, 28 Apr 2004 23:28:33 -0700 (PDT) Received: from email07.aon.at (WARSL402PIP8.highway.telekom.at [195.3.96.97]) by mx1.FreeBSD.org (Postfix) with SMTP id B084243D45 for ; Wed, 28 Apr 2004 23:28:32 -0700 (PDT) (envelope-from shoesoft@gmx.net) Received: (qmail 90580 invoked from network); 29 Apr 2004 06:28:31 -0000 Received: from m112p002.dipool.highway.telekom.at (HELO ?62.46.3.226?) ([62.46.3.226]) (envelope-sender ) by 172.18.5.236 (qmail-ldap-1.03) with SMTP for ; 29 Apr 2004 06:28:31 -0000 From: Stefan Ehmann To: Thomas Quinot In-Reply-To: <20040428100007.GC61713@melusine.cuivre.fr.eu.org> References: <1081935197.722.17.camel@boots> <20040428100007.GC61713@melusine.cuivre.fr.eu.org> Content-Type: text/plain Message-Id: <1083220109.797.12.camel@taxman> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 29 Apr 2004 08:28:29 +0200 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: atapicam troubles - pc doesn't boot (sometimes) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 29 Apr 2004 06:28:33 -0000 On Wed, 2004-04-28 at 12:00, Thomas Quinot wrote: > * Stefan Ehmann, 2004-04-14 : > > > Since latest cvsup kernel doesn't boot about half of the time. Without > > ATAPICAM it just boots fine every time. > > Can you show a kernel backtrace at the point where the kernel hangs? > > > (probe0:ata0:0:0:0): error 22 > > (probe1:ata0:0:1:0): error 22 > > Do you hava anything connected to ata0? First of all, my first analysis turned out to be pretty wrong: The problem also happens with older kernels and also without atapicam. Though with atapicam disabled it seems to be much less likely. atacontrol list gives this: ATA channel 0: Master: ad0 ATA/ATAPI revision 6 Slave: ad1 ATA/ATAPI revision 5 ATA channel 1: Master: acd0 ATA/ATAPI revision 0 Slave: acd1 ATA/ATAPI revision 5 I changed master/slave of the cdrom devices which seemed to fix it at first but turned out to just improve chance of successfull booting. trace in ddb shows this after manual break to debugger scgetc() sckbdevent() atkdb_intr() atkbd_isa_intr() ithread_loop() fork_exit() fork_trampoline() A photo with a bit more detail can be found here (to save me frome typing all those numbers): http://stud4.tuwien.ac.at/~e0125637/fbsd/hang.jpg