From: Linus Torvalds <torvalds@linux-foundation.org>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: David Brownell <david-b@pacbell.net>,
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 22:29:40 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0807052212200.3016@woody.linux-foundation.org> (raw)
In-Reply-To: <200807060859.58971.arvidjaar@mail.ru>
On Sun, 6 Jul 2008, Andrey Borzenkov wrote:
> On Sunday 06 July 2008, Linus Torvalds wrote:
> >
> > 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).
>
> Looks much better; I am writing this now under 2.6.26-rc8 with above
> commit reverted.
Ok, that's certainly pretty conclusive. Thanks for the great console logs
making it so straightforward to narrow it down to this (even if it was
just a wild guess - with your extensive logs it was still fairly
informed).
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.
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
controlle is the ALI M5237).
For all I know, that may not be the best possible chipset out there, but
it's not something extremely odd either. The machine may be a bit long in
the tooth by now (I think it's a 750MHz PIII in there), but that may also
explain why most developers wouldn't have seen this issue..
Hmm?
Linus
next prev parent reply other threads:[~2008-07-06 5:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 7:08 All 2.6.26-rcX hang immediately after loading ohci_hcd 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 [this message]
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.0807052212200.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.