Re: 2.5.2-pre1 dbench 32 hangs in vmstat "b" state

rwhron@earthlink.net
Mon, 24 Dec 2001 11:59:53 -0500


On Mon, Dec 24, 2001 at 03:03:37PM +0100, Jens Axboe wrote:
> On Fri, Dec 21 2001, rwhron@earthlink.net wrote:
> What IDE controller are you using? The two other reports so far have
> been with VIA, maybe that's a clue.

I do have one of the perhaps buggier VIA chipsets.

00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10)
00:0f.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04)

00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Subsystem: VIA Technologies, Inc. Bus Master IDE
Flags: bus master, medium devsel, latency 32
I/O ports at d000 [size=16]
Capabilities: <available only to root>

It's been reliable for a long time, but it wouldn't compile an Athlon
optimized kernel until 2.4.1x. (Kernel would Oops at boot time unless
compiled with CONFIG_M586=y)

It was reliable when not optimized for Athlon.

> Anyways, could you please reproduce with this applied?
>
> --
> Jens Axboe

With the patch, it still hangs on this system. I recompiled with
CONFIG_NOHIGHMEM=y and CONFIG_M586=y, but that ended up with all processes
in "b" state during dbench 32 too.

I tried unpatched 2.5.2-pre1 on a k6-2. dbench 32 hung similarly with
32 in "b", bo and bi = 0, and id = 100. That machine is ill now and can't
find "init" when booting, boot single, or boot init=/bin/bash.

-- 
Randy Hron

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