spinbot Posted December 4, 2009 Share Posted December 4, 2009 I look at my syslog periodically , although I may not understand 99% of it, I do understand UnMenu highlights in red, potential problems. I've got these two red lines: Dec 3 09:16:59 Tower kernel: atiixp 0000:00:14.1: simplex device: DMA disabled Dec 3 09:16:59 Tower kernel: ide1: DMA disabled Here's a few lines before and after it: Dec 3 09:16:59 Tower kernel: sd 5:0:0:0: [sdg] 2930275055 512-byte hardware sectors: (1.50 TB/1.36 TiB) Dec 3 09:16:59 Tower kernel: sd 5:0:0:0: [sdg] Write Protect is off Dec 3 09:16:59 Tower kernel: sd 5:0:0:0: [sdg] Mode Sense: 00 3a 00 00 Dec 3 09:16:59 Tower kernel: sd 5:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 3 09:16:59 Tower kernel: sd 5:0:0:0: [sdg] 2930275055 512-byte hardware sectors: (1.50 TB/1.36 TiB) Dec 3 09:16:59 Tower kernel: sd 5:0:0:0: [sdg] Write Protect is off Dec 3 09:16:59 Tower kernel: sd 5:0:0:0: [sdg] Mode Sense: 00 3a 00 00 Dec 3 09:16:59 Tower kernel: sd 5:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Dec 3 09:16:59 Tower kernel: sdg: sdg1 Dec 3 09:16:59 Tower kernel: sd 5:0:0:0: [sdg] Attached SCSI disk Dec 3 09:16:59 Tower kernel: Uniform Multi-Platform E-IDE driver Dec 3 09:16:59 Tower kernel: atiixp 0000:00:14.1: IDE controller (0x1002:0x439c rev 0x00) Dec 3 09:16:59 Tower kernel: ATIIXP_IDE 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Dec 3 09:16:59 Tower kernel: atiixp 0000:00:14.1: not 100%% native mode: will probe irqs later Dec 3 09:16:59 Tower kernel: ide0: BM-DMA at 0xfa00-0xfa07 Dec 3 09:16:59 Tower kernel: atiixp 0000:00:14.1: simplex device: DMA disabled Dec 3 09:16:59 Tower kernel: ide1: DMA disabled Dec 3 09:16:59 Tower kernel: Probing IDE interface ide0... Dec 3 09:16:59 Tower kernel: hda: ST320011A, ATA DISK drive Dec 3 09:16:59 Tower kernel: hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 Dec 3 09:16:59 Tower kernel: hda: UDMA/100 mode selected Dec 3 09:16:59 Tower kernel: Probing IDE interface ide1... Dec 3 09:16:59 Tower kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Dec 3 09:16:59 Tower kernel: ide1 at 0x170-0x177,0x376 on irq 15 Dec 3 09:16:59 Tower kernel: ide-gd driver 1.18 Dec 3 09:16:59 Tower kernel: hda: max request size: 128KiB Dec 3 09:16:59 Tower kernel: hda: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63 Dec 3 09:16:59 Tower kernel: hda: cache flushes not supported Anything I should be concerned about? Thanks! EDIT: I just updated from 4.5 beta6 to 4.5 beta12 and the error still exists: Dec 4 10:01:42 Tower kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Dec 4 10:01:42 Tower kernel: atiixp 0000:00:14.1: IDE controller (0x1002:0x439c rev 0x00) Dec 4 10:01:42 Tower kernel: ATIIXP_IDE 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Dec 4 10:01:42 Tower kernel: atiixp 0000:00:14.1: not 100%% native mode: will probe irqs later Dec 4 10:01:42 Tower kernel: ide0: BM-DMA at 0xfa00-0xfa07 Dec 4 10:01:42 Tower kernel: atiixp 0000:00:14.1: simplex device: DMA disabled Dec 4 10:01:42 Tower kernel: ide1: DMA disabled Dec 4 10:01:42 Tower kernel: Probing IDE interface ide0... Dec 4 10:01:42 Tower kernel: hda: ST320011A, ATA DISK drive Dec 4 10:01:42 Tower kernel: hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 Dec 4 10:01:42 Tower kernel: hda: UDMA/100 mode selected Dec 4 10:01:42 Tower kernel: Probing IDE interface ide1... Dec 4 10:01:42 Tower kernel: ide1: no devices on the port Dec 4 10:01:42 Tower kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Dec 4 10:01:42 Tower kernel: ide1 at 0x170-0x177,0x376 on irq 15 Dec 4 10:01:42 Tower kernel: ide-gd driver 1.18 Dec 4 10:01:42 Tower kernel: hda: max request size: 128KiB Dec 4 10:01:42 Tower kernel: hda: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63 Dec 4 10:01:42 Tower kernel: hda: cache flushes not supported Link to comment
RobJ Posted December 5, 2009 Share Posted December 5, 2009 It is not an error, should be classified as a 'false positive'. I think if you check your BIOS settings, you will find that DMA is not enabled for the second IDE channel onboard. That appears to be quite common, and I found a number of other syslogs with similar. All that I saw, including yours, are not using IDE1 (the second IDE channel) anyway, so it does not matter that DMA is not enabled for it. The kernel is not reporting it as an error, just as an FYI. I originally red-flagged the string "DMA disabled", because it only happened with sequences of disk errors that resulted in DMA being disabled and the drive falling back to PIO modes. Every now and then, a case like this occurs, where a string matches an 'innocent' syslog line, and I or someone will have to add these exceptions to the match cases for syslog color-coding. The colors should never be completely trusted, as they were a crude attempt to highlight lines known to be of some importance, and possibly help new users more easily find important information in their syslog. But I've fallen far behind in keeping up with all of the changes. Joe made some good changes, including re-architecting the syslog matching routine, and I have never gotten around to merging my changes into his changes. And I have a bad habit of 'running hot and cold', going hard for awhile then losing interest. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.