From owner-freebsd-current Fri May 22 01:22:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA06073 for freebsd-current-outgoing; Fri, 22 May 1998 01:22:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA06053 for ; Fri, 22 May 1998 01:22:21 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 19235 invoked by uid 100); 22 May 1998 08:23:23 -0000 Message-ID: <19980522012319.A19152@top.worldcontrol.com> Date: Fri, 22 May 1998 01:23:19 -0700 To: freebsd-current@FreeBSD.ORG Subject: softupdates and god (panic no more) Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been having softupdate related panics within 3 minutes of boot on my system regularly for the past few weeks. the panic has been: softdep_deallocate_dependencies: dangling deps (trace included below) I finally decided to throw in the towel and setup a serial console so I could capture the panic and the back trace so I could actually be of help. I fashioned myself a serial crossover cable, and read up on how to get the serial console running. I built a completely fresh /sys with the latest CAM and softupdates. After a few tries with the serial console and an rs232-alyzer I had everything where I wanted it, in fact, I even had the panic just as I was about ready. However, I had not turned on the 'capture' feature of the serial terminal emulator so I missed capturing the panic message, but did turn it on and captured the trace. The panic has been perfectly reliable, so with everything in place I rebooted the system and waited for the panic, and waited, and waited ... I started a buildworld and waited, 10 minutes had gone, still no panic. Then the buildworld completed. I did another and it completed. The system has been up 3 hours. This just isn't fair. Anyone want to bet that if I go back to a standard console, the system will return to panicing? 8-) Here is the trace that I did manage to capture, before things went failure free: db> trace _Debugger(f0131dd3) at _Debugger+0x35 _panic(f01cebfe,ffffffff,0,f495ecc0,f014abe5) at _panic+0x8d _softdep_deallocate_dependencies(f1cf25f8) at _softdep_deallocate_dependencies+0 x18 _brelse(f1cf25f8,495630,0,f08eea00,f015111e) at _brelse+0x79 _ffs_indirtrunc(f08eea00,fffffff4,495630,ffffffff,0,f495ed90) at _ffs_indirtrunc +0x2bc _ffs_truncate(f4995ba0,1d8a,0,0,f082e900) at _ffs_truncate+0x8e8 _ufs_setattr(f495eeec,f495ef64,f0156594,f495eeec,f48dfe40) at _ufs_setattr+0x1c9 _ufs_vnoperate(f495eeec,f48dfe40,f0253b38,4,f4995ba0) at _ufs_vnoperate+0x15 _ftruncate(f48dfe40,f495ef94) at _ftruncate+0x114 _syscall(27,27,30000,1,efbfde08) at _syscall+0x127 _Xsyscall() at _Xsyscall+0x55 --- syscall 0xc6, eip = 0x2006fa41, esp = 0xefbfdde8, ebp = 0xefbfde08 --- Unfortunately, I can't recreate it anymore. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message