From owner-freebsd-current@FreeBSD.ORG Sun Dec 7 11:54:34 2003 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 601AD16A4CE for ; Sun, 7 Dec 2003 11:54:34 -0800 (PST) Received: from quack.kfu.com (quack.kfu.com [64.168.71.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id F324443FDD for ; Sun, 7 Dec 2003 11:54:32 -0800 (PST) (envelope-from nsayer@kfu.com) Received: from minerva.kfu.com (minerva.kfu.com [IPv6:2002:40a8:47d1:1:206:25ff:fe3d:aa11]) (authenticated bits=0) by quack.kfu.com (8.12.8p2/8.12.8) with ESMTP id hB7JsBU4042506 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Sun, 7 Dec 2003 11:54:12 -0800 (PST) (envelope-from nsayer@kfu.com) X-Message-Flag: Why aren't you using a Macintosh yet? Mime-Version: 1.0 (Apple Message framework v606) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Nick Sayer Date: Sun, 7 Dec 2003 11:52:59 -0800 To: freebsd-current@freebsd.org X-Mailer: Apple Mail (2.606) X-Spam-Status: No, hits=-5.4 required=5.0 tests=BAYES_01,USER_AGENT_APPLEMAIL version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: 5.1-RELEASE-p11 - ACPI panic during shutdown, USB panic w/ USB2 HD 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: Sun, 07 Dec 2003 19:54:34 -0000 I don't have huge amounts of detail. I'm sort of writing this to see if I can get a rough idea how likely it is these items are already fixed in the pending 5.2 release. Case #1: I have an Asus P5A based machine that I recently upgraded to RELENG_5_1. When I was done, I found that when it was shutting down, just at (what I perceive to be, anyway) the last step before it would reboot, it would go into what appeared to be a trap loop of some sort. It would quickly scroll 'trap 12' frames and then hang. The only recovery is to press the reset button. This isn't really a big pain, but it does mean that I can't remotely reboot this machine at all. It must be at least happening after the filesystems are dismounted, because they always come back up clean. I note that this machine has to have kern.timecounter.hardware="TSC" in sysctl.conf to keep the clock from running at double speed. Is this something fixed in 5.2 or is this something unfixable except in hard/firmware? --- Case #2: This is an older machine with a USB 2.0 PCI controller card and an external USB 2.0 disk enclosure. Excerpts from dmesg.boot: ohci0: mem 0xe7000000-0xe7000fff irq 5 at device 9 .0 on pci0 usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xe6800000-0xe6800fff irq 11 at device 9.1 on pci0 usb1: OHCI version 1.0 usb1: on ohci1 usb1: USB revision 1.0 uhub1: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0xe6000000-0xe60000ff irq 10 at d evice 9.2 on pci0 ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 usb2: EHCI version 0.95 usb2: companion controllers, 3 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: NEC EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 5 ports with 5 removable, self powered Shortly after disk I/O begins on the USB disk, there is a fatal trap panic and reboot. This disk/controller pair worked just fine under 4.8-RELEASE, albeit not at high speed. --- Should I not worry about these and just wait for 5.2? Thanks in advance.