Disk light on full time with kernels => 2.4.13

Disk light on full time with kernels => 2.4.13

Post by CE » Tue, 29 Jan 2002 04:39:52

I've been trying to figure out what is going on with kernels 2.4.13 and
higher on my hardware.  The hardware disk activity light stays on full
time, even if no data is written to the disk.  2.4.17 (which I just
installed) has the same problem.
        My hardware is quite standard.  The system I'm seeing this problem on is
a Pentium II 300 with 256 MB of PC100 RAM, Asus P2B-S motherboard, and
two 8 GB IDE disks.
        The problem is not intrusive, and I can just boot an older kernel upon
reboot.  What I would like to know is if anybody has any experience with
this type of problem.  If you know what has changed in the kernel to
cause this I would love to know.  I scoured the changelogs but didn't
spot anything that would cause this.  Thanks.

1. Deadlock in kernel > 2.4.13-pre6

Hi everyone,

I've recently compiled and tested each kernel since 2.4.13-pre6[0], and
I've noticed a recurrent (and reproducible[1]) deadlock on my system
when I try to play an mp3[2].

It occurs randomly, i.e. not after a precise amount of time the mp3 is
playing, but each and every time I try to play an mp3 file, my box
suddenly ``freeze'': no life signs at all (SysRq keys, network, even via
a serial terminal), no Oops, no trace in logs. The box simply `dies'.

I've tried hundreds of combinations, trying to understand where the
problem lies, and I've come up with... er... nothing...

o       it's not ext3: even vanilla kernels lock up;
o       it's not an hardware problem: I've tested my RAM and compiled
        kernels over kernels with (and without) optimization;
o       kernels <= 2.4.13-pre6 works properly;
o       it's not the player/library fault: I've tried many players, on
        different libraries; besides, a user-level program shouldn't
        cause such deadlocks;
o       every other operation on kernels > 2.4.13-pre6 works quite well
        (this new VM is *great*), *except* when I try to listen a
        mp3[3]: that always leads to disaster.

So far, I've excluded everything but a bug in the OSS sound drivers,
but, according to the ChangeLogs, they did not change from 2.4.13-pre6
(the last working kernel) to 2.4.13.


[0] Mainly, because it was the first kernel with the new VM and with the
ext3 patch available, excluding 2.4.10.

[1] At least, on my box.

[2] I use a SoundBlaster AWE64 (ISA) perfectly recognized both by isapnp
and 2.4.x kernels, using OSS modules. Yes, I've also tried not to use
modules. No, I did not try ALSA. Yes, the card works perfectly.

[3] Any other format, except .MOD files, works perfectly. And that's why
I suspect the sequencer code.


Emmanuele Bassi (Zefram)               [ http://digilander.iol.it/ebassi ]
GnuPG Key fingerprint = 4DD0 C90D 4070 F071 5738  08BD 8ECC DB8F A432 0FF4

2. ALERT!! - 2.2.x i386 Linux kernel has 2.4.x DoS!!!!

3. Deadlock on kernels > 2.4.13-pre6

4. kppp and serial port modems

5. Upgrading kernel 2.4.9 -> 2.4.13 causes ex2fsck-problems.

6. execlp(),fork() and tar, I need some backup

7. Heavy IO in 2.4.13-ac4 with preempt patch -> kupdated hogs system

8. Missing /bin/bash

9. idea-cipher problems during upgrade 2.4.5 -> 2.4.13

10. 2.4.13-pre6 breaks Nvidia's kernel module

11. aic7xxx freezes with kernel 2.4.13

12. aic7xxx freezes with kernel 2.4.13 - solved

13. Kernel panic: Loop 1 (aic7xxx under 2.4.13-ac[246])