From: Borislav Petkov <bbpetkov@yahoo.de>
To: David Brownell <david-b@pacbell.net>
Cc: Borislav Petkov <bbpetkov@yahoo.de>,
Aleksey Gorelov <Aleksey_Gorelov@Phoenix.com>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
greg@kroah.com
Subject: Re: Linux 2.6.14 ehci-hcd hangs machine
Date: Wed, 2 Nov 2005 14:33:28 +0100 [thread overview]
Message-ID: <20051102133328.GA16365@gollum.tnic> (raw)
In-Reply-To: <200511011018.05117.david-b@pacbell.net>
On Tue, Nov 01, 2005 at 10:18:04AM -0800, David Brownell wrote:
> On Tuesday 01 November 2005 3:23 am, Borislav Petkov wrote:
> > Yeah, the symptoms are really weird. Let me rehash the whole history:
> > First, we did some testing with 2.6.14-rc4, _with_ the patch and the
> > 'handoff' cmd option and it worked. Then, several boots later, I noticed
> > that it started hanging itself again at the same position not while rebooting
> > but at _initial_ boot in the morning. ...
>
> So you're saying your hardware doesn't act consistently.
> Is there a BIOS update you can try? The failure sure seems
> to be board-specific.
Just did a BIOS update - the 2.6.14 git version from yesterday booted
just fine.
>
>
> > ... 2.6.13, in contrast, boots just fine. Hope
> > that helps,
>
> Well that's news, and not mentioned in the bug report; in fact, you
> said explicitly that it _never_ worked on earlier kernels (see your
> comment #2).
Ups, my bad, i got kinda confused by the formulation "most recent kernel
where..", sorry.
> This means you could use "git bisect" to point a finger at a patch that,
> if it doesn't actually cause the problem, at least surfaces a latent bug
> in other code. Could you please try that?
>
> I'm starting to suspect some IRQ setup problem here; those are classically
> issues in ACPI code, even when the breakage shows only with USB.
This is superfluous, I guess, now that 2.6.14 boots.
Thanks for your help.
Regards,
Boris.
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
next prev parent reply other threads:[~2005-11-02 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 17:53 Aleksey Gorelov
2005-10-31 22:15 ` Borislav Petkov
2005-11-01 0:24 ` David Brownell
2005-11-01 11:23 ` Borislav Petkov
2005-11-01 18:18 ` David Brownell
2005-11-02 13:33 ` Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-28 0:28 Linux 2.6.14 Linus Torvalds
2005-10-30 7:36 ` Linux 2.6.14 ehci-hcd hangs machine Borislav Petkov
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=20051102133328.GA16365@gollum.tnic \
--to=bbpetkov@yahoo.de \
--cc=Aleksey_Gorelov@Phoenix.com \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®