From: Kevin Brosius <cobra@compuserve.com>
To: Greg KH <greg@kroah.com>
Cc: Oliver Neukum <oliver@neukum.name>,
kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.44-ac3 usb audio - illegal sleep call
Date: Sat, 26 Oct 2002 18:21:34 -0400 [thread overview]
Message-ID: <3DBB156E.8AB7C79D@compuserve.com> (raw)
In-Reply-To: <20021026185333.GA2876@kroah.com>
Greg KH wrote:
>
>
> On Sat, Oct 26, 2002 at 02:13:42PM -0400, Kevin Brosius wrote:
> > Oliver Neukum wrote:
> > >
> > >
> > > Am Samstag, 26. Oktober 2002 16:13 schrieb Kevin Brosius:
> > > > I've been trying to get USB up to test a audio device and just managed
> > > > to get it all working to some extent. When using xmms to play audio
> > > > (usb audio module - oss soundcore) I see the following kernel messages
> > > > repeatedly, maybe once a second or so:
> > >
> > > Go edit usbout_completed() and usbin_completed(). Change the GFP_KERNEL
> > > in usb_submit_urb to GFP_ATOMIC.
> > > Does that help ?
> > >
> > > Regards
> > > Oliver
> >
> >
> > Hi guys,
> > No... Well, actually, it does change which function gives the
> > warning. Now usbout_sync_completed is complaining.
>
> Heh, can you change that instance of GFP_KERNEL to GFP_ATOMIC too?
>
> thanks,
Yes, I went ahead and tried that. I also had do it in usbout_start()
and usbin_sync_completed(). Now I can play audio without any of those
warnings showing up in the log.
This may be unrelated, but I also see the usb audio device fail after
some uses. For example, using xine with the oss output module will only
play audio for a short time, then audio stops. After that point it is
impossible to restore audio function from everything I've tried. I am
unable to kill -9 xine successfully, and unable to rmmod the usb audio
driver to try and reload it. Only a full reboot will bring it back to
life (I'm sure there are things I haven't tried...)
--
Kevin
next prev parent reply other threads:[~2002-10-26 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 14:13 Kevin Brosius
2002-10-26 17:02 ` Oliver Neukum
2002-10-26 18:13 ` Kevin Brosius
2002-10-26 18:53 ` Greg KH
2002-10-26 22:21 ` Kevin Brosius [this message]
2002-10-26 17:11 ` Greg KH
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=3DBB156E.8AB7C79D@compuserve.com \
--to=cobra@compuserve.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.name \
/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
Powered by JetHome