mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Linus Torvalds <torvalds@linux-foundation.org>
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: Sun, 6 Jul 2008 09:35:20 +0400	[thread overview]
Message-ID: <200807060935.21678.arvidjaar@mail.ru> (raw)
In-Reply-To: <alpine.LFD.1.10.0807052212200.3016@woody.linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 3380 bytes --]

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



[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-07-06  5:35 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 [this message]
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=200807060935.21678.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=akpm@linux-foundation.org \
    --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 \
    --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®