From: crosser@average.org (Eugene Crosser)
To: linux-kernel@vger.kernel.org
Subject: Re: Patch for bizzare oops in USB
Date: 21 Aug 2001 02:12:35 +0400 [thread overview]
Message-ID: <9ls20j$g3f$1@pccross.average.org> (raw)
In-Reply-To: <3B80FBA9.556B7B2B@scs.ch>
In article <3B80FBA9.556B7B2B@scs.ch>,
Thomas Sailer <sailer@scs.ch> writes:
>> --- linux-2.4.8/drivers/usb/usb.c Tue Jul 24 14:20:56 2001
>> +++ linux-2.4.8-e/drivers/usb/usb.c Fri Aug 17 22:03:27 2001
>> @@ -1066,7 +1066,7 @@
>>
>> awd.wakeup = &wqh;
>> init_waitqueue_head(&wqh);
>> - current->state = TASK_INTERRUPTIBLE;
>> + current->state = TASK_UNINTERRUPTIBLE; /* MUST BE SO. -- zaitcev */
>> add_wait_queue(&wqh, &wait);
>> urb->context = &awd;
>> status = usb_submit_urb(urb);
>
> This is bad for other users of usb_control_msg/usb_bulk_msg that depend on
> the sleep to be interruptible. Instead of bouncing back and forth whether
> those routines shall sleep interruptibly or uninterruptibly, we should either
> provide two routines or a parameter that specifies whether the sleep
> shall be interruptible, or create a local version of usb_control_msg
> if ov511 is the only user requiring uninterruptible sleep.
I observe similar Oops with D-Link USB radio tuner on uhci when I hit
Ctrl-C (SMP system, UP system with ohci works). I was preparing to
post ksymoops report when I read Pete's message ;)
Eugene
prev parent reply other threads:[~2001-08-20 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-18 5:31 Patch for bizzare oops in USB Pete Zaitcev
2001-08-20 11:59 ` Thomas Sailer
2001-08-20 21:06 ` Pete Zaitcev
2001-08-21 8:29 ` Thomas Sailer
2001-08-20 21:44 ` Pete Zaitcev
2001-08-21 4:01 ` Johannes Erdfelt
2001-08-21 4:17 ` Pete Zaitcev
2001-08-20 22:12 ` Eugene Crosser [this message]
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='9ls20j$g3f$1@pccross.average.org' \
--to=crosser@average.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox