From nobody@FreeBSD.org Sun Apr 30 18:58:41 2000 Return-Path: Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3211D37B5E5 for ; Sun, 30 Apr 2000 18:58:40 -0700 (PDT) (envelope-from nobody@FreeBSD.org) Received: (from nobody@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id SAA77735; Sun, 30 Apr 2000 18:58:40 -0700 (PDT) (envelope-from nobody@FreeBSD.org) Message-Id: <200005010158.SAA77735@freefall.freebsd.org> Date: Sun, 30 Apr 2000 18:58:40 -0700 (PDT) From: sch@aristotle.net Sender: nobody@FreeBSD.org To: freebsd-gnats-submit@FreeBSD.org Subject: System hang when doing back-to-back captures from bt848/878 to file X-Send-Pr-Version: www-1.0 >Number: 18315 >Category: kern >Synopsis: System hang when doing back-to-back captures from bt848/878 to file >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Apr 30 19:00:00 PDT 2000 >Closed-Date: Sat Jul 21 18:55:47 PDT 2001 >Last-Modified: Sat Jul 21 18:56:37 PDT 2001 >Originator: Stephen Harris >Release: 4.0-RELEASE, 3.3, 3.4 >Organization: >Environment: FreeBSD dell.home.net 4.0-RELEASE FreeBSD 4.0-RELEASE #1: Mon Apr 24 20:13:54 CDT 2000 root@dell.home.net:/usr/src/sys/compile/DELL i386 >Description: Short program causes system to lock-up completely ( no response to any keys, can't telnet to it, harddrive light doesn't go off even though there's no audible activity, num-lock key doesn't toggle its light). The program just repeatedly captures an image and writes it to disk, all in a SIGALRM handler. If the spacing between the SIGALARM's is made to be such that the disk writes run together (hard drive light on continuously), the system locks solid after a few seconds. This happened with release 3.3 also, I've never tried 3.4. I have tried it on both a bt848 and a bt878 and have gotten lockups on both (release 3.3 with bt848 and release 4.0 with bt878). Note that just repeatedly capturing and reading the buffer (and not writing to file), or just repeatedly writing the capture buffer to file (after only capturing once, initially), does not lead to a hang. You have to capture and write repeatedly (close together) to get the hang. >How-To-Repeat: Assuming you have a bt848/bt878 installed: Contact me at sch@aristotle.net and I'll send you "lockup.c", (or tell me where I should have posted it!). cc -o lockup lockup.c (save any work and "sync") ./lockup & wait for the hang >Fix: >Release-Note: >Audit-Trail: State-Changed-From-To: open->feedback State-Changed-By: mike State-Changed-When: Sat Jul 21 18:54:11 PDT 2001 State-Changed-Why: Does this problem still occur in newer versions of FreeBSD, such as 4.3-RELEASE? http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18315 State-Changed-From-To: feedback->closed State-Changed-By: mike State-Changed-When: Sat Jul 21 18:55:47 PDT 2001 State-Changed-Why: Superseded by PR: kern/18316 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18315 >Unformatted: