From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Steven Walter <srwalter@yahoo.com>
Cc: tytso@mit.edu, linux-kernel@vger.kernel.org
Subject: Re: [BUG] serial ioctl not returning with 2.4.3
Date: Wed, 11 Apr 2001 16:50:21 -0400 [thread overview]
Message-ID: <3AD4C38D.2C970A60@mandrakesoft.com> (raw)
In-Reply-To: <20010411142538.A27290@hapablap.dyn.dhs.org>
Steven Walter wrote:
>
> When I try to start "agetty" on my serial line, agetty hangs in an
> ioctl; according to strace, this ioctl is "SNDCTL_TMR_STOP". This
> doesn't sound right, but that ioctl is defined as _IO('T', 3) if that
> makes any more sense.
>
> The reason that this must be a kernel bug is because agetty works
> flawlessly in an identically-configured 2.4.2 kernel, and even a 2.4.3
> kernel with the debugging tokens defined. I'd be glad to give any help
> that I could.
I am not sure this is a serial driver bug:
[jgarzik@rum linux_2_4]$ find . -name '*.[ch]'|xargs grep -wn
SNDCTL_TMR_STOP
./arch/sparc64/kernel/ioctl32.c:3503:COMPATIBLE_IOCTL(SNDCTL_TMR_STOP)
./drivers/sound/mpu401.c:1522: case SNDCTL_TMR_STOP:
./drivers/sound/sequencer.c:1352: case SNDCTL_TMR_STOP:
./drivers/sound/sound_timer.c:195: case SNDCTL_TMR_STOP:
./drivers/sound/sys_timer.c:206: case SNDCTL_TMR_STOP:
./include/linux/soundcard.h:165:#define SNDCTL_TMR_STOP
_SIO ('T', 3)
--
Jeff Garzik | Sam: "Mind if I drive?"
Building 1024 | Max: "Not if you don't mind me clawing at the dash
MandrakeSoft | and shrieking like a cheerleader."
next prev parent reply other threads:[~2001-04-11 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 19:25 [BUG] serial ioctl not returning with 2.4.3 Steven Walter
2001-04-11 20:50 ` Jeff Garzik [this message]
2001-04-11 21:12 ` Russell King
2001-04-11 22:36 ` Steven Walter
2001-04-12 9:06 ` Russell King
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=3AD4C38D.2C970A60@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srwalter@yahoo.com \
--cc=tytso@mit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.