mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kevin Brosius <cobra@compuserve.com>
To: Oliver Neukum <oliver@neukum.name>, Greg KH <greg@kroah.com>
Cc: kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.44-ac3 usb audio - illegal sleep call
Date: Sat, 26 Oct 2002 14:13:42 -0400	[thread overview]
Message-ID: <3DBADB56.C782BD1D@compuserve.com> (raw)
In-Reply-To: <200210261902.32626.oliver@neukum.name>

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.


Oct 26 13:54:18 sea kernel: Debug: sleeping function called from illegal
context at mm/slab.c:1374
Oct 26 13:54:18 sea kernel: Call Trace:
Oct 26 13:54:18 sea kernel:  [<c013fd0b>] __kmem_cache_alloc+0x17b/0x180
Oct 26 13:54:18 sea kernel:  [<e0a38bb5>] ohci_urb_enqueue+0xb5/0x2d0
[ohci-hcd]
Oct 26 13:54:18 sea kernel:  [<e09b9017>] hcd_submit_urb+0x117/0x180
[usbcore]
Oct 26 13:54:18 sea kernel:  [<e09c9d20>] usb_hcd_operations+0x0/0x40
[usbcore]
Oct 26 13:54:18 sea kernel:  [<e09b993b>] usb_submit_urb+0x1db/0x250
[usbcore]
Oct 26 13:54:18 sea kernel:  [<e0a2bd45>]
usbout_sync_completed+0xe5/0x110 [audio]
Oct 26 13:54:18 sea kernel:  [<e09b9409>] usb_hcd_giveback_urb+0x19/0x30
[usbcore]
Oct 26 13:54:18 sea kernel:  [<e0a38add>] dl_done_list+0x13d/0x160
[ohci-hcd]
Oct 26 13:54:18 sea kernel:  [<e0a3945b>] ohci_irq+0xfb/0x160 [ohci-hcd]
Oct 26 13:54:18 sea kernel:  [<e09b9442>] usb_hcd_irq+0x22/0x60
[usbcore]
Oct 26 13:54:18 sea kernel:  [<c010b8c5>] handle_IRQ_event+0x45/0x70
Oct 26 13:54:18 sea kernel:  [<c010bb6a>] do_IRQ+0xba/0x160
Oct 26 13:54:18 sea kernel:  [<c0107100>] default_idle+0x0/0x50
Oct 26 13:54:18 sea kernel:  [<c010a1ba>] common_interrupt+0x42/0x58

-- 
Kevin

  reply	other threads:[~2002-10-26 18:02 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 [this message]
2002-10-26 18:53     ` Greg KH
2002-10-26 22:21       ` Kevin Brosius
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=3DBADB56.C782BD1D@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