From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] usb/usbaudio and output speed?
Date: Thu, 24 Oct 2002 09:49:17 -0400 [thread overview]
Message-ID: <200210241349.g9ODnHi22652@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Wed, 23 Oct 2002 16:12:14 EDT." <ca013c3feff926500112769f47e727c4@plan9.bell-labs.com>
> If you can reliably make ps hang, please tell me how.
> I've seen it happen only three times in the last three
> months, and there's never enough information to figure
> out exactly how it got into the state.
Okay, I can reliably (sic) make ps et al hang. This is on an IBM
Thinkpad T21 aquired circa December, 2000. The only USB device
connected to it at the time was a Xitel HiFi-LINK (USB audio). It was
plugged into City power, and there was an audio CD (Rachmaninoff piano
concertos, I believe; I doubt that's relevant, but you never know) in
the CD-ROM drive at the time. Here's what I did:
I booted up and logged in as none to minimize potential problems due to
my local environment; hopefully this should make this repeatable for
others. My termrc is more or less what's in the distrubtion, modulo
some minor changes setting environment variables and the like, and one
``if ...'' that detects what network I'm using (and invokes ipconfig
accordingly) based on plan9.ini, so that should add minimal noise to
the mix. I did an ``aux/vga -l $vgasize'' and started rio. I swept
out a window and executed the following:
term% usb/usbd
term% usb/usbaudio
term% usb/usbaudio # Note, invoking usb/usbaudio twice.
term% kill usbaudio | rc
...And the last command hung. I then swept out another window, tried
to run ps, but it also hung. I then swept a third window, halted KFS,
and rebooted. I repeated the experiment a couple of times to make sure
it wasn't a fluke, but each time got the same result. I didn't have
time last night to investigate further (neither do I have time at the
moment, unfortunately).
Anyway, it seems that ps hangs pretty consistently when I do this. Russ,
can you duplicate it?
- Dan C.
next prev parent reply other threads:[~2002-10-24 13:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 20:12 Russ Cox
2002-10-23 21:40 ` Dan Cross
2002-10-24 13:49 ` Dan Cross [this message]
2002-10-24 14:27 ` Boyd Roberts
2002-10-24 15:52 ` Aharon Robbins
2002-10-25 4:58 ` Jim Choate
2002-10-24 17:07 ` Dan Cross
2002-10-25 9:04 ` Anthony Mandic
-- strict thread matches above, loose matches on Subject: below --
2002-10-25 15:56 Russ Cox
2002-10-24 17:31 nigel
2002-10-24 17:37 ` Dan Cross
2002-10-23 0:40 Russ Cox
2002-10-23 18:38 ` Dan Cross
2002-10-23 0:00 Russ Cox
2002-10-23 0:28 ` Dan Cross
2002-10-22 19:21 Dan Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200210241349.g9ODnHi22652@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).