[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#423682: marked as done (DMA issues with piix kernel driver on Etch)



Your message dated Wed, 17 Dec 2008 21:49:37 +0100
with message-id <20081217204937.GA12188@galadriel.inutil.org>
and subject line Re: Source of problems udftools/UDF packet writing driver?
has caused the Debian Bug report #423682,
regarding DMA issues with piix kernel driver on Etch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
423682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=423682
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-12etch1

I'd installed a fresh Debian Etch on my PC. My motherboard is a ASUS P4PE with ICH4 chip. Therefore the piix kernel driver was used.

On boot the right DMA modes are detected, but I get errors in the messages log.

With hdparm I'd setted DMA to 1. After media changes I get error messages, too. And DMA mode was resetted to 0:

...
kernel: ICH4: chipset revision 2
kernel: ICH4: not 100%% native mode: will probe irqs later
kernel:     ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
kernel:     ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio
kernel: hda: Maxtor 6Y120L0, ATA DISK drive
kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
kernel: hdc: HL-DT-STDVD-RAM GSA-H20L, ATAPI CD/DVD-ROM drive
kernel: ide1 at 0x170-0x177,0x376 on irq 15
kernel: hda: max request size: 128KiB
kernel: hda: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
kernel: hda: cache flushes supported
kernel:  hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
kernel: hdc: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
kernel: Uniform CD-ROM driver Revision: 3.20
...
kernel: hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete DataRequest }
kernel: ide: failed opcode was: unknown
kernel: hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
kernel: ide: failed opcode was: unknown
kernel: hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
kernel: ide: failed opcode was: unknown
...
kernel: hda: CHECK for good STATUS
...
kernel: cdrom: This disc doesn't have any tracks I recognize!



Notice: No cdrom/dvd was inserted. smartctl recognize no disk failure.



Error when changing media (dvd drive):
...
kernel: hdc: irq timeout: status=0xc0 { Busy }
kernel: ide: failed opcode was: unknown
kernel: hdc: DMA disabled
kernel: hdc: ATAPI reset complete
kernel: hdc: irq timeout: status=0xc0 { Busy }
kernel: ide: failed opcode was: unknown
kernel: hdc: ATAPI reset complete
...



Because I didn't want a data loss, I removed the Etch kernel.

I downloaded the vanilla kernel 2.6.21.1 and build a kernel for my own.

The result was, there wasn't any error messages on boot, but the system freeze on media change.

So I switched from piix to ata_piix. From this point (ata_piix with kernel 2.6.21.1) I didn't get any error messages and system freezes.

In my opinon either the piix drive in kernel 2.6.18 works right or it's a irq conflict.

Is there a possibility to fix this error? I'd like to use the Etch kernel with my system instead of compiling a kernel for my own...
-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger


--- End Message ---
--- Begin Message ---
Version: 2.6.22-1

On Fri, Jun 22, 2007 at 06:02:08PM +0200, tuXXer wrote:
> Well, after uninstallation of the package "udftools" I do not get this errors, anymore. 
> 
> It seems that pktsetup calling the device when a DVD/CD-ROM is ejected. Therefore the drive getting resetted. Maybe it depends on the kernel UDF packet driver, too. Because with higher kernel versions the problem does not exists...

Hmm, I'm unsure what caused this.

Anyway, marking 2.6.22 as fixed.

Cheers,
        Moritz


--- End Message ---

Reply to: