2003-06-01 15:32:43

by Bernhard Rosenkraenzer

[permalink] [raw]
Subject: 2.5.70 and 2.5.70-mm3 hang on bootup

Both 2.5.70 and 2.5.70-mm3 hang right after "Ok, booting the kernel..." on
one of my test boxes (at the point, nothing works, not even turning on/off
the NumLock LED).

Hardware: ASUS A7S333, Athlon 2600+, 1 GB RAM
Compiler: gcc 3.3

Haven't had the time to debug this yet (and probably won't have the time
for a couple more days, busy with work ATM); any ideas?

LLaP
bero


2003-06-01 17:11:50

by Stewart Smith

[permalink] [raw]
Subject: Re: 2.5.70 and 2.5.70-mm3 hang on bootup

On Monday, June 2, 2003, at 01:46 AM, Bernhard Rosenkraenzer wrote:
> Both 2.5.70 and 2.5.70-mm3 hang right after "Ok, booting the
> kernel..." on
> one of my test boxes (at the point, nothing works, not even turning
> on/off
> the NumLock LED).

Running -bk6 fixed this for me. bk5 might have worked as well, but by
the time i'd built that, bk6 was out :)

------------------------------
Stewart Smith
[email protected]
Ph: +61 4 3884 4332
ICQ: 6734154
http://www.flamingspork.com/ http://www.linux.org.au

2003-06-01 17:39:29

by John Stoffel

[permalink] [raw]
Subject: Re: 2.5.70 and 2.5.70-mm3 hang on bootup


Bernhard> Both 2.5.70 and 2.5.70-mm3 hang right after "Ok, booting the
Bernhard> kernel..." on one of my test boxes (at the point, nothing
Bernhard> works, not even turning on/off the NumLock LED).

Bernhard> Hardware: ASUS A7S333, Athlon 2600+, 1 GB RAM
Bernhard> Compiler: gcc 3.3

Make sure you've turned off APIC mode, even for UP processors. I'm
trying to get 2.5.70-mm3 working with SMP and I've narrowed it down to
an APIC problem. Doesn't matter if I'm SMP or UP if I have APIC
enabled. Booting with 'noapic' doesn't seem to help, but I'm probably
doing that part wrong.

My machine is a Dell Precision 610MT, dual 550 Mhz PIII Xeon, 440BX
chipset. Latest BIOS from Dell, but it's a pretty stripped down one,
not much to poke at.

John

2003-06-02 02:50:31

by John Stoffel

[permalink] [raw]
Subject: Re: 2.5.70 and 2.5.70-mm3 hang on bootup

>>>>> "John" == John Stoffel <[email protected]> writes:

Bernhard> Both 2.5.70 and 2.5.70-mm3 hang right after "Ok, booting the
Bernhard> kernel..." on one of my test boxes (at the point, nothing
Bernhard> works, not even turning on/off the NumLock LED).

Bernhard> Hardware: ASUS A7S333, Athlon 2600+, 1 GB RAM
Bernhard> Compiler: gcc 3.3

John> Make sure you've turned off APIC mode, even for UP processors. I'm
John> trying to get 2.5.70-mm3 working with SMP and I've narrowed it down to
John> an APIC problem. Doesn't matter if I'm SMP or UP if I have APIC
John> enabled. Booting with 'noapic' doesn't seem to help, but I'm probably
John> doing that part wrong.

John> My machine is a Dell Precision 610MT, dual 550 Mhz PIII Xeon, 440BX
John> chipset. Latest BIOS from Dell, but it's a pretty stripped down one,
John> not much to poke at.

I'm an idiot, I have a 440GX (not B) chipset, as shown by lspic:

> lspci
00:00.0 Host bridge: Intel Corporation 440GX - 82443GX Host bridge
00:01.0 PCI bridge: Intel Corporation 440GX - 82443GX AGP bridge
00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
00:0d.0 PCI bridge: Hint Corp: Unknown device 0021 (rev 13)
00:0e.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro
100] (rev 05)
00:10.0 SCSI storage controller: Adaptec AIC-7881U
00:13.0 PCI bridge: Digital Equipment Corporation DECchip 21152 (rev
03)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP
(rev 82)
02:08.0 USB Controller: NEC Corporation USB (rev 41)
02:08.1 USB Controller: NEC Corporation USB (rev 41)
02:08.2 USB Controller: NEC Corporation: Unknown device 00e0 (rev 02)
02:0b.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8020
03:0a.0 SCSI storage controller: Adaptec AHA-2940U2/W / 7890
03:0e.0 SCSI storage controller: Adaptec AIC-7880U (rev 01)

Just to follow up here, it's still not working for me with 2.5.70-bk6,
it hangs on bootup when I have UP compilied in, along with "Local APIC
support on uniprocessors".

