All of lore.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-kernel@vger.kernel.org, bunk@stusta.de, jikos@jikos.cz
Subject: Re: [BUG] no boot with 2.6.21-rc3 and later
Date: Wed, 21 Mar 2007 15:24:12 -0700	[thread overview]
Message-ID: <1174515853.5477.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20070321220038.5D962DBA1@gherkin.frus.com>

On Wed, 2007-03-21 at 16:00 -0600, Bob Tracy wrote:
> john stultz wrote:
> > Hmmm. Are you able to capture a full dmesg?
> 
> For the "it hangs" case, short of either trying to boot with the
> console I/O redirected to a serial port or hooking up a printer to
> the console and scanning in the resulting output, I don't think so.
> There's too much output prior to the hang point to make manual
> transcription feasible.

Hmm. You could give netconsole a try(see
Documentation/networking/netconsole.txt), although if the hang is before
that inits you might be out of luck.

> > Also, does booting w/ "clocksource=jiffies" change the behavior?
> 
> I'll build a post-"bad"-commit kernel later this evening and let you
> know.  Unfortunately, real life has to intrude for a few hours :-).

No problem. When you can get to it. :)

Also trying booting w/ "notsc" would be a useful data point.

> If specifying the clocksource allows for a normal bootup, would you
> like to see the corresponding dmesg output?

No, although a pre-bad-commit dmesg would help.

thanks
-john


  reply	other threads:[~2007-03-21 22:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 19:54 [BUG] no boot with 2.6.21-rc3 and later Bob Tracy
2007-03-21 20:18 ` Bartlomiej Zolnierkiewicz
2007-03-21 21:34   ` john stultz
2007-03-21 22:00     ` Bob Tracy
2007-03-21 22:24       ` john stultz [this message]
2007-03-22  3:45         ` Bob Tracy
2007-03-22 18:35           ` john stultz
2007-03-22 19:14             ` Bob Tracy
2007-03-22 19:25               ` john stultz
2007-03-22 19:39                 ` Bob Tracy
2007-03-22 19:56                   ` john stultz
2007-03-22 20:13                     ` Bob Tracy
2007-03-22 19:43                 ` Thomas Gleixner
2007-03-22 20:25           ` [PATCH] correct slow acpi_pm rating (fixes no boot with 2.6.21-rc3 and later) john stultz
  -- strict thread matches above, loose matches on Subject: below --
2007-03-20  1:43 [BUG] no boot with 2.6.21-rc3 and later Bob Tracy
2007-03-20  7:14 ` Jiri Kosina
2007-03-18  1:09 Bob Tracy
2007-03-18 18:59 ` Jiri Kosina

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=1174515853.5477.18.camel@localhost.localdomain \
    --to=johnstul@us.ibm.com \
    --cc=bunk@stusta.de \
    --cc=bzolnier@gmail.com \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rct@gherkin.frus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.