[Bug 225] New: DMA Errors When Booting with Sis 5597 Chipset

https://bugzilla.arklinux.org/bugzilla/show_bug.cgi?id=225

           Summary: DMA Errors When Booting with Sis 5597 Chipset
           Product: Ark Linux
           Version: 1.0 alpha8
          Platform: i586 (PC, Intel)
        OS/Version: All
            Status: NEW
          Severity: Normal
           Affects: Hardware Support
         Component: kernel
        AssignedTo: [email protected]
        ReportedBy: [email protected]
         QAContact: [email protected]


Description of Problem: 
 
Version-Release number of selected component (if applicable): 
 
Linux version 2.4.21-2ark ([email protected]) (gcc version 3.3 (Ark 
Linux 1.0 3.3-2ark)) 
 
How Reproducible: Always 
 
Actual Results: 
 
The following error message show up in the dmesg log at least 5 times during 
booting, the computer hesitate for about 30 seconds before the error is shown 
each time resulting in linux taking about 5 minutes to load- 
 
hda: dma_timer_expiry: dma status == 0x21 
hda: error waiting for DMA 
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } 
 
Expected Results: 
 
Additional Information: 
 
The computer I am using has an AMD K6-350Mhz processor and an Asus SP97v mobo 
with 128Meg of RAM.  The IDE controller is on the mobo.   
 
I thought the fix was explained here: 
http://gyver.homeip.net/sis5513/ 
supposedly added to the kernel in 2.4.21-pre2 pre-release.  I tried the latest 
out of dockyard and still had the same problem. 
 
Here is the detection code from the log: 
---- 
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx 
SIS5513: IDE controller at PCI slot 00:01.1 
PCI: Assigned IRQ 10 for device 00:01.1 
SIS5513: chipset revision 208 
SIS5513: not 100% native mode: will probe irqs later 
SIS5513: SiS5597 ATA 33 controller 
    ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio 
    ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:pio 
hda: Maxtor 90845D4, ATA DISK drive 
blk: queue 403ec340, I/O limit 4095Mb (mask 0xffffffff) 
 
 
 
Below is a segment of the log so you can get a feel for where the errors are 
showing up: 
-------- 
hda: attached ide-disk driver. 
hda: host protected area => 1 
hda: 16514064 sectors (8455 MB) w/512KiB Cache, CHS=1027/255/63, UDMA(33) 
Partition check: 
 hda: hda1 hda2 
IEEE 802.2 LLC for Linux 2.1 (c) 1996 Tim Alpaerts 
NET4: Linux TCP/IP 1.0 for NET4.0 
IP Protocols: ICMP, UDP, TCP, IGMP 
IP: routing cache hash table of 1024 buckets, 8Kbytes 
TCP: Hash tables configured (established 8192 bind 16384) 
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. 
RAMDISK: Compressed image found at block 0 
Freeing initrd memory: 90k freed 
VFS: Mounted root (ext2 filesystem). 
hda: dma_timer_expiry: dma status == 0x21 
hda: error waiting for DMA 
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } 
 
kjournald starting.  Commit interval 5 seconds 
hda: dma_timer_expiry: dma status == 0x21 
hda: error waiting for DMA 
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } 
 
EXT3-fs: mounted filesystem with ordered data mode. 
Freeing unused kernel memory: 420k freed 
Real Time Clock Driver v1.10e 
hda: dma_timer_expiry: dma status == 0x21 
hda: error waiting for DMA 
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest } 
 
hda: dma_timer_expiry: dma status == 0x21 
hda: error waiting for DMA 
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.