linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sean MacLennan <smaclennan@pikatech.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: USB problems in 2.6.28-rc*
Date: Sat, 15 Nov 2008 14:42:43 -0500	[thread overview]
Message-ID: <20081115144243.02ec88d0@lappy.seanm.ca> (raw)

Anybody else seeing USB problems in the 2.6.28 kernels? The warp has a
USB 1.1 port off the 440EP processor. 

In 2.6.26 we had some problems with certain USB keys, but 2.6.27 fixed
it. However, the 2.6.28 stream broke it again before rc1. We get this
twice when you try to use the usb key:

sd 0:0:0:0: [sda] 990865 512-byte hardware sectors: (507 MB/483 MiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI removable disk
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
usb 1-1: reset full speed USB device using ppc-of-ohci and address 2
sd 0:0:0:0: timing out command, waited 60s

It then seems to work. I haven't looked into it too much since we
aren't switching to 2.6.28 anytime soon (it breaks our Secure Digital
card driver).

But I am hoping somebody might know a quick fix... something like "have
you got CONFIG_x set" type answer ;)

Cheers,
   Sean

             reply	other threads:[~2008-11-15 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15 19:42 Sean MacLennan [this message]
2008-11-15 21:01 ` USB problems in 2.6.28-rc* Benjamin Herrenschmidt

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=20081115144243.02ec88d0@lappy.seanm.ca \
    --to=smaclennan@pikatech.com \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).