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

Bug#386352: marked as done (linux-image-2.6.17-2-686: ide driver lockup)

Your message dated Mon, 22 Jan 2007 11:22:59 +0100
with message-id <20070122102259.GB29435@nancy.stro.at>
and subject line Bug#386352: linux-image-2.6.17-2-686: ide driver lockup
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: linux-image-2.6.17-2-686
Version: 2.6.17-8
Severity: important

After upgrading to 2.6.17 from 2.6.16-1-686, I found the stability of my
unicpu PIII system was next to nonexistent (it would completely lock up
after only a day or two of uptime).  After enabling netconsole, I was able
to capture the following from the kernel:
hda: dma_timer_expiry: dma status == 0x61
hda: DMA timeout error
hda: dma timeout error: status=0x50 { DriveReady SeekComplete }
ide: failed opcode was: unknown
hdb: dma_timer_expiry: dma status == 0x41
hdb: DMA timeout error

Both hard disks appear to be fine, and shouldn't be causing any problems.
Going back to 2.6.16 appears to resolve the stability issues, which implies
software, and not hardware, is at fault.

System in use has an Intel D815EEA2 motherboard, 1 GHz CPU, and 512 MB of
memory, using the onboard ide controller
(Intel Corporation 82801BA IDE U100 (rev 11)).


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages linux-image-2.6.17-2-686 depends on:
ii  initramfs-tools [linux-initra 0.77b      tools for generating an initramfs
ii  module-init-tools             3.2-pre9-3 tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-9   Yet Another mkInitRD

Versions of packages linux-image-2.6.17-2-686 recommends:
pn  libc6-i686                    <none>     (no description available)

-- debconf information:
  linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false
  linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk:
* linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686:
  linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686:
  linux-image-2.6.17-2-686/postinst/really-run-bootloader-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686:
  linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686:
  linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true
  linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/kimage-is-a-directory:
  linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true
  linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false
  linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686:

--- End Message ---
--- Begin Message --- 
On Fri, 19 Jan 2007, Mike Edwards wrote:

> It appears to work fairly well, though I've since moved to the Xen
> version of that kernel.
> 

ok closing.
 
--
maks

--- End Message ---
Reply to: