[CentOS] System freezes completely under kernel

[Olaf Mueller]

Karanbir Singh wrote:

Hello,

> On 08/25/2009 01:38 PM, Olaf Mueller wrote:
>> Is someone else this seeing?
> not me, I've got the new kernel on about 6 machines, and my laptop
> with no problems. What is the prev kernel you were running ?
this is the second time the system freezes completely with kernel
2.6.18-128.7.1.el5 with the same error message 'kernel: hdg:
dma_timer_expiry: dma status == 0x21'. Now I am back under kernel
2.6.18-128.4.1.el5, no problems so far. My system:


# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Pentium(R) 4 CPU 1.80GHz
stepping        : 4
cpu MHz         : 1798.564
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm up
bogomips        : 3599.16


# lspci | grep storage
02:07.0 Mass storage controller: Promise Technology, Inc. PDC20268
(Ultra100 TX2) (rev 02)


# grep hdg /var/log/dmesg
    ide3: BM-DMA at 0x4008-0x400f, BIOS settings: hdg:pio, hdh:pio
hdg: WDC WD5000AAKB-00H8A0, ATA DISK drive
hdg: max request size: 512KiB
hdg: 976773168 sectors (500107 MB) w/16384KiB Cache, CHS=60801/255/63,
UDMA(100)
hdg: cache flushes supported
 hdg: hdg1
EXT3 FS on hdg1, internal journal


The harddisk is connected to the Promise Technolog IDE Controller as a
master (ide2). Also there is a second identical harddisk connected to
this controller as a master (ide 1).

Over month there were no problems with previous kernels. After updating
to kernel 2.6.18-128.7.1.el5 the systems freezes for two times within a
few hours. And since booting into the old kernel, everything seems good
so far. In my opinion this is a kernel bug.

Two notebooks and two desktops are waiting here for the new kernel
update. I will do that now. Maybe the error is reproducible on
different hardware.


regards
Olaf