mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Timo Lindemann" <tlindemann@arcor.de>
Cc: "David Brownell" <david-b@pacbell.net>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: kernel hang in ohci init
Date: Sun, 15 Jul 2007 16:59:24 +0530	[thread overview]
Message-ID: <a781481a0707150429y22b8b10bv413f5f6ba498d3e4@mail.gmail.com> (raw)
In-Reply-To: <a781481a0707150418o35e4d60fs59cba3f835ebef67@mail.gmail.com>

On 7/15/07, Satyam Sharma <satyam.sharma@gmail.com> wrote:
> On 7/15/07, Timo Lindemann <tlindemann@arcor.de> wrote:
> [...]
> > >>> 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.

There could be another thing, of course. The kernel sources (or .config)
needn't be the only variable here -- if you're using the "old" kernel image
for the 2.6.20 kernel that works, it could be the case that perhaps you've
upgraded userspace packages (compiler/toolchain) in the meanwhile
that's causing this breakage ... so to test, try compiling the 2.6.20 on
your system again (with same .config) and see if it works now ...

  reply	other threads:[~2007-07-15 11:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12  8:53 Timo Lindemann
2007-07-13  3:15 ` Satyam Sharma
2007-07-13  3:40   ` David Brownell
2007-07-15 10:41     ` Timo Lindemann
2007-07-15 11:18       ` Satyam Sharma
2007-07-15 11:29         ` Satyam Sharma [this message]
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=a781481a0707150429y22b8b10bv413f5f6ba498d3e4@mail.gmail.com \
    --to=satyam.sharma@gmail.com \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tlindemann@arcor.de \
    /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®