Re: [SuSE Linux] 2.2 Boot problems

Bill C. Riemers (bcr@feynman.com)
Thu, 10 Jun 1999 14:17:54 -0400


"Andre M. Hedrick" wrote:
>
> On Thu, 10 Jun 1999, Bill C. Riemers wrote:
> > > Tell us what you rip apart and why.
> > > For the record, Mark is "The Former-Linux IDE guy" bestowing me the task.
> > >
> > > Now which "PIIX" is the problem??? PIIXa-PIIXb-PIIX3-PIIX4
> >
> > You've seen the boot log, so you know probably more than I do. The PIIX messages are

OK. Then to review, here is the output I get during a boot. (Most of this scrolls by
too fast to read, but I captured it with my video camera:

compressing Linux... Ok, booting the kernel.
Linux version 2.2.7 (root@cc343841-a) (gcc version 2.7.2.3) #1
07:47 EDT 1999
mapped APIC to ffffe000 (00239000)
mapped IOAPIC to ffffd000 (0023a000)
Detect 451031641 Hz processor.
Console: colour VGA+ 80x24
Calibrating delay loop... 448.92 BogoMIPS
Memory 128116k/131072k available (896k kernel code 420k ??? ...
?8k init)
Checking 386/387 compiling... OK, FPU using exception 16 error
Checking 'hlt' instruction... OK.
per-CPU timeslice cutoff: 100.00 usecs
CPU0: Intel Pentium II (Deschutes) stepping 02
SMP motherboard not detected. Using dummy APIC emulation.
PCI: PCI BIOS revision 2.10 entry at 0xfb1c0
PCI: Using configuration type 1
PCI: Probing PCI hardware Linux
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET 3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
Starting kswapd v 1.5
Detected PS/2 Mouse Port.
Serial driver version 4.27 with no serial options enabled
ttyS00 at 0x3f8 (irq = 4) is a 16660A
pty: 256 Unix98 ptys configured
Real Time Clock Driver v1.09
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, ...
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, ...
_

Now this is where it freezes the computer, so even the power button locks up. Fortunately
someone on this list pointed out the feature if I hold down on the button for 4 seconds
the machine will turn off anyway.

In comparison, this is what I get when I boot with 2.0.36 as recorded in /var/adm/boot.msg:

Inspecting /boot/System.map
Loaded 5141 symbols from /boot/System.map.
Symbols match kernel version 2.0.36.
Loaded 51 symbols from 5 modules.
klogd 1.3-3, log source = /proc/kmsg started.
<4>Memory: sized by int13 088h
<4>Console: 16 point font, 400 scans
<4>Console: colour VGA+ 80x25, 1 virtual console (max 63)
<4>pcibios_init : BIOS32 Service Directory structure at 0x000fad10
<4>pcibios_init : BIOS32 Service Directory entry at 0xfb190
<4>pcibios_init : PCI BIOS revision 2.10 entry at 0xfb1c0
<4>Probing PCI hardware.
<4>Calibrating delay loop.. ok - 450.56 BogoMIPS
<4>Memory: 127988k/131072k available (632k kernel code, 384k reserved, 2068k data)
<6>Swansea University Computer Society NET3.035 for Linux 2.0
<6>NET3: Unix domain sockets 0.13 for Linux NET3.035.
<4>Swansea University Computer Society TCP/IP for NET3.034
<4>IP Protocols: ICMP, UDP, TCP
<4>Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
<4>Checking 'hlt' instruction... Ok.
<4>Linux version 2.0.36 (root@cc343841-a) (gcc version 2.7.2.3) #12 Sat Jun 5 14:19:42 EDT 1999
<4>Starting kswapd v 1.4.2.2
<6>Serial driver version 4.13p with no serial options enabled
<6>ttyS00 at 0x03f8 (irq = 4) is a 16550A
<4>Real Time Clock Driver v1.09
<4>ide: i82371 PIIX (Triton) on PCI bus 0 function 57
<4> ide0: BM-DMA at 0xf000-0xf007
<4> ide1: BM-DMA at 0xf008-0xf00f
<4>hda: WDC AC22100H, 2014MB w/128kB Cache, CHS=1022/64/63, DMA
<4>hdb: Maxtor 91360D8, 12970MB w/256kB Cache, CHS=1653/255/63, UDMA
<4>hdc: TOSHIBA DVD-ROM SD-M1202, ATAPI CDROM drive
<4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
<4>ide1 at 0x170-0x177,0x376 on irq 15
<6>Floppy drive(s): fd0 is 1.44M
<6>FDC 0 is a post-1991 82077
<6>(scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 4/0
<6>(scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
<6>(scsi0) Warning - detected auto-termination
<6>(scsi0) Please verify driver detected settings are correct.
<6>(scsi0) If not, then please properly set the device termination
<6>(scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A when prompted
<6>(scsi0) during machine bootup.
<6>(scsi0) Cables present (Int-50 NO, Int-68 NO, Ext-68 YES)
<6>(scsi0) Downloading sequencer code... 419 instructions downloaded
<4>scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.5/3.2.4
<4> <Adaptec AHA-294X Ultra SCSI host adapter>
<4>scsi : 1 host.
<4> Vendor: HP Model: C6270A Rev: 3828
<4> Type: Processor ANSI SCSI revision: 02
<4>Detected scsi generic sga at scsi0, channel 0, id 4, lun 0
<4>scsi : detected total.
<4>Partition check:
<4> hda: hda1 hda2 < hda5 >
<4> hdb: hdb1 hdb2 < hdb5 hdb6 hdb7 hdb8 >
<4>VFS: Mounted root (ext2 filesystem) readonly.
<4>Adding Swap: 96352k swap-space (priority -1)
<4>Adding Swap: 96352k swap-space (priority -2)
<4>Adding Swap: 96352k swap-space (priority -3)
Kernel logging (proc) stopped.
Kernel log daemon terminating.

If the 2.0 and 2.2 kernels initialize in the same order, the next thing I expected to see
from the 2.2 kernel would be the equivalent of:

<4>hda: WDC AC22100H, 2014MB w/128kB Cache, CHS=1022/64/63, DMA
<4>hdb: Maxtor 91360D8, 12970MB w/256kB Cache, CHS=1653/255/63, UDMA
<4>hdc: TOSHIBA DVD-ROM SD-M1202, ATAPI CDROM drive

So, I expect it is freezing in the code that detects the hard drive geometry...

I have tried a variety of configuration options when compiling my kernel, but a quick
calculations shows, if I try all possable combinations of the IDE/PCI bus options, I'll
have 128 kernels to compile and try booting.

Versions of the kernel I have tried, to boot that have this problem:

2.1.115
2.1.122
2.2.5.SuSE
2.2.7.SuSE
2.2.0-pre7
Most of the precompiled SuSE 2.2.X kernels from SuSE 6.0 and 6.1.
(several other versions, I didn't bother to save a record of my attempt.)

> Now hold up. Are you not primary SCSI, or is my vision/memory blurring.
> Resend the missed logs, and we'll start over.

The SCSI bus only contains a scanner. So, if you thing that might be a source of problems
I can easily eliminate it from my selected compile options.

> Let's not point to SuSE until we resolve a hardware question or two.

I'm not blaiming SuSE. I'm certain I'd have the same problem with ANY linux distribution
that uses the 2.2 kernel, or even if I wasn't using a distribution at all.

Bill

-
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/