From: "Anthony Barbachan" <barbacha@Hinako.AMBusiness.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: PC Speaker ocassionally hangs on an FIC VA-503+ under 2.4.[567]
Date: Sun, 22 Jul 2001 19:57:18 -0400 [thread overview]
Message-ID: <002001c1130a$0a98a0a0$9865fea9@optima> (raw)
Hi,
I have noticed the following problem on a system which I installed on a
FIC VA-503+ motherboard with a 450 Mhz K6-2 CPU. This problem is consistent
and is present in kernels from 2.4.5 - 2.4.7. The problem is that
occasionally the PC speaker will hang when making a beep. When the hang
occurs the beep stays on, the screen blanks out, and all processing on the
system appears to hang. After a few moments the system appears to unhang
itself, the screen returns, and everything returns to normal. While it is
not consistent, as not all beeps from the PC speaker causes the hanging, but
it is frequent enough to make working on the console almost unbearable. The
hanging behavior can be easily reproduced if I do anything to cause multiple
system beeps; such as pressing tab a few times on an empty bash prompt which
causes a beep to occur from the auto command completion feature as it warns
you that multiple possible substitutions exist for your command completion
request.
Is this a known bug?
If so is there a fix for it?
If it is not know how can I help in resolving this? (No oops exists so
nothing to send from there)
next reply other threads:[~2001-07-22 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-22 23:57 Anthony Barbachan [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 18:06 PC Speaker ocassionally hangs on an FIC VA-503+ under 2.4.[567] Nate Eldredge
2001-07-23 18:10 ` Nate Eldredge
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='002001c1130a$0a98a0a0$9865fea9@optima' \
--to=barbacha@hinako.ambusiness.com \
--cc=linux-kernel@vger.kernel.org \
/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