lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 5 Jul 2008 22:29:40 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Andrey Borzenkov <arvidjaar@...l.ru>
cc:	David Brownell <david-b@...bell.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-usb@...r.kernel.org, Alan Stern <stern@...land.harvard.edu>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: All 2.6.26-rcX hang immediately after loading ohci_hcd



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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