From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Andi Kleen <ak@suse.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: VIA x86-64 bootlogs needed
Date: Thu, 27 Jul 2006 02:35:16 +0100 [thread overview]
Message-ID: <1153964116.2865.15.camel@localhost.portugal> (raw)
In-Reply-To: <200607270333.38873.ak@suse.de>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
dmesg | grep -i lost
Bootdata ok (command line is ro root=LABEL=/1 report_lost_ticks notsc
apic=verbose)
Kernel command line: ro root=LABEL=/1 report_lost_ticks notsc
apic=verbose
time.c: Lost 576 timer tick(s)! rip console_init+0x0/0x2e)
time.c: Lost 2 timer tick(s)! rip release_console_sem+0x185/0x201)
time.c: Lost 9 timer tick(s)! rip setup_boot_APIC_clock+0x11f/0x121)
time.c: Lost 1 timer tick(s)! rip __do_softirq+0x48/0xca)
On Thu, 2006-07-27 at 03:33 +0200, Andi Kleen wrote:
> On Wednesday 26 July 2006 14:26, Sergio Monteiro Basto wrote:
> > This APIC rework have the goal of resolve problem with lost tickets ?
>
> What is a lost ticket?
>
> But unlikely. In fact it only cleans up some code.
>
> -Andi
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
next prev parent reply other threads:[~2006-07-27 1:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 16:24 VIA x86-64 bootlogs needed Andi Kleen
2006-07-25 17:32 ` Nicholas Miell
2006-07-25 22:18 ` [discuss] " Andi Kleen
2006-07-25 23:05 ` Nicholas Miell
2006-07-25 19:58 ` Bongani Hlope
2006-07-25 23:10 ` [discuss] " Jon Mason
2006-07-26 12:26 ` Sergio Monteiro Basto
2006-07-27 1:33 ` Andi Kleen
2006-07-27 1:35 ` Sergio Monteiro Basto [this message]
2006-07-27 1:29 ` Sergio Monteiro Basto
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 17:46 Hans-Frieder Vogt
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=1153964116.2865.15.camel@localhost.portugal \
--to=sergio@sergiomb.no-ip.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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