mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Dmitry Nezhevenko <dion@inhex.net>,
	herton@mandriva.com.br,
	Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.27-rc5 doesn't boot on a Pavilion laptop
Date: Wed, 3 Sep 2008 16:07:05 -0300	[thread overview]
Message-ID: <20080903160705.0efd7308@doriath.conectiva> (raw)
In-Reply-To: <alpine.LFD.1.10.0809032030271.3243@apollo.tec.linutronix.de>

Em Wed, 3 Sep 2008 20:40:55 +0200 (CEST)
Thomas Gleixner <tglx@linutronix.de> escreveu:

| >  As the dmesg has various WARN_ON() outputs I'm attaching it, this is
| > the first one:
| > 
| > """
| > PCI: Using ACPI for IRQ routing
| > DMAR:parse DMAR table failure.
| > hpet0: at MMIO 0xfed00000, IRQs 2, 8, 31
| > hpet0: 3 32-bit timers, 25000000 Hz
| > Switched to high resolution mode on CPU 0
| >
| > tick_broadcast_set_event is stuck f09fa64 f0a01e4
| 
| Hmm, so we fail to force program that HPET with the standard minimum
| delta.
| 
| I now see why this is happening and it is happening only on systems
| with a fast HPET. Your's running 25MHz, so the delta is only 1.92
| usec. I was staring at lots of those bugreports without noticing the
| frequency.
| 
| Sigh. The idea to take a fixed number of HPET cycles as the minimum
| was not really brilliant it seems.
| 
| Does the patch below help ? Keep the debug patch applied, as we can
| see whether the check triggers or not.

 Yeah, it works. I have booted three times with no warnings.

 I will revert the debug patch and test again just to be sure, if
this is of any help:

Tested-by: Luiz Fernando N. Capitulino <lcapitulino@mandriva.com.br>

 By the way, is this the definitive fix?

-- 
Luiz Fernando N. Capitulino

  parent reply	other threads:[~2008-09-03 19:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02 19:35 Luiz Fernando N. Capitulino
2008-09-02 20:18 ` Thomas Gleixner
2008-09-02 20:40   ` Diego Woitasen
2008-09-03 13:38     ` Luiz Fernando N. Capitulino
2008-09-02 20:55   ` Luiz Fernando N. Capitulino
2008-09-03 10:04     ` Thomas Gleixner
2008-09-03 13:41       ` Luiz Fernando N. Capitulino
2008-09-03 14:36         ` Thomas Gleixner
2008-09-03 15:15           ` Thomas Gleixner
2008-09-03 16:40             ` Luiz Fernando N. Capitulino
2008-09-03 16:44             ` Dmitry Nezhevenko
2008-09-03 17:05               ` Thomas Gleixner
2008-09-03 17:36                 ` Luiz Fernando N. Capitulino
2008-09-03 18:40                   ` Thomas Gleixner
2008-09-03 19:01                     ` Dmitry Nezhevenko
2008-09-03 19:08                       ` Thomas Gleixner
2008-09-03 19:21                         ` Dmitry Nezhevenko
2008-09-03 19:35                           ` Thomas Gleixner
2008-09-03 19:07                     ` Luiz Fernando N. Capitulino [this message]
2008-09-03 19:10                       ` Thomas Gleixner
2008-09-03 19:36                         ` Luiz Fernando N. Capitulino
2008-09-03 17:54                 ` Dmitry Nezhevenko
2008-09-03 18:58                   ` Thomas Gleixner
2008-09-03 16:38           ` Luiz Fernando N. Capitulino

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=20080903160705.0efd7308@doriath.conectiva \
    --to=lcapitulino@mandriva.com.br \
    --cc=dion@inhex.net \
    --cc=herton@mandriva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikhail.kshevetskiy@gmail.com \
    --cc=tglx@linutronix.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

all inboxes | Powered by JetHome®