Mailinglist Archive: opensuse (4498 mails)
| < Previous | Next > |
Re: [SLE] ide dma problem
- From: Istvan Gabor <suseuser04@xxxxxxxxxxx>
- Date: Fri, 3 Nov 2006 13:34:10 +0000 (UTC)
- Message-id: <freemail.20061003143358.81306@xxxxxxxxxxxxxxxx>
Hi Carlos:
Thankf for your reply.
> Forget Yast. Use:
>
> hdparm -d /dev/hdc
>
> Or
>
> hdparm -d -c -u /dev/hdc
>
> to see the state. Then use "- 1" to activate if possible.
Thanks. I read hdparm man several times but it was not clear
for me that -d also reports dma status.
For hdparm -d -c -u /dev/hdd I get:
/dev/hdd:
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
Is this good or bad (for unmaskirq and IO_support)?
> Probably. Bu why don't you use k3b instead of a windows in
linux thing?
According to my knowledge neroLINUX is a native linux
program. I had several problems with k3b before.
Unfortunately there is not a decent GUI cdburning software for
linux. All of them ruins directory dates on burned media. But
this would be a different topic.
> > 1. What can cause that dma is turned off?
>
> Check the kernel log.
Is the /var/log/messages file the kernel log? Or dmesg?
I found lines in /var/log/messages like these:
kernel: hdc: irq timeout: status=0xd0 { Busy }
kernel: ide: failed opcode was: unknown
kernel: hdc: DMA disabled
kernel: hdc: ATAPI reset complete
kernel: hdc: tray open
kernel: end_request: I/O error, dev hdc, sector 64
kernel: Buffer I/O error on device hdc, logical block 16
kernel: hdc: tray open
kernel: end_request: I/O error, dev hdc, sector 68
and:
kernel: hdc: drive_cmd: status=0x01 { Error }
kernel: hdc: drive_cmd: error=0x04 { AbortedCommand }
kernel: ide: failed opcode was: 0xec
kernel: hdd: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
kernel: hdd: drive_cmd: error=0x04 { AbortedCommand }
kernel: ide: failed opcode was: 0xec
syslog-ng[2053]: STATS: dropped 0
kernel: hdc: irq timeout: status=0xd0 { Busy }
kernel: ide: failed opcode was: unknown
kernel: hdc: ATAPI reset complete
kernel: hdc: tray open
kernel: end_request: I/O error, dev hdc, sector 64
kernel: Buffer I/O error on device hdc, logical block 16
kernel: hdc: tray open
kernel: end_request: I/O error, dev hdc, sector 68
kernel: Buffer I/O error on device hdc, logical block 17
I don't know which of these report problems and which are
normal.
However recently I had also bootup problems. At certain point
boot hangs and I have to reset. I can't remember the
messages at which boot hangs (not always the same) but next
time I will write it down. Couldit be a problem with the MB or
bad wiring?
Thanks and cheers,
IG
___________________________________________________________________________
2534 állásajánlat között biztosan találsz olyat, ami Neked is megfelel!
http://ad.adverticum.net/b/cl,1,6022,120678,191335/click.prm
Thankf for your reply.
> Forget Yast. Use:
>
> hdparm -d /dev/hdc
>
> Or
>
> hdparm -d -c -u /dev/hdc
>
> to see the state. Then use "- 1" to activate if possible.
Thanks. I read hdparm man several times but it was not clear
for me that -d also reports dma status.
For hdparm -d -c -u /dev/hdd I get:
/dev/hdd:
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
Is this good or bad (for unmaskirq and IO_support)?
> Probably. Bu why don't you use k3b instead of a windows in
linux thing?
According to my knowledge neroLINUX is a native linux
program. I had several problems with k3b before.
Unfortunately there is not a decent GUI cdburning software for
linux. All of them ruins directory dates on burned media. But
this would be a different topic.
> > 1. What can cause that dma is turned off?
>
> Check the kernel log.
Is the /var/log/messages file the kernel log? Or dmesg?
I found lines in /var/log/messages like these:
kernel: hdc: irq timeout: status=0xd0 { Busy }
kernel: ide: failed opcode was: unknown
kernel: hdc: DMA disabled
kernel: hdc: ATAPI reset complete
kernel: hdc: tray open
kernel: end_request: I/O error, dev hdc, sector 64
kernel: Buffer I/O error on device hdc, logical block 16
kernel: hdc: tray open
kernel: end_request: I/O error, dev hdc, sector 68
and:
kernel: hdc: drive_cmd: status=0x01 { Error }
kernel: hdc: drive_cmd: error=0x04 { AbortedCommand }
kernel: ide: failed opcode was: 0xec
kernel: hdd: drive_cmd: status=0x51 { DriveReady
SeekComplete Error }
kernel: hdd: drive_cmd: error=0x04 { AbortedCommand }
kernel: ide: failed opcode was: 0xec
syslog-ng[2053]: STATS: dropped 0
kernel: hdc: irq timeout: status=0xd0 { Busy }
kernel: ide: failed opcode was: unknown
kernel: hdc: ATAPI reset complete
kernel: hdc: tray open
kernel: end_request: I/O error, dev hdc, sector 64
kernel: Buffer I/O error on device hdc, logical block 16
kernel: hdc: tray open
kernel: end_request: I/O error, dev hdc, sector 68
kernel: Buffer I/O error on device hdc, logical block 17
I don't know which of these report problems and which are
normal.
However recently I had also bootup problems. At certain point
boot hangs and I have to reset. I can't remember the
messages at which boot hangs (not always the same) but next
time I will write it down. Couldit be a problem with the MB or
bad wiring?
Thanks and cheers,
IG
___________________________________________________________________________
2534 állásajánlat között biztosan találsz olyat, ami Neked is megfelel!
http://ad.adverticum.net/b/cl,1,6022,120678,191335/click.prm
| < Previous | Next > |