From: Timo Lindemann <tlindemann@arcor.de>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel hang in ohci init
Date: Sun, 15 Jul 2007 12:41:15 +0200 [thread overview]
Message-ID: <4699F9CB.5010407@arcor.de> (raw)
In-Reply-To: <200707122040.36800.david-b@pacbell.net>
David Brownell wrote:
> On Thursday 12 July 2007, Satyam Sharma wrote:
>
> Note that hangs in that file almost always mean "your BIOS is goofy".
> Hunt for BIOS settings related to USB, and change them.
This laptop's BIOS only offers "legacy support" enabled or disabled,
both of which lead to frozen kernel. I will investigate whether the GIT
tree freezes at the same point.
>>> after this, kernel apparently goes into busy waiting (fans gradually
>>> turn louder) and hangs indefinitely. I have also made sure that writel
>>> (in linux/include/asm/io.h) really is entered, but never returns.
>
> Does the current kernel.org GIT tree do the same thing? A bunch
> of USB patches were recently merged, including ISTR one in that
> area ...
It does the same thing, git5, that is. Sorry I took so long, but I didnt
get to testing this earlier.
It is just odd that up to (not including) the 2.6.21-series every kernel
boots, and after that, they just freeze.
I am kinda stumped here.
Regards
TL
--
next prev parent reply other threads:[~2007-07-15 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 8:53 PROBLEM: kernel hang in ohci init Timo Lindemann
2007-07-13 3:15 ` Satyam Sharma
2007-07-13 3:40 ` David Brownell
2007-07-15 10:41 ` Timo Lindemann [this message]
2007-07-15 11:18 ` Satyam Sharma
2007-07-15 11:29 ` Satyam Sharma
2007-07-15 11:49 ` Timo Lindemann
2007-09-16 10:43 ` Satyam Sharma
2007-09-16 10:47 ` Satyam Sharma
2007-09-16 13:19 ` Satyam Sharma
2007-07-16 5:06 ` 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=4699F9CB.5010407@arcor.de \
--to=tlindemann@arcor.de \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.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