linux-kernel - Re: All 2.6.26-rcX hang immediately after loading ohci

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:	Sun, 6 Jul 2008 09:35:20 +0400
From:	Andrey Borzenkov <arvidjaar@...l.ru>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
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 Sunday 06 July 2008, Linus Torvalds wrote:
> 
> 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).
> 

yes

{pts/0}% lspci -nn
00:00.0 Host bridge [0600]: ALi Corporation M1644/M1644T Northbridge+Trident [10b9:1644] (rev 01)
00:01.0 PCI bridge [0604]: ALi Corporation PCI to AGP Controller [10b9:5247]
00:02.0 USB Controller [0c03]: ALi Corporation USB 1.1 Controller [10b9:5237] (rev 03)
00:04.0 IDE interface [0101]: ALi Corporation M5229 IDE [10b9:5229] (rev c3)
00:06.0 Multimedia audio controller [0401]: ALi Corporation M5451 PCI AC-Link Controller Audio Device [10b9:5451] (rev 01)
00:07.0 ISA bridge [0601]: ALi Corporation M1533/M1535 PCI to ISA Bridge [Aladdin IV/V/V+] [10b9:1533]
00:08.0 Bridge [0680]: ALi Corporation M7101 Power Management Controller [PMU] [10b9:7101]
00:0a.0 Ethernet controller [0200]: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 [8086:1229] (rev 08)
00:10.0 CardBus bridge [0607]: Texas Instruments PCI1410 PC card Cardbus Controller [104c:ac50] (rev 01)
00:11.0 CardBus bridge [0607]: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support [1179:0617] (rev 32)
00:11.1 CardBus bridge [0607]: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support [1179:0617] (rev 32)
00:12.0 System peripheral [0880]: Toshiba America Info Systems SD TypA Controller [1179:0805] (rev 03)
01:00.0 VGA compatible controller [0300]: Trident Microsystems CyberBlade XPAi1 [1023:8820] (rev 82)

Handle 0x0001, DMI type 1, 25 bytes
System Information
        Manufacturer: TOSHIBA
        Product Name: PORTEGE 4000
        Version: PP400E-0CJPX-0V
        Serial Number: Z1109698G
        UUID: 440FA000-001B-11D6-8000-C3D0A1109698
        Wake-up Type: Power Switch



> 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
> 
> 



Download attachment "signature.asc " of type "application/pgp-signature" (198 bytes)