public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timo Lindemann <tlindemann@arcor.de>
To: Satyam Sharma <satyam.sharma@gmail.com>
Cc: linux-kernel@vger.kernel.org, David Brownell <david-b@pacbell.net>
Subject: Re: PROBLEM: kernel hang in ohci init
Date: Sun, 15 Jul 2007 13:49:29 +0200	[thread overview]
Message-ID: <469A09C9.6000608@arcor.de> (raw)
In-Reply-To: <a781481a0707150429y22b8b10bv413f5f6ba498d3e4@mail.gmail.com>

To sum this up:

the userspace 2.6.20.6 (the "good" kernel) and 2.6.22 (the "bad" kernel)
were compiled in is exactly the same setup. I recompiled "good" to check
for that, earlier, but "good" also works then.

"good" does not exhibit the printks I placed in the section (the same
ones I did for "bad"), making it plausible that the section is not
executed at all.

dmesg is not captured to disk, netconsole and serial console also do not
work (they both did in the "good" kernel). Also, my keyboard does not
work with "bad" during that phase -- Magic SysRq is also not working then.

I can try to hook up the laptop to an external monitor to capture some
more dmesg, and just shoot a photo, but I am right now trying to work
with git, as Satyam suggested.

Thanks very much for reading and helping :-)

Regards,
TL

-- 


  reply	other threads:[~2007-07-15 11:49 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
2007-07-15 11:18       ` Satyam Sharma
2007-07-15 11:29         ` Satyam Sharma
2007-07-15 11:49           ` Timo Lindemann [this message]
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=469A09C9.6000608@arcor.de \
    --to=tlindemann@arcor.de \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=satyam.sharma@gmail.com \
    /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