And since I haven't been able to get 2.5.x to run in the past (though
admittedly I was always using SMP builds) I can't tell you when this
got broken.

Here's the output of /proc/version and interrupts from my currently
working 2.4.x SMP setup:

> cat /proc/version
Linux version 2.4.21-pre5-ac1 (john@jfsnew) (gcc version 2.96 20000731
(Red Hat Linux 7.2 2.96-112.7.2)) #4 SMP Thu Mar 6 17:21:37 EST 2003
> cat /proc/interrupts
CPU0 CPU1
0: 30769 31439 IO-APIC-edge timer
1: 793 791 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
5: 1 0 IO-APIC-edge Crystal audio controller
8: 1 0 IO-APIC-edge rtc
11: 7043 4241 IO-APIC-edge Cyclom-Y
12: 429 435 IO-APIC-edge PS/2 Mouse
14: 613 336 IO-APIC-edge ide0
16: 0 0 IO-APIC-level usb-ohci
17: 1323 1393 IO-APIC-level usb-ohci, eth0
18: 3966 3863 IO-APIC-level aic7xxx, aic7xxx
19: 32 28 IO-APIC-level aic7xxx
NMI: 0 0
LOC: 62121 62119
ERR: 0
MIS: 0



Here's the output from what I can boot 2.5.70-mm3 in UP mode with APIC
turned off, notice how all my devices are on Interuppt 11, and that my
Cyclom-Y ISA serial board isn't detected properly. The driver sorta
finds it, but can't get an interrupt properly.

> cat /proc/interrupts
CPU0
0: 136453 XT-PIC timer
1: 93 XT-PIC i8042
2: 0 XT-PIC cascade
9: 0 XT-PIC acpi
10: 52 XT-PIC eth0
11: 4555 XT-PIC aic7xxx, aic7xxx, aic7xxx, ehci-hcd,
uhci-hcd
12: 397 XT-PIC i8042
14: 118 XT-PIC ide0
NMI: 0
ERR: 0


Hopefully this will help people who know more than I about APIC stuff
to debug this. I'm willing to try out patches, now that 2.5.70-mm3
seems have a pretty solid RAID1 setup. Which I'll test a bit more
tonight.

John




2003-06-03 13:45:54

by John Stoffel

[permalink] [raw]
Subject: Re: 2.5.70 and 2.5.70-mm3 hang on bootup


Just a followup on my problems getting 2.5.70-mm3 up and running on my
box. Once I turned off ACPI in my config, I can now boot and run both
UP and SMP with APIC and IO-APIC running (my system actually needs
this) and I'm now running with the following:

2.5.70-mm3, SMP, PREEMPT, RAID1

All seems ok so far, no major problems except getting ALSA to work
with my sound card again, but I haven't spent much time on it yet.
I've also gotten my Cyclom-Y/ISA multiport serial board working (see
the patch I sent out seperately) properly too.

Thanks for all the help, my initial thoughts that APIC was the root of
my problem was wrong, it was all ACPI issues. Maybe we should put in
a note in the Kconfig help entries for people to disable ACPI if they
enable SMP and/or UP APIC options?

John

2003-06-03 14:46:20

by Martin Schlemmer

[permalink] [raw]
Subject: Re: 2.5.70 and 2.5.70-mm3 hang on bootup

On Tue, 2003-06-03 at 15:58, John Stoffel wrote:

> Thanks for all the help, my initial thoughts that APIC was the root of
> my problem was wrong, it was all ACPI issues. Maybe we should put in
> a note in the Kconfig help entries for people to disable ACPI if they
> enable SMP and/or UP APIC options?
>

Both my previous board (Asus P4T533-C with 850E chipset) and current
one (Asus P4C800 with 875P chipset) works fine with ACPI, APIC, and
IO-APIC enabled ....


--
Martin Schlemmer


2003-06-03 15:17:47

by John Stoffel

[permalink] [raw]
Subject: Re: 2.5.70 and 2.5.70-mm3 hang on bootup



Martin> On Tue, 2003-06-03 at 15:58, John Stoffel wrote:
>> Thanks for all the help, my initial thoughts that APIC was the root of
>> my problem was wrong, it was all ACPI issues. Maybe we should put in
>> a note in the Kconfig help entries for people to disable ACPI if they
>> enable SMP and/or UP APIC options?
>>

Martin> Both my previous board (Asus P4T533-C with 850E chipset) and
Martin> current one (Asus P4C800 with 875P chipset) works fine with
Martin> ACPI, APIC, and IO-APIC enabled ....

You have much newer chipsets that I do, I have a 440GX board. My
suggestion for the note in Kconfig is merely that if your system hangs
after printing just a couple of lines on bootup, try disabling ACPI in
your kernel.

I probably wasn't clear enough.

John