From: "J . A . Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.4-ac2
Date: Tue, 1 May 2001 17:06:32 +0200 [thread overview]
Message-ID: <20010501170632.A1057@werewolf.able.es> (raw)
In-Reply-To: <E14uXjN-0001UN-00@the-village.bc.nu>
In-Reply-To: <E14uXjN-0001UN-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, May 01, 2001 at 12:50:07 +0200
Hi,
On 05.01 Alan Cox wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
>
Hangs after APIC init:
(bootlog from ac1)
Using local APIC timer interrupts.
calibrating APIC timer ...
.... CPU clock speed is 400.9211 MHz.
.... host bus clock speed is 100.2300 MHz.
cpu: 0, clocks: 1002300, slice: 334100
CPU0<T0:1002288,T1:668176,D:12,S:334100,C:1002300>
cpu: 1, clocks: 1002300, slice: 334100
CPU1<T0:1002288,T1:334080,D:8,S:334100,C:1002300>
checking TSC synchronization across CPUs: passed.
<ac2 stops here>
PCI: PCI BIOS revision 2.10 entry at 0xfdb81, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
Now I am going to spread printk's over the source, and set APIC_DEBUG=1,
but if someone has a clue ?
Ask for more info if it can be useful...
--
J.A. Magallon # Let the source
mailto:jamagallon@able.es # be with you, Luke...
Linux werewolf 2.4.4-ac1 #1 SMP Tue May 1 11:35:17 CEST 2001 i686
next prev parent reply other threads:[~2001-05-01 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 10:50 Linux 2.4.4-ac2 Alan Cox
2001-05-01 15:06 ` J . A . Magallon [this message]
2001-05-01 15:50 ` Hugh Dickins
2001-05-01 16:07 ` J . A . Magallon
2001-05-01 17:12 ` boris
2001-05-01 17:27 ` J . A . Magallon
[not found] ` <Pine.LNX.4.21.0105011835240.1576-100000@localhost.localdomain>
2001-05-01 18:55 ` [PATCH] " J . A . Magallon
2001-05-01 19:09 ` Mark Hahn
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=20010501170632.A1057@werewolf.able.es \
--to=jamagallon@able.es \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.