From: James Curbo <jcurbo@acm.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: a couple of USB related Oopses
Date: Fri, 8 Mar 2002 09:26:45 -0600 [thread overview]
Message-ID: <20020308152645.GA936@carthage> (raw)
In-Reply-To: <20020305184604.GA4590@carthage> <20020305192307.GB10151@kroah.com> <20020305193317.GA5339@carthage> <20020305193732.GC10151@kroah.com> <20020306050349.GA1152@carthage> <20020307063905.GA18676@kroah.com>
In-Reply-To: <20020307063905.GA18676@kroah.com>
OK, I applied the patch; I don't get the panic anymore. I'm still
getting kernel messages like this:
usb-uhci.c: ENXIO 80000280, flags 0, urb d76c4840, burb d79b1d40
usbfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
usb-uhci.c: ENXIO 80000280, flags 0, urb d76c4840, burb d79b1d40
usbfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
usb-uhci.c: ENXIO 80000280, flags 0, urb d76c4840, burb d79b1d40
usbfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
usb-uhci.c: ENXIO 80000280, flags 0, urb d74c59c0, burb d79b1d40
usbfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
usb-uhci.c: ENXIO 80000280, flags 0, urb d74c59c0, burb d79b1d40
usbfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
usb-uhci.c: ENXIO 80000280, flags 0, urb d74c59c0, burb d79b1d40
usbfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq 6 len 18 ret -6
usb-uhci.c: ENXIO 80000280, flags 0, urb d74c5b40, burb d79b1d40
usb-uhci.c: ENXIO 80000280, flags 0, urb d74c5b40, burb d79b1d40
usb-uhci.c: ENXIO 80000280, flags 0, urb d74c5b40, burb d79b1d40
usb-uhci.c: ENXIO 80000280, flags 0, urb d74c5b40, burb d79b1d40
usb-uhci.c: ENXIO 80000280, flags 0, urb d76c4640, burb d79b1d40
usb-uhci.c: ENXIO 80000280, flags 0, urb d76c4640, burb d79b1d40
usb-uhci.c: ENXIO 80000280, flags 0, urb d76c4640, burb d79b1d40
usb-uhci.c: ENXIO 80000280, flags 0, urb d76c4640, burb d79b1d40
Also, while now I don't get the panic when I try to print, it still
doesn't print.. CUPS says "USB port busy, retrying in 30 seconds"
Unfortunately I can't remember what kernel version I was using when it
worked last.
On Mar 06, Greg KH wrote:
> Crud, missed another driver. Can you please try the patch below and let
> me know if it fixes the problem for you?
>
> thanks,
>
> greg k-h
--
James Curbo <jcurbo@acm.org> <jc108788@rc.hsu.edu>
Undergraduate Computer Science, Henderson State University
PGP Keys at <http://reddie.henderson.edu/~curboj/>
Public Keys: PGP - 1024/0x76E2061B GNUPG - 1024D/0x3EEA7288
prev parent reply other threads:[~2002-03-08 15:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 18:46 a couple of USB related Oopses James Curbo
2002-03-05 19:23 ` Greg KH
2002-03-05 19:33 ` James Curbo
2002-03-05 19:37 ` Greg KH
2002-03-06 4:02 ` James Curbo
2002-03-06 5:03 ` James Curbo
2002-03-06 9:14 ` [linux-usb-devel] " Martin Diehl
2002-03-07 6:39 ` Greg KH
2002-03-08 15:26 ` James Curbo [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=20020308152645.GA936@carthage \
--to=jcurbo@acm.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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