Your message dated Wed, 28 Nov 2007 01:11:08 +0100
with message-id <[EMAIL PROTECTED]>
and subject line kernel-image-2.6.3-1-k7: VIA KT600 problem : DMA activation
causes crash on boot
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: kernel-image-2.6.3-1-k7
Version: 2.6.3-2
Severity: critical
Tags: sid
Justification: breaks the whole system
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.0-1-k7
Locale: LANG=C, LC_CTYPE=C
Versions of packages kernel-image-2.6.3-1-k7 depends on:
ii coreutils [fileutils] 5.0.91-2 The GNU core utilities
ii fileutils 5.0.91-2 The GNU file management
utilities
ii initrd-tools 0.1.61 Tools to generate an initrd
image.
ii module-init-tools 3.0-pre10-1 tools for managing Linux
kernel mo
-- no debconf information
When the system boots, IDE hard drive autodetection activates DMA usage
on my main HD, which causes the complete system to crash. My hardware is
an Asus A7V600 motherboard with BIOS rev. 1004 .
On 2.6.0, the hard disk was detected with DMA too, but DMA was _not_
activated by default (I tried activating it with hdparm, and it causes
the system to crash at once).
However, I diffed the sources of the driver
(drivers/ide/pci/via82cxxx.c) and I do not think the changes from 2.6.0
to 2.6.3 may cause this new behavior.
Possible suspects are : ide-dma.c , ide.c and perhaps ide-disk.c (these
files related to the IDE system have been changed a lot - mostly
DMA-related changes).
Since I don't want to crash my system again, I won't be able to give you
a dump of the error ; if you _really_ need it please tell me.
--- End Message ---
--- Begin Message ---
very unlikely to be still an issue in stable 2.6.18 linux images,
thus closing.
if you can still reproduce please holler loudly.
thanks for report
--
maks
--- End Message ---
