kernel 2.4.22 hpt370 dma
Hi
Vor einigen Tagen erstellte ich mir auf basis der 2.4.18-bf24 config einen neuen 2.4.22 kernel (Quelle kernel.org ).
Dieser funktioniert auch fehlerfrei. Nun bemerke ich die Festplatte ist etwas langsam und behindert das System.
hdparm zeigt mir an der DMA ist nicht aktiviert. Lässt sich aber auch nicht aktivieren.
Die entsprechenden Meldungen aus der Syslog lauten:
Mit den alten kernel:
Aug 27 03:02:34 client2 kernel: VP_IDE: IDE controller on PCI bus 00 dev 39
Aug 27 03:02:34 client2 kernel: VP_IDE: chipset revision 6
Aug 27 03:02:34 client2 kernel: VP_IDE: not 100%% native mode: will probe irqs later
Aug 27 03:02:34 client2 kernel: VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
Aug 27 03:02:34 client2 kernel: ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio
Aug 27 03:02:34 client2 kernel: ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:DMA, hdd:pio
Aug 27 03:02:34 client2 kernel: HPT370: IDE controller on PCI bus 00 dev 98
Aug 27 03:02:34 client2 kernel: PCI: Found IRQ 11 for device 00:13.0
Aug 27 03:02:34 client2 kernel: HPT370: chipset revision 3
Aug 27 03:02:34 client2 kernel: HPT370: not 100%% native mode: will probe irqs later
Aug 27 03:02:34 client2 kernel: ide2: BM-DMA at 0xe400-0xe407, BIOS settings: hde:pio, hdf:pio
Aug 27 03:02:34 client2 kernel: ide3: BM-DMA at 0xe408-0xe40f, BIOS settings: hdg:pio, hdh:pio
Aug 27 03:02:34 client2 kernel: hda: TOSHIBA DVD-ROM SD-M1502, ATAPI CD/DVD-ROM drive
Aug 27 03:02:34 client2 kernel: hdc: AOPEN CD-RW CRW3248 1.15 20020520, ATAPI CD/DVD-ROM drive
Aug 27 03:02:34 client2 kernel: hde: Maxtor 4W060H4, ATA DISK drive
Aug 27 03:02:34 client2 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Aug 27 03:02:34 client2 kernel: ide1 at 0x170-0x177,0x376 on irq 15
Aug 27 03:02:34 client2 kernel: ide2 at 0xd400-0xd407,0xd802 on irq 11
Aug 27 03:02:34 client2 kernel: hde: 120033900 sectors (61457 MB) w/2048KiB Cache, CHS=119081/16/63, UDMA(100)
Mit dem neuen Kernel gibt es immer diesen Fehler
Oct 14 14:17:09 client2 kernel: VP_IDE: IDE controller at PCI slot 00:07.1
Oct 14 14:17:09 client2 kernel: VP_IDE: chipset revision 6
Oct 14 14:17:09 client2 kernel: VP_IDE: not 100%% native mode: will probe irqs later
Oct 14 14:17:09 client2 kernel: VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
Oct 14 14:17:09 client2 kernel: ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio
Oct 14 14:17:09 client2 kernel: ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:DMA, hdd:pio
Oct 14 14:17:09 client2 kernel: HPT370: IDE controller at PCI slot 00:13.0
Oct 14 14:17:09 client2 kernel: PCI: Found IRQ 11 for device 00:13.0
Oct 14 14:17:09 client2 kernel: HPT370: chipset revision 3
Oct 14 14:17:09 client2 kernel: HPT370: not 100%% native mode: will probe irqs later
Oct 14 14:17:09 client2 kernel: HPT37X: using 33MHz PCI clock
Oct 14 14:17:09 client2 kernel: ide2: BM-DMA at 0xe400-0xe407, BIOS settings: hde:pio, hdf:pio
Oct 14 14:17:09 client2 kernel: ide3: BM-DMA at 0xe408-0xe40f, BIOS settings: hdg:pio, hdh:pio
Oct 14 14:17:09 client2 kernel: hda: TOSHIBA DVD-ROM SD-M1502, ATAPI CD/DVD-ROM drive
Oct 14 14:17:09 client2 kernel: hdc: AOPEN CD-RW CRW3248 1.17 20020620, ATAPI CD/DVD-ROM drive
Oct 14 14:17:09 client2 kernel: hde: Maxtor 4W060H4, ATA DISK drive
Oct 14 14:17:09 client2 kernel: hde: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Oct 14 14:17:09 client2 kernel: hde: set_drive_speed_status: error=0x04 { DriveStatusError }
Oct 14 14:17:09 client2 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Oct 14 14:17:09 client2 kernel: ide1 at 0x170-0x177,0x376 on irq 15
Oct 14 14:17:09 client2 kernel: ide2 at 0xd400-0xd407,0xd802 on irq 11
Oct 14 14:17:09 client2 kernel: hde: attached ide-disk driver.
Oct 14 14:17:09 client2 kernel: hde: host protected area => 1
Oct 14 14:17:09 client2 kernel: hde: setmax LBA 120103200, native 120033900
Bei dem Board handelt es sich um ein KT7A-Raid
Die Festplatte ist am Raid damit jedes Gerät seinen eigenen Kanal hat.
Meine Frage lautet eigentlich nur liegt dieses Problem generell am Kernel oder an der config?
und hat jemand das gleiche Problem?
MFG
Thomas Müller
Reply to: