linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Meier <droebbel.melta@gmx.de>
To: linux-ide@vger.kernel.org
Subject: dma problems with via82cxxx after suspend
Date: Mon, 14 Mar 2005 18:54:10 +0100	[thread overview]
Message-ID: <1110822850.11750.0.camel@localhost.localdomain> (raw)

I get DMA errors after resuming from suspend (S3).

I had switched DMA off before suspending.

Kernel: 2.6.10 (ubuntu, 2.6.10-27), same with 2.6.8.1. Boot Parameters:
ro nobiospnp noapic pci=usepirqmask; same problem without those.

Hardware: Asus K8V SE Deluxe, Via K8T800 Chipset, via82cxxx loaded or
compiled in. No errors with a kernel without that module.


This is the last dmesg:

hda: DMA disabled
hdb: DMA disabled
hdc: DMA disabled
hdd: DMA disabled
Stopping tasks: ==============================================|
Back to C!
powernow-k8: ph2 null fid transition 0xc
ACPI: PCI interrupt 0000:00:07.0[A] -> GSI 11 (level, low) -> IRQ 11
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 10 (level, low) -> IRQ 10
eth1: link down
ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt 0000:00:0f.1[A] -> GSI 11 (level, low) -> IRQ 11
Restarting tasks... done
usb 5-4: USB disconnect, address 3
VFS: busy inodes on changed media.
input: AT Translated Set 2 keyboard on isa0060/serio0
usb 5-4: new high speed USB device using ehci_hcd and address 4
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 4
usb-storage: waiting for device to settle before scanning
  Vendor: HL-DT-ST  Model: DVDRAM GSA-4163B  Rev: A101
  Type:   CD-ROM                             ANSI SCSI revision: 00
sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
Attached scsi CD-ROM sr0 at scsi3, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi3, channel 0, id 0, lun 0,  type 5
usb-storage: device scan complete
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }

ide: failed opcode was: unknown
hda: status timeout: status=0xd0 { Busy }

ide: failed opcode was: unknown
hdb: DMA disabled
hda: drive not ready for command
ide0: reset: success
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }

ide: failed opcode was: unknown
hda: status timeout: status=0xd0 { Busy }

ide: failed opcode was: unknown
hda: drive not ready for command
ide0: reset: success
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }

ide: failed opcode was: unknown
hda: status timeout: status=0xd0 { Busy }

ide: failed opcode was: unknown
hda: drive not ready for command
ide0: reset: success
hda: dma_timer_expiry: dma status == 0x21
hda: DMA timeout error
hda: dma timeout error: status=0x58 { DriveReady SeekComplete
DataRequest }

ide: failed opcode was: unknown
hda: status timeout: status=0xd0 { Busy }

ide: failed opcode was: unknown
hda: drive not ready for command
ide0: reset: success


Thanks
David



             reply	other threads:[~2005-03-14 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 17:54 David Meier [this message]
2005-03-18 16:27 ` dma problems with via82cxxx after suspend Bartlomiej Zolnierkiewicz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1110822850.11750.0.camel@localhost.localdomain \
    --to=droebbel.melta@gmx.de \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).