From owner-freebsd-current Fri Jul 5 20:44:40 2002 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 9FB4637B400 for ; Fri, 5 Jul 2002 20:44:35 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D810743E3B for ; Fri, 5 Jul 2002 20:44:34 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id XAA07345; Fri, 5 Jul 2002 23:44:29 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g663hxt29836; Fri, 5 Jul 2002 23:43:59 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15654.26495.25741.948480@grasshopper.cs.duke.edu> Date: Fri, 5 Jul 2002 23:43:59 -0400 (EDT) To: julian@elischer.org Cc: freebsd-current@freebsd.org Subject: panic broken on alpha or scsi or up X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Julian, When I panic an alpha these days, I end up with the random_kthread spinning on the cpu stuck in msleep, and I never get the disks sync'ed (or, if I disable sync'ing, I never get through a dump): panic: vm_page_wakeup: page not busy!!! panic Stopped at Debugger+0x34: zapnot v0,#0xf,v0 db> c syncing disks... 3 3 Stopped at siointr1+0x198: br zero,siointr1+0x330 db> tr siointr1() at siointr1+0x198 siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x24 alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 interrupt() at interrupt+0x110 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- msleep() at msleep+0x20 random_kthread() at random_kthread+0xb4 fork_exit() at fork_exit+0xe0 exception_return() at exception_return --- root of call graph --- db> c Stopped at siointr1+0x198: br zero,siointr1+0x330 db> where No such command db> tr siointr1() at siointr1+0x198 siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x24 alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 interrupt() at interrupt+0x110 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- critical_exit() at critical_exit+0x20 _mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0x94 msleep() at msleep+0x290 random_kthread() at random_kthread+0xb4 fork_exit() at fork_exit+0xe0 exception_return() at exception_return --- root of call graph --- db> reboot If I disable the randomness thing, I end up getting stuck in another kernel process: db> tr siointr1() at siointr1+0x198 siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x24 alpha_dispatch_intr() at alpha_dispatch_intr+0xd0 interrupt() at interrupt+0x110 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- critical_exit() at critical_exit+0x20 _mtx_unlock_spin_flags() at _mtx_unlock_spin_flags+0x94 msleep() at msleep+0x290 buf_daemon() at buf_daemon+0x1f4 fork_exit() at fork_exit+0xe0 exception_return() at exception_return --- root of call graph --- I don't have this problem on my x86 testbox, but it has an IDE disk and is SMP. The alpha with the problem is UP, and uses a SCSI disk (isp controller). Any ideas? Are people able to get crashdumps on UP SCSI x86s? Thanks, Drew PS: I was going to make the subject "can't take a dump", but I thought the better of it ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message