From: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.18-rcx: Dual P3 + VIA + APIC
Date: Wed, 20 Feb 2002 11:41:29 +0100 [thread overview]
Message-ID: <20020220104129.GP13774@os.inf.tu-dresden.de> (raw)
Hi,
trying to boot a 2.4.18-rc1, 2.4.18-rc2-ac1 or 2.5.5pre1 on a dual P3
with a VIA chipset hangs (randomly) at the "=====" signs, sometimes the
screen is flickering:
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check reporting enabled on CPU#0.
CPU0: Intel Pentium III (Coppermine) stepping 06
per-CPU timeslice cutoff: 731.39 usecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Booting processor 1/0 eip 2000
Initializing CPU#1
masked ExtINT on CPU#1
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Calibrating delay loop... 1874.32 BogoMIPS
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check reporting enabled on CPU#1.
CPU1: Intel Pentium III (Coppermine) stepping 06
Total of 2 processors activated (3742.10 BogoMIPS).
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
..TIMER: vector=0x31 pin1=2 pin2=0
=====
testing the IO APIC.......................
.................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 937.5155 MHz.
..... host bus clock speed is 133.9307 MHz.
cpu: 0, clocks: 1339307, slice: 446435
CPU0<T0:1339296,T1:892848,D:13,S:446435,C:1339307>
cpu: 1, clocks: 1339307, slice: 446435
=====
CPU1<T0:1339504,T1:446480,D:14,S:446505,C:1339515>
checking TSC synchronization across CPUs: passed.
Waiting on wait_init_idle (map = 0x2)
All processors have done init
=====
or it hangs after initialising the SCSI driver (sym), IDE, network etc.
seems ok:
...
sym0: SCSI BUS has been reset.
scsi0 : sym-2.1.17a
=====
It never went further.
Booting with "noapic" works, as do UP 2.4 kernels and 2.2.20 SMP
kernels.
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:04.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00:04.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)
00:04.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 16)
00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
Adam
--
Adam adam@os.inf.tu-dresden.de
Lackorzynski http://a.home.dhs.org
next reply other threads:[~2002-02-20 10:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-20 10:41 Adam Lackorzynski [this message]
2002-02-20 15:24 ` 2.4.18-rcx: Dual P3 + VIA + APIC Alan Cox
2002-02-20 15:40 ` Adam Lackorzynski
2002-02-21 17:58 ` Fernando Korndorfer
2002-02-21 20:11 ` Stephan von Krawczynski
2002-02-22 13:02 ` Adam Lackorzynski
2002-02-22 13:11 ` Stephan von Krawczynski
2002-02-22 13:54 ` Fernando Korndorfer
2002-02-22 16:45 ` Adam Lackorzynski
2002-02-22 17:04 ` Stephan von Krawczynski
2002-02-22 18:20 ` Adam Lackorzynski
2002-02-23 16:38 ` Stephan von Krawczynski
2002-02-23 17:22 ` Alan Cox
2002-02-23 22:18 ` Stephan von Krawczynski
2002-02-24 16:42 ` Martin J. Bligh
2002-02-25 13:19 ` Adam Lackorzynski
2002-02-25 15:32 ` Martin J. Bligh
2002-02-25 16:17 ` Adam Lackorzynski
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=20020220104129.GP13774@os.inf.tu-dresden.de \
--to=adam@os.inf.tu-dresden.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