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: Tue, 2 Mar 2010 13:04:18 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1003021302360.4245@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.1003012114470.4245@localhost.localdomain>

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

Asbjørn,

can you please run the following tests and report the results ?

1) Add "maxcpus=1" to the kernel command line

2) Add "nomsi" to the kernel command line

Thanks,

	tglx

  reply	other threads:[~2010-03-02 12:05 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
2010-03-02 12:04       ` Thomas Gleixner [this message]
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.1003021302360.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