public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Carlos R. Mafra" <crmafra2@gmail.com>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Bug #10117] 2.6.25-current-git hangs on boot (pci=nommconf helps)
Date: Wed, 9 Apr 2008 07:42:53 -0300	[thread overview]
Message-ID: <20080409104253.GA3786@localhost.ift.unesp.br> (raw)
In-Reply-To: <1207731482.9487.46.camel@localhost>

On Wed  9.Apr'08 at 10:58:02 +0200, Soeren Sonnenburg wrote:
> On Wed, 2008-04-09 at 01:02 +0200, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of recent regressions.
> > 
> > The following bug entry is on the current list of known regressions
> > from 2.6.24.  Please verify if it still should be listed.
> > 
> > 
> > Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=10117
> > Subject		: 2.6.25-current-git hangs on boot (pci=nommconf helps)
> > Submitter	: Soeren Sonnenburg <kernel@nn7.de>
> > Date		: 2008-02-23 18:55 (46 days old)
> > References	: http://lkml.org/lkml/2008/2/23/263
> > 		  http://lkml.org/lkml/2008/4/4/41
> 
> I could not anymore trigger this, though suddenly Carlos...

Yes, I can reproduce it with 10% chance. I will also reply in another
thread to Venkatesh, but here it goes:

1) Does not hang with CONFIG_CPUIDLE=n (17 boots OK)

2) It hangs with processor.max_cstate=2 (hung at the 10th boot)

3) Does not hang with processor.max_cstate=1 (20 boots OK)

      reply	other threads:[~2008-04-09 10:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08 23:02 [Bug #10117] 2.6.25-current-git hangs on boot (pci=nommconf helps) Rafael J. Wysocki
2008-04-09  8:58 ` Soeren Sonnenburg
2008-04-09 10:42   ` Carlos R. Mafra [this message]

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=20080409104253.GA3786@localhost.ift.unesp.br \
    --to=crmafra2@gmail.com \
    --cc=kernel@nn7.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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