public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob McElrath <mcelrath+linux@draal.physics.wisc.edu>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB UHCI broken again w/ visor
Date: Tue, 28 Aug 2001 10:53:30 -0500	[thread overview]
Message-ID: <20010828105330.S16752@draal.physics.wisc.edu> (raw)
In-Reply-To: <20010828013239.N16752@draal.physics.wisc.edu> <20010828083537.B7376@kroah.com>
In-Reply-To: <20010828083537.B7376@kroah.com>; from greg@kroah.com on Tue, Aug 28, 2001 at 08:35:37AM -0700

[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]

Greg KH [greg@kroah.com] wrote:
> On Tue, Aug 28, 2001 at 01:32:40AM -0500, Bob McElrath wrote:
> > USB verbose debug is ON, using driver usb-uhci, on an alpha, kernel
> > 2.4.9, new batteries in the thing.  This worked with 2.4.7.  What
> > happened?  It seems like every other kernel version it gets broken
> > again, and I can't sync my visor.
> 
> It looks like your uhci controller is not getting interrupts anymore.
> Does the value of /proc/interrupts for the usb-uhci driver get
> incremented?

No, it seems stuck at a non-zero value.

(0)<mcelrath@draal:/home/mcelrath/minijam> cat /proc/interrupts
  1:     224376          XT-PIC   keyboard
  2:          0          XT-PIC   cascade
  8:  250012322             RTC  +timer
 11:    3019583          XT-PIC   PAS16
 12:    1891610          XT-PIC   PS/2 Mouse
 14:      60292          XT-PIC  +ide0
 16:     650152       CABRIOLET   BusLogic BT-958
 18:      23085       CABRIOLET   usb-uhci
 19:     304381       CABRIOLET   eth0
 20:          0       CABRIOLET   isa-cascade
ERR:          0

The non-zero value is probably because I was using another device.

> Does any other usb devices work on this system?

Yes, I have a SanDisk ImageMage (SDDR-12) that sorta-works with the
usb-storage driver.

The device times out though after transferring a few files.  I don't
know if the problem is with the usb-storage driver, usb-uhci, or the
device itself.  But this problem has existed for a long time, and OHCI
users don't report this problem.  (using usb-storage with this device
and my little program to transfer files to it:
http://www.sourceforge.net/projects/mj-tools/)  I haven't been able to
track this bug down yet...

The behaviour of the usb-storage stuff is unchanged from 2.4.7, but the
visor definitely did work with 2.4.7, where it doesn't now.

Thanks,
-- Bob

P.S. please CC me as I am not on linux-kernel.

Bob McElrath (rsmcelrath@students.wisc.edu) 
Univ. of Wisconsin at Madison, Department of Physics

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

  reply	other threads:[~2001-08-28 15:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-28  6:32 USB UHCI broken again w/ visor Bob McElrath
2001-08-28 15:35 ` Greg KH
2001-08-28 15:53   ` Bob McElrath [this message]
2001-08-28 16:01     ` Greg KH
2001-08-28 16:08       ` Bob McElrath
2001-08-28 16:18         ` Greg KH
2001-08-28 16:36           ` Bob McElrath

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=20010828105330.S16752@draal.physics.wisc.edu \
    --to=mcelrath+linux@draal.physics.wisc.edu \
    --cc=greg@kroah.com \
    --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