public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [2.6.23-rc8-mm2] System hangs (loops?) during boot
Date: Sun, 30 Sep 2007 23:50:29 +0200	[thread overview]
Message-ID: <200709302350.30612.elendil@planet.nl> (raw)
In-Reply-To: <20070930154424.68e4218e@laptop.hypervisor.org>

On Sunday 30 September 2007, you wrote:
> On Sat, 29 Sep 2007 13:02:34 -0700 Andrew Morton (AM) wrote:
> AM> On Sat, 29 Sep 2007 21:40:22 +0200 Frans Pop wrote:
> AM> > 3fe6c0016fd863b233097a8219a0d8577c2fd503 is first bad commit
> AM> > commit 3fe6c0016fd863b233097a8219a0d8577c2fd503
> AM> > Author: Udo A. Steinberg <...>
> AM> >     hpet-force-enable-on-ich34
> AM> >
> AM> > Guess the comments about thin ice and testing were justified :-)
> AM> >
> AM> Great, thanks for doing that.
> AM>
> AM> I guess I'll drop the patch for now in that case.
>
> I somehow doubt that the HPET patch itself is the culprit. In fact, the
> reason it shows up on git-bisect is probably because without it HPET
> functionality is not enabled on the platform. So the problem could really
> be anywhere in the HPET-driven timer infrastructure.
>
> Frans, could you try out the -hrt patchset from Thomas Gleixner and see
> if that works? 

I'm not sure what you mean. I fetched the branch I think you referred to 
[1], but when I did a merge of that on top of v2.6.23-rc8-mm2 I 
got "Already up-to-date", so AFAICT that branch is fully merged into mm and 
I'm already running with you latest code...
Please correct me if I'm doing anything wrong.

[1] git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-hrt

> Also, what ICH does your platform have? ICH3 or ICH4?

It is ICH4.
See the link below (which I already included) for more details:
> AM> > lspci and a 2.6.23-rc6 dmesg for this system can be found in:
> AM> > http://lkml.org/lkml/2007/9/19/300

Cheers,
FJP

  reply	other threads:[~2007-09-30 21:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28 20:25 [2.6.23-rc8-mm2] System hangs (loops?) during boot Frans Pop
2007-09-29  0:32 ` Frans Pop
2007-09-29  8:37   ` Andrew Morton
     [not found]     ` <200709292140.23593.elendil@planet.nl>
2007-09-29 20:02       ` Andrew Morton
2007-09-30 13:44         ` Udo A. Steinberg
2007-09-30 21:50           ` Frans Pop [this message]
2007-09-30 22:00             ` Udo A. Steinberg
2007-10-01  0:07               ` Frans Pop
2007-10-01  0:44                 ` Udo A. Steinberg
2007-10-01  1:12                   ` Frans Pop
2007-10-01  2:24                 ` Andrew Morton
2007-09-29 22:15 ` [2.6.23-rc8-mm2] kernel BUG at mm/slab.c:591! | invalid opcode: 0000 [#1] SMP Frans Pop
2007-09-30 10:45   ` Andrew Morton
2007-09-30 22:30     ` Miklos Szeredi
2007-09-30 22:59     ` [2.6.23-rc8-mm2] Fails to resume from s2mem (was:kernel BUG at mm/slab.c:591! ...) Frans Pop

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=200709302350.30612.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=us15@os.inf.tu-dresden.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