From: Peter Jones <pjones@redhat.com>
To: ultralinux@vger.kernel.org
Subject: Re: Another Brute Force And Ignorance(tm) derived question...
Date: Mon, 12 Apr 1999 04:50:47 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-92389299507372@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-92387605531299@msgid-missing>
On Sun, 11 Apr 1999, David Miller wrote:
> Date: Mon, 12 Apr 1999 00:04:05 -0400 (EDT)
> From: Peter Jones <pjones@redhat.com>
>
> > Might want to double-check on strace, have it print out the raw hex
> > value for the ioctl cmd code and make sure it matches up.
>
> open("/dev/mixer", O_RDWR) = 4
> ioctl(0x4, 0x40044dfe, 0x2563c) = -1 (errno 22)
>
> No dice, matches up just fine. Any more ideas?
>
> Could be a compiler bug then, put some debugging printk's into
> sys32_ioctl(), one right before the big switch which goes:
>
> printk("sys32_ioctl(before switch): cmd(%08x) "
> "SOUND_MIXER_READ_DEVMASK(%08x)\n",
> cmd, SOUND_MIXER_READ_DEVMASK);
>
> Then put a similar printk right below the case for
> SOUND_MIXER_READ_DEVMASK itself.
>
> This bug would explain some problems I had with the gnome mixer applet
> and some other sound programs on sparc64...
Hrm. Odd. When aumix calls that, its sending 0x20044dfe, which is what
kernelspace is _expecting_ to get. somewhere in the middle its becoming
0x40044dfe , which is falling through the case. Any ideas?
Anyway, I'm going to bed. I've managed to be in line for a 9:30 meating
tomorrow.
-- Peter
Stay sane inside insanity.
-- RHPS
next prev parent reply other threads:[~1999-04-12 4:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-12 0:08 Another Brute Force And Ignorance(tm) derived question Peter Jones
1999-04-12 1:26 ` David Miller
1999-04-12 4:04 ` Peter Jones
1999-04-12 4:11 ` David Miller
1999-04-12 4:50 ` Peter Jones [this message]
1999-04-12 4:58 ` David Miller
1999-04-12 5:14 ` Jakub Jelinek
1999-04-12 12:46 ` Peter Jones
1999-04-12 13:22 ` Jakub Jelinek
1999-04-12 14:53 ` Peter Jones
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=marc-linux-ultrasparc-92389299507372@msgid-missing \
--to=pjones@redhat.com \
--cc=ultralinux@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 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.