mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-usb@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>,
	Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: All 2.6.26-rcX hang immediately after loading ohci_hcd
Date: Sun, 6 Jul 2008 10:25:52 -0700	[thread overview]
Message-ID: <200807061025.52560.david-b@pacbell.net> (raw)
In-Reply-To: <alpine.LFD.1.10.0807052212200.3016@woody.linux-foundation.org>

On Saturday 05 July 2008, Linus Torvalds wrote:
> Greg, Alan, David - at this point I think the commit should just be 
> reverted. We're past -rc9, and unless either of you can see some obvious 
> alternate fix (eg some bug in the commit that explains Adrey's problems 
> that can just be fixed), I'm not seeing any good alternatives.

Right.  I tried RC9 on some OHCI hardware I have locally,
and none of it seems to have this problem.  If I had more
PCI slots, I could test more OHCI silicon ... but those
are going the way of the serial port (at least on PCs).

The only regresion I uncovered is that my OMAP1 OSK stopped
booting sometime after RC2; that's not because of OHCI.


> I don't know what the hardware details are, but based on the bootup 
> messages it seems to be a Toshiba motherboatd with an ALI 1535 chipset - I 
> think it's a Toshiba Portege 4000 (which would mean that the OHCI 
> controller is the ALI M5237).

I don't recall anything unusual about ALI and OHCI.  They
worked fine for me in some K6 and K7 hardware I had back
then ... then they got renamed to ULI, bought by NVidia,
and killed.

- Dave


      parent reply	other threads:[~2008-07-06 17:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-05  7:08 Andrey Borzenkov
2008-07-05 20:51 ` Linus Torvalds
2008-07-06  0:04   ` David Brownell
2008-07-06  0:28     ` Linus Torvalds
2008-07-06  4:59       ` Andrey Borzenkov
2008-07-06  5:29         ` Linus Torvalds
2008-07-06  5:35           ` Andrey Borzenkov
2008-07-06 16:40           ` Alan Stern
2008-07-11  5:03             ` Andrey Borzenkov
2008-07-11 14:16               ` Alan Stern
2008-07-06 17:25           ` David Brownell [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=200807061025.52560.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@linux-foundation.org \
    --cc=arvidjaar@mail.ru \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®