Date: Thu, 21 May 1998 11:04:54 +1000 (EST) From: tonym@angis.org.au To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: kern/6702: tsleep and new snd (pcm0) Message-ID: <199805210104.LAA29772@whale.angis.org.au>
next in thread | raw e-mail | index | archive | help
>Number: 6702 >Category: kern >Synopsis: tsleep and new snd (pcm0) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed May 20 18:10:04 PDT 1998 >Last-Modified: >Originator: Tony Maher >Organization: University of Sydney >Release: FreeBSD 2.2.6-STABLE i386 >Environment: Kernel config file: controller pnp0 device pcm0 at isa? port ? tty irq ? drq ? flags ? vector pcmintr >Description: Since making a new kernel incorporating the new snd code (pcm0) emiclock has problems starting up. It appears but remains a blank white image. When it is killed the console logs tsleep returns -1 It doesn't appear to affect other clocks from the ports section. >How-To-Repeat: Just start emiclock with pcm0 configured in kernel. >Fix: By starting then killing /usr/X11R6/bin/auvoxware emiclock will then work normally. You can restart auvoxware and no problems. But subsequently started emiclocks will be blank. I note in problem report 5034 they write: "Not sure, but somewhere some code is probably calling tsleep() without the PCATCH argument (as it should)." Tsleep is called in code in /usr/src/sys/i386/isa/snd with and without PCATCH. Removing pcm0 and rebuilding kernel also solves the problem ;-) >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805210104.LAA29772>