From: Johannes Erdfelt <johannes@erdfelt.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB-related lockup in test12-pre5
Date: Thu, 7 Dec 2000 13:40:14 -0500 [thread overview]
Message-ID: <20001207134013.L935@sventech.com> (raw)
In-Reply-To: <11659.976180540@redhat.com>
In-Reply-To: <11659.976180540@redhat.com>; from David Woodhouse on Thu, Dec 07, 2000 at 09:15:40AM +0000
On Thu, Dec 07, 2000, David Woodhouse <dwmw2@infradead.org> wrote:
> Haven't tried test12-pre7 yet. Is enabling bus mastering likely to make
> this magically go away? I doubt it.
Probably not. Enabling bus mastering is the difference between USB
working at all (transfering data to the device) and not working.
> This happened when trying to run excel under wine. Dual Celeron with
> CONFIG_USB_UHCI.
Could you try the alternate UHCI driver? You may need to disable the
UHCI driver you have configured for the option to become visible.
> >>EIP; c0270c21 <stext_lock+4e6d/8f50> <=====
> Trace; c01f488e <usb_submit_urb+1e/30>
> Trace; ca8578be <[audio]usbout_completed+7e/c0>
> Trace; c01ffc3e <process_urb+1de/230>
> Trace; c01ffd49 <uhci_interrupt+b9/120>
It looks like you were using USB audio? Could you explain what you were
doing when the oops happened?
JE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-07 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 9:15 USB-related lockup in test12-pre5 David Woodhouse
2000-12-07 18:40 ` Johannes Erdfelt [this message]
2000-12-08 23:23 ` David Woodhouse
2000-12-09 0:54 ` Johannes Erdfelt
2000-12-09 1:05 ` Johannes Erdfelt
2000-12-09 8:34 ` David Woodhouse
2000-12-09 14:00 ` [FIXED] " David Woodhouse
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=20001207134013.L935@sventech.com \
--to=johannes@erdfelt.com \
--cc=dwmw2@infradead.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 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.