From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Brownell <david-b@pacbell.net>
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: Sat, 5 Jul 2008 17:28:58 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0807051724090.3016@woody.linux-foundation.org> (raw)
In-Reply-To: <200807051704.56141.david-b@pacbell.net>
On Sat, 5 Jul 2008, David Brownell wrote:
>
> I seem to recall some oddness with RHSC on some platforms,
> way back when I had lots of OHCI hardware and did comparative.
> testing. RHSC and RD did not act quite like the docs said ...
>
> Simple experiments: add "distrust_firmware=y" to the ohci
> module options. Or: try a kernel without CONFIG_PM enabled.
I think Andrey said he was leaving for a week, so I don't think he'll be
testing now.
But Andrey - if you are on-line and have access to the machine, one thing
to try would be to just do a
git revert e872154921a6b5
in case it really was that particular commit. It seems to revert cleanly
(although I didn't actually check if the result then compiled/worked).
And a "git bisect" would obviously be wonderful in case it wasn't.
Linus
next prev parent reply other threads:[~2008-07-06 0:29 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 [this message]
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
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=alpine.LFD.1.10.0807051724090.3016@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=arvidjaar@mail.ru \
--cc=david-b@pacbell.net \
--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 \
/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®