The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: bugzilla-daemon@bugzilla.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	"pm list" <linux-pm@lists.linux-foundation.org>,
	"Andreas Herrmann" <andreas.herrmann3@amd.com>,
	"Asbjørn Sannes" <kernelbugzilla@sannes.org>,
	"Venkatesch Pallipadi" <venkatesh.pallipadi@intel.com>
Subject: Re: [Bug 15289] Regression 2.6.32 -> 2.6.33, Kernel needs a helping key to boot :)
Date: Mon, 1 Mar 2010 22:21:39 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1003012114470.4245@localhost.localdomain> (raw)
In-Reply-To: <201003012103.00609.rjw@sisk.pl>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2087 bytes --]

On Mon, 1 Mar 2010, Rafael J. Wysocki wrote:
> [Swithing to e-mail, please keep bugzilla-daemon in the CC list.]
> 
> On Monday 01 March 2010, bugzilla-daemon@bugzilla.kernel.org wrote:
> > http://bugzilla.kernel.org/show_bug.cgi?id=15289
> > 
> > --- Comment #30 from Asbjørn Sannes <kernelbugzilla@sannes.org>  2010-03-01 06:17:06 ---
> > hm, so from what I have gathered the previously bisected commit only exposes
> > another bug (hidden by enabling hpet). So I started bisecting again, this time
> > with hpet=disabled all the way and found:
> > 
> > commit aa276e1cafb3ce9d01d1e837bcd67e92616013ac
> > Author: Thomas Gleixner <tglx@linutronix.de>
> > Date:   Mon Jun 9 19:15:00 2008 +0200
> > 
> > x86, clockevents: add C1E aware idle function
> > 
> > Reverting this from a non-working 2.6.27 makes it work also. Things have
> > changed considerably since then so I was not able to revert it from the newest
> > kernel.
> > 
> > Maybe that disabling of SBX00 hpet msi, only should be done when you do
> > actually have floppy support? Makes more people boot atleast :P
> 
> Thomas, it looks like something's missing in our C1E handling.  Can you have
> a look at this bug report, please?

Groan. We have been through that exercise of blaming the above commit
and the C1E handling for a couple of times now. It never turned out to
be the real culprit.

Looking at the various steps Asbjorn took to analyse that problem it
simply boils down to the oldest problem with timers on ATI chipsets:

       the irq0 timer interrupt routing is hosed

I have no clue yet, why this is not detected by the test logic we have
in place for that, but it might be something which gets borked later
in the boot process.

Enabling MSI for HPET just papers over the problem as it uses a
different interrupt vector and mechanism.

Disabling HPET does not help simply because PIT is using IRQ0 as well
as the MSI disabled HPET.

I need some sleep to come up with a reasonable method to debug that,
but maybe someone else has an brilliant idea before I have to twist my
brain around it.

Thanks,

	tglx

  reply	other threads:[~2010-03-01 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-15289-10028@http.bugzilla.kernel.org/>
     [not found] ` <201003010617.o216HBix024914@demeter.kernel.org>
2010-03-01 20:03   ` [Bug 15289] Regression 2.6.32 -> 2.6.33, Kernel needs a helping key to boot :) Rafael J. Wysocki
2010-03-01 21:21     ` Thomas Gleixner [this message]
2010-03-02 12:04       ` Thomas Gleixner
2010-02-21 21:25 2.6.33-rc8-git6: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-02-21 21:30 ` [Bug #15289] Regression 2.6.32 -> 2.6.33, Kernel needs a helping key to boot :) Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
2010-02-14 23:31 2.6.33-rc8: Reported regressions from 2.6.32 Rafael J. Wysocki
2010-02-14 23:38 ` [Bug #15289] Regression 2.6.32 -> 2.6.33, Kernel needs a helping key to boot :) Rafael J. Wysocki

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=alpine.LFD.2.00.1003012114470.4245@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=andreas.herrmann3@amd.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kernelbugzilla@sannes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rjw@sisk.pl \
    --cc=venkatesh.pallipadi@intel.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