public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	John Stultz <johnstul@us.ibm.com>
Subject: Re: X fails to start with latest Linus git
Date: Sun, 27 Jan 2008 13:41:20 +0100	[thread overview]
Message-ID: <20080127124120.GA23377@elte.hu> (raw)
In-Reply-To: <20080127123702.GB21282@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> it seems you've got hpet active by default:
> 
>  /sys/devices/system/clocksource/clocksource0/current_clocksource:
>  hpet
>  /sys/devices/system/clocksource/clocksource0/available_clocksource:
>  hpet acpi_pm pit jiffies tsc

btw., it's quite mysterious how this can lock up. ktime_get() on a hpet 
clocksource does a very straightforward:

 static cycle_t read_hpet(void)
 {
         return (cycle_t)hpet_readl(HPET_COUNTER);
 }

which is a very simple thing:

c0119470 <hpet_readl>:
c0119470:       8b 15 b8 b4 ae c0       mov    0xc0aeb4b8,%edx
c0119476:       55                      push   %ebp
c0119477:       89 e5                   mov    %esp,%ebp
c0119479:       5d                      pop    %ebp
c011947a:       01 d0                   add    %edx,%eax
c011947c:       8b 00                   mov    (%eax),%eax
c011947e:       c3                      ret

basically just a memory access to an ioremap()-ed area.

hm, perhaps it's due to the xtime lock dependency:

        do {
                seq = read_seqbegin(&xtime_lock);
                getnstimeofday(ts);
                tomono = wall_to_monotonic;

        } while (read_seqretry(&xtime_lock, seq));

perhaps your system somehow generates a printk from within an xtime_lock 
locked section?

	Ingo

  reply	other threads:[~2008-01-27 12:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-27  0:19 X fails to start with latest Linus git Kevin Winchester
2008-01-27  0:35 ` Kevin Winchester
2008-01-27  6:27   ` Ingo Molnar
2008-01-27 10:42     ` Jan Engelhardt
2008-01-27 12:31     ` Kevin Winchester
2008-01-27 12:35       ` Ingo Molnar
2008-01-27 23:08         ` Kevin Winchester
2008-01-27 12:37       ` Ingo Molnar
2008-01-27 12:41         ` Ingo Molnar [this message]
2008-01-27 12:42           ` Ingo Molnar
2008-01-27 23:12             ` Kevin Winchester
2008-01-27 23:35             ` Kevin Winchester
2008-01-27 23:10         ` Kevin Winchester
2008-01-27  7:12 ` [git pull] printk fix (was: Re: X fails to start with latest Linus git) Ingo Molnar

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=20080127124120.GA23377@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=johnstul@us.ibm.com \
    --cc=kjwinchester@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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