From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Timo Lindemann" <tlindemann@arcor.de>
Cc: linux-kernel@vger.kernel.org, "David Brownell" <david-b@pacbell.net>
Subject: Re: PROBLEM: kernel hang in ohci init
Date: Sun, 16 Sep 2007 16:17:29 +0530 [thread overview]
Message-ID: <a781481a0709160347t647fab9fs505dd053f3fe203d@mail.gmail.com> (raw)
In-Reply-To: <a781481a0709160343l530b067bg55a4679e1cf864ab@mail.gmail.com>
On 9/16/07, Satyam Sharma <satyam.sharma@gmail.com> wrote:
> Hi Timo,
>
>
> On 7/15/07, Timo Lindemann <tlindemann@arcor.de> wrote:
> > 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.
>
> Any updates on this for us? Or did the kernel start booting magically again
> ca. 2.6.23-rc6? ;-)
Should again add that best would still be to simply git-bisect Linus' (mainline)
kernel tree between 2.6.20 (not 2.6.20.6) and 2.6.22 and just find the commit
after which your box stops booting ...
> Anyway, it appears the bug got introduced sometime between 2.6.20 and
> 2.6.22 so probably bugzilla becomes a better place to track this one. Could
> you open up a bug report (similar to your original post) there?
>
> Thanks,
>
> Satyam
>
next prev parent reply other threads:[~2007-09-16 10:47 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
2007-07-15 11:49 ` Timo Lindemann
2007-09-16 10:43 ` Satyam Sharma
2007-09-16 10:47 ` Satyam Sharma [this message]
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=a781481a0709160347t647fab9fs505dd053f3fe203d@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®