From: Jakub Jelinek <jj@sunsite.ms.mff.cuni.cz>
To: ultralinux@vger.kernel.org
Subject: Re: Another Brute Force And Ignorance(tm) derived question...
Date: Mon, 12 Apr 1999 13:22:12 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-92392640729141@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-92387605531299@msgid-missing>
> When I add
>
> printk("sys32_ioctl(before switch): cmd(%#010x) "
> "SOUND_MIXER_READ_DEVMASK(%#010x)\n",cmd,SOUND_MIXER_READ_DEVMASK);
I think you wrote in some other mail that strace prints out 0x40044dfe, thus
it has really no value to look for bugs in the kernel.
Either gcc is broken, or you have some problems with includes, or whatever.
Anyway, what distribution is it? UP, BlueSky or what?
On UP1.1.9, I get
open("/dev/mixer", O_RDWR) = 7
ioctl(7, 0x20044dfe, 0x25a20) = -1 ENOTTY (Inappropriate ioctl for device)
and no kernel errors from that ioctl (ENOTTY because my /dev/mixer is ->
/dev/null, no soundcard here).
So, I'd suggest carefully looking at gcc -E output and step through it with
gdb.
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jj@sunsite.mff.cuni.cz | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
___________________________________________________________________
UltraLinux | http://ultra.linux.cz/ | http://ultra.penguin.cz/
Linux version 2.2.5 on a sparc64 machine (3958.37 BogoMips)
___________________________________________________________________
next prev parent reply other threads:[~1999-04-12 13:22 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
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 [this message]
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-92392640729141@msgid-missing \
--to=jj@sunsite.ms.mff.cuni.cz \
--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.