Re: strange SCSI boot problem on a dual pentium machine

Amos Shapira (amos@gezernet.co.il)
Wed, 09 Dec 1998 23:48:52 +0200


On Sun, December 6 1998, Alan Cox <alan@cymru.net> wrote:
|> On Sat, December 5 1998, Alan Cox <alan@cymru.net> wrote:
|> |If you build a non SMP 2.1.x kernel does it then work
|>
|> Yes.
|
|Ok thats an APIC interrupt bug of some sort. Right next move to confirm this
|get 2.1.131 and apply the 2.1.131ac4 patch from
|ftp.linux.org.uk:/pub/linux/alan/2.1/ . Boot it and ensure it still fails
|now boot it with the boot command line option "noapic". Does it then still
|fail ?

Sorry it took so long to get back to you - my faulty memory collapsed
totally as I was compiling the kernel. I just got new memory and
testted the kernel 2.1.131 with your patch 6.

It does indeed fail without noapic and succeed with noapic.

|Finally can you write down the APIC mapping table it dumps on boot (if
|the noapic option works boot that way and it'll be ok in oyur syslog)
|and mail that table and a report to linux-kernel@vger.rutgers.edu

I think these are the lines you asked about:

Dec 10 01:31:25 butch kernel: mapped APIC to ffffe000 (fee00000)
Dec 10 01:31:25 butch kernel: mapped IOAPIC to ffffd000 (fec00000)

As for a full report to linux-kernel:

The situation:

I have a Dual Pentium 200 MHz machine (Tyan Tomcat IIID mobo) which
worked fine for years. When I tried to boot 2.1.131 on it (with SMP
enabled, of course), it kept reseting the BusLogic 958 UW SCSI
controller over and over again.

With Alan Cox advice, I compiled a newer kernel (2.1.131ac6) and tried
to boot it once as is (it did its thing again) and once with "noapic"
on the boot command line. The "noapic" seems to have fixed that since
the kernel boots fine that way.

The interesting part is as follows:

A friend of mine owns exactly the same hardware (same mobo, two
Pentium 200, same SCSI controller, same SCSI disk) but have no problem
with that. The only significant hardware difference I see is that my
machine dropped its clock rate to (what it reports as) 193MHz a couple
of months ago (probably due to installing a 3.3v EDO memory with 5v
settings), but otherwise kept working fine under 2.0.35 kernels.

I kept around the full kernel boot log in case anyone wants it.

Thanks,

--Amos

--Amos Shapira | "Of course Australia was marked for
133 Shlomo Ben-Yosef st. | glory, for its people had been chosen
Jerusalem 93 805 | by the finest judges in England."
ISRAEL amos@gezernet.co.il | -- Anonymous

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/