2.1.99+ boot hang with IDEDMA and K6/VP2

noel@megsinet.net
Fri, 29 May 1998 00:06:49 -0400 (EDT)

I've got a K6/200 on an FIC PA-2012 motherboard (VIA Apollo VP2
chipset -- Intel Outside ;-). The kernel hangs at some point
during the boot process whenever I enable CONFIG_BLK_DEV_IDEDMA.
The point at which it hangs does not seem to be deterministic.
Sometimes it makes it as far as mounting the filesystems before
hanging, other times it hangs when trying to run init (or /bin/sh
when I use init=/bin/sh).

The hang seems complete. Magic SysReq doesn't do a thing. I don't
have this thing on a network, so I can't check if it responds to
pings, though.

I've chased it back through the versions...2.1.98 works with
IDEDMA turned on, while 2.1.99 through 2.1.104-pre1 all hang
with depressing regularity.

I trimmed 2.1.99 down to nearly the absolute minimum needed
to boot (see .config below) before I found that it's IDEDMA, and it's
consistent. IDEDMA=y always hangs during boot, IDEDMA=n always
boots fine.

I tried removing the peripheral boards (serial and sound),
but that didn't help.

Other things that have been mentioned recently on the list:

I'm using gcc 2.7.2.3, so it shouldn't be the compiler.

I've tried backing down to binutils 2.8.?, as well as 2.9 and
2.9.1 -- again, no change in the behaviour.

There've been a number of other emails on the list recently
with hangs like this -- have y'all tried turning off IDEDMA?

Hardware details:

Motherboard: FIC PA-2012 MB (VIA Apollo VP2)
RAM: 1 - 64MB ECC SDRAM DIMM
hda: Maxtor 90576D4, ATA DISK drive
hdb: ATAPI CDROM, ATAPI CDROM drive
hdc: QUANTUM LPS270A, ATA DISK drive
hdd: JTS CORPORATION CHAMPION MODEL C2100-2A, ATA DISK drive
video: Matrox Millennium II (4MB)
other boards: 16650 serial port board
SoundBlaster AWE64 PNP

Oh, in case it helps, here's the .config I used for 2.1.99
when I finally found what was doing it:

CONFIG_M686=y
CONFIG_NET=y
CONFIG_PCI=y
CONFIG_PCI_BIOS=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_BINFMT_ELF=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_PARIDE_PARPORT=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_NOSR=y
CONFIG_SKB_LARGE=y
CONFIG_EXT2_FS=y
CONFIG_PROC_FS=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_VGA_CONSOLE=y

I'm not much of a kernel hacker, but if someone could let me
know what else to check, I'd be delighted...

-- 
      Availability may be limited, especially during peak hours.
                                          - America On Line TV ad
Noel Maddy <noel@megsinet.net>




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu