From: Mikhail Kshevetskiy <mikhail.kshevetskiy@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc3-hrt2 stall during boot on ASUS F3T (x86_64)
Date: Mon, 20 Aug 2007 15:32:07 +0400 [thread overview]
Message-ID: <20070820153207.278df810@localhost> (raw)
In-Reply-To: <1187602270.7007.173.camel@chaos>
On Mon, 20 Aug 2007 11:31:10 +0200
Thomas Gleixner <tglx@linutronix.de> wrote:
> On Mon, 2007-08-20 at 12:35 +0400, Mikhail Kshevetskiy wrote:
> > > > > at 73.442744: I do nothing, the kernel continue to boot after 168 sec
> > > > >
> > > > > at 243.497822: After 2 hours i press and hold "shift" button to continue booting
> > > > >
> > > > > The dmesg output and my kernel configuration are listed below.
> > > > >
> > > > > I test i386 version of the same kernel with very similar configuration, it boot normally.
> > >
> > > Can you please add "noapictimer" to the kernel command line ?
> >
> > This helps, thank you.
> > Why it is not required for i386 kernel?
> > Is it possible to fix this problem without disabling of apic timer?
>
> Probably, but we need more information about the breakage. I assume that
> the 64 bit kernel does something different with the power states on idle
>
> Can you please provide the output of /proc/acpi/processor/CPU0/power for
> both the 32 and the 64 bit kernel ?
>
> tglx
>
>
2.6.22.3 (x86_64)
====================================
kl@aspid:~$ cat /proc/acpi/processor/P001/power
active state: C0
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
2.6.23-rc3-hrt2 (x86_64, noapictimer)
====================================
kl@aspid:~$ cat /proc/acpi/processor/P001/power
active state: C0
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
C1: type[C1] promotion[--] demotion[--] latency[000] usage[00000000] duration[00000000000000000000]
2.6.23-rc3-hrt2 (x86_64)
====================================
kl@aspid:~$ cat /proc/acpi/processor/P001/power
active state: C0
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
C1: type[C1] promotion[--] demotion[--] latency[000] usage[00000000] duration[00000000000000000000]
2.6.22.1 (i386)
====================================
kl@aspid:~$ cat /proc/acpi/processor/P001/power
active state: C0
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
2.6.23-rc3-hrt2 (i386)
====================================
kl@aspid:~$ cat /proc/acpi/processor/P001/power
active state: C0
max_cstate: C8
bus master activity: 00000000
maximum allowed latency: 8000 usec
states:
C1: type[C1] promotion[--] demotion[--] latency[000] usage[00000000] duration[00000000000000000000]
prev parent reply other threads:[~2007-08-20 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 6:44 2.6.23-rc3-hrt2 stall during boot on ASUS F3T (x86_64) Mikhail Kshevetskiy
2007-08-20 6:51 ` Peter Zijlstra
2007-08-20 7:54 ` Thomas Gleixner
2007-08-20 8:35 ` Mikhail Kshevetskiy
2007-08-20 9:31 ` Thomas Gleixner
2007-08-20 11:32 ` Mikhail Kshevetskiy [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=20070820153207.278df810@localhost \
--to=mikhail.kshevetskiy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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